locked
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC RRS feed

  • Question

  • 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: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: fffffa6001900180, The PRCB address of the hung processor.
    Arg4: 0000000000000001, 0.

    Debugging Details:
    ------------------


    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT_SERVER
    PROCESS_NAME:  notepad++.exe
    CURRENT_IRQL:  d
    STACK_TEXT:  
    fffffa60`032ed6d8 fffff800`022b5c26 : 00000000`00000101 00000000`00000019 00000000`00000000 fffffa60`01900180 : nt!KeBugCheckEx
    fffffa60`032ed6e0 fffff800`0224d18a : fffff800`027502d0 fffffa60`032ed800 fffffa80`907a2210 fffff800`027502d0 : nt! ?? ::FNODOBFM::`string'+0x2914
    fffffa60`032ed720 fffff800`0272dca8 : 00000000`71f4416a fffffa80`98cd8380 fffffa60`032edc20 fffff6fb`7da00008 : nt!KeUpdateSystemTime+0xea
    fffffa60`032ed750 fffff800`0224bd23 : fffffa80`00000020 00000000`00000001 fffffa60`032ed800 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8c
    fffffa60`032ed780 fffff800`022592d0 : fffff800`022a9763 00000000`00000001 fffff800`0224bdad 00000000`00000020 : nt!KiInterruptDispatchNoLock+0x93
    fffffa60`032ed918 fffff800`022a9763 : 00000000`00000001 fffff800`0224bdad 00000000`00000020 00000000`00000001 : nt!KiDispatchInterrupt
    fffffa60`032ed920 fffff800`0224bdad : 00000000`00000020 00000000`00000001 fffffa60`032ed9b0 00000000`00000000 : nt!KiDpcInterruptBypass+0x13
    fffffa60`032ed930 fffff800`02244f12 : fffffa80`905cc010 00000000`00000000 00000000`0007e548 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x11d
    fffffa60`032edac0 fffff800`0226f174 : 00000000`00000964 00000000`00002000 00000000`71f4416a fffffa80`90a31060 : nt!ExfAcquirePushLockExclusive+0xc2
    fffffa60`032edb30 fffff800`02254432 : 00000000`00000008 00000000`71f4416a 00000000`7efdd001 00000000`00000000 : nt!MmAccessFault+0x1a44
    fffffa60`032edc20 00000000`71f4416a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x2f2
    00000000`00128934 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x71f4416a


    STACK_COMMAND:  kb
    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: Unknown_Module
    IMAGE_NAME:  Unknown_Image
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
    BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
    Followup: MachineOwner

    Wednesday, October 10, 2018 12:24 PM

All replies

  • What does this have to do with Microsoft Virtual Server 2005?
    Wednesday, October 10, 2018 7:42 PM