Windows 10: Microsoft-Windows-WER-SystemErrorReporting EventID 6008

GHi, folks. The day before yesterday, I reintall win10 and it is all fine, but yesterday, after I install ubuntu, change WSL setting, they system would restart in 2 hours automatically...

HHere is the event detail:

<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-03-22T23:17:44.0819384Z" />
<EventRecordID>2248</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>DESKTOP-Q8J7PEM</Computer>
<Security />
</System>
- <EventData>
<Data>6:55:57 PM</Data>
<Data>‎3/‎22/‎2021</Data>
<Data />
<Data />
<Data>4808</Data>
<Data />
<Data />
<Binary>E507030001001600120037003900C100E507030001001600160037003900C100600900003C000000010000006009000001000000B00400000100000000000000</Binary>
</EventData>

</Event>

and here is the event log at the same time around event ID 6008.Could anybody help me to check what is wrong



:)

 

This is causing 90% of my Win7 64bit BSOD's...

- System

- Provider

[ Name] Microsoft-Windows-WER-SystemErrorReporting
[ Guid] {ABCE23E7-DE45-4366-8631-84FA6C525952}
[ EventSourceName] BugCheck

- EventID 1001

[ Qualifiers] 16384

Version 0

Level 2

Task 0

Opcode 0

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2010-04-18T13:44:16.000000000Z

EventRecordID 75672

Correlation

- Execution

[ ProcessID] 0
[ ThreadID] 0

Channel System

Computer FATTYMCGHEE-PC

Security


- EventData

param1 0x000000d1 (0xfffff8800bf8ded8, 0x0000000000000002, 0x0000000000000000, 0xfffff880018656b5)
param2 C:\Windows\MEMORY.DMP
param3 041810-13384-01

 

Windows 10 suffers EventID's 6008 & 1001 & 41(63) - "System has rebooted without cleanly shutting down first" - after hibernate

Hi all

I initially posted about BSOD's on my system (Cross-link to other MS post) but
didn't notice any further BSOD's after downgrading my GPU driver, however, my system continued to experience these System Errors (in chronological order):

• I will hibernate my system (seemingly without problem)
  
• Upon resume, I have a fresh / empty desktop and no error messages.
  
• Going into Event Viewer and filtering for Critical and Error:
  
  • Error EventID 6008 - The previous system shutdown at 10:38:31 PM on ‎2018/‎03/‎09 was unexpected
    
  • Critical EventID 41(63) - The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    
  • Error EventID 1001 - The computer has rebooted from a bugcheck. The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff8019248c370, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: d9a9550e-fc49-4be7-a7e8-9904a878b3c4.

This has been going on for several months (same error messages above every time), the steps I've followed to try and resolve this:

• Update Firmware on Lenovo T460P
• Update drivers on all devices
• Expand free disk space (currently 100GB of 512GB is free)
• Eventually had the motherboard swapped out (faulty USB port)
• Attempted steps mentioned in cross-linked post (above)
• Did a Windows reset (keep old files but reinstall Windows)
• Within a day of the Windows reset it's doing this again.

I can only suspect it's a hardware fault - how can I troubleshoot this?

I get loads of DistributedCOM error messages in Event Viewer but I've read that these are innocuous and can be ignored.

--->

Error Event #1:

Log Name: System

Source: EventLog

Date: 2018/03/12 09:53:34

Event ID: 6008

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: LT460p-BTX

Description:

The previous system shutdown at 10:38:31 PM on ‎2018/‎03/‎09 was unexpected.

Event Xml:

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

<System>

<Provider Name="EventLog" />

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

<Level>2</Level>

<Task>0</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2018-03-12T07:53:34.335522200Z" />

<EventRecordID>629</EventRecordID>

<Channel>System</Channel>

<Computer>LT460p-BTX</Computer>

<Security />

</System>

<EventData>

<Data>10:38:31 PM</Data>

<Data>‎2018/‎03/‎09</Data>

<Data>

</Data>

<Data>

</Data>

<Data>28739</Data>

<Data>

</Data>

<Data>

</Data>

<Binary>E207030005000900160026001F00B303E207030005000900140026001F00B303DC0500003C00000001000000DC05000001000000580200000100000000000000</Binary>

</EventData>

</Event>

Critical Event #2:

Log Name: System

Source: Microsoft-Windows-Kernel-Power

Date: 2018/03/12 09:53:24

Event ID: 41

Task Category: (63)

Level: Critical

Keywords: (70368744177664),(2)

User: SYSTEM

Computer: LT460p-BTX

Description:

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Event Xml:

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

<System>

<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />

<EventID>41</EventID>

<Version>6</Version>

<Level>1</Level>

<Task>63</Task>

<Opcode>0</Opcode>

<Keywords>0x8000400000000002</Keywords>

<TimeCreated SystemTime="2018-03-12T07:53:24.051630700Z" />

<EventRecordID>639</EventRecordID>

<Correlation />

<Execution ProcessID="4" ThreadID="8" />

<Channel>System</Channel>

<Computer>LT460p-BTX</Computer>

<Security UserID="S-1-5-18" />

</System>

<EventData>

<Data Name="BugcheckCode">307</Data>

<Data Name="BugcheckParameter1">0x1</Data>

<Data Name="BugcheckParameter2">0x1e00</Data>

<Data Name="BugcheckParameter3">0xfffff8019248c370</Data>

<Data Name="BugcheckParameter4">0x0</Data>

<Data Name="SleepInProgress">0</Data>

<Data Name="PowerButtonTimestamp">0</Data>

<Data Name="BootAppStatus">0</Data>

<Data Name="Checkpoint">0</Data>

<Data Name="ConnectedStandbyInProgress">false</Data>

<Data Name="SystemSleepTransitionsToOn">3</Data>

<Data Name="CsEntryScenarioInstanceId">0</Data>

<Data Name="BugcheckInfoFromEFI">true</Data>

<Data Name="CheckpointStatus">0</Data>

</EventData>

</Event>

Error Event #3:

Log Name: System

Source: Microsoft-Windows-WER-SystemErrorReporting

Date: 2018/03/12 09:54:16

Event ID: 1001

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: LT460p-BTX

Description:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff8019248c370, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: d9a9550e-fc49-4be7-a7e8-9904a878b3c4.

Event Xml:

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

<System>

<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />

<EventID Qualifiers="16384">1001</EventID>

<Version>0</Version>

<Level>2</Level>

<Task>0</Task>

<Opcode>0</Opcode>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2018-03-12T07:54:16.078085900Z" />

<EventRecordID>696</EventRecordID>

<Correlation />

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

<Channel>System</Channel>

<Computer>LT460p-BTX</Computer>

<Security />

</System>

<EventData>

<Data Name="param1">0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff8019248c370, 0x0000000000000000)</Data>

<Data Name="param2">C:\WINDOWS\MEMORY.DMP</Data>

<Data Name="param3">d9a9550e-fc49-4be7-a7e8-9904a878b3c4</Data>

</EventData>

</Event>

 

Windows 10 seizes, EventID 6008

Hi,

For us to have a better understanding of your concern, we'd like to ask the following questions:

• What is the make and model of your device?
• Which version of Window 10 are you currently using? To check, click Start, type
  WINVER, and press Enter. Please include the OS Build and version of your device.
• Have you made any recent changes on your device?
• What steps have you made to resolve your concern?

We're looking forward to your response.