Dreaded Kernel-Power 41

Swi1ch

Swi1ch

Swi1ch

Associate
Joined
19 Nov 2008
Posts
1,579
Specs:

5900x
MSI x570 Tomahawk
32GB TG8P Edition
Nvidia 3080TI
Corsair RMx1000

Issue:

Initially freezing completely at random (no response at all to any input), while machine was idle. Had to kill power and reboot. Happened maybe 4 times over a week.

Since then randomly cutting to black and restarting, once or twice every couple days. So far only when idle or light usage (Played plenty of BF2042 without issue). Started after I had it unplugged for a week as I was away.

Only thing in the event log is the Kernel-Power 41. Machine is just over a year old and have had no issues at all in that time. Tried the usual gumpf - setting power plan, making sure the drives don't sleep ever etc to no effect. Windows and graphics drivers are up to date. BIOS was up to date although if there's been a new one in the last year I've not updated to it - kinda scared to too with power issues.

I've got a replacement PSU on the way out just in case, but before I break the seal on that and my ability to return it, is there anything else I could try to try and diagnose? I don't even know where to start - literally only thing I can say is the PSU looks a touch dusty and might need a clean.
 
mickyflinn said:
I would test the memory with memtest just in case.
Click to expand...
Will do, it just now completely froze up with no warning as I was sitting here watching TV. The machine was still actually on and the fans running etc, just completely unresponsive to input. Would seem to suggest it's not (purely) a PSU issue.
 
Quartz said:
The latest Windows Update is known to call BSODs.

https://www.theregister.com/2022/12/20/microsoft_windows_10_crash/
Click to expand...
Oh man I guess this is a good thing - that was the day I got back from my trip and updated everything so hopefully that's all it is. If so you're a lifesaver pal.

At least I hope this is right? Looks like that is causing systems to boot directly into BSOD, and the workarounds are just to get a machine to boot rather than stay on.

Reckon it's worth me just formatting and reinstalling windows?
 
Last edited:
Quartz said:
No. The fix is given in the article: boot to a command prompt and copy over one file.
Click to expand...
Unfortunately this hasn't worked. I tried it exactly as given in the article/microsoft page at first, then a tweaked version as there appears to be a duplicated slash. Reading more into it I'm not sure this is related as everyone else suffering from the BSODs caused by the update are getting them on boot up, hence the need to use the recovery console.

I've also set windows to not automatically restart on crash to try and force a BSOD instead of a reboot, but it just resets.
 
this sounds very familiar, i think i did a fresh windows install and started all over again. That is my fix for everything lol.
 
My 5800X did similar when I got it. Try LLC (load-line calibration) in the UEFI settings. Mode 1 sorted the problem straight out for me. (On both CPU and SOC settings).
BSODs at idle often mean the voltage drops a little too low- I think it's particular to individual chips.

May also be worth setting DRAM voltage at 1.37v or so rather than the 1.35v XMP/DOCP default.
 
Last edited:
DoneADougalOnSofa said:
My 5800X did similar when I got it. Try LLC (load-line calibration) in the UEFI settings. Mode 1 sorted the problem straight out for me. (On both CPU and SOC settings).
BSODs at idle often mean the voltage drops a little too low- I think it's particular to individual chips.

May also be worth setting DRAM voltage at 1.37v or so rather than the 1.35v XMP/DOCP default.
Click to expand...
This machine has run for a year with no issues so seems a bit odd that I would be having a voltage issue now? If a reformat doesn't help i'll give it a go.

I've still not seen an actual BSOD - either the machine hard-resets, or freezes up completely.
 
I'm suddenly getting something in the event log:

WHEA-Logger
A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Cache Hierarchy Error
Processor APIC ID: 3
 
DoneADougalOnSofa said:
My 5800X did similar when I got it. Try LLC (load-line calibration) in the UEFI settings. Mode 1 sorted the problem straight out for me. (On both CPU and SOC settings).
BSODs at idle often mean the voltage drops a little too low- I think it's particular to individual chips.

May also be worth setting DRAM voltage at 1.37v or so rather than the 1.35v XMP/DOCP default.
Click to expand...
Had a look into this as I'm still having issues.

My board apparently doesn't have an option for LLC.

My DRAM voltage is already at 1.37 - I never changed this myself.
 
Swi1ch said:
My board apparently doesn't have an option for LLC.
Click to expand...
It will have a better look, you tried running with xmp disabled, test both ram sticks individually, whats your soc voltage? the processor still under warranty? test the basics if you cant find anything pester someone for a replacement.
 
Dg834man said:
It will have a better look, you tried running with xmp disabled, test both ram sticks individually, whats your soc voltage? the processor still under warranty? test the basics if you cant find anything pester someone for a replacement.
Click to expand...
If I run with XMP disabled then my RAM gets shunted down to 2400mhz - I can test this if it matters? Both this machine and the previous one (no common components) ran like dirt without XMP enabled.
Same exact issues with XMP disabled.

I've not tested each stick individually but I ran memtest for 8 passes/12 hours with no issues - obviously not conclusive but should probably point in the direction of something else.

I cannot find my SOC voltage - google suggests that on AMD boards this could be called 'NB Voltage' but I still cannot find any reference in my BIOS.
SOC Voltage hovers around 1.1v.

Who and what am I chasing for a replacement? I think RAM and PSU are probably OK so I'm leaning motherboard or CPU? Having finally got something in my event viewer with WHEA errors seems to suggest that the CPU might be at fault?

Edit. Did some googling on the WHEA error and apparently updating BIOS is a thing that should happen - I've flashed to the latest BIOS and no change.
 
Last edited:
Probably PSU…

I thought I could get away with running an undervolted 5800X and an undervolted 3080 FE with a Seasonic 650W SFX PSU. But I would get random hard freezes, sudden restarts, etc.

A Silverstone 1000W SFX PSU solved my problems.
 
Major774 said:
Probably PSU…

I thought I could get away with running an undervolted 5800X and an undervolted 3080 FE with a Seasonic 650W SFX PSU. But I would get random hard freezes, sudden restarts, etc.

A Silverstone 1000W SFX PSU solved my problems.
Click to expand...
I'm currently running a RM1000x, so I guess that could be on it's way out.

That said I've started having BSODs - volmgr.sys failures - which I don't think is PSU related.

I posted my minidump on the microsoft forum and someone went through it and said that the volume manager driver was throwing issues and they've had me run the system file checker. I was on a fresh format so I didn't think it would do anything, yet the scan did find errors and apparently fixed them, so I'll see how that goes.
 
Same mobo and cpu here.. had this a while back and was driving me insane m.. tried all the hardware testing that I could, turns out a fresh windows installed sorted my issue.
 
labbby said:
Same mobo and cpu here.. had this a while back and was driving me insane m.. tried all the hardware testing that I could, turns out a fresh windows installed sorted my issue.
Click to expand...
Completely wiped and formatted with no improvement.

I'm currently trying Windows 11 to rule out the recent Windows 10 update issues.

Edit. Windows 11 no luck either
 
Last edited:
I would strip everything to the bare minimum, fresh install of Windows. Update the bios, restore motherboard defaults after bios update and see from there.

Still no joy, I would look at the motherboard.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom