Computer not booting can't enter BIOS

John Labrier

Reputable
Mar 5, 2014
28
0
4,530
My desktop PC just stopped working out of the blue. Didn't install anything new except for the game "South Park: The Stick of Truth" which I was able to play for about 14 hours with no problem.

When I turn on the PC it does it's usual start up until the "Loading Operating System" black screen where it just gets stuck. I have tried unplugging the HDD and booting but it still does the same thing.

Pressing any key on the key board isn't taking us to the BIOS set-up or Safe mode or anything. It just keeps going to the "Loading Operating System" like it's unresponsive to the keyboard.

My PC specs are:
Windows 7 Professional
GTX 590
i7-2700K
32 GB RAM
2TB HDD

Please let me know if you need more info, and any suggestions would be highly appreciated.
 
Solution
USB3 needs a driver that has to run under windows

USB2 functions are built in to the chipset of the mb and do not need a driver . The USB3 port should probably have defaulted to USB2 functions , but something went wrong .

Glad its working for you now

John Labrier

Reputable
Mar 5, 2014
28
0
4,530


It's actually USB 3.0. I unplugged it and plugged it into the USB 2.0 port and it started working.
I dont know why it wasn't working in the USB 3.0, but after it got past the Loading Operating System screen and I plugged it back in the USB 3.0 ports it started working again. All is good.

Thank you for your time.
 

John Labrier

Reputable
Mar 5, 2014
28
0
4,530


It's actually USB 3.0. I unplugged it and plugged it into the USB 2.0 port and it started working.
I dont know why it wasn't working in the USB 3.0, but after it got past the Loading Operating System screen and I plugged it back in the USB 3.0 ports it started working again. All is good.

Thank you for your time.
 
USB3 needs a driver that has to run under windows

USB2 functions are built in to the chipset of the mb and do not need a driver . The USB3 port should probably have defaulted to USB2 functions , but something went wrong .

Glad its working for you now
 
Solution