Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

More Info on Driver Writing and Debugging


The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.


Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/


Before Posting...

Please check out the Community Guidelines in the Announcements and Administration Category.

Windows 2008 R2 Issue

eric_tsangeric_tsang Member Posts: 31
Recently we upgraded some of our servers to Windows 2008 R2, one of the computer crashed from time as following, another one issue is: if I leave the computer for a few days, I come back and my mouse and keyboard don't work. Or, the right screen resolution changes to 640X480 and can't be reset. Or, run out of system resources and have to reboot.

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

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


BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: d

STACK_TEXT:
fffff880`023b4d88 fffff800`01c86443 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`0205d180 : nt!KeBugCheckEx
fffff880`023b4d90 fffff800`01ce25f7 : 00000000`00000000 fffff800`00000002 00000000`00002711 00000000`000000ff : nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff880`023b4e20 fffff800`01c29895 : fffff800`01c4e460 fffff880`023b4fd0 fffff800`01c4e460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`023b4f20 fffff800`01cd63f3 : fffff800`01e52e80 00000000`00000001 fffffa80`0b456250 fffffa80`0b456102 : hal!HalpHpetClockInterrupt+0x8d
fffff880`023b4f50 fffff800`01c992c9 : 00000000`00000000 00000000`00000000 00000000`00000000 ffff0000`0135a32e : nt!KiInterruptDispatchNoLock+0x163
fffff880`023b50e0 fffff800`01f7064f : 00000000`00000000 fffff880`023b5700 00000000`00000000 00000000`00000000 : nt!KeFlushProcessWriteBuffers+0x65
fffff880`023b5150 fffff800`01fd4a06 : fffff8a0`061340a8 00000000`0001ff58 fffff880`023b52e0 00000000`00000000 : nt!ExpGetProcessInformation+0x7f
fffff880`023b52a0 fffff800`01fd5e49 : fffff8a0`061340a8 fffffa80`6365734b 00000000`00000000 fffff880`023b5c20 : nt!ExpQuerySystemInformation+0xf14
fffff880`023b5640 fffff800`01cd9153 : fffff880`023b5710 fffff800`01cd80fd 00000000`00000001 fffffa80`09dfce70 : nt!NtQuerySystemInformation+0x4d
fffff880`023b5680 fffff800`01cd56f0 : fffff880`01826a9c 00000000`00000001 fffff880`023b5844 fffffa80`0b174270 : nt!KiSystemServiceCopyEnd+0x13
fffff880`023b5818 fffff880`01826a9c : 00000000`00000001 fffff880`023b5844 fffffa80`0b174270 fffff880`03f87d58 : nt!KiServiceLinkage
fffff880`023b5820 fffff880`0182656d : fffffa80`09dfce70 00000000`00000000 fffff800`20206f49 fffff800`01ce4ac1 : cng!GatherRandomKey+0x22c
fffff880`023b5be0 fffff800`01fd3541 : 00000000`00000000 fffffa80`14771a00 fffffa80`14771a00 fffffa80`09a48b60 : cng!scavengingWorkItemRoutine+0x3d
fffff880`023b5c80 fffff800`01ce7161 : fffff800`01e7d500 fffff800`01fd3504 fffffa80`09a48b60 00000000`00000000 : nt!IopProcessWorkItem+0x3d
fffff880`023b5cb0 fffff800`01f7d166 : 407c407c`d145d145 fffffa80`09a48b60 00000000`00000080 fffffa80`09a3e040 : nt!ExpWorkerThread+0x111
fffff880`023b5d40 fffff800`01cb8486 : fffff880`0213f180 fffffa80`09a48b60 fffff880`0214a0c0 b04cb04c`bf70bf70 : nt!PspSystemThreadStartup+0x5a
fffff880`023b5d80 00000000`00000000 : fffff880`023b6000 fffff880`023b0000 fffff880`023b5410 00000000`00000000 : nt!KxStartSystemThread+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_8_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner

Anyone any suggestion?

Thanks
Eric

Comments

  • Pavel_LebedinskyPavel_Lebedinsky Member - All Emails Posts: 435
    > CLOCK_WATCHDOG_TIMEOUT (101)
    > Arg3: fffff8800205d180, The PRCB address of the hung processor.

    You need to get the stack trace for the stuck processor. Use "dt nt!_KPRCB
    fffff8800205d180 Number" to get the processor number.

    > Or, the right screen resolution changes to 640X480 and can't be reset.
    > Or, run out of system resources and have to reboot.

    What's the output of !vm ?

    --
    Pavel Lebedinsky/Windows Kernel Test
    This posting is provided "AS IS" with no warranties, and confers no rights.
  • eric_tsangeric_tsang Member Posts: 31
    "dt nt!_KPRCB fffff8800205d180 Number" return "+0x024 Number : 2"

    I dump all processors stack trace as following:

    !running

    System Processors: (00000000000000ff)
    Idle Processors: (00000000000000da) (0000000000000000) (0000000000000000) (0000000000000000)

    Prcbs Current Next
    0 fffff80001e52e80 fffffa8009a48b60 fffffa800babaae0 ................
    2 fffff8800205d180 fffff880020680c0 fffffa80100b6b60 ................
    5 fffff880021b0180 fffffa800fc5eb60 ................

    1: kd> !cpuinfo
    CP F/M/S Manufacturer MHz PRCB Signature MSR 8B Signature Features
    0 6,26,5 GenuineIntel 2666 0000001100000000 211b3dfe
    1 6,26,5 GenuineIntel 2666 0000001100000000 211b3dfe
    2 6,26,5 GenuineIntel 2666 0000001100000000 211b3dfe
    3 6,26,5 GenuineIntel 2666 0000001100000000 211b3dfe
    4 6,26,5 GenuineIntel 2666 0000001100000000 211b3dfe
    5 6,26,5 GenuineIntel 2666 0000001100000000 211b3dfe
    6 6,26,5 GenuineIntel 2666 0000001100000000 211b3dfe
    7 6,26,5 GenuineIntel 2666 0000001100000000 211b3dfe
    Cached Update Signature 0000001100000000
    Initial Update Signature 0000001100000000
    1: kd> !cpuid
    CP F/M/S Manufacturer MHz
    0 6,26,5 GenuineIntel 2666
    1 6,26,5 GenuineIntel 2666
    2 6,26,5 GenuineIntel 2666
    3 6,26,5 GenuineIntel 2666
    4 6,26,5 GenuineIntel 2666
    5 6,26,5 GenuineIntel 2666
    6 6,26,5 GenuineIntel 2666
    7 6,26,5 GenuineIntel 2666
    1: kd> 1k
    Child-SP RetAddr Call Site
    fffff880`009d9ca0 fffff800`01ce26cc nt!PoIdle+0x51f
    fffff880`009d9d80 00000000`00000000 nt!KiIdleLoop+0x2c
    1: kd> 2k
    Child-SP RetAddr Call Site
    fffff880`02085b88 fffff800`01c33401 hal!HalpHalt+0x1
    fffff880`02085b90 fffff800`01c26380 hal!HalpResetThisProcessor+0x1dd
    fffff880`02085bc0 fffff800`01cd63f3 hal!HalpApicRebootService+0x58
    fffff880`02085bf0 fffff800`01ce26d2 nt!KiInterruptDispatchNoLock+0x163
    fffff880`02085d80 00000000`00000000 nt!KiIdleLoop+0x32
    1: kd> 3k
    Child-SP RetAddr Call Site
    fffff880`020f6ca0 fffff800`01ce26cc nt!PoIdle+0x51f
    fffff880`020f6d80 00000000`00000000 nt!KiIdleLoop+0x2c
    1: kd> 4k
    Child-SP RetAddr Call Site
    fffff880`02167ca0 fffff800`01ce26cc nt!PoIdle+0x51f
    fffff880`02167d80 00000000`00000000 nt!KiIdleLoop+0x2c
    1: kd> 5k
    *** WARNING: Unable to verify timestamp for win32k.sys
    Child-SP RetAddr Call Site
    fffff880`0e57ac18 fffff800`01cd9153 win32k!NtUserPostMessage+0x3
    fffff880`0e57ac20 00000000`74c7fcba nt!KiSystemServiceCopyEnd+0x13
    00000000`068ae778 00000000`00000000 0x74c7fcba
    1: kd> 6k
    Child-SP RetAddr Call Site
    fffff880`0225bca0 fffff800`01ce26cc nt!PoIdle+0x51f
    fffff880`0225bd80 00000000`00000000 nt!KiIdleLoop+0x2c
    1: kd> 7k
    Child-SP RetAddr Call Site
    fffff880`022ccca0 fffff800`01ce26cc nt!PoIdle+0x51f
    fffff880`022ccd80 00000000`00000000 nt!KiIdleLoop+0x2c
    1: kd> 0k
    Child-SP RetAddr Call Site
    fffff880`023b4d88 fffff800`01c86443 nt!KeBugCheckEx
    fffff880`023b4d90 fffff800`01ce25f7 nt! ?? ::FNODOBFM::`string'+0x4e3e
    fffff880`023b4e20 fffff800`01c29895 nt!KeUpdateSystemTime+0x377
    fffff880`023b4f20 fffff800`01cd63f3 hal!HalpHpetClockInterrupt+0x8d
    fffff880`023b4f50 fffff800`01c992c9 nt!KiInterruptDispatchNoLock+0x163
    fffff880`023b50e0 fffff800`01f7064f nt!KeFlushProcessWriteBuffers+0x65
    fffff880`023b5150 fffff800`01fd4a06 nt!ExpGetProcessInformation+0x7f
    fffff880`023b52a0 fffff800`01fd5e49 nt!ExpQuerySystemInformation+0xf14
    fffff880`023b5640 fffff800`01cd9153 nt!NtQuerySystemInformation+0x4d
    fffff880`023b5680 fffff800`01cd56f0 nt!KiSystemServiceCopyEnd+0x13
    fffff880`023b5818 fffff880`01826a9c nt!KiServiceLinkage
    fffff880`023b5820 fffff880`0182656d cng!GatherRandomKey+0x22c
    fffff880`023b5be0 fffff800`01fd3541 cng!scavengingWorkItemRoutine+0x3d
    fffff880`023b5c80 fffff800`01ce7161 nt!IopProcessWorkItem+0x3d
    fffff880`023b5cb0 fffff800`01f7d166 nt!ExpWorkerThread+0x111
    fffff880`023b5d40 fffff800`01cb8486 nt!PspSystemThreadStartup+0x5a
    fffff880`023b5d80 00000000`00000000 nt!KxStartSystemThread+0x16
  • Pavel_LebedinskyPavel_Lebedinsky Member - All Emails Posts: 435
    > 1: kd> 2k
    > Child-SP RetAddr Call Site
    > fffff880`02085b88 fffff800`01c33401 hal!HalpHalt+0x1
    > fffff880`02085b90 fffff800`01c26380 hal!HalpResetThisProcessor+0x1dd
    > fffff880`02085bc0 fffff800`01cd63f3 hal!HalpApicRebootService+0x58
    > fffff880`02085bf0 fffff800`01ce26d2 nt!KiInterruptDispatchNoLock+0x163
    > fffff880`02085d80 00000000`00000000 nt!KiIdleLoop+0x32


    This might be a known issue that's currently being investigated, possibly
    caused by a hardware problem. Is it reproducible?

    --
    Pavel Lebedinsky/Windows Kernel Test
    This posting is provided "AS IS" with no warranties, and confers no rights.
  • eric_tsangeric_tsang Member Posts: 31
    Yes, It happened once almost every day. It only happened after upgraded to windows 2008 R2,
    it never happened in windows 2008 before.
  • Pavel_LebedinskyPavel_Lebedinsky Member - All Emails Posts: 435
    > Yes, It happened once almost every day. It only happened after
    > upgraded to windows 2008 R2, it never happened in windows
    > 2008 before.

    Can you try disabling the use of ACPI C-states in the BIOS and see
    if that helps?

    --
    Pavel Lebedinsky/Windows Kernel Test
    This posting is provided "AS IS" with no warranties, and confers no rights.
  • eric_tsangeric_tsang Member Posts: 31
    After disabled ACPI C-states,It is working fine for one week till now.

    Thanks Pavel.
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. Sign in or register to get started.

Upcoming OSR Seminars
OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!
Internals & Software Drivers 15 November 2021 Live, Online
Writing WDF Drivers 24 January 2022 Live, Online
Developing Minifilters 7 February 2022 Live, Online
Kernel Debugging 21 March 2022 Live, Online