F5F Stay Refreshed Power Users Overclocking Accidental 8700k overvolt

Accidental 8700k overvolt

Accidental 8700k overvolt

A
Areeend
Member
142
01-17-2017, 07:40 PM
#1
I recently increased my machine's performance by running Prime 95 with blended mode and small FFTs for several hours to check stability. Everything seemed normal at first.

The specifications are:
CPU: Delidded 8700K at 4.5 GHz, 1.145V, Copper IHS
RAM: 32GB Corsair DDR4 @ 3600MHz
CPU Cooler: Corsair H115i
Motherboard: Asus ROG Z370G
PSU: Corsair 860i
OS: Windows 10 64-bit

Last night, while testing adjustments to the LLC and VCORE to reach 4.7GHz, I mistakenly set the voltage to 1.55V and started the machine. Once I opened Prime 95 and ran a small FFT test with HWmonitor open, the temperature rose to 1.55V. I immediately restarted and lowered it back to 1.2V.

Since then, during idle periods of about 10 minutes, Prime 95 stress tests for five cycles have caused BSODs at CLOCK_WATCHDOG_TIMEOUT. I've also observed a BSOD after a system restart when DPC_WATCHDOG_TIMEOUT was triggered.

Some users mentioned that at 1.55V during idle the CPU wouldn't have been affected, especially since temperatures stayed around 70°C. However, significant damage appears to occur only after prolonged stress tests.

Any guidance would be very helpful.
A
Areeend
01-17-2017, 07:40 PM #1

I recently increased my machine's performance by running Prime 95 with blended mode and small FFTs for several hours to check stability. Everything seemed normal at first.

The specifications are:
CPU: Delidded 8700K at 4.5 GHz, 1.145V, Copper IHS
RAM: 32GB Corsair DDR4 @ 3600MHz
CPU Cooler: Corsair H115i
Motherboard: Asus ROG Z370G
PSU: Corsair 860i
OS: Windows 10 64-bit

Last night, while testing adjustments to the LLC and VCORE to reach 4.7GHz, I mistakenly set the voltage to 1.55V and started the machine. Once I opened Prime 95 and ran a small FFT test with HWmonitor open, the temperature rose to 1.55V. I immediately restarted and lowered it back to 1.2V.

Since then, during idle periods of about 10 minutes, Prime 95 stress tests for five cycles have caused BSODs at CLOCK_WATCHDOG_TIMEOUT. I've also observed a BSOD after a system restart when DPC_WATCHDOG_TIMEOUT was triggered.

Some users mentioned that at 1.55V during idle the CPU wouldn't have been affected, especially since temperatures stayed around 70°C. However, significant damage appears to occur only after prolonged stress tests.

Any guidance would be very helpful.

B
baconandfries
Member
215
01-20-2017, 12:41 AM
#2
Just because the temperature stayed at 1.55 instead of shutting down doesn't mean your CPU was fine. It's possible that the 1.55 vcore caused excessive stress on the tiny parts inside. This might have damaged your CPU, so you probably fried it. Read this article for more details.
B
baconandfries
01-20-2017, 12:41 AM #2

Just because the temperature stayed at 1.55 instead of shutting down doesn't mean your CPU was fine. It's possible that the 1.55 vcore caused excessive stress on the tiny parts inside. This might have damaged your CPU, so you probably fried it. Read this article for more details.

H
HEROBRITT
Junior Member
35
01-20-2017, 03:14 AM
#3
Just because the temperature stayed at 1.55 instead of shutting down doesn't mean your CPU was fine. Probably the 1.55 vcore caused too much strain on its tiny parts. It seems like you might have damaged it, sorry to say. Check this out.
H
HEROBRITT
01-20-2017, 03:14 AM #3

Just because the temperature stayed at 1.55 instead of shutting down doesn't mean your CPU was fine. Probably the 1.55 vcore caused too much strain on its tiny parts. It seems like you might have damaged it, sorry to say. Check this out.

D
Destructor52
Junior Member
46
01-21-2017, 10:38 PM
#4
I hope you haven't, but I would reset your system by clearing CMOS, restoring default settings, and then running the tests once more. Perhaps even reinstalling Windows. Then begin retesting to verify everything functions properly. If not, as urbancamper mentioned, it might be dead, but it's worth trying a reset before finalizing...
D
Destructor52
01-21-2017, 10:38 PM #4

I hope you haven't, but I would reset your system by clearing CMOS, restoring default settings, and then running the tests once more. Perhaps even reinstalling Windows. Then begin retesting to verify everything functions properly. If not, as urbancamper mentioned, it might be dead, but it's worth trying a reset before finalizing...