WHEA Logger Event ID 18

[Shou Miko]

I have read a little on the WHEA Logger Event ID 18 and Matt_AMD on the AMD Community answered this thread about the same issue: https://community.amd.com/t5/processors/whea-logger-event-id-18/m-p/494858/highlight/true#M44250

Checking the ts-tips side on WHEA you can check the following:

Link: https://www.amd.com/en/support/kb/faq/ts-tips

If this doesn't help then try to get in touch with AMD and MSI about their issue of that AMD writes doesn't help you out.

 

[Chrispy_]

Cache Hierarchy type WHEA is strictly CPU core related. If it was Fabric/memory controller, it would be Bus/Interconnect type (WHEA 19 I think).

Either:

• the board you have doesn't like your CPU and isn't giving it enough idle or load Vcore,
• the BIOS you're currently on doesn't like your CPU and isn't it giving it enough Vcore,
• or your CPU is bad and needs to be RMA'd

Have not yet heard of bent pins causing Cache Hierarchy, but you never know. CPU being bad is rare, but WHEA 18 used to happen quite a bit for earlier production Ryzen 5000 (late 2020 or very early 2021).

In the meantime, you can try some different BIOSes, or up the Vcore a bit by using a slight positive Vcore offset (don't exactly remember how the MSI BIOS setting is laid out), or using positive Curve Optimizer offset on the affected APIC ID cores (looks like it's all over the place so maybe just apply to all cores).

Otherwise, you can try turning Power Supply Idle Current to Typical as mentioned. More drastic measure would be to disable C-states entirely (Global Cstates setting, not DF Cstates).

If all fails, it's time to hit up AMD RMA. They will try to make you jump through troubleshooting hoops, just document what you've already done and be persistent that troubleshooting is useless.

Yup, this is what I've been saying from the beginning. Posts #2, #5, #10.

It doesn't hurt to update motherboard firmware and run the IMC as slow as possible (JEDEC speeds), but cache hierarchy is CPU cores. As I said, I've built several hundred and dealt with bad RAM dozens of times, this isn't a bad RAM error that I've ever seen.

There's a lot of "try this, try that" in this thread but the error message is pinpoint accurate, not a vague "oh it could be anything" error. It's an error that only ever comes up when there's a CPU core fault, and typically it's an RMA job if it's not a firmware bug undervolting the CPU incorrectly via bad LLC or auto-PBO etc.

 

[strikemaker]

Small update:

Since swapping my Corsair RAM to Crucial RAM the BSOD disappeared. But now i'm back to 2x 8GB unfortunatly.

Any recommendations?

I could but 2 more of the exact same RAM or I could upgrade to 2x 16GB.

Read online that a G.Skill RAM 2x 16GB could work with my Ryzen7 5800x. Any suggestions?


My errors since the RAM swap.

 

[ricardom07]

I was using a Ryzen 7 2700x with 6600 XT with no problems at all, i've purchased a 5600 to upgrade the processor, my motherboard should be fine to support the 5600 since the TDP is lower than the 2700x. Since i've installed the processor, i was looking to test the COD Warzone and the PC insta reboots, i've looked at the Windows event log and the WHEA LOGGER 18 showed up...

I think since my 2700x was good for about 2 years and then i upgraded to 5600, the 5600 is the problem here, should i RMA the chip?

 

[thegnome]

Does it happen often running idle? I've only seen similar errors on undervolted Zen 3 chips, where they run very well in any load, but shut down in any (near) idle state, atleast once a day.

Oh and also, 99% of those errors in event viewer are nothing to worry about, every system I've had has enough of those errors without any noticeable problems whatsoever.

 

[eidairaman1]

Small update:

Since swapping my Corsair RAM to Crucial RAM the BSOD disappeared. But now i'm back to 2x 8GB unfortunatly.

Any recommendations?

I could but 2 more of the exact same RAM or I could upgrade to 2x 16GB.

Read online that a G.Skill RAM 2x 16GB could work with my Ryzen7 5800x. Any suggestions?


My errors since the RAM swap.
View attachment 256642

Crucial Ballistix Gaming 3600 32GB (2x16) works just fine on the 5800 oem in a b550 steel legend board.

Corsair strikes again, smh

 

[Chrispy_]

Crucial Ballistix Gaming 3600 32GB (2x16) works just fine on the 5800 oem in a b550 steel legend board.

Corsair strikes again, smh

Don't be too quick to judge the RAM; Could easily still be an IMC fault with the CPU in memory capacities >16GB.

I've had both Intel and AMD CPUs where a whole channel of the IMC failed, presumably memory registers can be faulty too.