Clock_watchdog_timeout

kadjar · Apr 21, 2012

I saw another thread on this, but couldn't find the files GMan indicated to delete.

Once or twice per night, my computer will freeze completely. Sometimes, I'll see a BSOD which briefly shows CLOCK_WATCHDOG_TIMEOUT.

DxDiag is here:
MGA dxdiag - Pastebin.com

Here's what I've found in the minidump:
MGA minidump - Pastebin.com
(note: not sure why it says AMD 64 in the debugger title, I have an intel processor)

Ran BlueScreenView, here are the results:
http://pastehtml.com/view/bvj8764st.

Thank you so much!

GMan · Apr 21, 2012

Hi,

Please run the tool in the top thread of this Crash subforum, then attach the zip of the files so I can run your dump file(s). Simply pasting a link to the text is of no help.

Alternatively, you can Take Ownership of C:\Windows\Minidump to copy the files in there to any other folder, then zip and attach.

kadjar · Apr 21, 2012

W8.zip attached.

Thank you!

GMan · Apr 21, 2012

kadjar said:
W8.zip attached.

Thank you!

Probably being caused by these, so update or completely uninstall:

Code:

3: kd> lmvm wacommousefilter
start             end                 module name
fffff880`04306000 fffff880`0430e000   wacommousefilter   (deferred)             
    Image path: \SystemRoot\System32\drivers\wacommousefilter.sys
    Image name: wacommousefilter.sys
    Timestamp:        Fri Feb 16 13:12:17 2007 (45D5F401)
    CheckSum:         00005ACE
    ImageSize:        00008000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Code:

3: kd> lmvm wacomvhid
start             end                 module name
fffff880`05018000 fffff880`0501aa00   wacomvhid   (deferred)             
    Image path: \SystemRoot\System32\drivers\wacomvhid.sys
    Image name: wacomvhid.sys
    Timestamp:        Mon Sep 21 19:29:14 2009 (4AB80C4A)
    CheckSum:         00010E49
    ImageSize:        00002A00
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Code:

3: kd> lmvm wacmoumonitor
start             end                 module name
fffff880`0426a000 fffff880`04273000   wacmoumonitor   (deferred)             
    Image path: \SystemRoot\System32\drivers\wacmoumonitor.sys
    Image name: wacmoumonitor.sys
    Timestamp:        Fri Oct 29 12:30:06 2010 (4CCAF68E)
    CheckSum:         00011EF6
    ImageSize:        00009000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

-------------

Navigate to C:\Windows\System32\drivers and delete this driver:

Code:

3: kd> lmvm PxHlpa64
start             end                 module name
fffff880`0143c000 fffff880`01447e00   PxHlpa64   (deferred)             
    Image path: \SystemRoot\System32\Drivers\PxHlpa64.sys
    Image name: PxHlpa64.sys
    Timestamp:        Tue Jun 23 19:16:35 2009 (4A416253)
    CheckSum:         000111B7
    ImageSize:        0000BE00
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

It will make your cd/dvd drive not work, very likely. We can fix that later after stable.

Reboot.

-----------

Could be causing, so look to uninstall this software if necessary:

Code:

3: kd> lmvm AsrAppCharger
start             end                 module name
fffff880`03ce1000 fffff880`03ce8000   AsrAppCharger   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\AsrAppCharger.sys
    Image name: AsrAppCharger.sys
    Timestamp:        Fri Jun 11 02:37:12 2010 (4C11D998)
    CheckSum:         0000D555
    ImageSize:        00007000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

and the same goes for this:

Code:

3: kd> lmvm AsrCDDrv
start             end                 module name
fffff880`19c4c000 fffff880`19c54000   AsrCDDrv   (deferred)             
    Image path: \??\C:\Windows\SysWOW64\Drivers\AsrCDDrv.sys
    Image name: AsrCDDrv.sys
    Timestamp:        Mon Dec 13 22:34:49 2010 (4D06E5D9)
    CheckSum:         0000B43C
    ImageSize:        00008000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

GMan · Apr 21, 2012

Some other crashes are 0x124 hardware type. Still could be caused by any of the above, but it would be an excellent idea to also update the motherboard bios to latest and then set Optimized Defaults in bios and save.

Quick question: This is a laptop, correct?

kadjar · Apr 21, 2012

Deleted wacommousefilter, wacomvhid, wacmoumonitor, and PxHlpa64, rebooted.

CD drive is indeed no longer functioning.

It is a desktop, actually.

In Device Manager, Optiarc DVD RW (etc), Wacom Virtual Hid Driver, and Wacom Mouse Monitor are flagged.

GMan · Apr 21, 2012

kadjar said:
Deleted wacommousefilter, wacomvhid, wacmoumonitor, and PxHlpa64, rebooted.

CD drive is indeed no longer functioning.

It is a desktop, actually.

In Device Manager, Optiarc DVD RW (etc), Wacom Virtual Hid Driver, and Wacom Mouse Monitor are flagged.

Alright. I saw an Intel video driver and an AMD driver, so usually that's a laptop. What you should do is go into the bios and disable the onboard video. Then boot to Windows and install this update for the AMD card:

AMD Catalyst 12.3 WHQL 64-bit download from Guru3D.com

--------

Use this manual method to fix the CD/DVD drive:

The CD drive or the DVD drive does not work as expected on a computer that you upgraded to Windows Vista

--------

As for the Wacom, try to find 2011 or 2012 drivers to install. If you can't find any like that, I would use a different mouse and disconnect that one, until all issues are resolved and we know the machine is perfectly stable.

Later, if you re-attach and things go bad, you can be sure.

kadjar · May 1, 2012

Hello!

Just wanted to say thank you for taking the time to help me out. I ended up deciding to downgrade to Windows 7 to resolve the issues, and also because there are some 3d drivers for my graphics card that require Windows 7. Hopefully, I won't run into the same issues!

I'd highly recommend that you add a 'donate' or 'thanks' button for people like me to chip a bit your way to show our appreciation

GMan · May 1, 2012

You're very welcome!

A little note though: Any video driver that works on Windows 7 can work on Windows 8. You might just have to install it using the device manager.

kadjar · May 1, 2012

Ugh.. I installed Windows 7, and I'm still getting the same issue.

Is it possible that the issue is hardware? A faulty core, perhaps? I ran a sensor test using RealTemp and Prime 95, and it caused a crash about 20% of the way in. (Real Temp - CPU temperature monitoring)

I've attached the latest minidump. Thank you so much.

GMan · May 1, 2012

kadjar said:
Ugh.. I installed Windows 7, and I'm still getting the same issue.

Is it possible that the issue is hardware? A faulty core, perhaps? I ran a sensor test using RealTemp and Prime 95, and it caused a crash about 20% of the way in. (Real Temp - CPU temperature monitoring)

I've attached the latest minidump. Thank you so much.

Installing Windows 7 was a complete step in the opposite direction. Now, everything we've done to try to eliminate the cause of the (usually hardware) 0x124 stop has been in vain and we are back to square one.

If motherboard bios has not been updated to latest, do so. Regardless, set Optimized Defaults in it then save.

Eliminate these drivers from the system:

Code:

FNETURPX FNETURPX.SYS Fri Oct 03 22:27:02 2008 (48E6D476)
PxHlpa64 PxHlpa64.sys Tue Jun 23 19:16:35 2009 (4A416253)
cfosspeed6 cfosspeed6.sys Mon Jul 04 09:18:51 2011 (4E11BDBB)
AsrIbDrv AsrIbDrv.sys Thu Jan 08 03:39:16 2009 (4965BBB4)
AxtuDrv  AxtuDrv.sys  Thu May 19 03:42:38 2011 (4DD4C9EE)

Update:
RTKVHD64 RTKVHD64.sys Tue Jun 14 07:28:43 2011

from Realtek's site.

kadjar · May 2, 2012

I uninstalled FNETURPX, PxHlpa64, and cfosspeed6, and updated the Realtek drivers. I could not find AsrIbDrv.sys or AxtuDrv.sys, however.

I flashed the bios to the most updated version as well.

I looked in the drivers folder for the other two drivers and ran a search. Are they hiding somewhere else?

GMan · May 2, 2012

kadjar said:
I uninstalled FNETURPX, PxHlpa64, and cfosspeed6, and updated the Realtek drivers. I could not find AsrIbDrv.sys or AxtuDrv.sys, however.

I flashed the bios to the most updated version as well.

I looked in the drivers folder for the other two drivers and ran a search. Are they hiding somewhere else?

Most excellent. We will wait for any problems to happen from here, and deal with things then if necessary.

(Just make sure you've set Optimized Defaults and save, in the new bios.)

If there are any new crashes, please post them. If not, congrats on fixing the machine.

GMan · May 2, 2012

Another thing:

I don't wish to over-complicate things for you, but if you're feeling confident enough that you know how to set up a dual-boot system with Windows 8 also, I wouldn't mind debugging that again for you if necessary.

There are excellent tutorials on this site that can show you how. Or if you honestly really want 8, and only 8, then you can upgrade your current Windows 7 to it now. That is not going to help nor hurt our current efforts, as long as you don't install any more 3rd party software until the issue is completely fixed.

Or keep Windows 7 alone as is.

Your choice, and any of them are good from here. (No 3rd party non-physical hardware drivers!!!

)

iskandar · Oct 27, 2012

Hi!
I've been using Windows 8 for about a week and today, out of nowhere, i got the blue screen and the clock_watchdog_timeout error message.

This is the archive containing the crash dump files.

I'd be very grateful if you could help me

Clock_watchdog_timeout

New Member

My Computer

Banned

My Computer

New Member

My Computer

Banned

My Computer

Banned

My Computer

New Member

My Computer

Banned

My Computer

New Member

My Computer

Banned

My Computer

New Member

My Computer

Banned

My Computer

New Member

My Computer

Banned

My Computer

Banned

My Computer

Banned

My Computer