No POST when power to the motherboard is fully lost

Spyagent1000

Reputable
Nov 18, 2014
5
0
4,510
Whenever I go to boot up after a full loss of power to the motherboard, weather it be a power-outage or I'm just servicing/tinkering on the machine, the computer will start up, but not POST. I get nothing to my monitors and no beep code.

The only way to get it on is to turn off the power supply and unplug it, then replug it and hope for the best. Sometimes its a combination of unplugging it or not turning off the PSU, I have seen no pattern.

Also, after finally getting the thing on I am forced to boot through BIOS and my system time is reset.

My first thought was a battery problem on the motherboard, but after replacing it with a new one I assume that it's not the problem.

My specs are
Windows 7 Home Premium (x64) Service Pack 1
3.60 gigahertz AMD FX-8150 Eight-Core
ASUSTeK COMPUTER INC. M5A99X EVO
NVIDIA GeForce GTX 650 Ti
8 gigs of ram
650 watt PSU
 

Spyagent1000

Reputable
Nov 18, 2014
5
0
4,510
It has posted before (when I mess with the power supply/unplugging plugging back) but I see no pattern

Also I just turned it off and cut it's power again to test it, when failing to POST there is a solid red led for the CPU led on the motherboard
 

Adroid

Distinguished
Why are you losing power to begin with? If you are in an area with frequent blackouts/brownouts I recommend a battery backup to regulate the power and prevent surges to your machine.

After complete power loss you may need to remove the battery and clear the CMOS, see if that helps. You consult your motherboard manual on how to clear CMOS.

Surges and spikes can damage your motherboard. I would suggest getting clean power with a power strip, or installing a battery backup asap.
 

Spyagent1000

Reputable
Nov 18, 2014
5
0
4,510
I always use clean power, but at the moment I have no power backup. The power has been cut very infrequently so its not that big of a deal to me at the moment.

Anyway, the problem is fixed, and I believe it was the CMOS. After resetting that and fiddling around with cables because I was discontent with the cable management the problem resolved. Thank you all!

Also, the "Best solution" to Paul NZ was a mis-click, and should probably go to Adroid, sorry I'm new to all this