Unexpected restart in Windows 11: use Event ID 41 as a timeline clue, not the diagnosis
Kernel-Power Event ID 41 confirms Windows detected an unclean restart; correlate its fields with bugcheck, power and recent-change evidence before deciding why.
- Record the exact Event ID 41 timestamp and source Microsoft-Windows-Kernel-Power.
- Open the event details and preserve any BugcheckCode and power-button fields instead of relying only on the Critical label.
- Check the same time window for WER-SystemErrorReporting Event ID 1001 and EventLog 6008.
- Write down what the PC was doing and any driver, Windows, firmware or hardware change immediately before failures began.
What this problem usually means
Microsoft states that Kernel-Power Event ID 41 is written after Windows starts and detects that the previous shutdown was not clean. The event proves an unexpected shutdown/restart occurred, but by itself it may not identify whether the cause was a stop error, lost power, a hard reset or a system hang.
Work from the narrowest fix to the broader one.
Correlate the restart with nearby system events
Low riskWhy this belongs here: Microsoft recommends using the surrounding event history because Event ID 41 alone often lacks enough information to identify the cause.
- Open Event Viewer > Windows Logs > System.
- Filter around the restart time for Event IDs 41, 1001, 1074 and 6008.
- If Event ID 1001 records a bugcheck, continue with the exact stop code and dump path.
- If 1074 records an intentional restart, do not misclassify it as unexplained power loss.
Branch on bugcheck data versus power/hang evidence
Low riskWhy this belongs here: A nonzero bugcheck path is materially different from a restart where Windows never captured a stop error.
- If the event or Event ID 1001 contains a stop code, use the matching blue-screen record and preserve the dump.
- If no bugcheck was captured, note whether the machine froze, lost power, or was hard-reset.
- Check power delivery, thermals and vendor hardware diagnostics when the symptom points outside Windows.
When this guide stops being the right path
Do not replace the power supply, reinstall Windows or blame a driver solely because Event ID 41 exists. The event is a record of an unclean shutdown, not a unique root-cause code.
If the problem is still not fixed
Use Event ID 1001/stop-code records when a bugcheck exists; use memory/storage/vendor hardware diagnostics when repeated restarts have supporting hardware evidence.
Sources reviewed for this page
Primary technical guidance is preferred. A source supports the scope stated here; it does not imply that every possible cause is covered.