• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Question 5950X Cache hierarchy error

P

pakotlar

Senior member
Got a random reboot when starting windows, event logger says WHEA cache hierarchy ID for APC ID 31. This corresponds to core 15 I believe, which is perf #12/13, so middle of pack. First reboot in about 4 months since enabling CO.

I have PBO enabled with curve optimizer set to -30 on that core. Additionally I had Fclk at 1866mhz and ran overclocked to 3733, 64GB (32 x 2, planning on 128 longer term for ML stuff) that is rated for 3600.

Anything to be concerned about (could CPU be faulty or is this clearly just effect of overclocking)? Is this more likely to be caused by memory, fclck, or CO? Before updating to Agesa 1.2.0.3 patch B I was able to do 1866 fclck no problem (but no curve optimizer).

So far have backed down to 1800 fclck and 3600mhz memory clock, but have left curve optimizer untouched. No reboots, but so sporadic I don’t expect them for many months.
 
Last edited:
I had been getting this error on my 5800x while playing Diablo 2 Resurrected. Would work perfectly fine but crash maybe once every ~10 hours. Was running PBO with a -20 offset. Moved it to -15 and it seemed to help, but still crashed eventually. Now at -12 and no crashes so far.

So it seems, anecdotal, it might have been a voltage issue for me.
 
pakotlar said:
Got a random reboot when starting windows, event logger says WHEA cache hierarchy ID for APC ID 31. This corresponds to core 15 I believe, which is perf #12/13, so middle of pack. First reboot in about 4 months since enabling CO.

I have PBO enabled with curve optimizer set to -30 on that core. Additionally I had Fclk at 1866mhz and ran overclocked to 3733, 64GB (32 x 2, planning on 128 longer term for ML stuff) that is rated for 3600.

Anything to be concerned about (could CPU be faulty or is this clearly just effect of overclocking)? Is this more likely to be caused by memory, fclck, or CO? Before updating to Agesa 1.2.0.3 patch B I was able to do 1866 fclck no problem (but no curve optimizer).

So far have backed down to 1800 fclck and 3600mhz memory clock, but have left curve optimizer untouched. No reboots, but so sporadic I don’t expect them for many months.
Click to expand...

I would lower the -30 on that core.
 
pakotlar said:
So far have backed down to 1800 fclck and 3600mhz memory clock, but have left curve optimizer untouched
Click to expand...
Why don't you loosen the magnitude for that core (which seems most logical to do right away) instead of messing with interchip and memory subsystem?
This is one of those rare cases when system clearly points to an issue.
Most of the time you see something like "kernel power event id 41" and put it however you want.
 
Last edited:
Yeah, I backed off to -25 on that core. No further issues. For safety I backed off tdc and edc as well, don’t need the extra few %
 
Yeah, sounds like CO isn't giving enough voltage. Even a -25 offset sounds very optimistic to me, but it depends on the chip and core, of course. Have you tested your CPU config with core cycler?
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top