PC Boots to BIOS but not Windows after PSU install

Nefarious_Nyx

Honorable
Dec 25, 2013
3
0
10,510
Hello, i just recently upgraded from a Cougar A-560 PSU to a Corsair Rm-750 in anticipation of crossfiring my currently single 7870 setup. My mobo is an Asus P8z77-vlk, I'm running two 4GB sticks of Gskill Sniper RAM, an I5-3570k (OC'd to 4.2 GHz), a Samsung 830 series SSD with Windows 7 and a Seagate Barracuda 2TB HDD for mass storage and non-vital programs (IE it holds everything my Steam addiction consumes :p). So, after uninstalling the A560, I made all my connections with the RM-750 and went to boot up - only to be met with that dreaded infinite loop of getting past BIOS and then failing to boot Windows. I get my POST beep, lights flash as usual, everything - I can enter BIOS just fine, and here I can find all of my devices - drives, peripherals, RAM, everything, which means they are getting power and are detected. I hit the CMOS button, that came back fine, said memory was good. I can display via either integrated or board GPU. I can monitor stats in BIOS, and temps are fine across the board, so this isn't a CPU heatsink issue. My boot order is set to disk drive, then solid state (where OS is installed). If I select only SSD and then boot, still no luck. The PSU is obviously producing power. All my fans work fine, no odd noises or error beeps or LED's flashing out of the ordinary. I've checked all my connections and remade my SSD and CPU 8pin connections just to be sure. At one point, I had forgotten to feed my GPU its 6-pin power, but that is hooked up now and it displays fine. The first boot after I connected the GPU and got a display, it was at the same initial screen I get when I run the CMOS clear, except it had said some along the lines of "overclock failed". I haven't seen that on boots since, and my OC multiplier of x42 does still show up in the BIOS menus. I really don't know what is going on here. Any help is greatly appreciated.
 
Try swapping the SATA cables (the HDD one connect it to the SSD). If still no go, disconnect the HDD and start only with the SSD connected.
Check also if SATA is set to AHCI in BIOS (I guess you installed Windows with SATA set to AHCI).
What you can also try is reinstalling Windows on the HDD (only for testing), SSD disconnected and see if booting.
 

Vic 40

Titan
Ambassador
Write down your settings and try the "standard default values" in the bios and save with F10+Y+enter.Look if the ram is running at the right speeds,latency's and voltage (maybe try xmp settings if available) after the clear cmos,also check time and date when you're at it.
 

Nefarious_Nyx

Honorable
Dec 25, 2013
3
0
10,510
Hm. This is a bit odd. I noticed this earlier (before these issues) when I tried to boot without my HDD - says I need to insert proper boot device and restart essentially. But I have nothing OS related on the HDD to my knowledge. Whent his happened earlier I didn't think much of it since I have a front mounted hotswap bay and reinserted my HDD. I don't have any drives configured for hotplugging if that makes a difference. Yes, my BIOS is set to AHCI for the drives. To be honest, I don't know a whole lot about the inner workings of AHCI vs IDE, except that I know it is much newer and always used with SSD's for trim...anyway, yes my Windows install was made with AHCI enabled. I tried swapping the ports tow which the drives were plugged on the mobo, but not completely swapping the cables. I'll give that a shot now.

EDIT- Cable swap did nothing. Still prompts to connect HDD or boot media if HDD isn't installed. Checked RAM - XMP v1.3 is being used, CAS latency and voltages correct after CMOS clear. Time and date remain accurate minus the number of seconds they were deactivated.
 

Nefarious_Nyx

Honorable
Dec 25, 2013
3
0
10,510
GOT it after cmos clear and BIOS reset. WOO! Now time to try out the new soundblasterZ card I got for xmas. Thanks for the help guys, and I'll be back with any further issues, like if I have to reset COS every time or something similar. Hopefully that solved that. Anyone want to go into why resetting CMOS fixes such an issue and how I can avoid doing that in the future if I'm pulling a PSU? Again, thank you so much. Merry Chrismachanakwanza.