• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

System cannot S3 suspend after unexpected shutdown

antef

Senior member
Hi everyone,

I built a new system a few months ago, specs in sig. Things have been fine until a couple days ago I went to move the mouse to wake up the monitors and the screens remained black, I had to reboot. Then last night the system rebooted on its own during normal use, in Event Viewer there is an event that says an unexpected shutdown occurred. Later that night when I went to sleep the system it appeared to sleep but the fans kept running, meaning probably it's only in S1. My motherboard doesn't have an explicit S1/S3 option, it only says Suspend to RAM and you can set it to Auto or Disabled.

Any ideas what could've gone wrong or where to look for clues? I've never dealt with a problem like this before. I disabled "Allow wake" on my NIC just in case, it didn't help, and it's already disabled for my keyboard and mouse. I ran powercfg /a and it reports the system is capable of S1 and S3, so for some reason it's just not entering S3. Any advice would be very appreciated. Thanks!
 
Last edited:
Back
Top