Facing Problems while gaming....

[MadGamerG90]

i builded my own PC and its 6 months now.I was able to Play every High-End games in ultra settings without any slightest problems.......bt now im facing some issues right now when playing certain games like GTA 5 , WWE2K15, WITCHER 3,FIFA15 ETC games are so lagging some times stucks at certain points...bt i was able to play these games smoothly under full settings 3-4 days ago. This problems started recently. I accessed BIOS SETTINGS recently to solve CLOCK_WATCHDOG-TIMEOUT. Is it something to do with RAM.

CAN anyone help.
I dont know what i did wrong.
so pls help me out.

My Specs are:
I5 4690
ASUS STRIX 970 4GB OC
Corsair Vengence 1600Mhz 8GB
1TB HDD
asus B8GM-G (MOBO)

 

[TechyInAZ]

What are your computer specifications?

 

[sizzling]

Those are all CPU intensive games. What is your entire pc spec and what is your CPU usage when the lagging occurs? Also what resolution are you playing at?

 

[MarkW]

The CLOCK_WATCHDOG_TIMEOUT error means that your processor is having trouble with cooperation from its cores and threads. Threads are tasks taken by cores, and some cores can take many threads simultaneously. The problem here is that a thread is waiting for a proper response from another thread — or a core is waiting for a response from another core — and those responses aren’t coming. Therefore, you get this BSoD error.
While this is a processor problem, this can be caused by two things: a driver error, which is very likely if you’re using Windows 8, or the OS itself isn’t playing nice with the processor.

First question: how long have you had this computer? Has it been working fine until now?

If so, just use System Restore to go back to a point where the system worked. Be wary of using any new devices that may have caused the problem.

Drivers are what is used to get your devices like your keyboard to interact with your computer, and while some misconfigured drivers can result in bad performance, bad drivers overwhelmingly result in BSoDs like CLOCK_WATCHDOG_TIMEOUT.

The above was stolen from:
http://www.reviversoft.com/blog/2013/01/clock-watchdog-timeout/