Constant BSODs - Watchdog Timeout

[etekiller]

It's my first post on this forum, so hello everybody!

My problem:

I started getting a BSOD recently after reinstalling Windows. I have no idea what is the problem, because I haven't installed any new hardware and it kinda started very suddenly. It used to be rare, common only while playing NBA 2k15 (even then it was like once after 5 hours of constant play).

Now I am getting those BSODs pretty frequently. If I play a game (even if it's a small game that's also playable on an iPad or some low-end mobile device) then a BSOD is guaranteed. Last game that didn't cause a BSOD was The Powder Toy... well actually it did after I threw all the explosives that game had available into action (my own version of a stress test). So it seems that I get BSODs as a result of "overloading" the CPU. Sometimes even watching ustream.tv causes this to happen (though it's extremely rare).

I thought that maybe it'd be a good idea to monitor the temperature of my CPU. I was shocked when I discovered that my CPU is at 80C (BIOS reading)! After buying a thermal paste, removing all of the dust from beneath the heatsink and putting the heatsink back I saw that the temperature was down to 60C (still a damn huge number). I was suspicious about that reading so I launched a software version of that temperature evaluation and what I saw was 35C... So I have no idea which of these is correct, but I doubt that at 80C my CPU would be fine even outside of games, so I doubt the BIOS reading. Especially because now it says again that it's 80C, it's impossible that nothing changed after all the work I've done to clean the heatsink and after applying a fresh layer of thermal paste.

So it was time for me to test if something has changed. As you probably have already guessed... nope. I got a bluescreen 5 minutes into a new game. This time I decided to take the .dmp file and take a closer look at it. That's what I got:

EDIT: I've placed the .dmp file readout in an answer, because this thread kept deleting it from my post.

My specs:
CPU: AMD Athlon 64x 6400+ (no overclocking EVER)
GPU: ASUS NVIDIA 9600 GT 1024MB/256bit
RAM: 3GB
OS: Windows 7 64x

Could you please help me with this? I am really out of ideas...

 

[etekiller]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000060, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009e6180, The PRCB address of the hung processor.
Arg4: 0000000000000001, 0.

Debugging Details:
------------------


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  Dizzel.exe

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`033d6b18 fffff800`02d29d5a : 00000000`00000101 00000000`00000060 00000000`00000000 fffff880`009e6180 : nt!KeBugCheckEx
fffff880`033d6b20 fffff800`02cdcad7 : 00000000`00000000 fffff800`00000001 00000000`00002626 00000000`00000009 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`033d6bb0 fffff800`02c1f1c0 : 00000000`00000000 fffff880`033d6d60 fffff800`02c3b460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`033d6cb0 fffff800`02ccf513 : 00000000`91efa428 fffff800`02c3b460 00000000`00000000 00000000`00000000 : hal!HalpRtcClockInterrupt+0x130
fffff880`033d6ce0 fffff800`02d08807 : fffff800`02e45e80 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`033d6e70 fffff800`02d0775d : 00000000`00000000 00000000`00000001 fffffa80`00000000 00000002`00000001 : nt!KxFlushEntireTb+0x93
fffff880`033d6eb0 fffff800`02d2bcc0 : 00000000`00000002 fffff8a0`02ac0fe8 00000000`00000001 00000000`00000004 : nt!KeFlushTb+0x119
fffff880`033d6f30 fffff800`02ce2b1f : fffff8a0`02ac0fe8 fffff880`033d6fc0 fffff800`02f05540 fffff800`02f05540 : nt! ?? ::FNODOBFM::`string'+0xad92
fffff880`033d6f70 fffff800`02cf10a5 : 00000000`00000001 fffff880`0ef70000 fffff880`033d7360 fffff8a0`02ac0fe8 : nt!MiResolveDemandZeroFault+0x1ff
fffff880`033d7060 fffff800`02cef893 : f8a002ac`0fe80400 fffff880`0ef70000 fffff6fc`40077b80 fffff800`02f05540 : nt!MiResolveProtoPteFault+0x4f5
fffff880`033d70f0 fffff800`02ce000b : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`0f08da51 : nt!MiDispatchFault+0x1c3
fffff880`033d7200 fffff800`02cd10ee : 00000000`00000001 fffff880`0ef70000 fffffa80`02c08800 fffff880`033d7db0 : nt!MmAccessFault+0xe1b
fffff880`033d7360 fffff880`0f15e0d0 : fffff880`033d7c70 fffff880`0f15dc7e fffff800`02cde32c 00001f80`00000011 : nt!KiPageFault+0x16e
fffff880`033d74f0 fffff880`033d7c70 : fffff880`0f15dc7e fffff800`02cde32c 00001f80`00000011 fffffa80`028911c0 : nvlddmkm+0x1320d0
fffff880`033d74f8 fffff880`0f15dc7e : fffff800`02cde32c 00001f80`00000011 fffffa80`028911c0 fffff880`033d7740 : 0xfffff880`033d7c70
fffff880`033d7500 fffff800`02cde32c : 00001f80`00000011 fffffa80`028911c0 fffff880`033d7740 00000000`00000000 : nvlddmkm+0x131c7e
fffff880`033d7508 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSecondaryClockInterrupt+0x13c


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner

 

[i7Baby]

What CPU temps are you getting atidle and while playing WatchDogs? - from your mobo uefi software.

WatchDogs - http://www.game-debate.com/games/index.php?g_id=4546&game=Watch%20Dogs

I don't know why you are trying to play that game with your PC

 

[Supernova1138]

He's not playing Watch Dogs, he's getting a specific BlueScreen error, which usually indicates a failing CPU. It's possible that your CPU has been permanently damaged from running at such a high temperature for a while, and now has stability issues. It may be time to look for a replacement. If you want to rule out the possibility of a software issue, you can try reformatting and reinstalling Windows cleanly.

 

[i7Baby]

The 35C is probably a margin temp - C from shutdown.

80C is too high. Blow the dust out of your case with compressed air. Increase the cpu fan rpm to as fast as it can go.

Your cpu at idle should be at 40C max and 60C while gaming.

If still not that low then re-seat your CPU cooler (Google it) and if still no good, get a better cooler eg Coolermaster Hyper 212 evo.

 

[etekiller]

He's not playing Watch Dogs, he's getting a specific BlueScreen error, which usually indicates a failing CPU. It's possible that your CPU has been permanently damaged from running at such a high temperature for a while, and now has stability issues. It may be time to look for a replacement. If you want to rule out the possibility of a software issue, you can try reformatting and reinstalling Windows cleanly.

To be honest I doubt that the CPU temperature is real. It was at 80C according to BIOS. Then I removed the heatsink, blew off all the dust, cleaned up the heatsink and the CPU from that old thermal paste, then I applied a new layer of thermal paste and put it all back together.

This should bring down the temperature at least a little, because there was quite a lot dust before I had done all of that. BIOS however is still saying that the temperature is at 80C. Software readouts show 35C though. If I were to judge by consequence, then I would say that the software readout is correct.

Another thing is that my OS has been running perfectly fine even before all of the things I did. I doubt it would function properly at 80C. It worked smoothly and pretty.

I was thinking about a possible driver problem, but I doubt that it's possible for a driver problem to get worse with time. OS problem however is likely to behave that way, the thing is that I do not want to reinstall my OS until I am fully sure that it's what's causing the BSODs.

 

[etekiller]

It seems that I managed to solve that problem, but I am not sure yet.

I uninstalled Virtual Box, then I disabled my second monitor (I have a dual monitor setup) and removed a WO Mic audio device (software device that emulates a microphone while using an Android Smartphone as a device). I'm not sure whether this problem is solved yet though. Time will tell.

I still got a critical error after finishing a game, but I was able to play that game for as long as I wanted and nothing crashed inside it. It could've been an isolated error, because this game is a free indie game, so problems are expected to occur. I will update you on the situation.