OC i5 6600K Results
OC i5 6600K Results
Hello! Your recent overclocking on the i5 6600K was successful, especially since you haven’t changed it for three years. With the MSI Z170A Gaming M3 motherboard, you achieved stable 4.5Ghz at around 1.190v, and temperatures stayed within a healthy range of 58-60°C after an hour in AIDA64. The Dark Rock Pro 4 maintained good performance. This is definitely a solid result—your first overclock in your life!
Your CPU is malfunctioning during that overclock. I wouldn't let it continue like this, as it could end up completely failing eventually.
It's a decent overclock. I'd try it with something other than AIDA64. Load RealBench and perform a 30-minute stress test using half your RAM, observing the temperatures. RealBench also puts pressure on your GPU and PSU. If you're only interested in testing your CPU, run the Prime95 torture test (disabling AVX) for 30 minutes.
I attempted Prime95 but after a short time I encountered these issues:
[Fri Feb 21 15:46:36 2020]
FATAL ERROR: Rounding was 0.4999961336, expected less than 0.4
Hardware failure detected, refer to stress.txt file.
FATAL ERROR: Rounding was 0.4964097877, expected less than 0.4
Hardware failure detected, refer to stress.txt file.
FATAL ERROR: Final result was B49014DB, expected: 87610A79.
Hardware failure detected, refer to stress.txt file.
Self-test 288K passed!
It seems three out of four cores experienced a hardware issue. The first one was still under stress testing.
Temperatures reached 69*C but only briefly before these errors appeared.
I don't think increasing the voltage would help—I didn't see any crashes, my games are running smoothly with normal temperatures, or I might be mistaken and need to address this.
EDIT: I recently ran a Cinebench test for a few minutes. It completed successfully at 60*C max.
Your CPU is malfunctioning during that overclock. I wouldn't let it continue like this, as it could end up completely failing eventually.
Sorry, the situation isn't stable, Aida was too weak. Running a stress test at version 1.9 caused the system to crash. The issue seems limited to worker 2, with only the second worker reporting an error after a few seconds. I changed from version 1.19 to 1.24 and the problem persists. Should I check if enabling or disabling the CPU's prime and avx options helps?