Clock_watchdog_timeout

Suiadan · Jul 18, 2013

I get this blue screen every so often (it happened when I first tried typing this too, haha) and they started about a day ago. From other threads on this it looks like a driver problem, but I have no idea WTF I'm doing so any help would be appreciated.

usasma · Jul 19, 2013

You have a 802.11 USB Wireless LAN Card:

I do not recommend using wireless USB network devices. Especially in Win7/Win8 systems.
These wireless USB devices have many issues with Win7(and I suspect with Win8) - using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Win7/Win8 drivers - DO NOT use Vista drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

Drivers for the Nexus S aren't installed. Please remove the device from your system while we're testing. Feel free to put it back on your system and install the appropriate drivers once the system is stabilized.

I suspect hardware, so here's a list of free diagnostics to perform: Hardware Diagnostics

And, in case I'm wrong, please run Driver Verifier according to these instructions: Driver Verifier Settings

Please note that there are no 3rd party drivers listed. I also scanned the original output and there are no Windows drivers listed. Although this is strongly suggestive of hardware, I'm unsure of it's significance as I've never seen this before.

Analysis:
The following is for informational purposes only.

Code:

[FONT=lucida console]**************************Thu Jul 18 11:47:48.330 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\071913-16894-01.dmp]
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Built by: [B]9200[/B].16628.amd64fre.win8_gdr.130531-1504
System Uptime:[B]0 days 0:34:11.991[/B]
Probably caused by :[B]Unknown_Image ( ANALYSIS_INCONCLUSIVE )[/B]
BugCheck [B]101, {31, 0, fffff8800125d180, 2}[/B]
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#Example"]CLOCK_WATCHDOG_TIMEOUT (101)[/URL]
Arguments: 
Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff8800125d180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

Clock_watchdog_timeout

Suiadan

New Member

My Computer

System One

usasma

Mr. Cranky Pants

My Computer

System One