Share via

Kernel Power 41 while PC is idle or suspended

Anonymous
2023-09-01T07:49:34+00:00

Hello,

My PC since the last month has been crashing almost daily without any BSOD. It seems like the power just goes out. When I checked the event viewer every time I got a Kernel Power 41 error with all bugcheck parameters set to 0 (except for a few times). I have tried everything I found online: I updated every driver (including chipset and GPU drivers), I have changed the power plan for Windows, disabled C-states, updated the BIOS, ran MemTest for about 3.5 hours and driver verifier, which bluescreened almost instantly twice. I even ran FurMark and Prime95, but it could handle it with no issues.

This issue occoured rarely a few years ago when playing Valorant, however now it happens almost every time i let my PC idle, either by suspending it or leaving for 10-30 minutes.

My specs are:

  • Ryzen 5 2600 on a b450m-dsh3 from Gigabyte
  • 16 GB ddr4 2666hz ram on two 8 GB sticks
  • 1060 6 GB GPU
  • 600W Thermaltake PSU

Here are the minidumps for the few times that it actually reported: https://drive.google.com/file/d/17EuMOkspxYrzAxTRP1QXt0YrkbRmIrbv/view?usp=drive_link

These are the minidumps that the driver verifier generated: https://drive.google.com/file/d/1sAsHUB3kTaRkJuRiWDeBXYOINhIzeMTf/view?usp=sharing

These are events where the Bugcheck parameters weren't all zeros:

  • <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>8</Version><Level>1</Level><Task>63</Task><Opcode>0</Opcode><Keywords>0x8000400000000002</Keywords><TimeCreated SystemTime="2023-08-14T14:12:25.0236983Z" /><EventRecordID>65547</EventRecordID><Correlation /><Execution ProcessID="4" ThreadID="8" /><Channel>System</Channel><Computer>DESKTOP-3L82ST0</Computer><Security UserID="S-1-5-18" /></System>
  • <EventData> <Data Name="BugcheckCode">270</Data><Data Name="BugcheckParameter1">0x33</Data><Data Name="BugcheckParameter2">0xffff8601bebddcb0</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">0</Data><Data Name="ConnectedStandbyInProgress">false</Data><Data Name="SystemSleepTransitionsToOn">3</Data><Data Name="CsEntryScenarioInstanceId">0</Data><Data Name="BugcheckInfoFromEFI">false</Data><Data Name="CheckpointStatus">0</Data><Data Name="CsEntryScenarioInstanceIdV2">0</Data><Data Name="LongPowerButtonPressDetected">false</Data></EventData> </Event>
  • <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>8</Version><Level>1</Level><Task>63</Task><Opcode>0</Opcode><Keywords>0x8000400000000002</Keywords><TimeCreated SystemTime="2023-06-04T22:04:53.4173089Z" /><EventRecordID>52411</EventRecordID><Correlation /><Execution ProcessID="4" ThreadID="8" /><Channel>System</Channel><Computer>DESKTOP-3L82ST0</Computer><Security UserID="S-1-5-18" /></System>
  • <EventData> <Data Name="BugcheckCode">159</Data><Data Name="BugcheckParameter1">0x4</Data><Data Name="BugcheckParameter2">0x12c</Data><Data Name="BugcheckParameter3">0xffffd9080da76040</Data><Data Name="BugcheckParameter4">0xffff8b0d1d899880</Data><Data Name="SleepInProgress">0</Data><Data Name="PowerButtonTimestamp">0</Data><Data Name="BootAppStatus">0</Data><Data Name="Checkpoint">0</Data><Data Name="ConnectedStandbyInProgress">false</Data><Data Name="SystemSleepTransitionsToOn">0</Data><Data Name="CsEntryScenarioInstanceId">0</Data><Data Name="BugcheckInfoFromEFI">false</Data><Data Name="CheckpointStatus">0</Data><Data Name="CsEntryScenarioInstanceIdV2">0</Data><Data Name="LongPowerButtonPressDetected">false</Data></EventData>

</Event>

  • <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>8</Version><Level>1</Level><Task>63</Task><Opcode>0</Opcode><Keywords>0x8000400000000002</Keywords><TimeCreated SystemTime="2023-05-01T22:11:16.5944786Z" /><EventRecordID>45930</EventRecordID><Correlation /><Execution ProcessID="4" ThreadID="8" /><Channel>System</Channel><Computer>DESKTOP-3L82ST0</Computer><Security UserID="S-1-5-18" /></System>
  • <EventData> <Data Name="BugcheckCode">159</Data><Data Name="BugcheckParameter1">0x4</Data><Data Name="BugcheckParameter2">0x12c</Data><Data Name="BugcheckParameter3">0xffffcb8cc73d8040</Data><Data Name="BugcheckParameter4">0xffff88810b6b5880</Data><Data Name="SleepInProgress">0</Data><Data Name="PowerButtonTimestamp">0</Data><Data Name="BootAppStatus">0</Data><Data Name="Checkpoint">0</Data><Data Name="ConnectedStandbyInProgress">false</Data><Data Name="SystemSleepTransitionsToOn">3</Data><Data Name="CsEntryScenarioInstanceId">0</Data><Data Name="BugcheckInfoFromEFI">false</Data><Data Name="CheckpointStatus">0</Data><Data Name="CsEntryScenarioInstanceIdV2">0</Data><Data Name="LongPowerButtonPressDetected">false</Data></EventData> </Event>
Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

7 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. DaveM121 879.6K Reputation points Independent Advisor
    2023-09-01T17:08:50+00:00

    This time it is the AMD chipset drivers listed as the cause of the crashes, re-install the version of AMD chipset drivers provided on the support page for your PC,

    Then ensure Driver Verifier is disabled and wait to see if your system is stable

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2023-09-01T10:40:14+00:00

    I have ran driver verifier and here are the resulting minidumps: https://drive.google.com/file/d/10B4Rzz2sS06wNc3yu4oU12jZetasnK3t/view?usp=sharing

    I also swapped the RAM sticks with my brother's (same brand and size, different speed) and ran driver verifier, here are the results: https://drive.google.com/file/d/1xtOzJZZLNgN7-HZgRqorYcM42gk08g5h/view?usp=sharing

    Regarding the settings of the driver verifier, I used the ones mentioned in these posts:

    https://answers.microsoft.com/en-us/windows/forum/all/kernel-power-event-id-41-is-killing-me-please-help/c40e7fb0-fef0-4789-9f16-a59f7d0cb0e4 

    https://answers.microsoft.com/en-us/windows/forum/all/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983 

    Thank you in advance.

    Was this answer helpful?

    0 comments
  3. DaveM121 879.6K Reputation points Independent Advisor
    2023-09-01T09:14:26+00:00

    If you have run a 3 pass scan with MemTest86 and no errors were indicated on your RAM, to try to force Windows 10 show any faulting drivers, the best option would be to turn on Driver Verifier, let your PC crash 3 times, then you must turn off Driver Verifier, and finally, upload any newly created minidump files

    Before you run Driver Verifier, please create a new System Restore Point

    https://answers.microsoft.com/en-us/windows/for...

    Note, if you have any difficulty getting into Windows with Driver Verifier enabled:

    Start your PC, just as Windows attempts to load (spinning dots), press and hold Power Button for 5 - 10 seconds to perform a Hard Shut Down

    Do this twice

    On the third start Windows will boot into the Recovery Environment and from there you can access System Repair, Safe Mode, Command Prompt... etc.

    Go to Troubleshoot - Advanced Option - Startup Settings and click Restart

    Upon restart, press 4 to enter Safe Mode

    Open Command Prompt as Administrator and run these two commands, then restart your PC.

    verifier /reset

    verifier /bootmode resetonbootfail

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-09-01T09:12:13+00:00

    Hello, thank you for the reply.

    I have updated the chipset driver and BIOS to the latest a few days ago, so after these minidumps were saved. I have already ran MemTest for 3 passes and it didn't detect anything, should i run it for 4 or more passes to be sure?

    Was this answer helpful?

    0 comments
  5. DaveM121 879.6K Reputation points Independent Advisor
    2023-09-01T08:23:30+00:00

    Hi, I am Dave, I will help you with this.

    Your minidump files just indicate memory (RAM) corruption no specific driver is listed

    1

    Go to the support page for your Motherboard on the manufacturers website, then from there, download and install the version of Chipset drivers they recommend and while there, check for any BIOS update that may need to be installed, your BIOS date is 2019.

    2

    Wait to see if your system stabilizes, if not, the best option is to download the widely available free utility MemTest86, then run a full 4 pass scan with that to test your RAM for physical errors

    Was this answer helpful?

    0 comments