Hello all, I was hoping someone could help me with this problem I'm having installing windows. Basically the first boot after windows installs, I get a bsod. It resets within 1 sec after the screen so I can't write down the hex code it gives you at the bsod. Has anyone else come across this problem after installing windows as well? By the way, I tried using x64 & x86 to no avail. Thanks in advance for any and all help.
Did you load SATA drivers during the Windows install? If not try to load them, see here:
This driver in particular:
P.S. I don't think you will be able to use online diagnostics because you don't have Windows correctly installed and hence can't go online. You may however use the F12 preboot diagnostics:
Yup, tried that already. Windows started crying about how the driver's not signed and recommended I download signed versions. It basically wouldn't let me use these drivers. I looked for said signed version and found there are none to be had. I'm currently reinstalling using usb instead of dvd. The disc I had was ever so slightly suspect and I'm hoping it's just a bad file copy.
Ok here is the bsod code i got 0x0000009c and about four memory addresses I couldn't write down. Also sometimes when I get most of the way thru installation, basically it's at the "Completing installation" stage. It tells me "Windows Setup could not configure Windows to run on this computer's hardware" Now I 'm stuck. I guessing it's a driver issue, but I really am just clasping at straws. Any help appreciated!
Its strange for Dell SATA drivers to be unsigned, particularly for Intel ones.
Does your Windows 7 installation DVD contain Service Pack 1 and the Media Refresh Update.
It may help but your system is still a good bit newer so will need SATA drivers. Unfortunately Microsoft didn't release Windows 7 Service Pack 2 which would have been expected to have more SATA drivers and support for USB 3.0.
Try direct from Intel:
Go into the BIOS and check to see if the system has been set to RAID rather than AHCI. I had this problem even after loading defaults back and received the same error messages you did. Once I changed the setting everything worked fine.