Windows 8 and 8.1 Forums


  1. #1

    Posts : 1
    Windows 8 64-bit


    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.

      My System SpecsSystem Spec

  2. #2

    Posts : 5,139
    Win8.1Pro - Finally!!!

    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.

    The following is for informational purposes only.
    **************************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: 9200.16628.amd64fre.win8_gdr.130531-1504
    System Uptime:0 days 0:34:11.991
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    BugCheck 101, {31, 0, fffff8800125d180, 2}
    BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
    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.
    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.
      My System SpecsSystem Spec

Related Threads
Solved Clock_watchdog_timeout in BSOD Crashes and Debugging
Blue screen started yesterday, both times I was playing a game. This is the first time I have had any bsod/lockups. Let me know if you need anymore info. Thanks for your time.
BSOD & Clock_Watchdog_Timeout in BSOD Crashes and Debugging
Hello fellas, Barely new windows 8 user on my 3.5 years old Dell Studio 1557 (not the least problematic series, for sure). So, I like Windows 8 so far, but I have been having BSOD lately with the Clock_Watchdog_Timeout error. Even though I have no clue, I suspect it could be something...
Solved Clock_watchdog_timeout in BSOD Crashes and Debugging
Hey, got some problems with my PC for 2 weeks now, I receive random BSOD with CLOCK_WATCHDOG_TIMEOUT error caused by hal.dll and ntoskrnl.exe. I reinstalled windows from scratch, 2 days worked fine, now I get the blue screen again and I cannot solve this :/ I attached W8 log collector archive,...
CLOCK_WATCHDOG_TIMEOUT Error in BSOD Crashes and Debugging
Hello guys I been getting this error like 6 times this week, when I installed Windows 8 pro 64bit. and have got it recently when I was editing with After effects. Your help would be greatly appreciated:confused:. Edit Happened again upload newer version
Clock_watchdog_timeout in BSOD Crashes and Debugging
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 -
Bsod: Clock_watchdog_timeout in BSOD Crashes and Debugging
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: 00000030, Clock interrupt time out interval in...
clock_watchdog_timeout in BSOD Crashes and Debugging
Every now and then my system stops working and I get a screen with this message before I need to turn off and restart. Anyone have any ideas what this message might mean? I never saw it at all in windows 7 which ran as stable as a rock.
Eight Forums Android App Eight Forums IOS App Follow us on Facebook