Windows 10: Event ID 6008 logged after unexpected shutdown and reboot. I can see the logs in event...

Discus and support Event ID 6008 logged after unexpected shutdown and reboot. I can see the logs in event... in Windows 10 BSOD Crashes and Debugging to solve the problem; I have a new computer build with z490 board and i3-10100 cpu. It started shutting down while playing a video game, but now notice it also shuts down... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by JohnArutha, Apr 14, 2021.

  1. Event ID 6008 logged after unexpected shutdown and reboot. I can see the logs in event...


    I have a new computer build with z490 board and i3-10100 cpu. It started shutting down while playing a video game, but now notice it also shuts down randomly while doing other work on computer as well.

    I can see that the event ID 6008 is logged at each one of these times, but I have been unable to decipher the log details which may explain what prompted or initiated the 6008 event.

    I have also been unable to find a guide yet that explains how to read a 6008 log so I can narrow down the cause so I may fix it. If there is a link to an in-depth guide explaining how to delve into the meaning of the 6008 data, please share it. I would love to be able to understand what this stuff means so I can figure out why the computer is shutting down.


    Also I should note, that I have Core Temp 1.17.1 running at all times and set to warn of an imminent cpu temp shutdown, but have not seen any warnings, and I do keep the win 10 pro OS up to date with the latest patches, and drivers up to date as well.


    Here are the last 2 logs from the most recent shutdowns:

    Log Name: System

    Source: EventLog

    Date: 4/14/2021 7:14:48 PM

    Event ID: 6008

    Task Category: None

    Level: Error

    Keywords: Classic

    User: N/A

    Computer: DESKTOP-NE0UP5C

    Description:

    The previous system shutdown at 7:13:29 PM on ‎4/‎14/‎2021 was unexpected.

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

    <System>

    <Provider Name="EventLog" />

    <EventID Qualifiers="32768">6008</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2021-04-15T02:14:48.6200006Z" />

    <EventRecordID>19475</EventRecordID>

    <Correlation />

    <Execution ProcessID="0" ThreadID="0" />

    <Channel>System</Channel>

    <Computer>DESKTOP-NE0UP5C</Computer>

    <Security />

    </System>

    <EventData>

    <Data>7:13:29 PM</Data>

    <Data>‎4/‎14/‎2021</Data>

    <Data>

    </Data>

    <Data>

    </Data>

    <Data>1986</Data>

    <Data>

    </Data>

    <Data>

    </Data>

    <Binary>E507040003000E0013000D001D00E601E507040004000F0002000D001D00E6013C0000003C000000000000000000000000000000000000000100000000000000</Binary>

    </EventData>

    </Event>


    And this one:Event ID: 6008

    Task Category: None

    Level: Error

    Keywords: Classic

    User: N/A

    Computer: DESKTOP-NE0UP5C

    Description:

    The previous system shutdown at 6:38:33 PM on ‎4/‎14/‎2021 was unexpected.

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

    <System>

    <Provider Name="EventLog" />

    <EventID Qualifiers="32768">6008</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2021-04-15T01:39:59.9432301Z" />

    <EventRecordID>19234</EventRecordID>

    <Correlation />

    <Execution ProcessID="0" ThreadID="0" />

    <Channel>System</Channel>

    <Computer>DESKTOP-NE0UP5C</Computer>

    <Security />

    </System>

    <EventData>

    <Data>6:38:33 PM</Data>

    <Data>‎4/‎14/‎2021</Data>

    <Data>

    </Data>

    <Data>

    </Data>

    <Data>109881</Data>

    <Data>

    </Data>

    <Data>

    </Data>

    <Binary>E507040003000E001200260021009B02E507040004000F000100260021009B023C0000003C000000000000000000000000000000000000000100000000000000</Binary>

    </EventData>

    </Event>

    :)
     
    JohnArutha, Apr 14, 2021
    #1
  2. RS_Ricky Win User

    Event 6008, Event Log.

    Hi ,

    I found my PC in the restart condition and when I checked the logs I found Event 6008.

    Message displayed " The previous system shutdown at 17:45:34 on 10/09/2019 was unexpected".

    Log Name: System

    Logged 10/09/2019 18:21:15.

    etc.. Please check attached image.

    Can you please help me with reason of event and why there are two time stamps?


    Event ID 6008 logged after unexpected shutdown and reboot. I can see the logs in event... [​IMG]


    If needed I can get the Details tab details.

    Thank you
     
    RS_Ricky, Apr 14, 2021
    #2
  3. Event ID 6008, Windows 10 1809

    We had a recent Power outage and I usually look for Event ID 6008 to tell me when the Unexpected shutdown occurred - I have looked at 5 PC's all affected by the power down and none have recorded a 6008, only 6009, 6005 & 6013 in that order.

    I've simulated crashes and still 6008 not being logged.

    This feature was active in 1803 but not being logged in 1809 - anybody else having this result ?
     
    BobBarkell, Apr 14, 2021
    #3
  4. Event ID 6008 logged after unexpected shutdown and reboot. I can see the logs in event...

    Event ID 6008, Windows 10 1809

    Thanks for your reply Leocadia - I understand your suggestions thank you.

    The point I was trying to make is our Win 10 Pro v1803 computers, log Event ID 6008 when an unexpected crash happens. However we have Win 10 pro v1809 machines that crashed when the power failed and did not record an Event ID 6008 so I was not able to tell
    when the power actually failed, only when they were rebooted. - so my question is :- is this a bug in the 1809 release or by Microsoft design and has anybosy else experienced this situation ??

    thanks Bob, IT Manager, Henry Riley LLP.
     
    BobBarkell, Apr 14, 2021
    #4
Thema:

Event ID 6008 logged after unexpected shutdown and reboot. I can see the logs in event...

Loading...
  1. Event ID 6008 logged after unexpected shutdown and reboot. I can see the logs in event... - Similar Threads - Event 6008 logged

  2. Event Log Says computer was shutdown but it was on, random PC frezze Event ID 6008

    in Windows 10 BSOD Crashes and Debugging
    Event Log Says computer was shutdown but it was on, random PC frezze Event ID 6008: Hi There, Recently I have been having some weird "happenings" on my windows 10 PC. Today it simply froze, no BSOD, Ctrl+Alt+Del didn't do anything, I could move the mouse but anything else was not working. This is probably the third time this has happened. I waited 30...
  3. Random shutdowns Event ID 6008

    in Windows 10 BSOD Crashes and Debugging
    Random shutdowns Event ID 6008: Hello, Over the past month I've had 10 random shutdown events. Checking temperatures seemed to indicate nothing wrong, though I did also clean the case of my PC for good measure. The hardware seems fine, the memory has no issues, the hard drives seem fine. There was an...
  4. Unexpected shutdown, event 6008

    in Windows 10 BSOD Crashes and Debugging
    Unexpected shutdown, event 6008: Hey guys. Twice I have been playing League of Legends and had my computer unexpectedly shut down. I've looked through event viewer and have no idea what the issue is. I've attached my system/application events as well as my system info, if anyone could help me out I'd be...
  5. Event 6008 The previous system shutdown was unexpected.

    in Windows 10 BSOD Crashes and Debugging
    Event 6008 The previous system shutdown was unexpected.: Hi, My laptop has been crashing, randomly but frequently, with "Something went wrong with your PC" for some time now and the consistent event log is 6008: The previous system shutdown at 09:03:17 on ‎22/‎02/‎2020 was unexpected. The thing is; there was no shut down at...
  6. Windows 10 unexpected shutdown with Event ID 1001,41, and 6008

    in Windows 10 BSOD Crashes and Debugging
    Windows 10 unexpected shutdown with Event ID 1001,41, and 6008: I physically moved my computer to a new location where other electronics have had no prior issues. I was gentle and it was simply to a new room. Anytime I stream or start a game, I will within 90 minutes get a blue screen. Looking at event viewer yields the following: 1001:...
  7. Windows 10 unexpected shutdown with Event ID 1001,41 and 6008.

    in Windows 10 BSOD Crashes and Debugging
    Windows 10 unexpected shutdown with Event ID 1001,41 and 6008.: Hi Team, I have just purchased windows 10 pro from Microsoft. I installed in my system with few software like Visual studio and development software. My system has restarted twice today. I went to system event viewer and found issues like below as error as latest on top....
  8. Event 6008, Event Log.

    in Windows 10 BSOD Crashes and Debugging
    Event 6008, Event Log.: Hi , I found my PC in the restart condition and when I checked the logs I found Event 6008. Message displayed " The previous system shutdown at 17:45:34 on 10/09/2019 was unexpected". Log Name: System Logged 10/09/2019 18:21:15. etc.. Please check attached image....
  9. event id 6008

    in Windows 10 Support
    event id 6008: I believe that event id 6008 is meant to indicate that the previous shutdown was unexpected. However on my computer it happens at odd times with successful shut downs in between. See the attached. I looked at what was happenning at 9:10:19 on 23rd February and the computer...
  10. Unexpected shutdowns with no warning - event logs attached

    in Windows 10 Support
    Unexpected shutdowns with no warning - event logs attached: This has been happening since last 24 hours, My toshiba laptops shuts down automatically without showing any warning, the first it happened about 20 minutes after I turned it on , after the shutdown I again hit the power button and it started normally but after 2 minutes it...

Users found this page by searching for:

  1. windows 1 event viewer error 6008 causes