F5F Stay Refreshed Power Users Overclocking Windows stops working when I exceed 4.5 ghz

Windows stops working when I exceed 4.5 ghz

Windows stops working when I exceed 4.5 ghz

S
SaadPlayZ
Junior Member
3
09-18-2017, 11:45 AM
#1
Here are the details you provided, rewritten in a different format while keeping the same length and structure:

So initially, my hardware setup includes a CPU with an Intel core i7 6700k running at 4.0 GHz, a GPU of Nvidia GFX GTX 1070 Ti, 2x 8 GB RAM sticks, and a motherboard from Asrock Z170 Pro4s. The system has an SSD along with two additional HDDs for extra storage. I first overclocked the GPU using MSI Afterburner and tested its stability with the Superposition benchmark. Then I moved on to the CPU, observing that its idle temperature reached 40°C. I attempted to push it to 1.2 volts and 4.5 GHz in BIOS, enabling all cores. After launching Windows, I began stress testing the CPU, which quickly heated up to 80-81°C within minutes. Eventually, the system crashed with a stop code indicating a clock watchdog timeout. I adjusted the BIOS settings, setting multiplayer to 44.4 GHz and 4.4 GHz to see if it would work better. It did, but I still find it puzzling why it doesn’t go higher, even when I try 1.3 volts, though it reverts back to 1.2. The biggest frustration is that it remained stable at 4.5 GHz until Windows decided not to run it anymore.
S
SaadPlayZ
09-18-2017, 11:45 AM #1

Here are the details you provided, rewritten in a different format while keeping the same length and structure:

So initially, my hardware setup includes a CPU with an Intel core i7 6700k running at 4.0 GHz, a GPU of Nvidia GFX GTX 1070 Ti, 2x 8 GB RAM sticks, and a motherboard from Asrock Z170 Pro4s. The system has an SSD along with two additional HDDs for extra storage. I first overclocked the GPU using MSI Afterburner and tested its stability with the Superposition benchmark. Then I moved on to the CPU, observing that its idle temperature reached 40°C. I attempted to push it to 1.2 volts and 4.5 GHz in BIOS, enabling all cores. After launching Windows, I began stress testing the CPU, which quickly heated up to 80-81°C within minutes. Eventually, the system crashed with a stop code indicating a clock watchdog timeout. I adjusted the BIOS settings, setting multiplayer to 44.4 GHz and 4.4 GHz to see if it would work better. It did, but I still find it puzzling why it doesn’t go higher, even when I try 1.3 volts, though it reverts back to 1.2. The biggest frustration is that it remained stable at 4.5 GHz until Windows decided not to run it anymore.

F
68
09-18-2017, 12:30 PM
#2
If it crashes after a while, it likely wasn't stable from the start.
F
FireDragon7754
09-18-2017, 12:30 PM #2

If it crashes after a while, it likely wasn't stable from the start.

B
berude2403
Member
69
09-18-2017, 09:13 PM
#3
If it crashes after a while, it likely wasn't stable from the start.
B
berude2403
09-18-2017, 09:13 PM #3

If it crashes after a while, it likely wasn't stable from the start.