Windows 8 and 8.1 Forums


Bsod: Clock_watchdog_timeout

  1. #1


    Posts : 2
    win8

    Bsod: Clock_watchdog_timeout


    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 nominal clock ticks.
    Arg2: 00000000, 0.
    Arg3: 8285f120, The PRCB address of the hung processor.
    Arg4: 00000003, 0.



    the problem occuerd when i want to restart the OS.
    Is this the problem of win8?

      My System SpecsSystem Spec

  2. #2


    Posts : 1,851
    8250 x86 + 7 SP1 x86 + Ubuntu 12.04 LTS x86


    Hi,

    Ouch. The machine is broken and there's nothing we can do, unfortunately.




    No, I'm only kidding.

    I've never seen these before so can't say for complete 100% sure, but I can say for complete 99.9999% sure instead:

    Code:
    start    end        module name
    a95f5000 a95f5b80   io         (deferred)             
        Image path: \??\C:\Windows\system32\drivers\io.sys
        Image name: io.sys
        Timestamp:        Sun Oct 11 18:58:15 1998 (36213807)
        CheckSum:         000073BD
        ImageSize:        00000B80
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Code:
    0: kd> lmvm dbgv
    start    end        module name
    ad0a1000 ad0a4d00   Dbgv       (deferred)             
        Image path: \??\C:\Windows\system32\Drivers\Dbgv.sys
        Image name: Dbgv.sys
        Timestamp:        Sat May 17 11:18:56 2008 (482EF760)
        CheckSum:         0000D5CD
        ImageSize:        00003D00
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4



    Delete those then reboot. Should be good to go.

    If it's well, enjoy. If not, please post again with a new crash dump.

    Code:
    BugCheck 101, {30, 0, 8285f120, 3}
    
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    
    
    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 nominal clock ticks.
    Arg2: 00000000, 0.
    Arg3: 8285f120, The PRCB address of the hung processor.
    Arg4: 00000003, 0.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  1c
    
    STACK_TEXT:  
    8953d90c 81b7d122 00000101 00000030 00000000 nt!KeBugCheckEx
    8953d984 81a43516 00052b49 00052b4a 81c2811b nt! ?? ::FNODOBFM::`string'+0xefa4
    8953d9e0 81fbcf8c 8953d9f8 81a71a20 ffffffff nt!KeUpdateTime+0x205
    8953da00 81fce2cd 8415c01b 000000d1 8953da98 hal!HalpTimerClockInterruptCommon+0x66
    8953da00 81a71a20 8415c01b 000000d1 8953da98 hal!HalpTimerClockInterrupt+0x199
    8953da98 81aaf260 88a00000 81c10a3c 00001825 nt!KxFlushEntireTb+0x111
    8953dae0 81aae73b 00000000 00000001 00000000 nt!KeFlushMultipleRangeTb+0x1ea
    8953dc80 81a5a518 00000002 0000000a 81c371c0 nt!MiFlushPteList+0x20
    8953dcbc 81a64d22 81c371c0 0000000a 00000100 nt!MiTrimOrAgeWorkingSet+0x93
    8953dd38 81a64a93 00000000 81a649de 83d63d40 nt!MiProcessWorkingSets+0x1a5
    8953dd74 81ca3080 00000000 64d41957 00000000 nt!MmWorkingSetManager+0x34
    8953ddb0 81b6a6d1 81a6493a 00000000 00000000 nt!PspSystemThreadStartup+0x4a
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
      My System SpecsSystem Spec

  3. #3


    Posts : 2
    win8


    Yes, it works well, thanks.
    Dbgv.sys is a component of DebugView
    Is it the problem of it and why? I want to know the reason.
    Thanks again.
      My System SpecsSystem Spec

  4. #4


    Posts : 1,851
    8250 x86 + 7 SP1 x86 + Ubuntu 12.04 LTS x86


    You're welcome. Glad to hear it.

    Very likely io.sys was the culprit. Thanks for telling us and enjoy.
      My System SpecsSystem Spec

Bsod: Clock_watchdog_timeout
Related Threads
So yeah, im "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 im asking your help and assistance. There have been several different bluescreen which come up while...
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...
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
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