Kernel-Power 41, the unexpected shutdown event, explained

Event ID 41 from the Kernel-Power source is not an error that breaks your PC. It is the note Windows writes at startup when it realizes the previous session ended without a clean shutdown: “The system has rebooted without cleanly shutting down first.” The crash, freeze, or power loss already happened; the event is the chalk outline, not the culprit. The real diagnosis is reading its details and finding what happened right before it.

The fix, in order

  1. Open the event and read its data. Event Viewer → Windows Logs → System, find the Kernel-Power 41 entry, open the Details tab (Friendly View, or XML for everything). Two fields matter most: BugcheckCode and PowerButtonTimestamp.
  2. Interpret BugcheckCode. If it is a non-zero number, a blue screen did occur, convert the number to hex and fix that stop code (for example 278 = 0x116, VIDEO_TDR_FAILURE). If it is 0, Windows recorded no crash: the machine lost power, froze so hard it could not write anything, or was reset or held down by the power button.
  3. Look at what came just before. In the System log, examine the minutes before the shutdown: disk errors (source Disk or Ntfs), WHEA-Logger hardware warnings, display driver failures, or a complete absence of entries, which itself suggests sudden power loss rather than a software death.
  4. Check for dump files. Look in C:\Windows\Minidump and for C:\Windows\MEMORY.DMP. Dumps mean a crash occurred and give you the stop code and driver; no dumps plus BugcheckCode 0 supports the power or hard-freeze theory.
  5. Rule out Fast Startup confusion. A Kernel-Power 41 can also be logged when a shutdown itself malfunctioned. Control Panel → Power Options → Choose what the power buttons do → uncheck “Turn on fast startup,” then test normal shutdowns and restarts.
  6. If power loss is the pattern, work the power chain. Try a different wall outlet (not a tired power strip), check the PSU’s age and wattage against the hardware, confirm cables are seated, and test with a UPS if the building’s power is suspect. Heat is the other silent killer: log CPU and GPU temperatures under load.
“It keeps restarting with no blue screen and no dumps” plus a BugcheckCode of 0 is a power or hardware story, not a Windows story. Reinstalling Windows does not repair a failing power supply. Spend the effort on the outlet, the PSU, cooling, and Event Viewer’s preceding entries first.

If it still happens

If the events cluster under heavy load (games, rendering), think heat and power delivery: clean the cooling, verify fan curves, and test with a known-good, adequately rated PSU. If they happen at idle or overnight, think sleep and wake faults: the DRIVER_POWER_STATE_FAILURE and WIN32K_POWER_WATCHDOG_TIMEOUT pages cover that family. Random freezes with BugcheckCode 0 and no power evidence justify a memory test and drive health check to close out the hardware list.

Common questions

How do I fix Kernel-Power 41? You do not fix the event itself; it is a record, not a fault. You fix what it recorded. A non-zero BugcheckCode sends you to that blue screen’s page. Zero sends you to power, heat, and hard-freeze checks. Deleting or suppressing the event would only erase the evidence.

My PC restarts while gaming with no error anywhere. Is it the PSU? It is a leading candidate. Gaming is peak power draw and peak heat together; a marginal power supply sags or a hot component shuts down, and Windows gets no chance to log anything except Kernel-Power 41 at the next boot. Confirm temperatures under load, then test with a known-good supply before buying parts.

Related errors

DRIVER_POWER_STATE_FAILURE · WHEA_UNCORRECTABLE_ERROR · WIN32K_POWER_WATCHDOG_TIMEOUT · CRITICAL_PROCESS_DIED