Frequent WHEA errors occurring with CPU L0 cache
Frequent WHEA errors occurring with CPU L0 cache
I assume no overclocking and no voltage adjustments were made. This could indicate a gradual issue. If correct, the problem typically appears every 15-20 minutes, making it easier to diagnose. Consider reducing the CPU multiplier slightly. Raising the voltage might help maintain performance, but it risks worsening the situation, so stick with the previous approach. The temperatures you experience are likely contributing to instability. If you've been running at high temperatures above 90°C consistently, that accelerates degradation. Also, identifying which CPU core is affected could allow for more targeted tuning.
The system operates without voltage fluctuations and overclocking is not applied. Errors appear periodically, roughly every few minutes. There are typically 10 to 30 issues, all marked as error code 2. These events occur during idle and while playing games. Temperatures in idle match the display shown in hwinfo. It seems I've never reached temperatures close to 90 degrees compared to benchmarks like Prime or Cinebench. I'm using a Noctua NH-D15 cooler. How can I determine which CPU core is affected?
When interpreting the data, I notice these important points. Decoding these logs isn't always straightforward, so I usually rely on specialized tools for community-driven log analysis. The entries highlight a memory-related concern. A flag indicating persistence of a page frame number suggests a hardware memory issue, possibly from RAM faults. It seems the system is trying to handle the problem by marking affected addresses as unusable. This kind of behavior often points to ECC RAM problems or physical damage. The mention of DDR5 and ECC hints at advanced features, but without proper documentation it's hard to confirm. If you're experiencing this, consider checking your overclocking settings or undervolting configurations—removing them might resolve the issue.
I don’t increase or lower voltages, everything runs normally at standard speeds. I also tested the DDR5 RAM on my girlfriend’s PC, but Windows still shows errors right after startup. My plan is to switch to an AMD system since Intel feels risky with the 13th/14th generation models, and I don’t want to spend weeks trying to fix something I can’t understand. I’ve ordered a 7D7800X3D, an ASUS TUF Gaming B850 Plus with Wi-Fi board, and will try them next week to see if the errors persist. If they do, I’m unsure what to do next.
Checking her PC's processor is a good idea. If it's a 12th, 13th, 14th generation model, you might be able to test her CPU in your own system to diagnose issues. Unfortunately, the i5 13600K is one of the affected models, though it's less common than i7 or i9. All i3 and non-K i5 from Raptor Lake are safe. (I have an i5 13400 that works just fine.) Once your new AMD build is running smoothly, consider using the extended warranty and sending the CPU back to Intel for replacement. You could even try reselling it if you don't plan to use it much.
She's using a 12700k for about four years now. I might give it another shot too. I could look into getting an i5 13600 non-K if those seem okay. Probably won't make much of a difference. I'm hoping switching from Intel to AMD for the motherboard and processor would suit me better. Her AMD GPU seems to work well in her setup, though mine often have problems. All my builds for others are fine, but mine tend to run into issues.
Warranty extended for models released on the 13th and 14th generation, keeping all 13th gen CPUs covered. Valid for five years from purchase, with the product debuting in October 2022—meaning even if bought at launch, you’re protected until October 2027. Keep in mind this doesn’t cover prebuilts, which receive a discount from Intel but have reduced warranty terms (typically one year on parts in the US).