none
BugCheck 101 : CLOCK_WATCHDOG_TIMEOUT (101) RRS feed

  • Question

  • Hi,

    I got a BSOD page with the following error  :

    Loading Dump File [C:\Windows\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available

    Symbol search path is: symsrv*symsrv.dll*C:\Windows\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (32 procs) Free x64
    Product: WinNt, suite: TerminalServer EmbeddedNT SingleUserTS
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Machine Name:
    Kernel base = 0xfffff800`02a54000 PsLoadedModuleList = 0xfffff800`02c976d0
    Debug session time: Wed Dec  4 15:30:17.032 2013 (UTC + 1:00)
    System Uptime: 0 days 1:10:50.450
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ............
    Loading User Symbols

    Loading unloaded module list
    ......

    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

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

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


    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_20_PROC

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  d

    STACK_TEXT: 
    fffff880`03f2a4f8 fffff800`02b20a4a : 00000000`00000101 00000000`00000007 00000000`00000000 fffff880`02f72180 : nt!KeBugCheckEx
    fffff880`03f2a500 fffff800`02ad36f7 : fffffa80`00000000 fffff800`00000002 00000000`00002711 fffffa80`154cd7f0 : nt! ?? ::FNODOBFM::`string'+0x4e3e
    fffff880`03f2a590 fffff800`02a15895 : fffff800`02a3b460 fffff880`03f2a740 fffff800`02a3b460 fffffa80`00000000 : nt!KeUpdateSystemTime+0x377
    fffff880`03f2a690 fffff800`02ac6113 : 00000000`4a8ad775 fffff800`02c44e80 fffff800`02c44e80 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
    fffff880`03f2a6c0 fffff800`02ad8a08 : fffff800`02c44e80 fffff880`00000001 00000000`00000000 fffff980`0e856fc0 : nt!KiInterruptDispatchNoLock+0x163
    fffff880`03f2a850 fffff800`02b78c36 : 00000000`00000000 fffff800`02c44e80 fffff980`0e856fc0 fffff880`03f2a980 : nt!KiIpiSendRequestEx+0x98
    fffff880`03f2a890 fffff800`02bd1a79 : 00000000`00000001 fffff880`03f2a950 fffff6fc`c00742b0 fffff980`0e856fc0 : nt!KeFlushSingleTb+0x126
    fffff880`03f2a910 fffff800`02bfc93b : fffff800`02a54000 00000000`20206f49 00000000`000d28c1 fffff980`0e856fc0 : nt!MmFreeSpecialPool+0x349
    fffff880`03f2aa60 fffff880`015943e7 : 00000000`000000ff fffff980`0e856fc0 fffffa80`198fb040 fffff980`0e856fc0 : nt!ExDeferredFreePool+0xf33
    fffff880`03f2ab10 fffff800`02dc01d3 : 00000000`00000001 00000000`00000001 00000000`00000000 fffffa80`198fb040 : NETIO!TickWorker+0x17
    fffff880`03f2ab40 fffff800`02ad3261 : fffff800`02dace00 fffffa80`198fb001 00000000`00000000 fffffa80`198fb040 : nt!IopProcessWorkItem+0x23
    fffff880`03f2ab70 fffff800`02d662ea : 00000000`00000000 fffffa80`198fb040 00000000`00000080 fffffa80`198c6ae0 : nt!ExpWorkerThread+0x111
    fffff880`03f2ac00 fffff800`02aba8e6 : fffff880`03524180 fffffa80`198fb040 fffff880`0352f6c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`03f2ac40 00000000`00000000 : fffff880`03f2b000 fffff880`03f25000 fffff880`03f2a8a0 00000000`00000000 : nt!KiStartSystemThread+0x16


    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_20_PROC_VRF_ANALYSIS_INCONCLUSIVE

    BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_20_PROC_VRF_ANALYSIS_INCONCLUSIVE

    Followup: MachineOwner
    ---------

    0: kd> ~2
    2: kd> !prcb
    PRCB for Processor 2 at fffff88002f72180:
    Current IRQL -- 0
    Threads--  Current fffffa801d624060 Next 0000000000000000 Idle fffff88002f7d6c0
    Processor Index 2 Number (0, 2) GroupSetMember 4
    Interrupt Count -- 013521b9
    Times -- Dpc    00000000 Interrupt 00000058
             Kernel 0003eeb8 User      000036e7

    WhoCrashed (www.resplendence.com/support) reports that the problem may be caused by ntoskrnl.exe and hal.dll. But I'm not convinced, because I'm using a new hardware/driver couple. I enabled the Windows Driver Verifier on the driver, but no error is reported. Any idea to track those kind of errors? Does the PCIe can block my CPU?

    Does the http://support.microsoft.com/kb/955076/fr hotfix may solve this issue ? (CPU = Intel Xeon E5 2670 / SandyBrigde-EP/EX)

    Thanx.
    Thursday, December 5, 2013 3:07 PM

All replies

  • What Windows OS are you running? Are you running Windows Embedded Standard 7?

    www.annabooks.com / www.seanliming.com / Book Author - Pro Guide to WE8S, Pro Guide to WES 7, Pro Guide to POS for .NET

    Thursday, December 5, 2013 3:45 PM
    Moderator
  • Hi Sean,

    Yes. I'm using a Win7Emb/Standard SP1.

    I have more information :

       [1] If I run my DMA R/W stress test application on my Xeon machine (with HT enabled), then I can see the BSOD.

       [2] If I run my DMA R/W stress test application on my Xeon machine (with HT disabled), then I do not see the BSOD (yet) (duration > [1]) - test still running. I will see results tomorrow morning.

       [3] If I run my DMA R/W stress test application on my Core i7 machine (with HT enabled), then I do not see the BSOD (yet) (duration > [1]) - test still running. I will see results tomorrow morning.


    Thanx.

    Thursday, December 5, 2013 6:17 PM
  • Hot news !

    [2] has failed with BSOD, but looks working longer (???). Need more tests.
    Thursday, December 5, 2013 6:25 PM
  • Have you pulled down all the updates using WEDU into your distribution share?

    Do you have all the drivers installed for both platforms?


    www.annabooks.com / www.seanliming.com / Book Author - Pro Guide to WE8S, Pro Guide to WES 7, Pro Guide to POS for .NET

    Thursday, December 5, 2013 7:44 PM
    Moderator
  • I do not install WEDU. I use Windows Update.
    Thursday, December 5, 2013 9:03 PM
  • I installed WEDU 1.1.92.0.

    When I run the WEDU on the Windows Embedded system, WEDU fails with the following error : "not supported product detected"... A new demonstration of the Murphy's Law ;)

    The system information utility confirms that the OS is a Windows Embedded Standard system, as show below :
    OS Name	Microsoft Windows Embedded Standard
    Version	6.1.7601 Service Pack 1 Build 7601
    Other OS Description 	Not Available
    OS Manufacturer	Microsoft Corporation
    System Name	TITANSDI-3
    System Manufacturer	INSYDE
    System Model	Romley
    System Type	x64-based PC
    Processor	Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz, 2600 Mhz, 8 Core(s), 16 Logical Processor(s)
    Processor	Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz, 2600 Mhz, 8 Core(s), 16 Logical Processor(s)
    BIOS Version/Date	Insyde Corp. BIOS_SCB_2025.02.17, 5/24/2012
    SMBIOS Version	2.7
    Windows Directory	C:\Windows
    System Directory	C:\Windows\system32
    Boot Device	\Device\HarddiskVolume1
    Locale	United States
    Hardware Abstraction Layer	Version = "6.1.7601.17514"
    User Name	Not Available
    Time Zone	Romance Standard Time
    Installed Physical Memory (RAM)	32.0 GB
    Total Physical Memory	32.0 GB
    Available Physical Memory	30.4 GB
    Total Virtual Memory	45.9 GB
    Available Virtual Memory	44.2 GB
    Page File Space	14.0 GB
    Page File	C:\pagefile.sys
    



    Monday, December 9, 2013 5:20 PM
  • WEDU is to be installed on Windows desktop and server so you can update the distribution share with the latest security updates and hot fixes.  I don't think it was intended to be installed on WES 7.

    www.annabooks.com / www.seanliming.com / Book Author - Pro Guide to WE8S, Pro Guide to WES 7, Pro Guide to POS for .NET

    Tuesday, December 10, 2013 4:57 PM
    Moderator
  • Hi Sean,

    I installed the WEDU on my WinES7 test machine and on my Win7Pro workstation, and both display the same error message. FYI, all machines are into the same domain.

    Thanx.
    Tuesday, December 10, 2013 5:06 PM