PC won't power on after motherboard drivers installed

Viper128

Honorable
May 21, 2013
5
0
10,510
Custom build, installed windows 7 pro x64, installed the AMD chipset drivers, was prompted to reboot and selected "Shutdown" instead as I had to leave. Came back to the PC and attempted to power it on, but the power switch doesn't turn on the Power supply any longer. Tried a different power supply with the same result. Could the chipset drivers have activated some jumper I need to move or something?

Motherboard: http://www.newegg.com/Product/Product.aspx?Item=N82E16813128514

Power Supply:
http://www.newegg.com/Product/Product.aspx?Item=N82E16817182067
 
Solution
If that's the case, get some fiber washers to put under your mounting holes - if it shorts when tight, it could easily short when flexing.

Glad you found the problem.

Viper128

Honorable
May 21, 2013
5
0
10,510


I cleared the CMOS and now the CPU/Power Supply/Case Fans will begin to spin for a fraction of a second when the power button is pressed for the first time. Subsequent presses have no effect. If I disconnect and reconnect the power cable to the tower, the cycle repeats, the first press turns on the fans/fan led's for a fraction of a second, and future presses do nothing
 

Viper128

Honorable
May 21, 2013
5
0
10,510


unfortunately I don't have one of these speakers. I don't think the PC is maintaining power long enough to even begin any sort of boot process. Power is supplied for a fraction of a second and then nada. My CMOS battery was reading 2.5V so I replaced it with a brand new battery and that didn't change anything.

 

Viper128

Honorable
May 21, 2013
5
0
10,510
I believe I have fixed the issue:

After digging around on this site I found someone who had the SAME issue, and they mentioned it was a short on the motherboard between the board and the case, a result of tightening the motherboard screws too tightly. I loosened all of mine, the problem went away. I tightened them, it came back. I loosened them again, and it went away.

Seems like this whole issue was my fault :oops:

I really appreciate your help though markwp :)