• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

WHEA LOGGER 18(Cache Hierarchy Error) KERNEL POWER 41. READ DESCRIPTION please help

K

kaladbolg

New Member
Joined
Jan 28, 2025
Messages
9 (0.08/day)
Hello all, i builded this rig two months ago and i just keep having these crashes while gaming.

Components:

Ryzen 5 5600
6700XT gigabyte OC
Asrock b550m steel legend
Ram kingston fury beast 16gb 3600mhz 18cl x2


Straight black screen with no BSOD and reboot, on event viewer it appears

WHEA LOGGER 18 A fatal hardware error has occurred.
Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Cache Hierarchy Error
Processor APIC ID: (no specific number here, it varies from multiple ones)


This is the XML view:
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{c26c4f3c-3f66-4e99-8f8a-39405cfed220}" />
<EventID>18</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2025-01-27T21:29:25.3186145Z" />
<EventRecordID>35596</EventRecordID>
<Correlation ActivityID="{6c2b4ed7-3573-437e-aeb8-7a972aace96f}" />
<Execution ProcessID="3992" ThreadID="4992" />
<Channel>System</Channel>
<Computer>user</Computer>
</System>
- <EventData>
<Data Name="ErrorSource">3</Data>
<Data Name="ApicId">5</Data>
<Data Name="MCABank">5</Data>
<Data Name="MciStat">0xbea0000000000108</Data>
<Data Name="MciAddr">0x7ff6c649f1f4</Data>
<Data Name="MciMisc">0xd0130fff00000000</Data>
<Data Name="ErrorType">9</Data>
<Data Name="TransactionType">2</Data>
<Data Name="Participation">256</Data>
<Data Name="RequestType">0</Data>
<Data Name="MemorIO">256</Data>
<Data Name="MemHierarchyLvl">0</Data>
<Data Name="Timeout">256</Data>
<Data Name="OperationType">256</Data>
<Data Name="Channel">256</Data>
<Data Name="Length">2063</Data>
<Data Name="RawData">435045521002FFFFFFFF040001000000020000000F080000141D15001B0119140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BB59A456850271DB01020000000000000000000000000000000000000000000000A0010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000001000000000000000000000000000000000000000000000060020000E00000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000001000000000000000000000000000000000000000000000040030000A80400000003000000000000011D1E8AF94257459C33565E5CC3F7E800000000000000000000000000000000010000000000000000000000000000000000000000000000E8070000270000000003000000000000A13248C3C302524CA9F19F1D5D7723FC000000000000000000000000000000000300000000000000000000000000000000000000000000007F010000000000000002010000000000120FA2000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000500000000000000000000000000000000000000000000000000000000000000000000000000000007010000000000000500000000000000120FA20000080C050B32F87EFFFB8B170000000000000000000000000000000000000000000000000000000000000000F50157A5EFE3DE43AC72249B573FAD2C03000000000000009F00020600000000F4F149C6F67F00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001000800800100000000000000000000000000000000000000000000000000000400000002000000CA74CB860271DB01050000000000000000000000000000000000000005000000080100000000A0BEF4F149C6F67F000000000000FF0F13D00A0000000500000000000000B00005000000004D00000000F9010000030000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000010000000000000000000000FF00000000000000000000000000000000000000000000000000</Data>
</EventData>
</Event>

it also shows alongside KERNEL POWER 41 with this view
- <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-01-27T21:29:20.7033818Z" />
<EventRecordID>35540</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>user</Computer>
</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">0</Data>
<Data Name="ConnectedStandbyInProgress">false</Data>
<Data Name="SystemSleepTransitionsToOn">0</Data>
<Data Name="CsEntryScenarioInstanceId">4</Data>
<Data Name="BugcheckInfoFromEFI">false</Data>
<Data Name="CheckpointStatus">0</Data>
<Data Name="CsEntryScenarioInstanceIdV2">4</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>

this has been happening non stop for the past two months since i bought this pc. I have tries the following benchmark test with NO errors in any of them

Furmark 2
3dmark
Superposition
OCCT (literally all of them multiple times, i only have free version so they were 1 hour test as its the limit)
Prime95(Small fft, left it on up to 3 hours)
Cinebench
Memtest86(full cycle with xmp 3600 activated, took 4 hours)

I dont know what else to do, i cant reproduce this error other than gaming. Even while gaming it can go for multiple days without crashing, until it does. Its does not happen while idle.

So far what i tried is the following:

-Disabled XMP profile
-Set RAM voltage to 1.38
-Set power suply idle to Typical
-Set Cpu voltage up to 1.28
-Disable all OC in every single component (PBO, CPB, everything related to gpu)
-Sent GPU to warranty where it showed no issues
-Connected PC straight into the wall socket
-Plug RAMS out and visually checked them, saw nothing wrong and cleaned the sockets with a brush.

I do have smart access memory activated but these crashes have been happening even before that. I do NOT have any temp issues, never, all my component run fairly cold( CPU max temp of 77º, GPU never goes beyond 70º).

Please help

EDIT:
I have already updated bios to 3.40 which is the lastest of my mb.

My psu is Gigabyte P650B. I bought it brand new along with the other components two months ago.

I do not have other components to test for errors and i do not have anyone to ask that kind of thing sadly.
 
Last edited:
Update your motherboard bios first, if no change try a different cpu.

If i were you id use a different system to get the bios update and set it up on a drive on that other system so you can do the flash within uefi or mobo makers flash procedure
 
Last edited:
Do as @eidairaman1 says and get bios up to date.

Then reset bios to default and leave it there for your testing. Tweaking things at random doesn't help the diagnostic process.

What about your power supply? Need to check it out.
 
Yes i already updated bios, forgot to put than ill edit it now.

I do not have another cpu or psu sadly. I also dont have anyone to ask that kind of thing. Going around sending every component to warranty is costly and takes a lot of time, i want to be sure i take the right component.

Also, i have only messed with voltages very recently in an attempt to fix these crashes. I have been having the errors since way before i messed with any of this.
 
kaladbolg said:
My psu is Gigabyte P650B. I bought it brand new along with the other components two months ago.

I do not have other components to test for errors and i do not have anyone to ask that kind of thing sadly.
Click to expand...
What were you using for a computer before this build? Is that computer still around? Perhaps you could temporarily swap in the PSU from that system?

I recommend you take everything out of the case and assemble the system on a clean, unfinished bread/cutting board and see what happens there. While everything is out, triple check you only have inserted in the case a standoff where there is a corresponding motherboard mounting hole.
 
Bill_Bright said:
What were you using for a computer before this build? Is that computer still around? Perhaps you could temporarily swap in the PSU from that system?

I recommend you take everything out of the case and assemble the system on a clean, unfinished bread/cutting board and see what happens there. While everything is out, triple check you only have inserted in the case a standoff where there is a corresponding motherboard mounting hole.
Click to expand...
My previous pc was VERY old and the only other psu i have is a generic 500w, which is not enought to safely power my current one as i understand.

I build the complete pc on the case myself, bought every component in different stores as it was cheaper. I assure you i put all the standoffs nedeed and put every screw in the motherboard
 
  • P650B
  • Type : Intel Form Factor ATX 12V v2.31

    Your PSU doesn't handle the power spike of the GPU because it is an old model. Try an ATX 3.0 or 3.1 with 650W~750W




 
It RMA the CPU with AMD or it gets the hose again.
 
Was the heat on when Windows rebooted itself suddenly?
 
kaladbolg said:
what do you mean heat on exactly? i never had any temp issues as i stated in post description
Click to expand...
Heat on in your room. I seemed to have issues like this, just because my room was warm, especially my MSI B450 Tomahawk (now defunct, since later on in August, 2022) and Ryzen 7 3700X. Even though the same Ryzen chip seems to work OK, it's in an ASRock A320M /ac motherboard now, because of the motherboard being bad.

I started wondering if there's some chip batches that literally become unstable at >55C.
 
RJARRRPCGP said:
Heat on in your room. I seemed to have issues like this, just because my room was warm, especially my MSI B450 Tomahawk (now defunct, since later on in August, 2022) and Ryzen 7 3700X. Even though the same Ryzen chip seems to work OK, it's in an ASRock A320M /ac motherboard now, because of the motherboard being bad.

I started wondering if there's some chip batches that literally become unstable at >55C.
Click to expand...
ahh nono, no chance. Its summer here and i have my AC literally over my pc desk aiming straight at it, no way its that

i have never heard of chips unstable at 55º, that weird as hell
 
Can give multiple examples of the fix.
Here's one example.

Re: 5600x / WHEA Logger 18 Cache Hierarchy Error / Kernel Power error 41

Well, for anyone having this issue, I just RMA the Ryzen and the Motherboard, so... Or the processor was faulty, or the mobo version or the mobo itself was faulty. Not very much help, but it is something.
community.amd.com community.amd.com

RMA the cpu is the solution of choices since it became prominent since Zen 2.

GLHF out there young bucks!!
 
I saw a reddit thread of this same issue recently with a bunch of 5600x and 5800x users and most of them solved it with updating their bios and AMD chipset drivers. Running theory was that Windows update messed up something in the older chipset driver and/or BIOS and updates sorted it out. I see you updated your BIOS, but did you also check/update the chipset driver?
 
ShrimpBrime said:
Can give multiple examples of the fix.
Here's one example.

Re: 5600x / WHEA Logger 18 Cache Hierarchy Error / Kernel Power error 41

Well, for anyone having this issue, I just RMA the Ryzen and the Motherboard, so... Or the processor was faulty, or the mobo version or the mobo itself was faulty. Not very much help, but it is something.
community.amd.com community.amd.com

RMA the cpu is the solution of choices since it became prominent since Zen 2.

GLHF out there young bucks!!
Click to expand...
Yes i have seen this post. As stated i already did all the tests that user said gave him errors, in my case not a single one of them gave me any so im just clinging to the hope that its fixable in bios
 
Bobaganoosh said:
I saw a reddit thread of this same issue recently with a bunch of 5600x and 5800x users and most of them solved it with updating their bios and AMD chipset drivers. Running theory was that Windows update messed up something in the older chipset driver and/or BIOS and updates sorted it out. I see you updated your BIOS, but did you also check/update the chipset driver?
Click to expand...
i installed the AMD drivers from this page https://www.amd.com/es/support/download/drivers.html

i have amd chipset ver 6.10.17.152 which i believe its the lastest one
 
Seemed more likely to happen with my Ryzen 7 3700X, out of all my Ryzens, which it has a manufacturing time code indicating sometime in 2019. In fact, it was fine shortly before my MSI B450 Tomahawk got a bad component. Those "Cache Hierarchy Error" incidents were more likely to happen in 2020 and 2021 on mine. I did have a baseboard radiator right behind the case at the time, it was before I moved into the current room in November, 2021. (same house)

Bobaganoosh said:
I saw a reddit thread of this same issue recently with a bunch of 5600x and 5800x users and most of them solved it with updating their bios and AMD chipset drivers. Running theory was that Windows update messed up something in the older chipset driver and/or BIOS and updates sorted it out. I see you updated your BIOS, but did you also check/update the chipset driver?
Click to expand...
My 5800X seemed weird, (non-X3D version, A.K.A., the "regular version") Beam NG seemed more likely to crash when spawning vehicles, but I don't know if the CPU core(s) were the cause or not.
But it was suspected of having a dud IMC! I stabilized it by downgrading to a 2x8GB RAM kit. IIRC, it was the same chip where Windows 11 suddenly gave me "MEMORY_MANAGEMENT" BSOD in May, 2023 with the G.Skill TridentZ Neo 2x16 GB C18 3600 kit. But it seems to work fine with my X3D variant on my Asus ROG Strix B550-F Gaming.
Was the ASRock B550 PG Velocita motherboard buggy earlier on? I'm still using that motherboard everyday.
 
Last edited:
kaladbolg said:
Yes i already updated bios, forgot to put than ill edit it now.

I do not have another cpu or psu sadly. I also dont have anyone to ask that kind of thing. Going around sending every component to warranty is costly and takes a lot of time, i want to be sure i take the right component.

Also, i have only messed with voltages very recently in an attempt to fix these crashes. I have been having the errors since way before i messed with any of this.
Click to expand...
Go to a shop for troubleshooting
 
go into your bios and under either AMD CBS or the other one is a toggle for PSU Idle Control. Set this from low/auto to "Typical".
that was "the fix" for idle crashing Zen 3 CPUs when they launched.
 
GerKNG said:
go into your bios and under either AMD CBS or the other one is a toggle for PSU Idle Control. Set this from low/auto to "Typical".
that was "the fix" for idle crashing Zen 3 CPUs when they launched.
Click to expand...
please read my post description man i literally typed everything i tried.
 
kaladbolg said:
please read my post description man i literally typed everything i tried.
Click to expand...
i've read it but i didn't saw it. probably because you didn't wrote the whole name of the feature.
anyways... good luck then.
 
eidairaman1 said:
Go to a shop for troubleshooting
Click to expand...

kaladbolg said:
please read my post description man i literally typed everything i tried.
Click to expand...
Erhmm, Most likely your cpu is faulty but to be 100% sure I advise you to get to a shop for further troubleshooting, it helps you to avoid buying unnecessary hardware and having to wait on returns.
 
kaladbolg said:
Yes i have seen this post. As stated i already did all the tests that user said gave him errors, in my case not a single one of them gave me any so im just clinging to the hope that its fixable in bios
Click to expand...
The repair was to RMA the cpu. That user also RMA'd the board as well.

Helped dozens with this particular whea error.

Fix = RMA.

Doesn't matter anything else.

RMA period.

But sadly I wish you luck. I know it's agrevating, there isn't any other way.
 
ShrimpBrime said:
The repair was to RMA the cpu. That user also RMA'd the board as well.

Helped dozens with this particular whea error.

Fix = RMA.

Doesn't matter anything else.

RMA period.

But sadly I wish you luck. I know it's agrevating, there isn't any other way.
Click to expand...
Wasn't there an issue where this only happened to very-very-early Vermeer batches? (or other WHEA crashes) (pre-'21 batches)
Apparently, multiple people reported the issue. Even my first Vermeer purchase was clear from that period.

So, if later than 20xx, then it's just a fluke, it looks like.

Unlike Raptor Lake, where if crashes start, it's too late and the CPU must be replaced. The BIOS fixes in that case, must be applied before any symptoms. Yes, the Ryzen must be replaced if new symptoms occur, but crashes and/or errors, are not known to be a widespread issue, unlike 13th-gen and 14th-gen Core i.
 
Last edited:
You must log in or register to reply here.
Back
Top