Asrock Z97 Pro4 Blue Screen during Win7 setup

RafaSuarez

Commendable
Jun 5, 2016
3
0
1,510
I've put together the following replacement rig for my recently RIP PC:
New- Asrock Z97 Pro4
New- Intel Core i7 4790K
New- 2x Crucial Ballistix 8GB DDR3 1600 CAS 9 9 9 24 x1.5V
Recycled- Option 1 WD30EZRX 3GB SATA Internal HDD
Recycled- Option 2 OCZ Vertex3 120GB SATA Internal SSD
Recycled- Thermaltake 600W PS
Old Win7 SP1 Ultimate previously installed in the drives

The drives are known-working pulls from a now temp creeping DG43GT build.
Upon booting Win7 on the 3TB within the new rig , immediate blue screens. Would not give me user prompt.
Win 7 Safe Mode allowed booting, but I decided to just do a clean install instead of removing all previous drivers manually.

As I installed Win 7 x64 on the 3TB HDD, I had to attempt to overcome the 2GB UEFI issue. It would create a bunch of partitions instead of installing a single 3TB. Microsofts' solution to Diskpart the drive, Clean and then set it as GPT allowed it to show the 2794 GBs, but in the end it always automatically repartitioned in 3 logical drives.

Giving up on a single 3TB volume, I allowed Win7 x64 to proceed. Blue Screen 0x0000005C. at the decompressing Windows stage, 3%.

Cleaned the 3TB drive again, did not partition at F11 Diskpart, did not set it as GPT. Setup now progressed up to 30% or so, and again Blue Screen.IRQ this time.

After several iterations of similar BSODs, I ended up pulling off the Microsoft Wireless BT KB/Mouse, Logitech external wireless network adapter, and turning off BIOS onboard Audio and NIC support. Set up the BIOS to onboard Video (instead of the default PCIE). As per Microsoft KB advise, I also reviewed the Auto CAS settings (which looked OK) , hardcoded the RAM CAS to 9 9 9 24 and even raised the RAM voltage from 1.5V to 1.55V (which made the system visibly unstable, so I elected to go back to BIOS RAM Auto cfg)

After this much tinkering, I got Win7 setup to reach 99% file decompression, and then you guessed it, another @#$% BSOD.

Thinking it could be the 3TB drive, I switched the HDD for the 120GB SSD. The BIOS would find no boot devices. After 3-4 setup cycles and a couple SATA plug re-arrangements, it finally detected the boot device. Cleaned with Diskpart, and once again it blew up in my face with the Win7 setup BSOD at 99% of file extraction. I think it stated it was a Master Table error or something similar, was too tired and dissapointed to make a note.

Has anyone come across this problem?

 
Solution
you might also just want to confirm your memory timings by running memtest86 on its own boot image.


the error code:
Error code: (HRESULT) 0x8007048f (2147943567) - The device is not connected.
I would make sure the device is on a SATA 2 port until the install completed and all the driver updates had been applied.

If you get the device not connect after formating a SSD, the SSD might just need to run its cleanup routines
(power the drive but leave it idle, after 5 mins its internal clean up routines will run, leave it for a hour or so to give it time to finish)
(sometimes you have to do a firmware update on old SSD driver, you can use crystaldiskinfo.exe to read the firmware version)


the first bugcheck was in the hardware...

RafaSuarez

Commendable
Jun 5, 2016
3
0
1,510
Update1:
Switched positions on the DIMMS to 'Priority 2', and setup completes on the SSD, with a warning about a corrupt lnk file.

Update 2: attepting another clean install on the HDD gives me error code 8007048F at about 33% files expansion.
 
you might also just want to confirm your memory timings by running memtest86 on its own boot image.


the error code:
Error code: (HRESULT) 0x8007048f (2147943567) - The device is not connected.
I would make sure the device is on a SATA 2 port until the install completed and all the driver updates had been applied.

If you get the device not connect after formating a SSD, the SSD might just need to run its cleanup routines
(power the drive but leave it idle, after 5 mins its internal clean up routines will run, leave it for a hour or so to give it time to finish)
(sometimes you have to do a firmware update on old SSD driver, you can use crystaldiskinfo.exe to read the firmware version)


the first bugcheck was in the hardware abstraction layer initilization
(looks like you got past that one)




 
Solution

RafaSuarez

Commendable
Jun 5, 2016
3
0
1,510