How to fix Kernel-Power 41 (63)

Стас Lime 0 Reputation points
2025-06-14T11:55:57.7833333+00:00

Hello!
I have a problem with the PC crashing (not a blue screen) during the game. This happens while playing CS2 after entering the Steam overlay. It happens randomly, no dumps are created. The sound freezes for a few seconds, the picture freezes completely, and then the computer does not respond to anything. There is no overheating. All new drivers. During stressful times, nothing crashes and everything works perfectly. There is a critical error Kernel-Power 41 in Event Manager, here are the details:
General:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log Name: System

Source: Microsoft-Windows-Kernel-Power

Date: 14.06.2025 13:56:15

Event ID: 41

Task Category: (63)

Level: Critical

Keywords: (70368744177664),(2)

User: SYSTEM

Computer: Lime

Description:

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

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />

<EventID>41</EventID>

<Version>10</Version>

<Level>1</Level>

<Task>63</Task>

<Opcode>0</Opcode>

<Keywords>0x8000400000000002</Keywords>

<TimeCreated SystemTime="2025-06-14T10:56:15.3858375Z" />

<EventRecordID>8122</EventRecordID>

<Correlation />

<Execution ProcessID="4" ThreadID="8" />

<Channel>System</Channel>

<Computer>Lime</Computer>

<Security UserID="S-1-5-18" />

</System>

<EventData>

<Data Name="BugcheckCode">0</Data>

<Data Name="BugcheckParameter1">0x0</Data>

<Data Name="BugcheckParameter2">0x0</Data>

<Data Name="BugcheckParameter3">0x0</Data>

<Data Name="BugcheckParameter4">0x0</Data>

<Data Name="SleepInProgress">0</Data>

<Data Name="PowerButtonTimestamp">0</Data>

<Data Name="BootAppStatus">0</Data>

<Data Name="Checkpoint">16</Data>

<Data Name="ConnectedStandbyInProgress">false</Data>

<Data Name="SystemSleepTransitionsToOn">3</Data>

<Data Name="CsEntryScenarioInstanceId">10</Data>

<Data Name="BugcheckInfoFromEFI">false</Data>

<Data Name="CheckpointStatus">0</Data>

<Data Name="CsEntryScenarioInstanceIdV2">10</Data>

<Data Name="LongPowerButtonPressDetected">false</Data>

<Data Name="LidReliability">false</Data>

<Data Name="InputSuppressionState">0</Data>

<Data Name="PowerButtonSuppressionState">0</Data>

<Data Name="LidState">3</Data>

<Data Name="WHEABootErrorCount">0</Data>

</EventData>

</Event>

Windows for business | Windows Client for IT Pros | User experience | Other
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. ck459 646 Reputation points
    2025-06-14T12:00:54.9766667+00:00
    0 comments No comments

  2. Henry Mai 1,970 Reputation points Independent Advisor
    2025-06-16T13:09:48.65+00:00

    Hello, I am Henry and I want to share my insight about this issue.Analysis of the Kernel-Power 41 (63) Error

    The "Kernel-Power 41" error is a generic log entry that simply means Windows was forced to restart without a clean shutdown. It's a symptom, not the root cause. The most important detail in the Event XML you provided is this line: <Data Name="BugcheckCode">0</Data>

    A BugcheckCode of 0 means the operating system did not even have a chance to initiate a Blue Screen of Death (BSOD) or create a memory dump file. This indicates that the problem is not a software crash (like a bad driver), but rather a hardware-level event that caused an instantaneous system hang or power loss.

    The fact that this happens during gaming (specifically when triggering the Steam overlay, which causes a sudden change in graphical load) points strongly towards an issue with power delivery under transient load spikes.

    For the action plan, you can follow a plan to isolate the fault.

    Step 1: BIOS and Software Configuration

    1. Disable All Overclocks (Including XMP/EXPO):
      1. Restart your PC and enter the BIOS.
      2. Disable any CPU overclock and, most importantly, disable the XMP or EXPO profile for your RAM.
      3. Save and exit the BIOS. Test the game again. Unstable RAM overclocks are a very common cause of these exact symptoms.
    2. Update BIOS and Chipset Drivers:
      1. Download and install the latest BIOS firmware for your specific model form your motherboard manufacturer's website.
      2. Download and install the latest Chipset drivers for your motherboard. BIOS/Chipset updates often include crucial stability and power management improvements.
    3. Set Windows Power Plan to High Performance:
      1. Go to Control Panel > Power Options.
      2. Set the plan to High Performance or Ultimate Performance.

    Step 2: Hardware Testing (Isolate the faulty component)

    If the issue persists after Step 1, it strongly reinforces the theory of a hardware fault, with the PSU being the primary suspect.

    1. Test with GPU Power Limit:
      • Download and install a tool like MSI Afterburner.
      • In Afterburner, find the "Power Limit" slider and reduce it to 80%. Click Apply.
      • This will reduce the GPU's maximum power draw and lessen the transient spikes it sends to the PSU.
      • Play your game and try to trigger the crash. If the crashing stops with the power limit in place, you have almost certainly confirmed that your PSU cannot handle the GPU's full power demand.
    2. Check All Physical Power Connections:
      • Power down and unplug your PC.
      • Firmly reseat all power cables: the 24-pin motherboard cable, the 8-pin CPU power cable(s), and especially the PCIe power cables going to your GPU. If you are using any adapter cables (like the 12VHPWR adapter for NVIDIA GPUs), ensure they are fully seated and not bent sharply near the connector.

    Hope this helps you.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.