Fix Kernel-Power Event ID 41: Bugcheck 0 & PSU Triage

To fix Kernel-Power Event ID 41, check the BugcheckCode in Event Viewer details. If it shows 0, your power supply lost power instantly due to an overloaded PCIe cable, failing PSU rail, or bad wall power. If non-zero, Windows crashed from a driver bugcheck before drawing the blue screen.

Random reboots are the most frustrating hardware failure in desktop computing. One second you are gaming or editing video. The next second, your monitor clicks black. Fans spin down, and your PC reboots with zero warning.

When you open Event Viewer under System logs, there it is: Event ID 41, Task Category (63), Kernel-Power.

Most forum advice tells you to run sfc /scannow or reinstall your audio drivers. In our lab, that almost never works. Event ID 41 is not a software bug. It is a symptom. It simply means Windows woke up and noticed it was shut down dirty without notice.

Here is our team’s hands-on diagnostic guide to pinpoint the exact failure.

Step 1: Check the Event Viewer XML Details.

Never guess what caused Event 41. The Event Log contains the exact clue you need.

Open Event Viewer and navigate to Windows Logs → System. In the right panel, click Filter Current Log. Type 41 into the event IDs field and click OK.

Click on the most recent Event 41 record. Select the Details tab and choose the XML View. Look closely at the <EventData> block.

<EventData>
  <Data Name="BugcheckCode">0</Data>
  <Data Name="BugcheckParameter1">0x0</Data>
  <Data Name="BugcheckParameter2">0x0</Data>
  <Data Name="PowerButtonTimestamp">0</Data>
</EventData>

Here is how our engineering team interprets these numbers.

If your BugcheckCode is 0, your operating system did not crash. The CPU lost electrical power so fast that it could not write a single byte to disk.

If your BugcheckCode is non-zero, your PC suffered a standard Blue Screen of Death (BSoD). The graphics card simply lost connection before Windows could draw the blue screen.

Step 2: Fixing BugcheckCode 0 (Instant Power Loss).

When BugcheckCode is 0, stop troubleshooting software. Your focus must be on power delivery, thermal protection, and wall power.

1. Stop Using Daisy-Chained PCIe Cables.

This is the number one cause of gaming reboots on our test bench.

Modern graphics cards can draw sudden power spikes up to double their rated wattage for 10 milliseconds. If you use a single “pig-tail” PCIe cable with two split heads, all that current travels down one single copper wire.

WRONG SETUP (Trips PSU Over-Current Protection):
Power Supply ════════(Single Cable)════════► [Split Plug 1] ──► GPU
                                             [Split Plug 2] ──► GPU

CORRECT SETUP (Dedicated Current Paths):
Power Supply ════════(Dedicated Cable 1)════► GPU (8-Pin Header 1)
Power Supply ════════(Dedicated Cable 2)════► GPU (8-Pin Header 2)

When the GPU spikes, the single wire heats up and voltage sags. The power supply detects over-current and shuts off instantly to prevent a fire.

Always run separate, independent PCIe cables from your modular PSU directly to each GPU power header.

2. Run the OCCT Power Supply Stress Test.

To confirm whether your power supply is dying under load, download the free hardware diagnostic tool OCCT.

1. Close all open apps and background browser tabs.
2. Launch OCCT and select the Power test tab.
3. This test runs your CPU and GPU at 100 percent load at the same time. This draws maximum wattage from your power supply.
4. Open HWiNFO64 in sensors-only mode. Watch the +12V Rail sensor reading.

In ATX specifications, the +12V rail must stay within 5 percent tolerance (between 11.40V and 12.60V). If your 12V rail drops below 11.40V under load, or if your PC clicks off instantly, your power supply is degraded and must be replaced.

3. Check for Thermal Cut-Offs.

Modern motherboards and processors feature built-in thermal safeguards.

If your CPU cooler pump fails, or if thermal paste dries out, CPU temperatures can hit 105°C in two seconds. When temperature limits are breached, the motherboard trips hardware protection and cuts power instantly.

Check HWiNFO64 idle temperatures. If your CPU sits above 65°C at idle or spikes past 95°C opening a browser, reseat your CPU cooler with fresh thermal paste.

Step 3: Fixing Idle Reboots (AMD C-States & Low-Power Idle).

Does your PC crash while sitting idle on the desktop or watching YouTube, but runs fine during heavy gaming?

This is a classic symptom of low-power idle instability, especially on AMD Ryzen processors.

When your computer is idle, the CPU drops into deep sleep states called C-States to save electricity. During this drop, the motherboard drops processor core voltage to near zero. If a CPU core drops voltage too low, it starves of power and reboots with Event ID 41.

How to Fix Idle C-State Drops in BIOS.

1. Restart your PC and press Delete or F2 to enter your BIOS.
2. Search for Global C-State Control (usually under Advanced CPU Configuration).
3. Change the setting from Auto to Disabled.
4. Set Power Supply Idle Control from Low Current Idle to Typical Current Idle.
5. Save settings and restart.

This tells the motherboard to keep a stable minimum voltage floor while your PC is idle, eliminating desktop reboots.

Step 4: Disable Windows Fast Startup.

Windows Fast Startup is a frequent software cause of false Event 41 errors.

Fast Startup does not actually shut your computer down. Instead, it logs off your user account and saves the Windows kernel session into a hibernation file on your SSD.

If a device driver fails to wake up cleanly, Windows crashes upon resume. On next boot, it logs Event ID 41.

To disable Fast Startup cleanly using PowerShell.

# Open PowerShell as Administrator and run:
powercfg /h off

This command disables hybrid hibernation entirely. It frees up gigabytes of SSD storage and forces Windows to boot from a clean state every time.

Step 5: Fixing Non-Zero Bugcheck Codes (Hidden Blue Screens).

If your Event ID 41 details show a number other than 0, your computer experienced a kernel crash.

Convert the hexadecimal BugcheckCode to find your error. Here are the most common values we see in our repair lab.

For detailed triage on specific stop codes, see our dedicated guides.

• Fix CLOCK_WATCHDOG_TIMEOUT 0x101 on Windows 11.
• Fix nvlddmkm Event ID 153 GPU Driver Crashes.
• Fix nvlddmkm.sys Event ID 13 Driver Crashes.
• Our Master Kernel, RAM & Driver Stability Runbook.

Summary Diagnostic Checklist.

Follow this checklist in order whenever Event ID 41 appears.

1. Read the XML block. Determine if BugcheckCode is 0 or non-zero.
2. If 0 and gaming: Replace split pigtail PCIe cables with dedicated lines.
3. If 0 and idle: Disable Global C-States in BIOS.
4. Stress test the PSU. Run the OCCT Power test while monitoring +12V rail voltage in HWiNFO64.
5. Turn off Fast Startup. Run powercfg /h off in PowerShell.
6. If non-zero: Inspect the Minidump file in C:\Windows\Minidump using WinDbg to find the faulting driver.