Frequent shutdowns at high speed - 5600x in 95°C with 40% efficiency
Frequent shutdowns at high speed - 5600x in 95°C with 40% efficiency
5600x paired with an AMD stock cooler, it's a used build. Paste seems quite probable. If the owner purchased it a year ago, it might have lasted longer. The paste applied beforehand on the stock coolers isn't great. I suggest starting with a fresh application—it covers all the issues, including the BSODs. Overheating and thermal throttling can lead to this kind of failure. Plus, the temperatures the owner shared clearly show overheating.
WHEA refers to a CPU or PCIe hardware problem. The most frequent cause now involves NVMe storage. If the issue lies with the NVMe and it's storing the page file, it can't save dump files because the drive becomes inaccessible during the crash. Visit C:\Windows\Minidump to see if any minidump files exist. If present, return to the Windows directory and move the Minidump folder to the Downloads folder (use your desktop if needed). Compress the moved folder and attach it to a post. Please adhere strictly to instructions, as Windows doesn't allow changes in this area. If no dump files are found, NVMe is likely the culprit, but further steps can help confirm.
All of these are showing an error with the CPU. It's alternating between an error when fetching and instruction from the L1 cache and and error when reading data from the L1 cache. If anything is overclocked or undervolted, remove it. Updating the BIOS is worth a shot. You have Q-Flash Plus so if it crashes during the update and corrupts the BIOS you should be able to recover from that by following those instructions for flashing a BIOS. Also check the temps in case the CPU is overheating. Fifth gen Ryzen does have an issue with WHEA crashes that are fixed by a tiny overvolt to the SOC. With those crashes though, it's usually only the data read errors you see, not the instruction fetch ones. So it's unlikely to be that, but it's worth a shot. The overvolt required is tiny like I said. We've only had to do a +0.050v (50mV, Millivolt) to resolve issues. So you can try that if you want to if none of the other things fixes it. And of course, a faulty CPU is the main suspect if none of the other things fixes it.