Motherboard Not Letting Windows 7 Install

Swocevoli

Reputable
Jul 2, 2014
6
0
4,510
I am looking for a solution that I haven't tried yet. I'll give the short version of events here: I have had to purchase a new mobo and cpu because of a power failure damaging my old mobo. First, I replaced the power supply and then is wanted me to repair Windows. Did that by hooking into another machine as I was in the bsod loop on mine. Once I "repaired", video went away and there were no boot beeps. Reset my memory and ran a memory test. Memory is good. Rebuilt the MBR using cmd mode and got the hdd to boot when hooked into the other machine. When I moved it back, the video had gone. Tested my cards on another machine; they're fine (nvidia 450 gts). Dr. Debug was no longer responding and on some searches discovered that the mobo is/was most likely dead. My new one is an Asrock Z97 Extreme4 with an Intel i7-4770K processor. I also have a new 750 power supply. I have tried all the suggestions on here. Basically, when i try to install Windows 7, it tells me that the controller setting for my hdd is not set in the bios. I have tried the unplugging, reseating, new sata cord, refreshing bios, resetting bios, reformatting the drive (3 times now), using diskpart.exe to set up partitions, scanned the hdd with all available scans, i.e. WD scan, chkdsk scans and fixes. I visited the Asrock site and downloaded the most current hdd drivers to a thumb drive and had Windows browse there for the drivers. But, Windows says they are not there. I know my Windows disk is good as I had to install Windows just last week on a new build for my son. He did not replace his hdd; just reformatted it and installed. The hdd is a WD1002FAEX 1TB. All the scans show is as healthy with nothing corrupted. I do have a surge protector and everything was (and is) plugged into it. But, the old mobo had been through several thunderstorms and blackouts. Not sure if they just caught up to it and burned it out or not. What can I try next?
 
Solution


Okay. Well, it is pretty obvious you know your way around these things pretty well. Everything I have suggested, you have already tried. It seems to be an issue with the controller, which is set in the BiOS ( should be AHCI which you've done ). Memory controllers are in the Intel Processor. As for the SATA controllers, They are either in the Southbridge or Northbrige Chipset on the...

First and foremost, you can not use one Installation disk on multiple computers. If it is an OEM copy, once installed on a computer that is where it stays and cannot be put on another computer. Changing out the motherboard, constitutes another computer unless you used the same exact motherboard, and then it may work. With a Reatail copy, you can move that from one copmputer to another, BUT, you only have it installed on one computer at a time.
 


OKay, then that shouldn't be an Issue. You haven't given any info on the Hdd. If it is a SATA drive, then it must be set to AHCI in the BiOS and NOT IDE.
 

Swocevoli

Reputable
Jul 2, 2014
6
0
4,510
I did include the drive information. It's a WD1002FAEX 1TB. I checked the compatibility with the mobo and it is compatible. I have also tried it in AHCI, IDE and raid mode, to no avail. Sorry, I thought I had included that, as well.
 


First, there was a lot of moving things from one machine to another. That can never be good. Are you getting any POST codes at startup ( beeps )? There should be just a single short beep. Anything else is trouble. BSOD usually indicates a hardware issue as well. The controller settings in the BiOS is AHCI / IDE. With a single Hdd, you don't really need raid. You may want to check the Device Manager and see if the controllers are there. If you installed the drivers that came with the Motherboard, they should be.
 

Swocevoli

Reputable
Jul 2, 2014
6
0
4,510
I only moved things to another machine to test them since there was no video on the original one. I have pretty much rebuilt the machine; only graphic cards and HDD are in the "new" machine. I am getting the single POST beep. Prior to formatting the HDD, Windows would start and then give me the 0x07B error. I have tried to install the drivers that came with the mobo, but Windows says they aren't there. That is why I went and got the newest ones from the Asrock site. But, Windows didn't recognize those, either. Not sure how to check the device manager since I have no OS on this HDD right now. I can hook it into another machine and check there, but I thought the WD scan would let me know if the drivers were missing. All scans done on this HDD show it to be "healthy" and no corruption. I've done a virus scan, chkdsk scans and the WD diagnostic scan.
 
I have the same Hdd in here as well as SSD. I can only assume that the Motherboard that got fried had the same Chipset ( Z87 ) as the new one, although I can't really see a problem there. I have been from a Z68 to Z87 with no issues. Anyway, reformatting the Hdd and Repartitioning it will usually take care of that issue. You have checked the DATA cable at both the Hdd and the header on the motherboard. You have reflashed the BiOS, which may or may not have been necessary. Those thing get updated, but I am of the mind, if it ain't broke don't fix it, at least in the case of the BiOS. I have played around with that in the past, but you can easily brick a machine messing with that. You won't get any drivers installed until you first install the OS. Once you install the OS, then you install the Motherboard stuff, then go from there ( Graphics Card Drivers & Etc. ) IN the BiOS, it should be set to AHCI and the boot device should be set to the Optical drive as you will be booting from that to load the OS if you are using an Installation disk.
 

Swocevoli

Reputable
Jul 2, 2014
6
0
4,510
I have done the reformatting and repartitioning to no avail. Tried new cables. I'm starting to wonder if the new mobo has some issues that I can't work out, repair or work around. I'm just stumped.
 


Is it POSTING? If you are getting no Beeps than I am assuming it isn't. Here is something to try. Take the Mother board out of the case an place it on the box it came in. Hook up the power connectors and install one stick of memory. Hook up the connections from the PSU and hook up the monitor, first to the Integrated Graphics and see if you get an image and it POSTs to the Manufacturer's Splash screen. If you get that and a single beep, then try the Dedicated card. At this pooint you are at bare bones, what we call bread boarding. If it POSTs then, you have pretty much ruled out the Motherboard, memory, and CPU. If you don't get an image with the card, then you have a bad card, but you said it worked in another machine. When you put the motherboard back in the case. make sure all of the standoffs are in place and snug. Before you do that, you can then try to plug in the optical drive and see if it posts and what kind of Beep code you get. You can then try the Hdd and see what happens. There could be an issue with the SATA header on the Motherboard.
 

Swocevoli

Reputable
Jul 2, 2014
6
0
4,510
I did bread board it before I put it in the case. It is also posting with no errors. It's when I try to install that the drive isn't being allowed to be a boot device. Right now I'm working with an old HDD that is only a boot drive to see if I can sort it out that way. I'll be trying to install on my main HDD this weekend. I'll keep you posted.
 


Okay. Well, it is pretty obvious you know your way around these things pretty well. Everything I have suggested, you have already tried. It seems to be an issue with the controller, which is set in the BiOS ( should be AHCI which you've done ). Memory controllers are in the Intel Processor. As for the SATA controllers, They are either in the Southbridge or Northbrige Chipset on the Motherboard. If either of those Chipsets are bad, all you can do is replace the Motherboard. ASRock is a quality board ( made by ASUS ) and one I frequently recommend ( especially the one you have ). If you have the Boot device set to what ever the OS is on ( Optical Drive or Flash Drive ) to install it and you are getting that message and you HAVE set it in the BiOS, I would start thinking about the Motherboard itself after all you have tried.
 
Solution