Windows 8 and 8.1 Forums


CLOCK_WATCHDOG_TIMEOUT Error

  1. #1


    Posts : 3
    Windows 8 Pro 64bit

    CLOCK_WATCHDOG_TIMEOUT Error


    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.

    Edit Happened again upload newer version
    Last edited by thrx; 03 Dec 2012 at 05:26.

      My System SpecsSystem Spec

  2. #2


    Posts : 3
    Windows 8 Pro 64bit


    Bump. Please anyone help
    not sure if this helps

    On Tue 12/4/2012 8:31:50 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\120412-16796-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7B040)
    Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFF880032D1180, 0x3)
    Error: CLOCK_WATCHDOG_TIMEOUT
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time
    Last edited by thrx; 04 Dec 2012 at 03:36.
      My System SpecsSystem Spec

  3. #3


    Posts : 3
    Windows 8 Pro 64bit


    Code:
    Code:
    On Tue 12/4/2012 10:45:16  AM GMT your computer crashed
    crash dump file:  C:\Windows\Minidump\120412-13437-01.dmp
    This was probably caused by the  following module: ntoskrnl.exe (nt+0x7B040) 
    Bugcheck code: 0x101  (0x18, 0x0, 0xFFFFF8800325E180, 0x2)
    Error: CLOCK_WATCHDOG_TIMEOUT
    file path:  C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &  System
    Bug check description: This indicates that an expected clock interrupt  on a secondary processor, in a multi-processor system, was not received within  the allocated interval. 
    This appears to be a typical software driver bug and  is not likely to be caused by a hardware problem. This problem might be caused  by a thermal issue. 
    The crash took place in the Windows kernel. Possibly  this problem is caused by another driver that cannot be identified at this time.  
    
    
    
    On  Tue 12/4/2012 10:13:41 AM GMT your computer crashed
    crash dump file:  C:\Windows\Minidump\120412-16578-01.dmp
    This was probably caused by the  following module: ntoskrnl.exe (nt+0x7B040) 
    Bugcheck code: 0x101  (0x18, 0x0, 0xFFFFF8800325E180, 0x2)
    Error: CLOCK_WATCHDOG_TIMEOUT
    file path:  C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &  System
    Bug check description: This indicates that an expected clock interrupt  on a secondary processor, in a multi-processor system, was not received within  the allocated interval. 
    This appears to be a typical software driver bug and  is not likely to be caused by a hardware problem. This problem might be caused  by a thermal issue. 
    The crash took place in the Windows kernel. Possibly  this problem is caused by another driver that cannot be identified at this time.  
    
    
    
    On  Tue 12/4/2012 8:44:26 AM GMT your computer crashed
    crash dump file:  C:\Windows\Minidump\120412-16703-01.dmp
    This was probably caused by the  following module: intelppm.sys (intelppm+0x2600) 
    Bugcheck code: 0x1E  (0xFFFFFFFFC0000005, 0xFFFFF88006B53600, 0x0, 0x8)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path:  C:\Windows\system32\drivers\intelppm.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Processor Device  Driver
    Bug check description: This indicates that a kernel-mode program  generated an exception which the error handler did not catch.
    This appears to  be a typical software driver bug and is not likely to be caused by a hardware  problem. 
    The crash took place in a standard Microsoft module. Your system  configuration may be incorrect. Possibly this problem is caused by another  driver on your system that cannot be identified at this time.  
    
    
    
    On  Tue 12/4/2012 8:31:50 AM GMT your computer crashed
    crash dump file:  C:\Windows\Minidump\120412-16796-01.dmp
    This was probably caused by the  following module: ntoskrnl.exe (nt+0x7B040) 
    Bugcheck code: 0x101  (0x18, 0x0, 0xFFFFF880032D1180, 0x3)
    Error: CLOCK_WATCHDOG_TIMEOUT
    file path:  C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &  System
    Bug check description: This indicates that an expected clock interrupt  on a secondary processor, in a multi-processor system, was not received within  the allocated interval. 
    This appears to be a typical software driver bug and  is not likely to be caused by a hardware problem. This problem might be caused  by a thermal issue. 
    The crash took place in the Windows kernel. Possibly  this problem is caused by another driver that cannot be identified at this time.  
    
    
    
    On  Tue 12/4/2012 8:25:06 AM GMT your computer crashed
    crash dump file:  C:\Windows\Minidump\120412-17140-01.dmp
    This was probably caused by the  following module: intelppm.sys (0xFFFFF88006BE3977) 
    Bugcheck code:  0x50 (0xFFFFF880080E3000, 0x0, 0xFFFFF88006BE3977, 0x0)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path:  C:\Windows\system32\drivers\intelppm.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Processor Device  Driver
    Bug check description: This indicates that invalid system memory has  been referenced.
    This appears to be a typical software driver bug and is not  likely to be caused by a hardware problem. 
    The crash took place in a  standard Microsoft module. Your system configuration may be incorrect. Possibly  this problem is caused by another driver on your system that cannot be  identified at this time. 
    
    
    
    On Tue 12/4/2012 5:45:19 AM GMT your computer  crashed
    crash dump file: C:\Windows\Minidump\120312-16562-01.dmp
    This  was probably caused by the following module: ntoskrnl.exe (nt+0x7B040) 
    Bugcheck code: 0xA  (0x2800000033F, 0x2, 0x1, 0xFFFFF8029DCB47DA)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path:  C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &  System
    Bug check description: This indicates that Microsoft Windows or a  kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This  appears to be a typical software driver bug and is not likely to be caused by a  hardware problem. 
    The crash took place in the Windows kernel. Possibly this  problem is caused by another driver that cannot be identified at this time.  
    
    
    
    On  Mon 12/3/2012 10:19:18 AM GMT your computer crashed
    crash dump file:  C:\Windows\Minidump\120312-5625-01.dmp
    This was probably caused by the  following module: ntoskrnl.exe (nt+0x7B040) 
    Bugcheck code: 0x101  (0x18, 0x0, 0xFFFFF88002A5E180, 0x2)
    Error: CLOCK_WATCHDOG_TIMEOUT
    file path:  C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &  System
    Bug check description: This indicates that an expected clock interrupt  on a secondary processor, in a multi-processor system, was not received within  the allocated interval. 
    This appears to be a typical software driver bug and  is not likely to be caused by a hardware problem. This problem might be caused  by a thermal issue. 
    The crash took place in the Windows kernel. Possibly  this problem is caused by another driver that cannot be identified at this time.  
    
    
    
    On  Mon 12/3/2012 8:49:08 AM GMT your computer crashed
    crash dump file:  C:\Windows\Minidump\120312-8546-01.dmp
    This was probably caused by the  following module: Unknown  (0xFFFFF80028CE7040) 
    Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFF88000A5E180,  0x2)
    Error: CLOCK_WATCHDOG_TIMEOUT
    Bug check description: This  indicates that an expected clock interrupt on a secondary processor, in a  multi-processor system, was not received within the allocated interval. 
    This  appears to be a typical software driver bug and is not likely to be caused by a  hardware problem. This problem might be caused by a thermal issue. 
    A  third party driver was identified as the probable root cause of this system  error. 
    Google query: CLOCK_WATCHDOG_TIMEOUT
    
    On Mon 12/3/2012 8:49:08 AM GMT  your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was  probably caused by the following module: Unknown (0xFFFFF80028CE7040) 
    Bugcheck code: 0x101  (0x18, 0x0, 0xFFFFF88000A5E180, 0x2)
    Error: CLOCK_WATCHDOG_TIMEOUT
    Bug check description: This  indicates that an expected clock interrupt on a secondary processor, in a  multi-processor system, was not received within the allocated interval. 
    This  appears to be a typical software driver bug and is not likely to be caused by a  hardware problem. This problem might be caused by a thermal issue. 
    A  third party driver was identified as the probable root cause of this system  error. 
    Google query: CLOCK_WATCHDOG_TIMEOUT
    
      My System SpecsSystem Spec

CLOCK_WATCHDOG_TIMEOUT Error
Related Threads
Hello folks. :geek: I may of made break through with a previous problem of mine, so Im posting this on Windows Eight Forums and Ubuntu forums to get knowledge from both sides to confirm my speculation. I had done a recent fresh install of Windows 8.1 a few days back and now I am in need of...
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.
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 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