F5F Stay Refreshed Power Users Overclocking Device powers off upon awakening from sleep, reboots autonomously, then powers down once more before restarting again

Device powers off upon awakening from sleep, reboots autonomously, then powers down once more before restarting again

Device powers off upon awakening from sleep, reboots autonomously, then powers down once more before restarting again

Z
Zemboyy
Member
Find
235
11-30-2016, 01:34 PM
#1
I assembled my PC about six years ago. It’s an ASUS ROG III MOBO with 12GB RAM, and it’s been running smoothly until recently. A few days back I noticed the mouse freezing and the keyboard lights flickering. After a hard reset, everything seemed normal. Then I put it to sleep and when I woke it up, it shut down completely—first a click, then silence. Three seconds later it clicked back on, started running, then shut down again, followed by another reboot. On the third attempt, with fans set to normal speed, it made loud noises and displayed an "Overclock failed!" message in BIOS. I’ve seen this before, so after another reset I adjusted the fan profiles to silent and changed the CPU/RAM settings back to XMP. After saving and exiting, the system restarted normally. When I tried putting it back into sleep mode, it worked fine, but waking it up again caused a repeated shutdown—"click" multiple times. It’s been functioning well for over six years, yet this keeps happening. Any advice on what might be causing this issue?
Reply
Reply
Z
Zemboyy
11-30-2016, 01:34 PM #1

I assembled my PC about six years ago. It’s an ASUS ROG III MOBO with 12GB RAM, and it’s been running smoothly until recently. A few days back I noticed the mouse freezing and the keyboard lights flickering. After a hard reset, everything seemed normal. Then I put it to sleep and when I woke it up, it shut down completely—first a click, then silence. Three seconds later it clicked back on, started running, then shut down again, followed by another reboot. On the third attempt, with fans set to normal speed, it made loud noises and displayed an "Overclock failed!" message in BIOS. I’ve seen this before, so after another reset I adjusted the fan profiles to silent and changed the CPU/RAM settings back to XMP. After saving and exiting, the system restarted normally. When I tried putting it back into sleep mode, it worked fine, but waking it up again caused a repeated shutdown—"click" multiple times. It’s been functioning well for over six years, yet this keeps happening. Any advice on what might be causing this issue?

Reply
Reply
X
XChristanX
Junior Member
Find
7
11-30-2016, 02:45 PM
#2
Also, I discovered that properly shutting down and restarting the PC allows it to boot normally up to Windows 10, but once it starts loading, it freezes repeatedly. The keyboard lights turn off and the mouse stops functioning entirely. I have to press the reset button to break the cycle, which then restarts the same issue. This is really frustrating. Could anyone help identify the problem? Might it be related to RAM, the motherboard, or another component? Thanks.
Reply
Reply
X
XChristanX
11-30-2016, 02:45 PM #2

Also, I discovered that properly shutting down and restarting the PC allows it to boot normally up to Windows 10, but once it starts loading, it freezes repeatedly. The keyboard lights turn off and the mouse stops functioning entirely. I have to press the reset button to break the cycle, which then restarts the same issue. This is really frustrating. Could anyone help identify the problem? Might it be related to RAM, the motherboard, or another component? Thanks.

Reply
Reply
L
leolo37
Junior Member
Find
38
12-02-2016, 04:23 AM
#3
After extensive testing and research, I found the problem was caused by defective RAM. The G.Skill Ripjaws model had DDR3-2000 3X4GB, but one of the modules was faulty. While searching for a different setting, I noticed Windows only recognized 8GB of RAM. I removed the faulty module, and everything worked smoothly after waking from sleep. I’m hoping the RMA process with G.Skill will go well. Thank you.
Reply
Reply
L
leolo37
12-02-2016, 04:23 AM #3

After extensive testing and research, I found the problem was caused by defective RAM. The G.Skill Ripjaws model had DDR3-2000 3X4GB, but one of the modules was faulty. While searching for a different setting, I noticed Windows only recognized 8GB of RAM. I removed the faulty module, and everything worked smoothly after waking from sleep. I’m hoping the RMA process with G.Skill will go well. Thank you.

Reply
Reply