Kernel-Power Event 41 in Windows 11: How to Find the Cause

You open Event Viewer and find a critical entry from Kernel-Power, Event ID 41, Task Category (63). The description says the system rebooted without cleanly shutting down first, and that is all it tells you. Many users chase this message for weeks because they treat Event 41 as the problem, when it is really only a record that the shutdown was dirty.

This guide shows how to read the event properly, separate an actual power loss from a hidden crash, and then fix the underlying cause.

PAGE CONTENT

• What Event ID 41 Actually Means
• Read the Event Details: BugcheckCode Is the Key
• Scenario 1: A Crash Recorded Inside Event 41
• Scenario 2: No Crash Data at All
• Check the Related Events Around the Same Time
• Fix 1: Rule Out Power, Cables, and Cooling
• Fix 2: Rule Out Memory and Overclocking
• Fix 3: Repair Windows and Disable Fast Startup
• FAQs About Kernel-Power Event 41
• Back Up and Restore Windows with Qiling Disk Master

What Event ID 41 Actually Means

Event ID 41 is logged by the Microsoft-Windows-Kernel-Power provider at Critical level, usually with Task Category (63). The full text reads:

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

The important word is "could". Windows knows the last session ended without a proper shutdown sequence, but it does not know why. The power may have cut out, the CPU may have frozen, a driver may have bug-checked, or the power button may have been held down.

That is why searching for "Event 41 fix" returns so many different answers. The event is a symptom, and the real cause is hidden in the extra fields stored with it.

Read the Event Details: BugcheckCode Is the Key

Step 1. Press Win + R, type eventvwr.msc, and press Enter.

Step 2. Go to Windows Logs > System and click "Filter Current Log". Tick Critical and Error, then click OK.

Step 3. Find the Kernel-Power entry with Event ID 41 and open it. Switch to the Details tab and select "Friendly view", or read the EventData section in the XML view.

Step 4. Look for these fields and write down their values:

• BugcheckCode — the stop code, if Windows managed to record one
• BugcheckParameter1 to BugcheckParameter4 — extra detail for that stop code
• PowerButtonTimestamp — non-zero means the power button was held down
• SleepInProgress and BootAppStatus — shows whether the failure happened during sleep or resume

Step 5. Note one critical detail: BugcheckCode is stored in decimal. To compare it with Microsoft's documentation you must convert it to hexadecimal. A value of 59 means 0x0000003B (SYSTEM_SERVICE_EXCEPTION), and 159 means 0x0000009F (DRIVER_POWER_STATE_FAILURE).

Scenario 1: A Crash Recorded Inside Event 41

If the BugcheckCode is not zero, Windows did record a stop error, and the reboot was caused by a crash rather than by power loss. Your job is now the same as for any blue screen.

Step 1. Convert the decimal BugcheckCode to hexadecimal and look up that stop code. This tells you the class of problem, such as a driver power failure or a video timeout.

Step 2. Open C:\Windows\Minidump and check whether a dump file was created at the same timestamp.

Step 3. Open the dump in a debugger and run !analyze -v. The module named in the output, for example a graphics or storage driver, is your primary suspect.

Step 4. Update, roll back, or cleanly reinstall that driver, and repeat the workload that triggered the crash.

Step 5. If the same module appears in several dumps, treat it as confirmed rather than coincidental and either replace the driver with a different version or, if it is a hardware driver, test the device in another slot.

Scenario 2: No Crash Data at All

If BugcheckCode is 0 and PowerButtonTimestamp is also 0, Windows recorded nothing useful. This pattern usually means the machine stopped so abruptly that no crash dump could be written.

Common causes in this situation are:

• A power supply that cannot deliver stable power under load
• Loose or daisy-chained PCIe and CPU power connectors
• Overheating that trips a hardware protection circuit
• Unstable memory, including aggressive XMP or EXPO profiles
• Motherboard or firmware issues

Treat this as a hardware stability investigation rather than a Windows problem, and work through the hardware fixes below before reinstalling anything.

Check the Related Events Around the Same Time

Step 1. Look for Event ID 6008 in the System log, which records an unexpected shutdown and confirms the timestamp.

Step 2. Look for volmgr Event ID 46, which means crash dump initialization failed. That explains why no dump exists and reinforces the "too abrupt to record" theory.

Step 3. Check for WHEA-Logger entries, which indicate hardware-detected errors such as corrected or uncorrected machine checks.

Step 4. Check the display driver events around the same minute. A GPU reset logged just before the reboot often means the graphics driver is the trigger.

Fix 1: Rule Out Power, Cables, and Cooling

Step 1. Reseat every power connector: the 24-pin ATX, the 8-pin CPU, and each PCIe connector on the graphics card. Push until it clicks.

Step 2. Avoid daisy-chaining a single PCIe cable into two connectors on a high-power card. Use separate cables from the power supply where possible.

Step 3. Check that the power supply wattage comfortably covers your CPU and GPU, and remember that an ageing unit loses capacity over time.

Step 4. If possible, test with a known-good power supply. This single swap resolves a surprising number of unexplained Event 41 loops.

Step 5. Clean dust from the case and graphics card, confirm every fan spins, and monitor CPU and GPU temperatures under load. Sustained overheating can shut a system down before any dump is written.

Step 6. If your region has unstable mains power, add a quality UPS. Dirty shutdowns caused by brief brownouts are recorded exactly like hardware faults.

Fix 2: Rule Out Memory and Overclocking

Step 1. Enter the BIOS or UEFI setup and load optimized defaults, then save and exit. This removes CPU overclocks, memory overclocking profiles such as XMP or EXPO, and any tuned voltages.

Step 2. Test at default JEDEC memory speed. If the crashes stop, the memory profile was the problem, and you can reintroduce it later at a lower setting.

Step 3. If your motherboard exposes a DRAM debug LED that lights up before the reboot, memory is the prime suspect.

Step 4. Test one memory module at a time in the same slot, then test the same module in each slot. This distinguishes a faulty module from a faulty slot.

Step 5. Run a thorough memory test from bootable media and let it complete several passes rather than one. The built-in Windows Memory Diagnostic is a starting point, not a definitive result.

Step 6. Confirm that all installed modules run at the same speed and configuration, since mismatched kits are a common source of instability.

Fix 3: Repair Windows and Disable Fast Startup

Step 1. Disable Fast Startup. Open Control Panel > Power Options > "Choose what the power buttons do" > "Change settings that are currently unavailable", then clear "Turn on fast startup" and restart. Fast Startup leaves the kernel in a hybrid state and is a known contributor to unexpected shutdowns.

Step 2. Repair system files from an elevated Command Prompt:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Step 3. Check the health of your drives with chkdsk C: /f /r and review the S.M.A.R.T. values of the system disk. A drive that stalls under load can produce abrupt restarts.

Step 4. Install all pending Windows updates, since firmware and driver stability fixes are regularly delivered through cumulative updates.

Step 5. Update the motherboard BIOS, chipset drivers, and storage drivers from the manufacturer's support page for your exact model.

Step 6. If the problem began after installing a specific utility, RGB lighting suite, monitoring tool, or anti-cheat component, remove it and retest. Low-level kernel components from these tools are frequent causes of unexplained restarts.

FAQs About Kernel-Power Event 41

Does Event ID 41 tell me what caused the restart?

No. It only confirms that the previous session ended without a clean shutdown. The cause must be inferred from the BugcheckCode, the related events around the same timestamp, and hardware testing.

Is Event 41 always a hardware problem?

No. If the BugcheckCode is non-zero, the restart was caused by a stop error, which is usually a driver problem. Event 41 with no bugcheck data is the pattern that points toward power, memory, thermal, or firmware issues.

Why is the bugcheck code in Event 41 so hard to recognize?

Because it is stored in decimal rather than hexadecimal. Converting a value such as 159 to 0x0000009F is what makes it match the documentation you find online.

My PC shows Event 41 only while gaming. What should I check first?

Start with the power path and cooling, then the graphics driver. Gaming pushes the power supply, the GPU, and the memory hardest, which is why marginal hardware fails there and nowhere else.

Does Event ID 41 mean my power supply is broken?

Not necessarily. It means power was interrupted or the system stopped responding. A defective power supply is one common explanation, but loose cables, overheating, and unstable memory produce the same event.

Will reinstalling Windows fix Event 41?

Usually not, if the cause is hardware or firmware, because those problems survive a clean install. Reinstalling Windows is worth considering only after the power, thermal, memory, and firmware checks have all passed.

Back Up and Restore Windows with Qiling Disk Master

Frequent unexpected restarts put your open documents and system files at risk, and hardware testing means opening the case, swapping the power supply, and reseating memory. Create a full system backup before you start. Qiling Disk Master handles both the backup and the restore.

• Free Download
• Windows 11/10/8/7, 100% Secure

Part 1: Create a Full System Backup

Step 1. Install and open Qiling Disk Master. On the home screen, open "Backup and Recovery" and choose "System Backup". This option automatically includes Windows and the hidden boot partitions, so you do not have to select them one by one.

Step 2. Check the source. The disk where Windows is installed and its system partitions are already ticked for you. If you only need your personal documents, run a separate "File Backup" task instead.

Step 3. Click the destination box and choose where the image should be saved. Use an external HDD or SSD, a NAS, or any drive other than the one Windows is installed on, and make sure it has enough free space.

Step 4. Review the task summary and click "Proceed". Wait until the progress bar reaches 100%. Do not unplug the drive or turn off the PC while the backup is running.

Part 2: Restore Windows from the Backup

Step 1. Open Qiling Disk Master again, go to "Backup and Recovery", and select the recovery option. Your backup images are listed, so pick the one you created before the troubleshooting began.

Step 2. Choose the target disk or partition. Normally you restore to the original system disk. If the drive was replaced, select the new disk instead, and the restore rebuilds Windows together with its boot partitions.

Step 3. Preview the restore plan, click "Proceed", and confirm the warning. The PC restarts to finish the job, and Windows comes back exactly as it was on the day the image was created, with your files and programs intact.

Conclusion

Kernel-Power Event 41 is a record of an unclean shutdown, not a diagnosis. Open the event and read the BugcheckCode: a non-zero value means a stop error occurred, so convert it from decimal to hexadecimal and troubleshoot that code as you would any blue screen. If the bugcheck data is empty, work through the hardware path instead, covering the power supply and cables, temperatures, memory profiles, and firmware. Repairing Windows or reinstalling it rarely helps until those checks are done.

Protect your PC with Qiling Backup—create a system image before your next troubleshooting step.

Related Articles

• LiveKernelEvent 141 in Windows 11: Causes and Fixes (2026)
  LiveKernelEvent 141 is the other common event Windows logs when the graphics driver resets. Learn how the two events differ and how to fix the driver behind both.
• Fix DRIVER_POWER_STATE_FAILURE BSOD (0x0000009F)
• Fix VIDEO_TDR_FAILURE BSOD in Windows 11
• Windows 11 Keeps Crashing? 8 Proven Fixes
  If Event 41 keeps appearing alongside random restarts, these eight fixes cover the driver, disk, and power causes behind repeated Windows 11 crashes.
• Computer Keeps Crashing When Playing Games