F5F Stay Refreshed Software Operating Systems PC occasionally stops working after entering sleep mode rather than restarting.

PC occasionally stops working after entering sleep mode rather than restarting.

PC occasionally stops working after entering sleep mode rather than restarting.

M
Me_Not_Trade
Member
Find
63
11-19-2021, 12:01 AM
#1
Hi
My computer's sleep mode has begun behaving strangely.
I usually use sleep when I don't need to use my PC, and I only turn it off overnight (it's a desktop with the latest 64-bit Windows 11, all updates applied).
Recently this issue occurs more often, though not always:
Sometimes when I try to wake up the machine from sleep, it shuts down instead of starting.
Other times (though rare) I return to a "sleeping" computer where the fans are running and it feels warm, so I have to force restart it.
Could a recent Windows update be affecting how my PC sleeps?
Or am I infected by some malware from a crypto miner?
😉
I'm not sure but this thought came to mind.
How can I find out what's happening?
Reply
Reply
M
Me_Not_Trade
11-19-2021, 12:01 AM #1

Hi
My computer's sleep mode has begun behaving strangely.
I usually use sleep when I don't need to use my PC, and I only turn it off overnight (it's a desktop with the latest 64-bit Windows 11, all updates applied).
Recently this issue occurs more often, though not always:
Sometimes when I try to wake up the machine from sleep, it shuts down instead of starting.
Other times (though rare) I return to a "sleeping" computer where the fans are running and it feels warm, so I have to force restart it.
Could a recent Windows update be affecting how my PC sleeps?
Or am I infected by some malware from a crypto miner?
😉
I'm not sure but this thought came to mind.
How can I find out what's happening?

Reply
Reply
L
LightCloud
Member
Find
145
11-19-2021, 05:45 PM
#2
Why do you bother sleeping it or shutting it down? My PCs are left running 24x7 and I've done that with every PC for the last 30 years at least. There's no need to sleep/shutdown really, unless for noise reasons. Modern PCs are best left running.
I think we're going to need more data, so please download the
SysnativeBSODCollectionApp
and save it to the Desktop. Then run it and upload the resulting zip file to a cloud service with a link to it here. I appreciate that you're not getting BSODs but the SysnativeBSODCollectionApp collects all the troubleshooting data we're likely to need. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.
You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that
here
.
Reply
Reply
L
LightCloud
11-19-2021, 05:45 PM #2

Why do you bother sleeping it or shutting it down? My PCs are left running 24x7 and I've done that with every PC for the last 30 years at least. There's no need to sleep/shutdown really, unless for noise reasons. Modern PCs are best left running.
I think we're going to need more data, so please download the
SysnativeBSODCollectionApp
and save it to the Desktop. Then run it and upload the resulting zip file to a cloud service with a link to it here. I appreciate that you're not getting BSODs but the SysnativeBSODCollectionApp collects all the troubleshooting data we're likely to need. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.
You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that
here
.

Reply
Reply
W
Wouterman1079
Member
Find
193
11-27-2021, 01:01 AM
#3
Another method to understand possible issues is by examining Reliability History/Monitor and Event Viewer.
These tools might record error codes, warnings, and informational events just before system malfunctions occur.
Reliability History/Monitor offers a timeline view (days or weeks) that can highlight recurring patterns.
It’s also worth checking Task Scheduler to see if any applications are activated during sleep or power-saving states.
= = = =
Additionally, review the system's power settings using "powercfg /list".
P.S.: https://learn.microsoft.com/en-us/window...ne-options
The output will be similar but may differ from what your computer shows.
For example: (bold font = my computer)
C:\Windows\System32>Powercfg /list
Existing Power Schemes (* Active)
Reply
Reply
W
Wouterman1079
11-27-2021, 01:01 AM #3

Another method to understand possible issues is by examining Reliability History/Monitor and Event Viewer.
These tools might record error codes, warnings, and informational events just before system malfunctions occur.
Reliability History/Monitor offers a timeline view (days or weeks) that can highlight recurring patterns.
It’s also worth checking Task Scheduler to see if any applications are activated during sleep or power-saving states.
= = = =
Additionally, review the system's power settings using "powercfg /list".
P.S.: https://learn.microsoft.com/en-us/window...ne-options
The output will be similar but may differ from what your computer shows.
For example: (bold font = my computer)
C:\Windows\System32>Powercfg /list
Existing Power Schemes (* Active)

Reply
Reply