[SOLVED] BSOD - CLOCK_WATCHDOG_TIMEOUT_8_PROC. FIX: I changed motherboard.

F

FunkyMaggot

Member
Joined
May 13, 2013
Posts
18
Hello everyone :wave:

I am hoping someone can help me here. I have been suffering blue screens for a couple of months but have only just had the time to really look into them. After checking a couple of guides on analysing windows dump files for windows I found the error CLOCK_WATCHDOG_TIMEOUT_8_PROC on multiple processes (putty, svchost, system and vmware.a). I haven't looked through all the dumps, but the CLOCK_WATCHDOG_TIMEOUT_8_PROC appears in all the ones i checked. I looked this up and found that this could be a processor issue.

EDIT:
The frequencies of my crashes vary it can be twice a day to a week.

It is worth mentioning that my PC was previously overclocked, although blue screens did not appear, the system would freeze. After a couple of months of trying to make the system stable I returned the settings to stock. My motherboard also seems to be having issues recognizing USBdevices on the back ports. I can overcome this by making sure USB devices are plugged in before the machine is booted. For a while I suspected that the USB devices were the cause of the bluescreens, but after disconnecting all USB device and using legacy hardware it still occurred.

I am hoping to nail find out what's causing this finally and get the issue resolved. I would replace the motherboard and processor but I would like to be 100% sure on what is causing the crashes.

I have attached request files and am in the process of running the additional scans. Please let me know if I have missed anything or if you need further information.

My current attempts of debugging my machine:
Upgraded BIOS
Upgraded drivers (i still have 1 unknown device in device manager)

Memtest:
-Tested both memeory sticks, A0 A1
-Tested both sticks individually in A0

Windows memeory diagnostic tests
-Tested both memeory sticks, A0 A1
-Tested both sticks individually in A0

Malware bytes full scan
-nothing detected

Antivirus scan with MSE
-nothing detected

Questions & Answers
OS - Windows 7 x64
What was original installed OS on system? Drive was empty, installed windows 7 - myself
Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? -No
Age of system - 2 years
Age of OS installation - 6 months
CPU - Intel Core i7 2600K UNLOCKED
Video Card - 1280MB MSI GTX570 TWIN FROZR 2 OC
MotherBoard - Asrock Z68 Extreme4 Intel Z68 (Socket 1155) DDR3 Motherboard (Corsair Vengeance 8GB)
Power Supply - CORSAIR 850W CMPSU-850TXV2 PSU
System Manufacturer - myself
 

Attachments

Last edited:
Do you have any full/kernel dumps? Minidumps are useless with bugcheck CLOCK_WATCHDOG_TIMEOUT.
 
Thanks for the reply. UNfortunatly i'm no so savvy with this sort of computing. I've had a quick google and found C:\Windows\MEMORY.DMP, this gave me similar information as the minidumps. Is there anyway for me to enable a more verbose/useful dump file?

MEMORY.DMP analysis:
Read More:
 
To configure a Kernel Memory Dump to be saved, then please follow these steps:


  1. Click Start, or press the Windows Flag key on your keyboard.
  2. Right-Click Computer, and then select Properties.
  3. In the right pane, select Advanced System Settings.
  4. In the Advanced tab, select Settings, under the Startup and Recovery group box.

Make sure your settings are configured to the same settings seen in my screenshot:

BSOD Config.JPG
 
Thanks for the guide, but it looks like my settings are identical already. Is there anything else I can do o get some more information?
 
USB problems frequently are caused by motherboard issues. I've often seen that when a mobo is going bad, the USB ports are some of the first items to go on it.

You'll want to provide us the actual kernel dump (MEMORY.DMP). Zip up and upload to a 3rd party filesharing site like Mirrorcreator.
 
Code: 
[COLOR=#ff0000]BugCheck 101[/COLOR], {19, 0, [COLOR=#008000]fffff880009b3180[/COLOR], 4}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Code: 
Usual causes:  Device driver, BIOS bug, hardware defect

It appears that the processor didn't respond to the clock interrupt within the given time interval.

Update:

Code: 
0: kd> [COLOR=#008000]!sysinfo machineid[/COLOR]
Machine ID Information [From Smbios 2.7, DMIVersion 39, Size=1553]
BiosMajorRelease = 4
BiosMinorRelease = 6
BiosVendor = American Megatrends Inc.
BiosVersion = P2.20
BiosReleaseDate = [COLOR=#ff0000]06/29/2012[/COLOR]
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
SystemFamily = To Be Filled By O.E.M.
SystemVersion = To Be Filled By O.E.M.
SystemSKU = To Be Filled By O.E.M.
BaseBoardManufacturer = ASRock
BaseBoardProduct =[COLOR=#ff0000] Z68 Extreme4[/COLOR]
BaseBoardVersion =

Your BIOS seems to be a little dated, I would suggest checking for any BIOS updates for your motherboard, they may have introduced some greater hardware compatibility and stability patches with the newer version.

I also noticed a few drivers in the raw stack text for the hung processor, here are my findings:

Code: 
4: kd>[COLOR=#008000][/COLOR] [COLOR=#008000]lmvm VBoxNetFlt[/COLOR]
start             end                 module name
fffff880`06eb9000 fffff880`06ee1000   VBoxNetFlt   (no symbols)           
    Loaded symbol image file: VBoxNetFlt.sys
    Image path: \SystemRoot\system32\DRIVERS\VBoxNetFlt.sys
    Image name: VBoxNetFlt.sys
    Timestamp:        [COLOR=#ff0000]Wed Dec 19 13:47:16 2012[/COLOR] (50D1C564)
    CheckSum:         0002B9C5
    ImageSize:        00028000
Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

This driver corresponds to VirtualBox network driver, please update the driver or remove the program if no improvement takes place after updating the driver. Here is the link - https://www.virtualbox.org/wiki/Downloads

Code: 
4: kd> [COLOR=#008000]lmvm k57nd60a[/COLOR]
start             end                 module name
fffff880`06ee3000 fffff880`06f4a000   k57nd60a   (no symbols)           
    Loaded symbol image file: k57nd60a.sys
    Image path: \SystemRoot\system32\DRIVERS\k57nd60a.sys
    Image name: k57nd60a.sys
    Timestamp:        [COLOR=#ff0000]Tue Feb 15 04:19:05 2011[/COLOR] (4D59FEB9)
    CheckSum:         00071F18
    ImageSize:        00067000
Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your Broadcom NetLink Gigabit Ethernet NDIS6.x Unified Driver seems to be a little outdated and may be a possible cause, please update the driver from here - Ethernet NIC Driver Downloads | Broadcom
 
Ah ha, well I think I found the USB problem. The one crashdump reported an issue with the VMWare USB driver and it looks like it corrupted some data. It's dated Oct 11, 2012, so if there's a VMware update go for it, otherwise you may need to turn off USB emulation in the meantime.

Btw, VMware and VirtualBox are two totally different products and different brands. I do not think that VirtualBox uses a VMware driver (correct me if wrong). Are you actually using multiple VM software? That's a definite no-no.
 
Hmm no update for VMWare Workstation it seems, and i'm not sure how to disable the USB emulation.

I do have virtual box installed as well as VMWare workstation. I've been moving over to workstation, maybe I can get rid of vbox completely. I had these problems before workstation though :/
 
True, but having both would've caused problems of its own, and it only complicates our analysis of the situation. It's best to get rid of what we know for sure would cause issues, rather than disregard them. You may have been suffering two different conditions that were creating BSODs by having this setup, rather than the one previously.

When I have time I'll scrutinize the crashdumps further.
 
Thanks, i'll see how long I can last without another blue screen...

I've noticed today that I get some mouse lag (usb mouse using a front port) and while streaming music it hung for a second. Will keep an eye on things...
 
Hey mate. How have things been so far? I unfortunately haven't had time to dive into that memory dump, and tbh, I don't see myself having it in the near future, so I apologize for the unnecessary wait.
 
I'll see what I can do about looking at them, but no guarantees. At least I can cross analyze to find any patterns between em. If anyone else wants to give it a shot feel free to do so.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top