- Dec 22, 2017
- 1
- 0
- 510
Hi. I've built a system with the following specs around 2 weeks ago:
Mobo: ASUS Prime Z270-A
CPU: i5-7600k
GPU: EVGA GTX 1080 FTW2
Case: Fractal Design R5
RAM: Corsair Vengeance LPX 2x8 DDR4-3000
PSU: EVGA Supernova G2 750W Fully Modular
CPU Cooler: Cooler Master Hyper 212 EVO
Unfortunately, I've run into many problems. For a start, when fully assembled with everything checked twice, it booted into Windows. Upon restarting it, however, it blue screened with the error CLOCK_WATCHDOG_TIMEOUT. After 2 days of messing around, swapping Windows installs, etc. I finally disabled Turbo Boost in the BIOS and it worked. Please note, I am on the latest BIOS version and have re-flashed it, and also reset the CMOS.
I've run a memtest to rule out the RAM, and it reported no errors. After a day of stability, the system crashed yet again. But during that day, I had achieved a stable 4.2 GHz overclock with a voltage of 1.35 volts. After the error, I reset everything to the default without turbo boost and it still gave me the CLOCK_WATCHDOG_TIMEOUT error. Woo-hoo.
I proceeded to underclock and overvolt the CPU and this worked for at least a week. But, to nobody's surprise, the system now blue screens with the same exact error even when underclocked. I tried it on different Windows installs (clean installs on different drives with Windows 10 Home, Windows 7 Pro, and Linux but none of these worked) yet on my older system (ASUS prebuilt), these installs worked beautifully. I've updated all of the drivers, reflashed the BIOS again and it still errors. I'm at a loss, and looking for an answer. It can be stable for a day: running high-intensity games and mining with no problem, and then it gives me the error out of the blue.
If anyone needs more information, please reply. I will gladly give any more information as I am just lost. Thanks!
UPDATE 12/26/17:
Since then, I've run the Intel diagnostic utility via a bootable drive. It looks like the CPU is overclocking itself, yet I have set everything in the BIOS settings to their default. If anyone could recommend some fix or additional information as to why this is being caused, please do so. Thanks!
Files:
https://drive.google.com/drive/folders/11HUlO5BNKxjdPXFbBSuQUZ73Gos2rQDx?usp=sharing
Mobo: ASUS Prime Z270-A
CPU: i5-7600k
GPU: EVGA GTX 1080 FTW2
Case: Fractal Design R5
RAM: Corsair Vengeance LPX 2x8 DDR4-3000
PSU: EVGA Supernova G2 750W Fully Modular
CPU Cooler: Cooler Master Hyper 212 EVO
Unfortunately, I've run into many problems. For a start, when fully assembled with everything checked twice, it booted into Windows. Upon restarting it, however, it blue screened with the error CLOCK_WATCHDOG_TIMEOUT. After 2 days of messing around, swapping Windows installs, etc. I finally disabled Turbo Boost in the BIOS and it worked. Please note, I am on the latest BIOS version and have re-flashed it, and also reset the CMOS.
I've run a memtest to rule out the RAM, and it reported no errors. After a day of stability, the system crashed yet again. But during that day, I had achieved a stable 4.2 GHz overclock with a voltage of 1.35 volts. After the error, I reset everything to the default without turbo boost and it still gave me the CLOCK_WATCHDOG_TIMEOUT error. Woo-hoo.
I proceeded to underclock and overvolt the CPU and this worked for at least a week. But, to nobody's surprise, the system now blue screens with the same exact error even when underclocked. I tried it on different Windows installs (clean installs on different drives with Windows 10 Home, Windows 7 Pro, and Linux but none of these worked) yet on my older system (ASUS prebuilt), these installs worked beautifully. I've updated all of the drivers, reflashed the BIOS again and it still errors. I'm at a loss, and looking for an answer. It can be stable for a day: running high-intensity games and mining with no problem, and then it gives me the error out of the blue.
If anyone needs more information, please reply. I will gladly give any more information as I am just lost. Thanks!
UPDATE 12/26/17:
Since then, I've run the Intel diagnostic utility via a bootable drive. It looks like the CPU is overclocking itself, yet I have set everything in the BIOS settings to their default. If anyone could recommend some fix or additional information as to why this is being caused, please do so. Thanks!
Files:
https://drive.google.com/drive/folders/11HUlO5BNKxjdPXFbBSuQUZ73Gos2rQDx?usp=sharing
Facebook
Twitter
Instagram