Windows 10: Event Log 6008: Computer restarts every few times while power saving/sleep mode

Hi, I'm recently having this issue as described in the title. It first happened around October and checking the event viewer, it happened maybe 3 to 4 times sequentially. It happened again this Friday, again, around 3 to 4 times until I tended to my computer and now I noticed it restarted today.I also notice that it is accompanied by an event 56 error from Application Popup. I checked WhoCrashed but it does not appear a dump file was created for these restarts.I made sure all of my drivers, especially my network devices were up to date.Specs:Windows version: Windows 10, 10.0, version 2009, bui

:)

 

restart and kernel-power event

Hi,



The kernel power event ID 41 error occurs when the computer is shut down, or it restarts unexpectedly. When a computer that is running Windows starts, a check is performed to determine whether the computer was shut down cleanly. If the computer was not shut
down cleanly, a Kernel Power Event 41 message is generated.



Try this, see if it works for you:

• Go to "Settings"
• Select "System"
• Select "Power and Sleep"
• Select "Additional Power Settings"
• Select "Choose what the power buttons do"
• Select "Change settings currently available"
• Ensure that "Turn on fast start up" is deselected (unticked)
• Click on "Save Changes"

Restart your computer after performing the steps.



Let us know if the above steps resolved the issue.

 

Windows 10 Event ID 6008 Restart Time

I am running Windows 10 Professional 64-bit 21H2. I am getting auto-reboots, which I think are hardware-related. In the System Event Log, Event ID 6008 message, there is a timestamp of the restart. I know that the timestamp listed is NOT the time of the reboot. That timestamp has a time that occurr3ed before the auto-reboot. From where is Windows 10 retrieving the time of the reboot.?

Example - I know that an auto-reboot takes about one minute or less, as I have been at my computer when the system as auto-rebooted. I have in my System Log:



07/23/2022 04:40:05AM "The previous system shutdown at 4:02:09 AM on ‎7/‎23/‎2022 was unexpected."

So I know that Windows 10 came back to life shortly before 4:40:05. I have Open Hardware Monitor monitoring and logging my CPU temperatures every two minutes, and the last timestamp in that log is 4:38:23. So I know that at 4:02:09 the system was running normally.

I have seen other thread in this forum about auto-reboots and their causes, so in this thread I am not interested in why the reboots are occurring. I am interested ONLY in the source of the INCORRECT timestamp in the EventID 6008 message.

 

Surface Book reboots rather than wake from sleep problem - Event ID 6008 and 41

I have a Surface Book i7, 16GB with NVidia graphics connected to a Surface Dock driving two 2 2560 x 1440 extended displays, mouse, numeric pad and HP Deskjet printer. I have the SB set to sleep and then hibernate after two hours when on battery power.
This seems to work fine when I am out of the office. My issue seems to occur only when plugged into and powered with the Surface Dock. The SB sometimes reboots instead of just waking from sleep. When I look at the Event Viewer Administrative Events this behavior
is always reported at the attempted wake up time with an Event ID 6008 Error and an Event ID 41 Critical Error. The description of the 6008 event is that the previous system shutdown at a given time and date was unexpected. The time and date reported is generally
while the SB is supposed to be sleeping. I find no Events reported at that particular time and date in the Event Viewer anywhere. I had one time that the particular reported time and date was while I was actually using the SB but did not get the error until
after I put the SB to sleep and then attempted to wake it back up.

I have looked through the items listed in the Task Scheduler and did not identify anything that might be occurring at the various reported times as well as in the Event Viewer. Does anyone have a suggestion for me to figure out what might be running
or happening at the particular times reported with the errors?