Skip to content
PCDecoder
Event ID 41Kernel-PowerEvent IDWidely reported

Event ID 41 Kernel-Power: why your PC restarted and how to find the cause

By Gaurav Rawat · Updated Oct 2, 2026 · Checked against Microsoft documentation · How this page is made

Quick answer

Event ID 41 (Kernel-Power) means Windows restarted without shutting down cleanly. It's a symptom, not a cause. Look at the BugcheckCode in the event details: a non-zero number points to a blue screen you can look up, while zero usually points to power, overheating or a hard freeze.

What it means

When Windows starts, it checks whether the last shutdown was clean. If it wasn't, it writes Event ID 41 to the System log with the message "The system has rebooted without cleanly shutting down first." That's all the event really says: something stopped Windows before it could shut down properly.

The useful part is in the event's Details tab, in two fields:

  • BugcheckCode. If this is a number other than 0, the restart was caused by a blue screen (a stop error), and the code tells you which one. It's shown in decimal, so convert it to hex: 159 becomes 0x9F, 309 becomes 0x135. Then look up that stop code.
  • PowerButtonTimestamp. If this isn't 0, the PC was turned off by holding the power button, usually because it had frozen.

When everything is zero

If BugcheckCode and PowerButtonTimestamp are both 0, Windows didn't get the chance to record anything. Microsoft's guidance is that this usually means hardware: the power was cut, a power supply couldn't keep up, the PC overheated, or it froze so hard it couldn't write to disk. This is the classic "PC turns off while gaming" pattern, where a graphics card's power spikes trip an undersized or ageing power supply.

Common causes

  • A blue screen (stop error). The BugcheckCode field shows which one.
  • Holding the power button to turn off a frozen PC.
  • Power loss: a tripped socket, a loose cable, or a laptop battery that ran flat.
  • A power supply that's failing or too small for the hardware, especially under gaming loads.
  • Overheating, or unstable overclocking or memory (XMP/EXPO) settings.

How to fix it

Safest and most likely fixes first. Readers' answers to "Did this fix it?" reorder this list over time.

  1. Read the BugcheckCode first

    Always. It tells you which of the other fixes applies.

    1. Press Win + X and open Event Viewer.
    2. Go to Windows Logs > System, then select Filter Current Log and enter 41 in the event ID box.
    3. Open the most recent event and select the Details tab.
    4. If BugcheckCode isn't 0, open Calculator in Programmer mode, type the number with Dec selected, and read the Hex value. That's your stop code.
    Did this fix it?

  2. Undo overclocks and memory profiles

    If BugcheckCode is 0 and the restarts happen under load, such as gaming or rendering.

    1. Restart into your BIOS/UEFI setup (usually Delete or F2 at power-on).
    2. Load optimised defaults, or turn off XMP/EXPO and any CPU or GPU overclock.
    3. Close any GPU tuning software in Windows that applies an overclock at startup.
    4. Use the PC normally for a few days to see if the restarts stop.
    Did this fix it?

  3. Check temperatures and power

    If the PC shuts off suddenly with no blue screen.

    1. Plug the PC straight into a wall socket, without an extension lead or cheap power strip.
    2. On a desktop, check that the power cables to the graphics card are firmly seated, using separate cables from the power supply if it has them.
    3. Clean dust from fans and vents, and make sure a laptop isn't sitting on something soft.
    4. Compare your power supply's wattage with your graphics card maker's recommendation. An undersized or ageing unit is a common cause.
    Did this fix it?

  4. Test your memory

    If the restarts are random and the bug check codes vary.

    1. Press Win + R, type mdsched.exe and press Enter.
    2. Choose Restart now and check for problems.
    3. After Windows restarts, the result appears as a notification and in Event Viewer under MemoryDiagnostics-Results.
    Did this fix it?

Is it just you?

25+ Microsoft Q&A threads discuss this, 1 active in the last 30 days. Most recent activity:

Checked Oct 2, 2026. Refreshed automatically every few days.

Sources

Frequently asked questions

Is Event ID 41 a virus?

No. It's Windows recording that the last shutdown wasn't clean. The cause is usually power, hardware or a blue screen.

What does BugcheckCode 0 mean in Event ID 41?

Windows couldn't record a stop code, which usually means the PC lost power or froze too hard to write anything. Hardware, power and temperature are the places to look.

Why does Event ID 41 happen while gaming?

Gaming loads cause sudden spikes in power and heat. An unstable overclock, an overheating part or a struggling power supply can then cut the PC off without warning.

Can I ignore Event ID 41?

If it appeared once after a power cut, yes. If it keeps happening, find the cause before it corrupts files.

Written by

Gaurav Rawat

Gaurav Rawat is a full-stack developer from Jaipur with a B.Tech in Information Technology. At PC Decoder, he writes practical guides on Windows 11 updates, error codes, and fixes for apps that stop working after an update, with an emphasis on clear steps that actually solve the problem.

More from Gaurav Rawat

More event ids decoded