ASRock z77 Extreme4 won't resume from sleep after replacing power supply

Toggle sidebar Toggle sidebar
J

jfriend00

Distinguished
Oct 13, 2007
49
0
18,560
I have had a happily performing ASRock Z77 Extreme4 motherboard since 2012 until my Corsair 520HX power supply died (the PSU was 10 years old). I ordered a Corsair RM650x to replace it. Everything works fine except that after the computer goes to sleep, it won't wake up properly. There's a very weird sequence that happens when it tries to wake up.


  • ■ I move the mouse
    ■ I hear the case fans briefly startup (like for 2 seconds) and then shut-down - system goes quiet, nothing.
    ■ I wait a few seconds and move the mouse again.
    ■ Same thing again with case fans briefly starting up and then shutting down.
    ■ Finally, I hit the sleep button on the case. The screen shows the BIOS as if it was going to be doing a normal boot from scratch, but then freezes. No matter how long I wait, nothing happens.
    ■ I hit the sleep button again and system then reboots from scratch. Prior sleep state is gone, it has done a clean reboot.

So, something with this new power supply and my system does not allow it to get out of sleep state properly. The only other thing I did when replacing the power supply was to also replace a couple case fans that had gotten noisy. FYI, I have hibernate turned off.

Any ideas what could be going on here? I've seen this set of symptoms described in some other internet posts, but did not find a resolution.

I have not updated the BIOS on my motherboard since purchase since everyone describes that as a potentially risky process and should not be done unless you know you really need to. Current BIOS version is P2.40 from 10/15/2012.

Other system info:

i7-3770K
Overclocked to 4.0MHz
32GB RAM DDR3
Boot drive is OCZ SSD
3 Hard drives
Four case fans
NVIDIA GeForce GTX 650 - GDDR5 2GB
 
Sort by date Sort by votes
J

jfriend00

Distinguished
Oct 13, 2007
49
0
18,560


I'm running latest version of Windows 10.

I tried removing the overclock (I thought the same as you) and upon next boot, I got a corrupted boot drive that had to be repaired. It took a long time, but Windows eventually repaired it and rolled Windows back to the last saved checkpoint. I can't see how that could have had anything to do with undoing overclock, but it was the very boot after going into the bios to remove the overclock that it had that issue. That has made me gun shy to muck with that any more. If I don't get any better ideas, I may try that again. I have dropped the overclock to as low as it can be set (awhile ago).

Do you have any specific ideas about sleep state settings? I've seen various settings related to that in the BIOS, but don't really understand what they are or what I would set them to.
 
Upvote 0 Downvote
J

jfriend00

Distinguished
Oct 13, 2007
49
0
18,560


FYI I've restored to all UEFI defaults (no overclocking or any other customizations) and the problem still persists.
 
Upvote 0 Downvote
J

jfriend00

Distinguished
Oct 13, 2007
49
0
18,560
Here's a new clue. When I watch the Dr. Debug LED display on the MOBO during a failed wake from sleep, it ends up stuck on A2 which according to the MOBO documentation A0-A7 is "Problem related to IDE or SATA devices". I've removed all other SATA drives from my system except for the boot SSD. So, I'm guessing it is having a problem with that SATA drive, but only when awaking from sleep, not when booting from scratch. I still don't know how to fix it, but perhaps I'm looking in the right area code at least.

Edit a bit later: Now, I'm not so sure it's actually a SATA issue and reading other accounts of it getting stuck on A2 ended up being something different than an actual SATA issue. The initial problem at starting is long before it gets frozen on this SATA step. I wiggle the mouse to come out of sleep. I hear a brief whir as a few fans run and then turn off again. A few seconds later, there's another brief whir just like the first one, followed be a little beep. Then a few seconds later, the fans come on again and it actually starts the boot process which ends with the screen frozen on the ASRock boot logo and the Dr. Debug display showing A2. I notice that when I boot from scratch, the Dr. Debug whizzes right through the A2 on the display (I see it only for a fraction of a second).

Per other things I've read about the Dr. Debug display, it shows the last operation that was logged to a debug port, but that operation could have already finished and it was busy doing something else that comes after, but that other operation doesn't log to the debug port. So, it's hard to say whether it's actually stuck on a SATA issue or not. Because there's mal-behavior in the startup process long before the SATA step, I think there's something else going on besides a SATA issue. Incidentally, I've tried my SATA boot SSD in several different SATA ports (both SATA 2 and SATA 3) and even cleared the CMOS, but nothing changed. The boot SSD works fine otherwise.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom