Windows 8 and 8.1 Forums


Random CLOCK_WATCHDOG_TIMEOUT BSOD (Win 8.1)

  1. #1

    Random CLOCK_WATCHDOG_TIMEOUT BSOD (Win 8.1)


    Hey guys,


    I am getting BSODs all the time. While playing games, watching videos or just while idling. I am very tired of it :(


    Please help to find the cause of failures so that I can fix it. (hardware configuration, outdated drivers or defective equipment)


    File uploaded, Hope somebody can help. Sorry for the google translation :)


    Attachment 64606


    UPD:
    -BIOS updated as possible (09/21/10 ver 1408 asus p6t motherboard)
    -Windows updated today
    -Graphics adapter device driver updated recently (nvidia 353.30)
    Last edited by Watch Dogs; 26 Mar 2017 at 13:46.

      My System SpecsSystem Spec

  2. #2



    BSOD Kernel Dump Analyst
    Posts : 2,274
    Windows 10 Pro


    If nobody else helps you in the meantime that I'm away, then I'll try to help you.
      My System SpecsSystem Spec

  3. #3



    BSOD Kernel Dump Analyst
    Posts : 2,274
    Windows 10 Pro


    I have taken a look into the files from this month.
    Most common: Clock Watchdog Timeout
    This error could be caused by the following:
    1. 1. BIOS bug
    2. 2. A driver problem
    3. 3. A hardware defect: tempterature, dust, voltage etc.


    Have you updated your BIOS before or after the last few crashes?

    Please use driver verifier to identify if any driver is causing problems. Read carefully the instructions. Sometimes it may go wrong with driver verifier, the instructions give you the possibility to recover windows when it goes wrong.
    Driver Verifier Settings


    The following is for information purposes only.
    Code:
    The following information contains the relevant information from the blue screen analysis: 
    **************************Sat Aug 8 11:50:52.511 2015 (UTC + 2:00)************************** 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64 
    
    System Uptime:0 days 0:09:12.265 
    
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE ) 
    
    BugCheck 101, {18, 0, ffffd0014b000180, 4} 
    BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101) 
    
    Arguments: 
    Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks. 
    Arg2: 0000000000000000, 0. 
    Arg3: ffffd0014b000180, The PRCB address of the hung processor. 
    Arg4: 0000000000000004, 0. 
    BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC 
    
    PROCESS_NAME: System 
    
    FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE 
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` 
    **************************Sat Aug 8 11:40:56.590 2015 (UTC + 2:00)************************** 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64 
    
    System Uptime:0 days 0:47:54.344 
    
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE ) 
    
    BugCheck 101, {18, 0, ffffd00071e00180, 4} 
    BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101) 
    
    Arguments: 
    Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks. 
    Arg2: 0000000000000000, 0. 
    Arg3: ffffd00071e00180, The PRCB address of the hung processor. 
    Arg4: 0000000000000004, 0. 
    BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC 
    
    PROCESS_NAME: csgo.exe 
    
    FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE 
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` 
    **************************Sat Aug 8 10:51:48.512 2015 (UTC + 2:00)************************** 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64 
    
    System Uptime:0 days 1:19:48.265 
    
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE ) 
    
    BugCheck 101, {18, 0, ffffd00077000180, 4} 
    BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101) 
    
    Arguments: 
    Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks. 
    Arg2: 0000000000000000, 0. 
    Arg3: ffffd00077000180, The PRCB address of the hung processor. 
    Arg4: 0000000000000004, 0. 
    BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC 
    
    PROCESS_NAME: System 
    
    FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE 
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` 
    **************************Sat Aug 8 09:32:03.426 2015 (UTC + 2:00)************************** 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64 
    
    System Uptime:0 days 0:00:03.180 
    
    Probably caused by :GenuineIntel 
    
    BugCheck 124, {0, ffffe001e3b5d4f8, 0, 0} 
    BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124) 
    
    Arguments: 
    Arg1: 0000000000000000, Machine Check Exception 
    Arg2: ffffe001e3b5d4f8, Address of the WHEA_ERROR_RECORD structure. 
    Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value. 
    Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value. 
    BUGCHECK_STR: 0x124_GenuineIntel 
    
    PROCESS_NAME: System 
    
    FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE_PRV 
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` 
    **************************Sat Aug 8 09:30:16.261 2015 (UTC + 2:00)************************** 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64 
    
    System Uptime:0 days 9:27:35.015 
    
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE ) 
    
    BugCheck 101, {18, 0, ffffd0015f000180, 4} 
    BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101) 
    
    Arguments: 
    Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks. 
    Arg2: 0000000000000000, 0. 
    Arg3: ffffd0015f000180, The PRCB address of the hung processor. 
    Arg4: 0000000000000004, 0. 
    BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC 
    
    PROCESS_NAME: chrome.exe 
    
    FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE 
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` 
    **************************Sat Aug 8 00:02:05.528 2015 (UTC + 2:00)************************** 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64 
    
    System Uptime:0 days 2:46:18.282 
    
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE ) 
    
    BugCheck 101, {18, 0, ffffd0012ca00180, 4} 
    BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101) 
    
    Arguments: 
    Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks. 
    Arg2: 0000000000000000, 0. 
    Arg3: ffffd0012ca00180, The PRCB address of the hung processor. 
    Arg4: 0000000000000004, 0. 
    BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC 
    
    PROCESS_NAME: System 
    
    FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE 
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` 
    **************************Fri Aug 7 19:40:49.513 2015 (UTC + 2:00)************************** 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64 
    
    System Uptime:0 days 0:39:54.266 
    
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE ) 
    
    BugCheck 101, {18, 0, ffffd000bcc00180, 4} 
    BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101) 
    
    Arguments: 
    Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks. 
    Arg2: 0000000000000000, 0. 
    Arg3: ffffd000bcc00180, The PRCB address of the hung processor. 
    Arg4: 0000000000000004, 0. 
    BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC 
    
    PROCESS_NAME: csgo.exe 
    
    FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE 
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` 
    **************************Fri Aug 7 19:00:08.511 2015 (UTC + 2:00)************************** 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64 
    
    System Uptime:0 days 2:34:30.266 
    
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE ) 
    
    BugCheck 101, {18, 0, ffffd001b1000180, 4} 
    BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101) 
    
    Arguments: 
    Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks. 
    Arg2: 0000000000000000, 0. 
    Arg3: ffffd001b1000180, The PRCB address of the hung processor. 
    Arg4: 0000000000000004, 0. 
    BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC 
    
    PROCESS_NAME: System 
    
    FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE 
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` 
    **************************Fri Aug 7 02:09:46.667 2015 (UTC + 2:00)************************** 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64 
    
    System Uptime:0 days 3:43:06.422 
    
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE ) 
    
    BugCheck 101, {18, 0, ffffd00128600180, 4} 
    BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101) 
    
    Arguments: 
    Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks. 
    Arg2: 0000000000000000, 0. 
    Arg3: ffffd00128600180, The PRCB address of the hung processor. 
    Arg4: 0000000000000004, 0. 
    BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC 
    
    PROCESS_NAME: System 
    
    FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE 
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` 
    **************************Thu Aug 6 22:26:01.513 2015 (UTC + 2:00)************************** 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64 
    
    System Uptime:0 days 9:52:48.266 
    
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE ) 
    
    BugCheck 101, {18, 0, ffffd00020600180, 4} 
    BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101) 
    
    Arguments: 
    Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks. 
    Arg2: 0000000000000000, 0. 
    Arg3: ffffd00020600180, The PRCB address of the hung processor. 
    Arg4: 0000000000000004, 0. 
    BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC 
    
    PROCESS_NAME: csgo.exe 
    
    FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE 
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` 
    **************************Thu Aug 6 12:28:45.761 2015 (UTC + 2:00)************************** 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64 
    
    System Uptime:0 days 1:22:17.516 
    
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE ) 
    
    BugCheck 101, {18, 0, ffffd001e33c7180, 2} 
    BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101) 
    
    Arguments: 
    Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks. 
    Arg2: 0000000000000000, 0. 
    Arg3: ffffd001e33c7180, The PRCB address of the hung processor. 
    Arg4: 0000000000000002, 0. 
    BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC 
    
    PROCESS_NAME: csgo.exe 
    
    FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE 
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` 
    **************************Thu Aug 6 11:06:31.192 2015 (UTC + 2:00)************************** 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64 
    
    System Uptime:0 days 0:00:02.947 
    
    Probably caused by :GenuineIntel 
    
    BugCheck 124, {0, ffffe000f2551788, 0, 0} 
    BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124) 
    
    Arguments: 
    Arg1: 0000000000000000, Machine Check Exception 
    Arg2: ffffe000f2551788, Address of the WHEA_ERROR_RECORD structure. 
    Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value. 
    Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value. 
    BUGCHECK_STR: 0x124_GenuineIntel 
    
    PROCESS_NAME: System 
    
    FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE_PRV 
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` 
    **************************Wed Aug 5 18:26:02.527 2015 (UTC + 2:00)************************** 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64 
    
    System Uptime:0 days 3:03:36.281 
    
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE ) 
    
    BugCheck 101, {18, 0, ffffd000a9400180, 4} 
    BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101) 
    
    Arguments: 
    Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks. 
    Arg2: 0000000000000000, 0. 
    Arg3: ffffd000a9400180, The PRCB address of the hung processor. 
    Arg4: 0000000000000004, 0. 
    BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC 
    
    PROCESS_NAME: csgo.exe 
    
    FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE 
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` 
    **************************Wed Aug 5 15:21:32.652 2015 (UTC + 2:00)************************** 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64 
    
    System Uptime:0 days 18:19:34.406 
    
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE ) 
    
    BugCheck 101, {18, 0, ffffd0014fc00180, 4} 
    BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101) 
    
    Arguments: 
    Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks. 
    Arg2: 0000000000000000, 0. 
    Arg3: ffffd0014fc00180, The PRCB address of the hung processor. 
    Arg4: 0000000000000004, 0. 
    BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC 
    
    PROCESS_NAME: System 
    
    FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE 
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` 
    **************************Tue Aug 4 18:59:38.513 2015 (UTC + 2:00)************************** 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64 
    
    System Uptime:0 days 0:31:36.266 
    
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE ) 
    
    BugCheck 101, {18, 0, ffffd00020600180, 4} 
    BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101) 
    
    Arguments: 
    Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks. 
    Arg2: 0000000000000000, 0. 
    Arg3: ffffd00020600180, The PRCB address of the hung processor. 
    Arg4: 0000000000000004, 0. 
    BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC 
    
    PROCESS_NAME: System 
    
    FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE 
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` 
    **************************Tue Aug 4 18:27:13.151 2015 (UTC + 2:00)************************** 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64 
    
    System Uptime:4 days 23:17:35.906 
    
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE ) 
    
    BugCheck 101, {18, 0, ffffd00174800180, 4} 
    BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101) 
    
    Arguments: 
    Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks. 
    Arg2: 0000000000000000, 0. 
    Arg3: ffffd00174800180, The PRCB address of the hung processor. 
    Arg4: 0000000000000004, 0. 
    BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC 
    
    PROCESS_NAME: csgo.exe 
    
    FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
      My System SpecsSystem Spec

Random CLOCK_WATCHDOG_TIMEOUT BSOD (Win 8.1)
Related Threads
Clock_Watchdog_Timeout BSOD at random times in BSOD Crashes and Debugging
I built my rig last year around this time and everything has been going fine when all of a sudden i have been getting clock_watchdog_timeout BSOD and i would love some help on how to solve this problem even if its confirming i need to replace my cpu thanks in advance.
Hello. I had Win 7 on my computer, after bought a new monitor, i decided to install Win8.1.Now i have Win8.1 Pro.I used to record Mount&Blade:Warband with OBS on Win7, was okay.But i started getting BSoD with an error CLOCK_WATCHDOG_TIMEOUT after i installed Win8.1.I tried some stuff to...
When upgrading to windows 10 my PC BSODs at around ~11% of the upgrade (copying files) with a CLOCK_WATCHDOG_TIMEOUT. I cannot manage to get the dump because it blue screens whilst updating and doesn't show up on BlueScreenView. If anyone could help with this problem it would be greatly appreciated...
BSOD - CLOCK_WATCHDOG_TIMEOUT error in BSOD Crashes and Debugging
I've been getting BSOD for months now... it used to be occasional, but lately it has started occurring several times a day. I've tried reinstalling OS a couple times now... not sure if its one of the device drivers or any software that is causing it. Attaching the necessary info. Please help.
So yeah, i┤m "new" here. Actually been using Seven forums for a while. Friend of mine been having a lot of bluescreens lately and unfortunately i have been unable pinpoint what the problem is so i┤m asking your help and assistance. There have been several different bluescreen which come up while...
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...
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...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook