Annoying sleep issue
Annoying sleep issue
This situation has been ongoing for about six months now, and I’m finally exhausted enough to seek assistance. My home LAN file server has the following specifications:
MSI Z390-A Pro BIOS version 1.F0
Intel I5 8400
4x8Gb Crucial RAM CMK16GX4M2A2400C16 – Yes, it’s two different kits, but it has always worked perfectly for years. I don’t think it’s connected to the sleep problem. I’ve replaced one kit at a time, and the issue still continues.
I’m using:
FSP Hydro GE 650W HGE650M
No discrete GPU
Win 11 Pro 24H2
Crucial MX 500 – Boot drive
Samsung 970 EVO Plus 2Tb – storage drive
The problem is that when I wake the PC from sleep using WOL, it immediately goes back to sleep within about a minute. I’ve managed to resolve this by adjusting my power plan settings, switching from the default balanced setting to something else like sleep in 1 hour. When I change the timeout duration, it works fine for either 1 or 2 hours. However, changing the time until sleep every time still causes it to fall asleep too quickly.
I’ve tried using “Restore Defaults,” but that didn’t help. I’ve also checked advanced power settings and confirmed the sleep timer is correctly configured, and SFC/Scannow shows no errors. The SMART status and diagnostic software for both drives report no issues. There are no other problems with the machine.
I’m open to suggestions from anyone who might have encountered a similar situation. Thanks!
If you're unsure of the issue, this option can be attempted prior to a complete system restart:
Settings > System > Fix problems using Windows Update.
I am registered as an admin. I don't need to restart Windows each time I adjust the sleep settings if that's your intention, though it seems Windows has been restarted multiple times for various reasons.
even after logging in as admin, it may differ from running with elevated privileges. Did you restart Windows immediately after adjusting the sleep settings?
I'm not sure about your intentions. After adjusting the sleep settings, I restarted Windows, but that didn't resolve the issue.