Le questioni 2500k con risultati di 4,8 GHz causano un timeout del CLOCK_WATCHDOG.
Le questioni 2500k con risultati di 4,8 GHz causano un timeout del CLOCK_WATCHDOG.
There are occasional BSODs related to "CLOCK_WATCHDOG_TIMEOUT" in Windows 10, especially when using an OC'ed i5 2500K. It appears the issue occurs randomly—sometimes once a day, other times every couple of days. When playing a game, I experience this problem intermittently, sometimes after just one day or two. If I leave a game running while idle, the error appears after roughly 10 to 15 minutes. This pattern has happened about five times now, indicating it’s not a random occurrence.
I’ve been using my i5 2500K at stock speeds (3.3GHz base, 3.7GHz turbo) for approximately a month without any problems. Recently, I decided to overclock it after noticing stuttering, and the OC process helped stabilize it. Running at 4.8GHz is still viable with my chip; it can reach up to 5GHz but only about 95% stable. I chose 4.8GHz to balance performance and stability, as I suspect the CPU might be in a C-state. However, whether this affects performance when the CPU is on or off remains unclear, and I don’t see any noticeable difference.
I have EIST enabled and certain Intel Turbo Boost settings active. If you need details about BIOS configurations, feel free to ask. Looking ahead, I plan to upgrade to an LGA 1151 socket and an I7 8700K, but I recently purchased an HTC Vive and prefer to stick with my current setup until I receive my next paycheck for a new CPU and motherboard.
Current specifications:
- i5-2500K @ 4.8GHz & 1.32V core voltage (water cooled, 40C idle, max 60C under load)
- Asus Strix GTX 970 with factory OC + my custom settings
- MSI P67A-GD55 B3 M.2
- 4x4GB HyperX Fury RAM
- 120GB Samsung SSD for Windows
- 1TB Toshiba HDD for storage
- Corsair 750W PSU
P.S. The Task Manager shows my CPU at 6.96GHz, which makes me wonder if Windows is interfering with the OC. But both CPU-Z and MSI Afterburner confirm a stable 4.8GHz.
The maximum voltage for that chip is 1.52. Increasing the voltage and adjusting the load line calibration to extreme will help. As long as you don't run your computer nonstop and turn it off when not in use, degradation won't be a major concern. It takes longer than people realize, but staying under the max voltage keeps things safe. I'm currently running at 4.9ghz with voltage fluctuating between 1.5 and 1.52. I just upgraded my cooler and am considering going back to 5ghz.
Alright, thanks for your input, I did as you said, running on 1.5 vcore right now with 55C on idle, on top of that, I also re-disabled C-State incase it attempts to do something funky and I also disabled OverSpeed protection to eliminate instability. I will follow up in few days unless I keep getting clock watchdog timeout or encounter something else.