• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

cache hierarchy errors with a 2 yeard old 5800x3D

Associate
Joined
11 Dec 2005
Posts
1,035
Location
Brighton
Hi folks,

In the last few weeks after a bios flash and upgrading to a Radeon 7800XT, I have been having loads of problems with W11, many related to security permissions but the worst is many fatal hardware errors because of Cache Hierarchy event ID 18'

The processor didn't give me any problems before so is it possible that it developed a fault after almost 2 years of operation without any problems? It is well cooled with a 240MM Corsair water cooler and the memory is Samsung Bdie also well proven. The motherboard is an Asrock X570 Phantom gaming X around 3 years old years ago so all parts are very good quality and well-used without any issues or troubles until now.

The processor was slightly undervolted before but now it is all default values. it doesn't make any difference running the memory at 2400 or 3600 Mhz (4x8GB).

I have been thinking about reinstalling W11 but I read that very probably is not worth the hassle as it won't fix it.

Any advice? many thanks
 
You could try adding some more voltage to the CPU, the newer BIOS may have different behaviour to the old one.
V-Cache tends to be extra sensitive to voltage and is why they don't clock as high. I'd be very careful about manually tweaking voltage above stock.
Entirely possible the BIOS upgrade is at fault as mentioned. May be worth a roll back.

I have been thinking about reinstalling W11 but I read that very probably is not worth the hassle as it won't fix it.
As far as I know you can still do in place upgrades on Win 11 - that might be less pain than you think.
Option two was the method I'm familiar with on Windows 10. The key part is to get a USB/ISO with the same build, edition, version etc as "winver" mentions.
In that case, you don't lose anything unless you choose the wrong option during the upgrade (see tutorial) and I've used this to great effect when Windows Update has broken itself on client machines, for instance.
 
Last edited:
Back
Top Bottom