Windows & BSOD · high

How to fix Kernel-Power Event ID 41 (PC restarts or shuts off unexpectedly)

Error code: EVENT-ID-41-KERNEL-POWER

What this error means

Event Viewer shows a critical Kernel-Power event 41 after the PC restarted or shut off on its own. Its text is "The system has rebooted without cleanly shutting down first", and Event ID 6008 (an unexpected previous shutdown) often appears with it. These events are not the cause; Windows logs them after it restarts to record that the last shutdown was not clean. Microsoft explains that the event's details tell you which of three situations happened: a blue screen crash (BugcheckCode is not 0), the power button was held down, or the PC lost power or froze, which typically points to hardware such as the power supply, overheating, memory or overclocking.

Updated

Applies to
Windows 11 and Windows 10
Difficulty
Beginner to intermediate
Before changes
Low

Reviewed by Matyáš Rada · Documentation checked: 2026-10-31 · Checked against Microsoft's Event ID 41 troubleshooting article; not tested on every configuration.

Before you begin

Note what the PC was doing when it restarted or shut off (gaming, idle, sleep) and whether the screen froze first. Event ID 41 only records that the shutdown was not clean; the steps below find out why. If Windows cannot start, see the startup guide.

Work through these checks

0 of 7 complete
01Read BugcheckCode and PowerButtonTimestamp

Microsoft uses these two values to separate a crash, a forced power-off and a power or hardware problem.

  1. Open Event Viewer (Win + R, eventvwr.msc) > Windows Logs > System and open the Kernel-Power event 41.
  2. On the Details tab, note BugcheckCode and PowerButtonTimestamp.
  3. BugcheckCode not 0: a blue screen happened (step 2). PowerButtonTimestamp not 0: the power button was held down. Both 0: the PC lost power or stopped responding, which typically indicates hardware (steps 4 to 7).
What to expect

You know which of the three situations applies.

If it does not help

Also check the events just before the Event ID 6008 time in the System and Application logs for clues.

Browse related errors
02If there is a stop code, follow its guide

When BugcheckCode is not 0, the restart was a blue screen and its code points to the cause.

  1. BugcheckCode is shown in decimal; convert it to hexadecimal (Calculator in Programmer mode). Microsoft's example: 159 is 0x9F (DRIVER_POWER_STATE_FAILURE).
  2. Find that stop code in the blue screen errors overview on this site and follow its guide.
What to expect

You are working on the actual stop code.

If it does not help

Common examples: 278 = 0x116 (VIDEO_TDR_FAILURE), 307 = 0x133 (DPC_WATCHDOG_VIOLATION), 292 = 0x124 (WHEA_UNCORRECTABLE_ERROR).

Browse related errors
03Show the blue screen instead of restarting

Microsoft recommends turning off automatic restart when a stop error appears that Event ID 41 does not record.

  1. Press Win + R, type sysdm.cpl, open Advanced > Startup and Recovery > Settings.
  2. Clear Automatically restart and click OK.
What to expect

The next crash stays on the blue screen so you can read the stop code.

If it does not help

If the PC still turns off instantly without any blue screen, the cause is almost certainly power or hardware.

Browse related errors
04Turn off overclocking

Microsoft lists overclocking as a cause and says to check whether the problem happens at default speeds.

  1. In the BIOS, choose Load optimized defaults, or turn off CPU and GPU overclocks and XMP/EXPO memory profiles.
  2. Close overclocking tools and use the PC normally for a few days.
What to expect

The unexpected restarts stop.

If it does not help

Re-enable settings one by one to find the unstable one.

Browse related errors
05Check temperatures

Overheating components are among the hardware causes Microsoft lists, and many PCs switch off to protect themselves.

  1. Watch CPU and GPU temperatures under load with a monitoring tool.
  2. Clean dust from fans, heatsinks and filters, and make sure all fans spin.
  3. On laptops, keep vents uncovered and use the PC on a hard surface.

Switch off and unplug the PC before cleaning inside it.

What to expect

Temperatures stay within the makers' limits and the PC stays on.

If it does not help

If the CPU runs very hot even when clean, check the cooler's mounting and thermal paste or have it serviced.

Browse related errors
06Check the power supply and power source

Microsoft lists power loss and an underpowered or faulty power supply as causes, and suggests a UPS if the power is unreliable.

  1. Plug the PC directly into a wall socket, without a power strip, and check that the cable is firm.
  2. Compare the power supply's wattage with your components, especially the graphics card maker's recommendation.
  3. If shutdowns happen under heavy load, test with a known-good power supply if possible. On laptops, check the battery and charger.

Never open a power supply; it holds dangerous voltage even when unplugged.

What to expect

The PC stays on under load.

If it does not help

If power cuts or flickers happen in your home, a UPS protects against them.

Browse related errors
07Test the memory

Microsoft lists faulty memory and mismatched memory speeds as causes.

  1. Run Windows Memory Diagnostic (Win + R, mdsched.exe) > Restart now and check for problems.
  2. Check that all memory modules are the same model and run at the same speed.
What to expect

The memory test passes.

If it does not help

If it fails, follow the memory test errors guide on this site. If everything passes, return the BIOS to defaults and, as Microsoft suggests, test the PC in its default configuration.

Browse related errors

Possible causes

  • A blue screen crash (the event records its stop code)
  • The power button was held down to force the PC off
  • Power loss or a faulty or underpowered power supply
  • Overheating or unstable overclocking
  • Faulty or mismatched memory

Useful Windows tools

These commands open Windows tools. Review changes before applying them.

eventvwr.msc
mdsched.exe

Sources & further reading