Windows 8 and 8.1 Forums

Clock_watchdog_timeout

  1. #1


    Posts : 4
    Windows 8

    Clock_watchdog_timeout


    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.

      My System SpecsSystem Spec

  2. #2


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


    SSD's were temperamental when they first came out, but their reliability has improved greatly over the last year or two. There are 2 things that MUST be checked on systems with BSOD's and SSD's:
    1) That the SSD firmware is the latest available for the SSD
    2) That the storage controller drivers on the motherboard are the most recent. They must date from late 2012 or later. This is ALL controllers, not just the one that the SSD is attached to.
    Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

    Alpham264.sys Tue Mar 20 05:51:03 2007 (45FFAE87)
    Ideazon ZBoard/Ideazon Fang MM USB HID driver
    http://www.carrona.org/drivers/driver.php?id=Alpham264.sys

    Alpham164.sys Mon Jul 23 03:57:03 2007 (46A45F4F)
    Ideazon ZBoard/Ideazon ZBoard Fang MM USB HID
    http://www.carrona.org/drivers/driver.php?id=Alpham164.sys

    HECIx64.sys Tue Oct 19 19:33:43 2010 (4CBE2AD7)
    Intel Management Engine Interface
    http://www.carrona.org/drivers/driver.php?id=HECIx64.sys

    Rt630x64.sys Wed Oct 19 08:12:55 2011 (4E9EBEC7)
    Realtek PCI/PCIe Adapters
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys

    In general these errors are caused by one of the following:
    - BIOS
    - Hardware
    - drivers

    We rule out drivers first, then we start on hardware diagnostics. If you'd like to get a headstart on the hardware diagnostics, please follow the instructions here: Hardware Diagnostics

    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Tue Aug 27 08:55:08.415 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082713-13968-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 15:00:50.110
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    BugCheck 101, {30, 0, fffff88002ad1180, 3}
    BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
    Arguments: 
    Arg1: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: fffff88002ad1180, The PRCB address of the hung processor.
    Arg4: 0000000000000003, 0.
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
    CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
    MaxSpeed:     3300
    CurrentSpeed: 3302
      BIOS Version                  P2.30
      BIOS Release Date             06/29/2012
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Aug 26 17:51:43.805 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082613-13750-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16628.amd64fre.win8_gdr.130531-1504
    System Uptime:3 days 0:51:25.500
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    BugCheck 101, {30, 0, fffff88002ad1180, 3}
    BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
    Arguments: 
    Arg1: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: fffff88002ad1180, The PRCB address of the hung processor.
    Arg4: 0000000000000003, 0.
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
    PROCESS_NAME:  payday2_win32_
    FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
    CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
    MaxSpeed:     3300
    CurrentSpeed: 3302
      BIOS Version                  P2.30
      BIOS Release Date             06/29/2012
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    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.
    Code:
    **************************Tue Aug 27 08:55:08.415 2013 (UTC - 4:00)**************************
    Alpham264.sys               Tue Mar 20 05:51:03 2007 (45FFAE87)
    Alpham164.sys               Mon Jul 23 03:57:03 2007 (46A45F4F)
    HECIx64.sys                 Tue Oct 19 19:33:43 2010 (4CBE2AD7)
    Rt630x64.sys                Wed Oct 19 08:12:55 2011 (4E9EBEC7)
    igdkmd64.sys                Fri May 25 00:24:33 2012 (4FBF0981)
    intelppm.sys                Mon Nov  5 22:55:02 2012 (50988A16)
    ISCTD64.sys                 Tue Nov 27 14:52:34 2012 (50B51A02)
    SbieDrv.sys                 Sun Dec 16 06:24:57 2012 (50CDAF89)
    dump_storahci.sys           Fri Mar  1 21:15:44 2013 (513160D0)
    vjoy.sys                    Tue Mar 19 14:16:09 2013 (5148AB69)
    nvlddmkm.sys                Fri Jun 21 05:06:16 2013 (51C41788)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Aug 26 17:51:43.805 2013 (UTC - 4:00)**************************
    cpuz136_x64.sys             Sat Oct 27 13:24:41 2012 (508C18D9)
    
    http://www.carrona.org/drivers/driver.php?id=Alpham264.sys
    http://www.carrona.org/drivers/driver.php?id=Alpham164.sys
    http://www.carrona.org/drivers/driver.php?id=HECIx64.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=ISCTD64.sys
    http://www.carrona.org/drivers/driver.php?id=SbieDrv.sys
    http://www.carrona.org/drivers/driver.php?id=dump_storahci.sys
    vjoy.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=cpuz136_x64.sys
      My System SpecsSystem Spec

Clock_watchdog_timeout
Related Threads
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...
Clock_watchdog_timeout in BSOD Crashes and Debugging
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.
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 - Pastebin.com
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