I7 5820K running at 0.22 GHz is unresponsive.
I7 5820K running at 0.22 GHz is unresponsive.
He brought an older PC with an i7 5820k and 980ti. I reset Windows and applied fresh thermal paste—it worked well. The system ran smoothly for more than two days, even playing DayZ. Later, he reported slow performance. Task manager showed the CPU at a low idle of 0.22 GHz, no unusual processes, and a quick scan came back clean. It seems the mount or thermal paste might have been an issue, but it functioned properly otherwise.
It wasn't overheating or experiencing problems before. It seems like a typical situation where everything is fine. If it wasn’t clearly struggling, it probably didn’t need fixing. "More than enough" might have been excessive and led to unintended results. Unless there were obvious signs of failure, the issue likely wasn’t critical.
Select your board and cooler, then verify specs with CPU-Z. Task Manager isn’t always trustworthy.
@StarsMars Advise your friend to run ThrottleStop and attempt clearing the BD PROCHOT box on the main screen. This frequently resolves CPUs stuck at the lowest speed. For WHEA warnings, the CPU may require additional voltage. Is it overclocked? Task Manager doesn’t always show these CPUs correctly. There’s something wrong, but the minimum speed is typically 800 MHz.
Uncertain about this situation. He doesn’t seem tech-savvy and it happened at his place recently. I’ve assembled many PCs and performed repairs before. It probably isn’t related to the paste quantity. He’ll bring it back for a mount check. Noctua nht1 is non-conductive, which I recall. I don’t remember exactly but it’s likely an MSI x99 board. He should be done soon. I’ll download cpu-z and verify it. Throttlestop isn’t familiar to me. There’s no overclocking involved. I understand Task Manager isn’t perfect, but the performance matches what’s reported. I’ll share updates once it’s resolved. I’m planning to test with a spare power supply if needed.
I was responsible for it. The asetec lock wasn't secured properly on the aio, causing the block to fall. I reworked, re-locked, and then installed it. Everything tested successfully.