locked
CLOCK_WATCHDOG_TIMEOUT_8_PROC BSOD RRS feed

  • Question

  • User getting this once every day:

    MODULE_NAME: nt

    FAULTING_MODULE: 83450000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  4f766ae5

    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    CURRENT_IRQL:  0

    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

    STACK_TEXT: 
    WARNING: Stack unwind information not available. Following frames may be wrong.
    a44430ac 834cba1f 00000101 00000019 00000000 nt+0xdee9c
    a44430e8 834cb06e 000186a0 00000000 00d85500 nt+0x7ba1f
    a4443128 834caf1b 83487c42 5097e018 00000000 nt+0x7b06e
    a4443180 834cfbb7 0000001b 0000001b 000000d1 nt+0x7af1b
    a4443194 83487c42 badb0d00 00000000 a44431c0 nt+0x7fbb7
    a4443224 835021a7 ff546000 00000002 a4443274 nt+0x37c42
    a4443304 834eeca9 c07faa38 00000002 00000002 nt+0xb21a7
    a4443344 8356f487 000006b9 00000021 89542e00 nt+0x9eca9
    a44433a8 834eb60d 00000021 00001020 00000ff0 nt+0x11f487
    a4443400 83570132 00000000 00000021 00001020 nt+0x9b60d
    a4443460 9aecc17e 00000021 00001018 6f746547 nt+0x120132
    a4443474 9aed3405 00001018 6f746547 00000000 win32k!_GetLayeredWindowAttributes+0xe2
    a4443488 9aeda1e9 00001008 6f746547 00000d0d win32k!SetProcDeviceRequest+0xf6
    a444370c 9aedc4dd fbfbf818 a44437e4 ff5efa68 win32k!GetPnpActionFromGuid+0x96
    a4443714 a44437e4 ff5efa68 a4443900 00000000 win32k!DeletePowerRequestList+0xf
    a4443a38 9ae6ba37 a4443bfc ff041700 ff04175c 0xa44437e4
    a4443ab4 9aebe266 02000000 ffbbe07c 00001004 win32k!SfnIMECONTROL+0x296
    a4443c24 8348e21c 000000ac 0019d9c4 0019d9d0 win32k!LookupDC+0xa
    a4443c34 77c37094 badb0d00 0019d9c4 00000000 nt+0x3e21c
    a4443c38 badb0d00 0019d9c4 00000000 00000000 0x77c37094
    a4443c3c 0019d9c4 00000000 00000000 00000000 0xbadb0d00
    a4443c40 00000000 00000000 00000000 00000000 0x19d9c4

    Tuesday, September 2, 2014 6:43 PM

All replies

  • Hi,

    We'll need a kernel-dump to properly debug this type of bug check as not information lies within the minidump. Please upload the kernel-dump to a 3rd party site such as Onedrive, Mediafire, etc.

    Kernel-dumps are located at C:\Windows and named MEMORY.DMP. If there is nothing there, you may need to enable generation of them - http://msdn.microsoft.com/en-us/library/windows/hardware/ff540128%28v=vs.85%29.aspx

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    Tuesday, September 2, 2014 10:39 PM
  • Hi,

    To add, for the BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC, please see:

    Bug Check 0x101: CLOCK_WATCHDOG_TIMEOUT

    The CLOCK_WATCHDOG_TIMEOUT bug check has a value of 0x00000101. This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.

    The cause of this kind BugCheck is the specified processor is not processing interrupts.  Typically, this occurs when the processor is nonresponsive or is deadlocked.

    For detailed information, please share us the dump file as Patrick Barker suggested.

    For information about how to recover from this error, see Resolving Blue Screen errors in Windows.

    Best regards


    Michael Shao
    TechNet Community Support

    Thursday, October 9, 2014 5:51 AM