Тип ошибки cache hierarchy error ид apic процессора 0

1

03.03.2022, 21:48. Показов 11548. Ответов 14

0

I’m just going to share this here since anyone else reading this using the same apps may be able to verify.

Full specs:
Ryzen 5 3600 4.2ghz All core undervolt 1.125v
DDR4 3600mhz 2x8gb ~C16,, HCImemtest 200% stable.
Gigabyte RX 6700 XT Slight undervolt, all big titles stable(Days gone, warzone, tarkov etc.).
Rebar enabled according to GPU-Z.
Agesa 1.1.0.0, updated to 1.2.0.2 mid-may in an attempt to fix the Hierarchy Error, seems the Agesa is innocent.
Radeon Driver 21.5.2(this is also suspect as I jumped on 21.5.1 as soon as it released).

I started getting frequent Cache Heirarchy reboots at the start of May, roughly the same time I started using HWinfo(launch at startup) along side MSI afterburner with a undervolted Ryzen 5 3600, now this CPU is ROCK stable in everything I throw at it including long idle periods(I was concerned about the Vcore being too low at first) but now I suspect it may be an issue with Resizable Bar & GPU behaviour + Compute mode COMBINED with CPU trying to ‘park’ and getting polled for temps too frequently which would obviously be aggravated by multiple sensor programs but Im honestly unsure how the CPU+GPU communicate and if things like Compute mode and Rebar make much difference at all, only a AMD Tech would be able to answer it properly.

So the long story is, I was doing on & off mining, 24hr stable for MONTHS until I started benchmarking games again and set HWinfo to ‘launch at startup’ to integrate with Afterburner OSD. This is when the Heirarchy crashes began(early May). At first I suspected my undervolt immediately as it’s 4.2ghz all core @ 1.125v,, but bumping up to 1.2v made no difference. I did not suspect HWinfo involvement at first, but over 3 weeks of very random and intermittent Heirarchy crashes(mostly at idle) I stumbled across a thread linking it to HWinfo(and other users confirming), so I disabled HWinfo launch at startup from that point, and stopped using all programs except MSI afterburner. 

No Heirarchy crashes until 13 days later, when I ran nicehash for all of 5 minutes but changed my mind and shut the PC down. The next day I was greeted with a Heirarchy crash when loading Cyberpunk shortly after boot. And THIS gave me a hint that a combination of not specifically sensor programs, but Mining software enabling ‘GPU compute’ mode was persisting after reboot and contributing to the Heirarchy crash, after a crash the GPU drivers reset which is why the issue seemed so intermittent. After the crash I loaded up Cyberpunk and tested for hours no problems.

So the TLDR is, Monitoring programs and any Mining software that may be enabling Compute mode are key factors in ‘triggering’ the Heirarchy issue, and it may be GPU related. I went from about 10 crashes between the first 2 weeks of May, to only one crash after removing HWinfo from my startup programs and avoiding ‘compute mode’ set by Nicehash. Its frustrating because while Compute mode can be manually enabled via mining software, its not as simple to disable since the switch back to graphics mode was removed from Radeon software.

The main reason for sharing this info is anyone with ‘similarities’ might have a clue were to start troubleshooting.

Modern CPUs are quite the powerhouses when it comes to computational power. That very power results in faster performance whether you’re playing your favourite games or just browsing the internet. However, with processors being more complicated, there are also more points of failure. If you’ve ever faced a CPU-related issue before, you know diagnosing CPUs isn’t easy either. 

In this article, we’re talking about the cache hierarchy error, its reasons and what you can do to fix the problem.

What causes the cache hierarchy error?

Regardless of whether your CPU is from Intel or AMD, you can run into this problem. Some common causes include:

• CPU overheating due to improper thermals or overclocking
• CPU isn’t getting enough power
• Corrupt or outdated drivers

Also read: How to fix the Winrar Checksum error?

How to fix cache hierarchy errors?

Here are five fixes you can try out.

Update your PC 

The first thing you should do is to update your PC. Updating your PC will, in most cases, update your drivers and fix any issues in the process.

Check out this detailed guide to know how to update your PC here

Check your CPU thermals

The leading cause of this issue is your CPU overheating. Regardless of whether you have an inefficient thermal system or your CPU is overclocked and running at higher temps, sustained performance at higher CPU temperatures isn’t possible and generally leads to a crash. 

Check out our detailed guide on how to fix CPU over-temperature errors here

Remove all new software

If you’ve installed any new programs recently, try removing them to see if that solves your problem. Once again, if you’re removing multiple programs, remove them one at a time and reboot your PC each time to isolate the program at fault. 

Also read: How to fix Make error 127? 

Update your CPU drivers

Updating your Realtek drivers can also often fix the issue.

Step 1: Press the Windows Key + X and click on Device Manager.

Step 2: Scroll down to find Processors. Double-click to see all available devices.

Step 3: Find your processor in there. Right-click it to open the context menu. Note that if you’re experiencing issues with some other device, locate that in the Device Manager. 

Step 4: Click on Uninstall device. This will remove the device and its drivers from your machine. 

Roll back your drivers

Alternatively, you can also opt to roll back to a previous version of the driver that was working fine for you. Here’s how.

Step 1: Press Windows key + R, type in devmgmt.msc and hit enter.

Step 2: Double-click your device to open its properties. 

Step 3: Under the Drivers tab, click Roll Back Driver. If the option is greyed out for you, the driver can’t be reverted to an older version or is already on the oldest version.

Restart your computer and try using it with the older driver. It should work fine for you now.

Also read: Minecraft launcher stuck downloading update files: Quick Fix