Getting clock_watchdog_timeout error all the sudden

[Bion1985]

So I've had this system for almost a year and it's been overclocked most the time I've had it. One day while playing Rise of the Tomb Raider I got clock_watchdog_timeout error. Then after a Nvidia driver update along with the game having an update I had no issues, played it quite a bit more with 0 issues. Yesterday I decided to play GTA 5, guess the most recent windows 10 update did something to the Xbox One controller (can read more here https://m.reddit.com/r/GrandTheftAutoV_PC/comments/48me06/psa_latest_windows_10_update_breaks_keyboard/ )But after getting past that issue I played the game for 30 minutes to a hour and got another clock_watchdog_timeout error. This game I've played for hours on end on this system in the past with 0 issues also. Wondering if anyone may have an idea what's going on. Here are my system specs for refrence.

 

System

I5 4690k 4.60hz @ 1.25v (if I remember correct)

16gb ddr4 2133mhz

Asus z97-a usb 3.1

Samsung 850 evo 128gb

2 2tb Seagate Barracuda drives

Ocz zx series 850 psu

System running Windows 10

 

Thanks everyone in advance.

 

Edit posted wrong link

[Guest]

I've only seen that error with an unstable OC. 

[Benergy]

1 minute ago, Bion1985 said:

So I've had this system for almost a year and it's been overclocked most the time I've had it. One day while playing Rise of the Tomb Raider I got clock_watchdog_timeout error. Then after a Nvidia driver update along with the game having an update I had no issues, played it quite a bit more with 0 issues. Yesterday I decided to play GTA 5, guess the most recent windows 10 update did something to the Xbox One controller (can read more here http://steamcommunity.com/app/274190/discussions/0/535152276584863931 ) But after getting past that issue I played the game for 30 minutes to a hour and got another clock_watchdog_timeout error. This game I've played for hours on end on this system in the past with 0 issues also. Wondering if anyone may have an idea what's going on. Here are my system specs for refrence.

 

System

I5 4690k 4.60hz @ 1.25v (if I remember correct)

16gb ddr4 2133mhz

Asus z97-a usb 3.1

Samsung 850 evo 128gb

2 2tb Seagate Barracuda drives

Ocz zx series 850 psu

System running Windows 10

 

Thanks everyone in advance.

First of all, ensure your temperatures are OK.

If that isn't a problem, dial back your overclock.

[Bion1985]

3 minutes ago, Benergy said:

First of all, ensure your temperatures are OK.

If that isn't a problem, dial back your overclock.

Temps were only in around the low 70's when game crashed.

 

Edited my op I posted wrong link about the Xbox one controller. 

[Benergy]

1 minute ago, Bion1985 said:

Temps were only in around the low 70'speed when game crashed.

Considering the stock clock of the 4960k is 3.5GHz, you still have a pretty hefty overclock on it. 

It's very likely to be the problem.

[Bion1985]

Just now, Benergy said:

Considering the stock clock of the 4960k is 3.5GHz, you still have a pretty hefty overclock on it. 

It's very likely to be the problem.

Yea i just found it very odd that this would pop up kinda out of nowhere.

[Benergy]

Just now, Bion1985 said:

Yea i just found it very odd that this would pop up kinda out of nowhere.

It is possible the CPU has degraded slightly from being overclocked that high for so long

[Guest]

2 minutes ago, Bion1985 said:

Yea i just found it very odd that this would pop up kinda out of nowhere.

Have you stress tested the OC with synthetic benchmarks?

 

 

[Bion1985]

8 minutes ago, Alexokan said:

Have you stress tested the OC with synthetic benchmarks?

 

 

Yes when I originally did the oc I tested with Aida some and intel extreme tuning seemed good. I also ran several 3d mark firestrike runs with no issues. Matter of fact when I had the game performance issues that were related to the Xbox one controller bug in the reddit post I went and ran 3d mark firestrike, ran perfectly.

 

@Benergy I won't rule out oc issue, think I may also try reverting to stock speed and seeing if error occurs again.