Question Crash issue with "critical Kernel-Power 41 (63)" error

Jan 4, 2025
11
0
10
I recently upgraded my PC with a new motherboard, RAM, power supply, and CPU Now, it crashes randomly while playing games, and when I look at the event viewer, I see several errors and critical messages. The key one that jumped out, and the most recent was the "critical Kernel-Power 41 (63)." I have a dump to share.

Google Drive dump

my new specs are:
OS: Win 10 64-bit
CPU: AMD Ryzen 7 7800X3D
RAM: 32.0GB Dual-Channel TEAMGROUP DDR5-5200 @ 3199MHz (32-39-39-84)
Motherboard: Micro-Star International Co., Ltd. MAG X670E TOMAHAWK WIFI (MS-7E12) (AM5)
Graphics card: NVIDIA GeForce RTX 2070 SUPER (Gigabyte)
CPU cooler: Cooler Master MasterLiquid ML240L ARGB V2 62 CFM Liquid CPU Cooler
Power Supply: be quiet! Dark Power 13 1000 W 80+ Titanium Certified Fully Modular ATX Power Supply
 
Last edited:
With this parts change, did you do a full OS wipe and reinstall?

The 41 error you see is not the 'problem'. It is merely the system telling you "I shut down unexpectedly. I do not know why. Human...please fix me."
no, I have not. I have the OS on its own m.2, do I need to just reset the OS or reinstall as I do not want to loose my windows key
 
I recently upgraded my PC with a new motherboard, RAM, power supply, and CPU Now, it crashes randomly while playing games, and when I look at the event viewer, I see several errors and critical messages. The key one that jumped out, and the most recent was the "critical Kernel-Power 41 (63)." I have a dump to share.

Google Drive dump

my new specs are:
OS: Win 10 64-bit
CPU: AMD Ryzen 7 7800X3D
RAM: 32.0GB Dual-Channel TEAMGROUP DDR5-5200 @ 3199MHz (32-39-39-84)
Motherboard: Micro-Star International Co., Ltd. MAG X670E TOMAHAWK WIFI (MS-7E12) (AM5)
Graphics card: NVIDIA GeForce RTX 2070 SUPER (Gigabyte)

what is the psu and what is your cpu cooler.
 
Remove any and all overclocks - including XMP / EXPO / DOCP and report back.
I restored my bios to recommended defaults, so let's see.
With this parts change, did you do a full OS wipe and reinstall?

The 41 error you see is not the 'problem'. It is merely the system telling you "I shut down unexpectedly. I do not know why. Human...please fix me."
I windows reset the drive with my OS and re-download windows, So let's see.
 
We need to rule out faulty RAM.

Run the Windows Memory Diagnostic application (initiated from within Windows), and when the PC reboots into the application, tap F1 (options) and select the extended test.

Does it complete successfully?
 
We need to rule out faulty RAM.

Run the Windows Memory Diagnostic application (initiated from within Windows), and when the PC reboots into the application, tap F1 (options) and select the extended test.

Does it complete successfully?
no errors after a memory diag that was run at extended.
did a Chkdisk as well no errors

also DDUed all my video drivers and reinstalled with NVclean

will report back if i have more BSOD
 
I have done a windows restart and reinstall through the recovery menu
It seems like you have done most of the tried and tested things, unfortunately. It might be worth reinstalling windows from the MS website using a USB stick. that way you know for sure that all the crud will be wiped off the boot drive.

You can then download the latest drivers from the manufacturer's websites or pull them from Windows updates from the optional updates setting.

The next step is a real P.I.T.A. and would involve swapping out components to find which one(s are faulty).
 

Surprise unknown device its not any USB devices could it be a video card i Re downloaded NVIDIA drivers and checked MSI for a amd chip set up date( there was one but no change after update). also heard about

still getting plenty of errors for metadata
Error 1/21/2025 7:30:47 AM DeviceSetupManager 131 None
Metadata staging failed, result=0x80070490 for container '{CA0E9E80-3E97-FCAC-730A-8CB080FA2581}'
 
Surprise unknown device its not any USB devices could it be a video card i Re downloaded NVIDIA drivers and checked MSI for a amd chip set up date( there was one but no change after update).
Go into device manager and right click on that device. Go to properties, then details, then search for hardware IDs. Copy and paste the topmost value into Google search and see what it returns.
 
  • Like
Reactions: Tailgater
Critical 1/21/2025 5:59:09 PM Kernel-Power 41 (63)
Error 1/21/2025 5:59:09 PM volmgr 161 None
Error 1/21/2025 5:59:16 PM EventLog 6008 None
Warning 1/21/2025 5:38:01 PM CertificateServicesClient-AutoEnrollment 64 None
Error 1/21/2025 5:38:01 PM DHCPv6-Client 1000 Address Configuration State Event
Error 1/21/2025 5:38:00 PM Kernel-EventTracing 2 Session
Warning 1/21/2025 9:41:04 AM DistributedCOM 10016 None
Warning 1/21/2025 9:40:51 AM DistributedCOM 10016 None
Error 1/21/2025 9:30:37 AM Kernel-EventTracing 3 Session
Warning 1/21/2025 9:30:37 AM Kernel-EventTracing 4 Logging
Warning 1/21/2025 9:28:44 AM DistributedCOM 10016 None
Warning 1/21/2025 9:28:41 AM DistributedCOM 10016 None
Warning 1/21/2025 9:28:23 AM User Device Registration 360 None
Warning 1/21/2025 9:28:22 AM DistributedCOM 10016 None
 
If a device driver is installed, it might mean a loss of functionality, but it should not result in BSODs.

At this point I think I would open up the case, clear off the dust, and remove / reseat all the components except the CPU - while referring to the motherboard manual. I'd take out the CMOS battery for a couple of minutes, too.

I would then be inclined to treat it as a virgin system, reinstall W11 from the USB installer, grab the GFX, mobo, and wifi drivers from their respective manufacturers, and pull any outstanding drivers from windows optional updates.

If that does not work, then I would suspect a hardware fault and, if possible, start swapping out components to find out which one is giving me grief.
 
Critical 1/21/2025 5:59:09 PM Kernel-Power 41 (63)
Error 1/21/2025 5:59:09 PM volmgr 161 None
I usually don't see that error unless there is something wrong with the PCIe power connector that is connected to the video card. Which a burnt pin can do that error. The connector usually gets warm too when its that issue.

The Kernel PNP error is usually a usb driver issue and Kernel-Power 41 is a power supply issue that I normally see a bad connector on the pcie video power.
 
Last edited: