Repeated Kernel-Power Issues

Question

My computer loses power about 10 times a day. What is the problem? Here's a screenshot and one of the events from Event Viewer.

Log Name: System

Source: Microsoft-Windows-Kernel-Power

Date: 5/19/2026 7:02:44 PM

Event ID: 41

Task Category: (63)

Level: Critical

Keywords: (70368744177664),(2)

User: SYSTEM

Computer: WilliamsonPC

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>10</Version>

<Level>1</Level>

<Task>63</Task>

<Opcode>0</Opcode>

<Keywords>0x8000400000000002</Keywords>

<TimeCreated SystemTime="2026-05-20T00:02:44.1876729Z" />

<EventRecordID>2000513</EventRecordID>

<Correlation />

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

<Channel>System</Channel>

<Computer>WilliamsonPC</Computer>

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

</System>

<EventData>

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

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

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

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

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

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

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

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

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

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

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

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

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

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

<Data Name="CsEntryScenarioInstanceIdV2">4</Data>

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

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

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

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

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

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

</EventData>

</Event>

Answer 1

See if your computer is creating minidump files.

To find these files, this is the path "C:\Windows\Minidump".

First copy and paste all the minidump files you have to another folder and then zip it. Then upload the ZIP file to the cloud OneDrive.

Choose to share or right click and get the share link.

Please post the link to the ZIP file here so it can be reviewed.

Answer 2

There are event ID 1001s associated with each shutdown. How do I find the driver causing the error? Here's the bugcheck info:

Log Name: System

Source: Microsoft-Windows-WER-SystemErrorReporting

Date: 5/19/2026 7:02:55 PM

Event ID: 1001

Task Category: None

Level: Error

Keywords:

User: SYSTEM

Computer: WilliamsonPC

Description:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000024 (0x000000b50019090d, 0xfffffa897e7d6e50, 0xfffffa897e7d6ef0, 0xfffff803c8a3634f). A dump was saved in: C:\WINDOWS\Minidump\051926-14125-01.dmp. Report Id: e0ff42f7-251a-493f-950f-cfdf6eb9b3d8.

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}" />

<EventID>1001</EventID>

<Version>1</Version>

<Level>2</Level>

<Task>0</Task>

<Opcode>0</Opcode>

<Keywords>0x8000000000000000</Keywords>

<TimeCreated SystemTime="2026-05-20T00:02:55.2926011Z" />

<EventRecordID>2000546</EventRecordID>

<Correlation />

<Execution ProcessID="1380" ThreadID="1384" />

<Channel>System</Channel>

<Computer>WilliamsonPC</Computer>

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

</System>

<EventData>

<Data Name="param1">0x00000024 (0x000000b50019090d, 0xfffffa897e7d6e50, 0xfffffa897e7d6ef0, 0xfffff803c8a3634f)</Data>

<Data Name="param2">C:\WINDOWS\Minidump\051926-14125-01.dmp</Data>

<Data Name="param3">e0ff42f7-251a-493f-950f-cfdf6eb9b3d8</Data>

</EventData>

</Event>

Answer 3

Event ID 41 (Kernel-Power) means Windows detected that the system restarted without a clean shutdown. It doesn’t by itself identify the exact cause; it records that the PC either crashed, hung, or lost power unexpectedly.

From the log:

• Event ID: 41, Level: Critical → unexpected reboot
• 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.”
• BugcheckCode is non‑zero (36) → the system is actually bug‑checking (Blue Screen / stop error), not just losing wall power.

To narrow down the cause:

1. Check whether reboots are normal or unexpected
   • In Event Viewer → Windows Logs → System, filter for Event IDs 13, 41, 1074, 6008, 6009.
   • Normal reboots: 1074 followed by 13 and 6009.
   • Unexpected reboots: 41 and 6008.
   • In the screenshot, the repeated 41 entries indicate repeated unexpected reboots.
2. Confirm if there is a bugcheck (Blue Screen)
   • Filter System log for Event ID 1001 (source: WER-SystemErrorReporting).
   • If present with text like “The computer has rebooted from a bugcheck. The bugcheck was: 0xXXXXXXXX… A dump was saved in: C:\Windows\MEMORY.DMP”, then a stop error is causing the reboot.
   • Use the bugcheck code and dump file to identify the failing driver or component.
3. Correlate with recent changes
   • Also filter for Event IDs 19 and 7045 in System:
     • 19 (WindowsUpdateClient) → OS or security updates.
     • 7045 (Service Control Manager) → new or updated drivers/services.
   • Look at the timeline: if 41/1001 start shortly after a driver, firmware, or Windows update, that change is a likely trigger.
4. Consider hardware or power issues
   • If some Event ID 41 entries have BugcheckCode = 0 or no 1001 events, that pattern often indicates power loss or PSU/battery issues (for example, power outage, faulty or underpowered PSU, drained/removed battery).
   • In that scenario, inspect power cabling, UPS/power strip, and PSU, and test on a different outlet.
5. Next steps
   • Use the stop code and MEMORY.DMP from Event ID 1001 to debug which driver or device is failing.
   • If no bugcheck is logged (BugcheckCode = 0) and only 41/6008 appear, focus on power delivery and hardware stability (PSU, motherboard, overheating, etc.).

In summary, the repeated Kernel-Power 41 entries mean the PC is repeatedly rebooting unexpectedly; the detailed cause must be derived by correlating Event ID 41 with Event ID 1001 (bugchecks), 6008 (unexpected shutdowns), and nearby update/driver events (19, 7045), and by checking for possible power or hardware faults.

---

References:

• Advanced troubleshooting for Event ID 41: "The system has rebooted without cleanly shutting down first"
• Troubleshoot unexpected reboots using system event logs
• Troubleshooting Windows unexpected restarts and stop code errors