0x101 dump on vista sp1

NTDEV
1

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: 00000061, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 806d1120, The PRCB address of the hung processor.
Arg4: 00000001, 0.

Debugging Details:

DEFAULT_BUCKET_ID: VISTA_RC

BUGCHECK_STR: 0x101

PROCESS_NAME: System

CURRENT_IRQL: 1c

LAST_CONTROL_TRANSFER: from 81ca2f7a to 81cf16d9

STACK_TEXT:
807809c0 81ca2f7a 00000101 00000061 00000000 nt!KeBugCheckEx+0x1e
807809f4 81ca469d 81c0a61b 000000d1 80780a88 nt!KeUpdateRunTime+0xd5
807809f4 81c70879 81c0a61b 000000d1 80780a88 nt!KeUpdateSystemTime+0xed
80780a88 81cc02d6 00000fff 00000000 81d245e8 nt!KxFlushEntireTb+0xba
80780aa0 81c7c6cd 00000000 00000001 a77fe000 nt!KeFlushTb+0x176
80780abc 81c7052f 81d246b4 00000000 00000001 nt!KeFlushMultipleRangeTb+0x91
80780c44 81c70066 81d44220 00000001 80780c80 nt!MiAgeWorkingSet+0x37c
80780c98 81c6bed1 00000002 80780cb4 00000001 nt!MiProcessWorkingSets+0x1ff
80780cd8 81c6bcda 00000000 83ca8870 00000000 nt!MmWorkingSetManager+0x19a
80780d7c 81dde6ad 00000000 86187273 00000000 nt!KeBalanceSetManager+0x12a
80780dc0 81cc5686 81c6bbb0 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KxFlushEntireTb+ba
81c70879 f390 pause

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!KxFlushEntireTb+ba

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a

FAILURE_BUCKET_ID: 0x101_nt!KxFlushEntireTb+ba
BUCKET_ID: 0x101_nt!KxFlushEntireTb+ba

any hints what could be the possible reason?
how to go ahead.

2

>

0: kd> !analyze -v

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:

snip

any hints what could be the possible reason?
how to go ahead.

Is this happening with a driver you have written?

Are you running in a virtualised environment?

James

3

james,

my sdio ndis wlan card was connected at the time of the dump.
i am trying to figure out if there is any possiblilty of my driver being the
culprit.

do you think it is possible?
no i am not running in virtualised environment

On Mon, May 18, 2009 at 3:10 PM, James Harper > wrote:

> >
> > 0: kd> !analyze -v
> >
> > 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:
>
> snip
>
> > any hints what could be the possible reason?
> > how to go ahead.
>
> Is this happening with a driver you have written?
>
> Are you running in a virtualised environment?
>
> James
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

4

> james,

my sdio ndis wlan card was connected at the time of the dump.
i am trying to figure out if there is any possiblilty of my driver
being the
culprit.

do you think it is possible?

Do you raise IRQL to IPI_LEVEL or higher at any point? That might do it
if you did it for any significant amount of time.

James

5

james,
no , this driver doesnt raise the irq level at any point of time.
only place is i think while aquiring spin lock when irql is elevated to
dispatch_level.
also this drivers maximum processing is done in work items so it runs at
passive_level
most of the times.
sdio function drivers in xp/vista also do not directly get isrs as pci ,so
no question of staying in elevated irql for long time.

do you think there are other ways of elevating to that IRQL?

On Mon, May 18, 2009 at 4:06 PM, James Harper > wrote:

> > james,
> >
> > my sdio ndis wlan card was connected at the time of the dump.
> > i am trying to figure out if there is any possiblilty of my driver
> being the
> > culprit.
> >
> > do you think it is possible?
>
> Do you raise IRQL to IPI_LEVEL or higher at any point? That might do it
> if you did it for any significant amount of time.
>
> James
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

6

The prcb of the hung proc is given to you, look at that. For the N procs you have do the following

Foreach(proc from 0 to N-1)
~proc
k

This will switch to each processor and show you the stack. There may be enough context left to show you what hung the proc

d

Sent from my phone with no t9, all spilling mistakes are not intentional.

From: joyjit mullick
Sent: Monday, May 18, 2009 1:01 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] 0x101 dump on vista sp1

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: 00000061, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 806d1120, The PRCB address of the hung processor.
Arg4: 00000001, 0.

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

DEFAULT_BUCKET_ID: VISTA_RC

BUGCHECK_STR: 0x101

PROCESS_NAME: System

CURRENT_IRQL: 1c

LAST_CONTROL_TRANSFER: from 81ca2f7a to 81cf16d9

STACK_TEXT:
807809c0 81ca2f7a 00000101 00000061 00000000 nt!KeBugCheckEx+0x1e
807809f4 81ca469d 81c0a61b 000000d1 80780a88 nt!KeUpdateRunTime+0xd5
807809f4 81c70879 81c0a61b 000000d1 80780a88 nt!KeUpdateSystemTime+0xed
80780a88 81cc02d6 00000fff 00000000 81d245e8 nt!KxFlushEntireTb+0xba
80780aa0 81c7c6cd 00000000 00000001 a77fe000 nt!KeFlushTb+0x176
80780abc 81c7052f 81d246b4 00000000 00000001 nt!KeFlushMultipleRangeTb+0x91
80780c44 81c70066 81d44220 00000001 80780c80 nt!MiAgeWorkingSet+0x37c
80780c98 81c6bed1 00000002 80780cb4 00000001 nt!MiProcessWorkingSets+0x1ff
80780cd8 81c6bcda 00000000 83ca8870 00000000 nt!MmWorkingSetManager+0x19a
80780d7c 81dde6ad 00000000 86187273 00000000 nt!KeBalanceSetManager+0x12a
80780dc0 81cc5686 81c6bbb0 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KxFlushEntireTb+ba
81c70879 f390 pause

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!KxFlushEntireTb+ba

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a

FAILURE_BUCKET_ID: 0x101_nt!KxFlushEntireTb+ba

BUCKET_ID: 0x101_nt!KxFlushEntireTb+ba

any hints what could be the possible reason?
how to go ahead.
— NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

7

0: kd> !pcr 0
KPCR for Processor 0 at 81d25800:
Major 1 Minor 1
NtTib.ExceptionList: 807805b0
NtTib.StackBase: 00000000
NtTib.StackLimit: 00000000
NtTib.SubSystemTib: 8013d000
NtTib.Version: 055dcc27
NtTib.UserPointer: 00000001
NtTib.SelfTib: 00000000

SelfPcr: 81d25800
Prcb: 81d25920
Irql: 0000001f
IRR: 00000000
IDR: ffffffff
InterruptMode: 00000000
IDT: 827f9400
GDT: 827f9000
TSS: 8013d000

CurrentThread: 83ca8870
NextThread: 00000000
IdleThread: 81d28e00

DpcQueue:
*0: kd> !pcr 1
KPCR for Processor 1 at 806d1000:
Major 1 Minor 1
NtTib.ExceptionList: ffffffff
NtTib.StackBase: 00000000
NtTib.StackLimit: 00000000
NtTib.SubSystemTib: 806d3130
NtTib.Version: 060124b7
NtTib.UserPointer: 00000002
NtTib.SelfTib: 00000000*

* SelfPcr: 806d1000
Prcb: 806d1120
Irql: 00000002
IRR: 00000000
IDR: ffffffff
InterruptMode: 00000000
IDT: 806d8950
GDT: 806d8550
TSS: 806d3130*

* CurrentThread: 806d51e0
NextThread: 861f8030
IdleThread: 806d51e0*
* DpcQueue: 0x84acae08 0x87e576b9 [Normal]
tcpip!TcpPeriodicTimeoutHandler
*

806d1120 00010001 806d51e0 861f8030 806d51e0
806d1130 00000001 00000002 0e080106 00000000
806d1140 00000000 00000000 00000000 00000000
806d1150 00000000 00000000 00000000 00000000
806d1160 00000000 00000000 00000000 00000000
806d1170 00000000 00000000 00000000 00000000
806d1180 00000000 00000000 00000000 00000000
806d1190 00000000 00000000 00000000 00000000
806d1120 00010001 806d51e0 861f8030 806d51e0
806d1130 00000001 00000002 0e080106 00000000
806d1140 00000000 00000000 00000000 00000000
806d1150 00000000 00000000 00000000 00000000
806d1160 00000000 00000000 00000000 00000000
806d1170 00000000 00000000 00000000 00000000
806d1180 00000000 00000000 00000000 00000000
806d1190 00000000 00000000 00000000 00000000
0: kd> dd 861f8030
861f8030 00780006 00000000 861f8038 861f8038
861f8040 140687db 00000009 00000009 00000000
861f8050 176cccc3 00000009 95aa0000 95a9d000
861f8060 95a9fc28 00000000 861f8068 861f8068
861f8070 861f8070 861f8070 87191300 0f000000
861f8080 00000001 00000000 00233db2 00000a03
861f8090 00000001 861b0e80 00000021 0000000d
861f80a0 00000000 806d2c78 00000000 00bff42f
861f8030 00780006 00000000 861f8038 861f8038
861f8040 140687db 00000009 00000009 00000000
861f8050 176cccc3 00000009 95aa0000 95a9d000
861f8060 95a9fc28 00000000 861f8068 861f8068
861f8070 861f8070 861f8070 87191300 0f000000
861f8080 00000001 00000000 00233db2 00000a03
861f8090 00000001 861b0e80 00000021 0000000d
861f80a0 00000000 806d2c78 00000000 00bff42f
0: kd> dps 861f8070
861f8070 861f8070
861f8074 861f8070
861f8078 87191300
861f807c 0f000000
861f8080 00000001
861f8084 00000000
861f8088 00233db2
861f808c 00000a03
861f8090 00000001
861f8094 861b0e80
861f8098 00000021
861f809c 0000000d
861f80a0 00000000
861f80a4 806d2c78
861f80a8 00000000
861f80ac 00bff42f
861f80b0 00000000
861f80b4 7ffda000
861f80b8 00750008
861f80bc 00000000
861f80c0 861f80c0
861f80c4 861f80c0
861f80c8 a5dddaec
861f80cc 000001c8
861f80d0 81d29a90 nt!KiTimerTableListHead+0x750
861f80d4 81d29a90 nt!KiTimerTableListHead+0x750
861f80d8 00000000
861f80dc 00000000
861f80e0 000000c0
861f80e4 00000000
861f80e8 861fc828
861f80ec 861fc828
861f8070 861f8070
861f8074 861f8070
861f8078 87191300
861f807c 0f000000
861f8080 00000001
861f8084 00000000
861f8088 00233db2
861f808c 00000a03
861f8090 00000001
861f8094 861b0e80
861f8098 00000021
861f809c 0000000d
861f80a0 00000000
861f80a4 806d2c78
861f80a8 00000000
861f80ac 00bff42f
861f80b0 00000000
861f80b4 7ffda000
861f80b8 00750008
861f80bc 00000000
861f80c0 861f80c0
861f80c4 861f80c0
861f80c8 a5dddaec
861f80cc 000001c8
861f80d0 81d29a90 nt!KiTimerTableListHead+0x750
861f80d4 81d29a90 nt!KiTimerTableListHead+0x750
861f80d8 00000000
861f80dc 00000000
861f80e0 000000c0
861f80e4 00000000
861f80e8 861fc828
861f80ec 861fc828
doron,
above is what i could see meaningful after dumping the stack of the prcb.
does it make any sense?

On Mon, May 18, 2009 at 7:47 PM, Doron Holan wrote:

> The prcb of the hung proc is given to you, look at that. For the N procs
> you have do the following
>
> Foreach(proc from 0 to N-1)
> ~proc
> k
>
> This will switch to each processor and show you the stack. There may be
> enough context left to show you what hung the proc
>
> d
>
> Sent from my phone with no t9, all spilling mistakes are not intentional.
>
> ------------------------------
> From: joyjit mullick
> Sent: Monday, May 18, 2009 1:01 AM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] 0x101 dump on vista sp1
>
> 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: 00000061, Clock interrupt time out interval in nominal clock ticks.
> Arg2: 00000000, 0.
> Arg3: 806d1120, The PRCB address of the hung processor.
> Arg4: 00000001, 0.
>
> Debugging Details:
> ------------------
>
>
> DEFAULT_BUCKET_ID: VISTA_RC
>
> BUGCHECK_STR: 0x101
>
> PROCESS_NAME: System
>
> CURRENT_IRQL: 1c
>
> LAST_CONTROL_TRANSFER: from 81ca2f7a to 81cf16d9
>
> STACK_TEXT:
> 807809c0 81ca2f7a 00000101 00000061 00000000 nt!KeBugCheckEx+0x1e
> 807809f4 81ca469d 81c0a61b 000000d1 80780a88 nt!KeUpdateRunTime+0xd5
> 807809f4 81c70879 81c0a61b 000000d1 80780a88 nt!KeUpdateSystemTime+0xed
> 80780a88 81cc02d6 00000fff 00000000 81d245e8 nt!KxFlushEntireTb+0xba
> 80780aa0 81c7c6cd 00000000 00000001 a77fe000 nt!KeFlushTb+0x176
> 80780abc 81c7052f 81d246b4 00000000 00000001 nt!KeFlushMultipleRangeTb+0x91
> 80780c44 81c70066 81d44220 00000001 80780c80 nt!MiAgeWorkingSet+0x37c
> 80780c98 81c6bed1 00000002 80780cb4 00000001 nt!MiProcessWorkingSets+0x1ff
> 80780cd8 81c6bcda 00000000 83ca8870 00000000 nt!MmWorkingSetManager+0x19a
> 80780d7c 81dde6ad 00000000 86187273 00000000 nt!KeBalanceSetManager+0x12a
> 80780dc0 81cc5686 81c6bbb0 00000000 00000000 nt!PspSystemThreadStartup+0x9d
> 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
>
>
> STACK_COMMAND: kb
>
> FOLLOWUP_IP:
> nt!KxFlushEntireTb+ba
> 81c70879 f390 pause
>
> SYMBOL_STACK_INDEX: 3
>
> SYMBOL_NAME: nt!KxFlushEntireTb+ba
>
> FOLLOWUP_NAME: MachineOwner
>
> MODULE_NAME: nt
>
> IMAGE_NAME: ntkrnlmp.exe
>
> DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a
>
> FAILURE_BUCKET_ID: 0x101_nt!KxFlushEntireTb+ba
> BUCKET_ID: 0x101_nt!KxFlushEntireTb+ba
>
>
> any hints what could be the possible reason?
> how to go ahead.
> — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and
> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
> the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

8

Based on this

CurrentThread: 806d51e0
NextThread: 861f8030
IdleThread: 806d51e0
Run
!thread 806d51e0
!thread 861f8030

And see if there is anything interesting going on

d

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of joyjit mullick
Sent: Tuesday, May 19, 2009 2:03 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] 0x101 dump on vista sp1

0: kd> !pcr 0
KPCR for Processor 0 at 81d25800:
Major 1 Minor 1
NtTib.ExceptionList: 807805b0
NtTib.StackBase: 00000000
NtTib.StackLimit: 00000000
NtTib.SubSystemTib: 8013d000
NtTib.Version: 055dcc27
NtTib.UserPointer: 00000001
NtTib.SelfTib: 00000000

SelfPcr: 81d25800
Prcb: 81d25920
Irql: 0000001f
IRR: 00000000
IDR: ffffffff
InterruptMode: 00000000
IDT: 827f9400
GDT: 827f9000
TSS: 8013d000

CurrentThread: 83ca8870
NextThread: 00000000
IdleThread: 81d28e00

DpcQueue:
0: kd> !pcr 1
KPCR for Processor 1 at 806d1000:
Major 1 Minor 1
NtTib.ExceptionList: ffffffff
NtTib.StackBase: 00000000
NtTib.StackLimit: 00000000
NtTib.SubSystemTib: 806d3130
NtTib.Version: 060124b7
NtTib.UserPointer: 00000002
NtTib.SelfTib: 00000000

SelfPcr: 806d1000
Prcb: 806d1120
Irql: 00000002
IRR: 00000000
IDR: ffffffff
InterruptMode: 00000000
IDT: 806d8950
GDT: 806d8550
TSS: 806d3130

CurrentThread: 806d51e0
NextThread: 861f8030
IdleThread: 806d51e0
DpcQueue: 0x84acae08 0x87e576b9 [Normal] tcpip!TcpPeriodicTimeoutHandler

806d1120 00010001 806d51e0 861f8030 806d51e0
806d1130 00000001 00000002 0e080106 00000000
806d1140 00000000 00000000 00000000 00000000
806d1150 00000000 00000000 00000000 00000000
806d1160 00000000 00000000 00000000 00000000
806d1170 00000000 00000000 00000000 00000000
806d1180 00000000 00000000 00000000 00000000
806d1190 00000000 00000000 00000000 00000000
806d1120 00010001 806d51e0 861f8030 806d51e0
806d1130 00000001 00000002 0e080106 00000000
806d1140 00000000 00000000 00000000 00000000
806d1150 00000000 00000000 00000000 00000000
806d1160 00000000 00000000 00000000 00000000
806d1170 00000000 00000000 00000000 00000000
806d1180 00000000 00000000 00000000 00000000
806d1190 00000000 00000000 00000000 00000000
0: kd> dd 861f8030
861f8030 00780006 00000000 861f8038 861f8038
861f8040 140687db 00000009 00000009 00000000
861f8050 176cccc3 00000009 95aa0000 95a9d000
861f8060 95a9fc28 00000000 861f8068 861f8068
861f8070 861f8070 861f8070 87191300 0f000000
861f8080 00000001 00000000 00233db2 00000a03
861f8090 00000001 861b0e80 00000021 0000000d
861f80a0 00000000 806d2c78 00000000 00bff42f
861f8030 00780006 00000000 861f8038 861f8038
861f8040 140687db 00000009 00000009 00000000
861f8050 176cccc3 00000009 95aa0000 95a9d000
861f8060 95a9fc28 00000000 861f8068 861f8068
861f8070 861f8070 861f8070 87191300 0f000000
861f8080 00000001 00000000 00233db2 00000a03
861f8090 00000001 861b0e80 00000021 0000000d
861f80a0 00000000 806d2c78 00000000 00bff42f
0: kd> dps 861f8070
861f8070 861f8070
861f8074 861f8070
861f8078 87191300
861f807c 0f000000
861f8080 00000001
861f8084 00000000
861f8088 00233db2
861f808c 00000a03
861f8090 00000001
861f8094 861b0e80
861f8098 00000021
861f809c 0000000d
861f80a0 00000000
861f80a4 806d2c78
861f80a8 00000000
861f80ac 00bff42f
861f80b0 00000000
861f80b4 7ffda000
861f80b8 00750008
861f80bc 00000000
861f80c0 861f80c0
861f80c4 861f80c0
861f80c8 a5dddaec
861f80cc 000001c8
861f80d0 81d29a90 nt!KiTimerTableListHead+0x750
861f80d4 81d29a90 nt!KiTimerTableListHead+0x750
861f80d8 00000000
861f80dc 00000000
861f80e0 000000c0
861f80e4 00000000
861f80e8 861fc828
861f80ec 861fc828
861f8070 861f8070
861f8074 861f8070
861f8078 87191300
861f807c 0f000000
861f8080 00000001
861f8084 00000000
861f8088 00233db2
861f808c 00000a03
861f8090 00000001
861f8094 861b0e80
861f8098 00000021
861f809c 0000000d
861f80a0 00000000
861f80a4 806d2c78
861f80a8 00000000
861f80ac 00bff42f
861f80b0 00000000
861f80b4 7ffda000
861f80b8 00750008
861f80bc 00000000
861f80c0 861f80c0
861f80c4 861f80c0
861f80c8 a5dddaec
861f80cc 000001c8
861f80d0 81d29a90 nt!KiTimerTableListHead+0x750
861f80d4 81d29a90 nt!KiTimerTableListHead+0x750
861f80d8 00000000
861f80dc 00000000
861f80e0 000000c0
861f80e4 00000000
861f80e8 861fc828
861f80ec 861fc828
doron,
above is what i could see meaningful after dumping the stack of the prcb.
does it make any sense?

On Mon, May 18, 2009 at 7:47 PM, Doron Holan > wrote:
The prcb of the hung proc is given to you, look at that. For the N procs you have do the following

Foreach(proc from 0 to N-1)
~proc
k

This will switch to each processor and show you the stack. There may be enough context left to show you what hung the proc

d

Sent from my phone with no t9, all spilling mistakes are not intentional.
________________________________
From: joyjit mullick >
Sent: Monday, May 18, 2009 1:01 AM
To: Windows System Software Devs Interest List >
Subject: [ntdev] 0x101 dump on vista sp1

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: 00000061, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 806d1120, The PRCB address of the hung processor.
Arg4: 00000001, 0.

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

DEFAULT_BUCKET_ID: VISTA_RC

BUGCHECK_STR: 0x101

PROCESS_NAME: System

CURRENT_IRQL: 1c

LAST_CONTROL_TRANSFER: from 81ca2f7a to 81cf16d9

STACK_TEXT:
807809c0 81ca2f7a 00000101 00000061 00000000 nt!KeBugCheckEx+0x1e
807809f4 81ca469d 81c0a61b 000000d1 80780a88 nt!KeUpdateRunTime+0xd5
807809f4 81c70879 81c0a61b 000000d1 80780a88 nt!KeUpdateSystemTime+0xed
80780a88 81cc02d6 00000fff 00000000 81d245e8 nt!KxFlushEntireTb+0xba
80780aa0 81c7c6cd 00000000 00000001 a77fe000 nt!KeFlushTb+0x176
80780abc 81c7052f 81d246b4 00000000 00000001 nt!KeFlushMultipleRangeTb+0x91
80780c44 81c70066 81d44220 00000001 80780c80 nt!MiAgeWorkingSet+0x37c
80780c98 81c6bed1 00000002 80780cb4 00000001 nt!MiProcessWorkingSets+0x1ff
80780cd8 81c6bcda 00000000 83ca8870 00000000 nt!MmWorkingSetManager+0x19a
80780d7c 81dde6ad 00000000 86187273 00000000 nt!KeBalanceSetManager+0x12a
80780dc0 81cc5686 81c6bbb0 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KxFlushEntireTb+ba
81c70879 f390 pause

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!KxFlushEntireTb+ba

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a

FAILURE_BUCKET_ID: 0x101_nt!KxFlushEntireTb+ba
BUCKET_ID: 0x101_nt!KxFlushEntireTb+ba

any hints what could be the possible reason?
how to go ahead.
— NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

— NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

9

0: kd> !thread 806d51e0
THREAD 806d51e0 Cid 0000.0000 Teb: 00000000 Win32Thread: 00000000 RUNNING
on processor 1
Not impersonating
DeviceMap 88c08d70
Owning Process 83c3c910 Image: System
Wait Start TickCount 0 Ticks: 12580201 (2:06:30:52.393)
Context Switch Count 24769841
UserTime 00:00:00.0000
KernelTime 12:21:27.0678
Win32 Start Address nt!KiIdleLoop (0x81c9f504)
Stack Init 806ed000 Current 806ecd4c Base 806ed000 Limit 806ea000 Call 0
Priority 0 BasePriority 0 PriorityDecrement 0
ChildEBP RetAddr Args to Child
00000000 00000000 00000000 00000000 00000000 0x0
0: kd> !thread 861f8030
THREAD 861f8030 Cid 0280.0338 Teb: 7ffda000 Win32Thread: ff8ad5a8 STANDBY
Not impersonating
DeviceMap 88c08d70
Owning Process 87191300 Image: csrss.exe
Wait Start TickCount 12579887 Ticks: 314 (0:00:00:04.898)
Context Switch Count 2309554
UserTime 00:00:00.0000
KernelTime 00:00:00.0093
Win32 Start Address 0x76119a30
Stack Init 95aa0000 Current 95a9fc28 Base 95aa0000 Limit 95a9d000 Call 0
Priority 15 BasePriority 13 PriorityDecrement 0
ChildEBP RetAddr Args to Child
95a9fc40 81ca1943 861f8030 00000000 861f80b8 nt!KiSwapContext+0x26 (FPO:
[Uses EBP] [0,0,4])
95a9fc84 81c9e999 861f8030 00000001 81c8b9c4 nt!KiSwapThread+0x433
95a9fcd8 920de55c 00000004 861ea250 00000001
nt!KeWaitForMultipleObjects+0x53d
95a9fd34 920decc6 00000001 00000002 9450e450 win32k!RawInputThread+0x482
(FPO: [Non-Fpo])
95a9fd48 921a2002 00000004 00fffec8 95a9fd64
win32k!xxxCreateSystemThreads+0x4a (FPO: [Non-Fpo])
95a9fd58 81c8d9aa 00000004 00ffff08 77a19a94 win32k!NtUserCallNoParam+0x1b
(FPO: [Non-Fpo])
95a9fd58 77a19a94 00000004 00ffff08 77a19a94 nt!KiFastCallEntry+0x12a (FPO:
[0,3] TrapFrame @ 95a9fd64)
WARNING: Frame IP not in any known module. Following frames may be wrong.
00ffff08 00000000 00000000 00000000 00000000 0x77a19a94
doron,
it seems some user io happening in the context of the next thread

On Tue, May 19, 2009 at 10:28 PM, Doron Holan wrote:

> Based on this
>
> * CurrentThread: 806d51e0**
> NextThread: 861f8030
> IdleThread: 806d51e0*
>
> Run
>
> !thread 806d51e0
>
> !thread 861f8030
>
>
>
> And see if there is anything interesting going on
>
>
>
> d
>
>
>
>
>
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] On Behalf Of joyjit mullick
> Sent: Tuesday, May 19, 2009 2:03 AM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] 0x101 dump on vista sp1
>
>
>
> 0: kd> !pcr 0
> KPCR for Processor 0 at 81d25800:
> Major 1 Minor 1
> NtTib.ExceptionList: 807805b0
> NtTib.StackBase: 00000000
> NtTib.StackLimit: 00000000
> NtTib.SubSystemTib: 8013d000
> NtTib.Version: 055dcc27
> NtTib.UserPointer: 00000001
> NtTib.SelfTib: 00000000
>
> SelfPcr: 81d25800
> Prcb: 81d25920
> Irql: 0000001f
> IRR: 00000000
> IDR: ffffffff
> InterruptMode: 00000000
> IDT: 827f9400
> GDT: 827f9000
> TSS: 8013d000
>
> CurrentThread: 83ca8870
> NextThread: 00000000
> IdleThread: 81d28e00
>
> DpcQueue:
> 0: kd> !pcr 1
> KPCR for Processor 1 at 806d1000:
> Major 1 Minor 1
> NtTib.ExceptionList: ffffffff
> NtTib.StackBase: 00000000
> NtTib.StackLimit: 00000000
> NtTib.SubSystemTib: 806d3130
> NtTib.Version: 060124b7
> NtTib.UserPointer: 00000002
> NtTib.SelfTib: 00000000
>
> * SelfPcr: 806d1000
> Prcb: 806d1120
> Irql: 00000002
> IRR: 00000000
> IDR: ffffffff
> InterruptMode: 00000000
> IDT: 806d8950
> GDT: 806d8550
> TSS: 806d3130
>
> * CurrentThread: 806d51e0*
> NextThread: 861f8030
> IdleThread: 806d51e0*
>
> * DpcQueue: 0x84acae08 0x87e576b9 [Normal]
> tcpip!TcpPeriodicTimeoutHandler**
>
>
> 806d1120 00010001 806d51e0 861f8030 806d51e0
> 806d1130 00000001 00000002 0e080106 00000000
> 806d1140 00000000 00000000 00000000 00000000
> 806d1150 00000000 00000000 00000000 00000000
> 806d1160 00000000 00000000 00000000 00000000
> 806d1170 00000000 00000000 00000000 00000000
> 806d1180 00000000 00000000 00000000 00000000
> 806d1190 00000000 00000000 00000000 00000000
> 806d1120 00010001 806d51e0 861f8030 806d51e0
> 806d1130 00000001 00000002 0e080106 00000000
> 806d1140 00000000 00000000 00000000 00000000
> 806d1150 00000000 00000000 00000000 00000000
> 806d1160 00000000 00000000 00000000 00000000
> 806d1170 00000000 00000000 00000000 00000000
> 806d1180 00000000 00000000 00000000 00000000
> 806d1190 00000000 00000000 00000000 00000000
>
> 0: kd> dd 861f8030
> 861f8030 00780006 00000000 861f8038 861f8038
> 861f8040 140687db 00000009 00000009 00000000
> 861f8050 176cccc3 00000009 95aa0000 95a9d000
> 861f8060 95a9fc28 00000000 861f8068 861f8068
> 861f8070 861f8070 861f8070 87191300 0f000000
> 861f8080 00000001 00000000 00233db2 00000a03
> 861f8090 00000001 861b0e80 00000021 0000000d
> 861f80a0 00000000 806d2c78 00000000 00bff42f
> 861f8030 00780006 00000000 861f8038 861f8038
> 861f8040 140687db 00000009 00000009 00000000
> 861f8050 176cccc3 00000009 95aa0000 95a9d000
> 861f8060 95a9fc28 00000000 861f8068 861f8068
> 861f8070 861f8070 861f8070 87191300 0f000000
> 861f8080 00000001 00000000 00233db2 00000a03
> 861f8090 00000001 861b0e80 00000021 0000000d
> 861f80a0 00000000 806d2c78 00000000 00bff42f
>
> 0: kd> dps 861f8070
> 861f8070 861f8070
> 861f8074 861f8070
> 861f8078 87191300
> 861f807c 0f000000
> 861f8080 00000001
> 861f8084 00000000
> 861f8088 00233db2
> 861f808c 00000a03
> 861f8090 00000001
> 861f8094 861b0e80
> 861f8098 00000021
> 861f809c 0000000d
> 861f80a0 00000000
> 861f80a4 806d2c78
> 861f80a8 00000000
> 861f80ac 00bff42f
> 861f80b0 00000000
> 861f80b4 7ffda000
> 861f80b8 00750008
> 861f80bc 00000000
> 861f80c0 861f80c0
> 861f80c4 861f80c0
> 861f80c8 a5dddaec
> 861f80cc 000001c8
> 861f80d0 81d29a90 nt!KiTimerTableListHead+0x750
> 861f80d4 81d29a90 nt!KiTimerTableListHead+0x750
> 861f80d8 00000000
> 861f80dc 00000000
> 861f80e0 000000c0
> 861f80e4 00000000
> 861f80e8 861fc828
> 861f80ec 861fc828
> 861f8070 861f8070
> 861f8074 861f8070
> 861f8078 87191300
> 861f807c 0f000000
> 861f8080 00000001
> 861f8084 00000000
> 861f8088 00233db2
> 861f808c 00000a03
> 861f8090 00000001
> 861f8094 861b0e80
> 861f8098 00000021
> 861f809c 0000000d
> 861f80a0 00000000
> 861f80a4 806d2c78
> 861f80a8 00000000
> 861f80ac 00bff42f
> 861f80b0 00000000
> 861f80b4 7ffda000
> 861f80b8 00750008
> 861f80bc 00000000
> 861f80c0 861f80c0
> 861f80c4 861f80c0
> 861f80c8 a5dddaec
> 861f80cc 000001c8
> 861f80d0 81d29a90 nt!KiTimerTableListHead+0x750
> 861f80d4 81d29a90 nt!KiTimerTableListHead+0x750
> 861f80d8 00000000
> 861f80dc 00000000
> 861f80e0 000000c0
> 861f80e4 00000000
> 861f80e8 861fc828
> 861f80ec 861fc828
>
> doron,
>
> above is what i could see meaningful after dumping the stack of the prcb.
>
> does it make any sense?
>
>
>
>
>
> On Mon, May 18, 2009 at 7:47 PM, Doron Holan
> wrote:
>
> The prcb of the hung proc is given to you, look at that. For the N procs
> you have do the following
>
> Foreach(proc from 0 to N-1)
> ~proc
> k
>
> This will switch to each processor and show you the stack. There may be
> enough context left to show you what hung the proc
>
> d
>
> Sent from my phone with no t9, all spilling mistakes are not intentional.
> ------------------------------
>
> From: joyjit mullick
> Sent: Monday, May 18, 2009 1:01 AM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] 0x101 dump on vista sp1
>
> 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: 00000061, Clock interrupt time out interval in nominal clock ticks.
> Arg2: 00000000, 0.
> Arg3: 806d1120, The PRCB address of the hung processor.
> Arg4: 00000001, 0.
>
> Debugging Details:
> ------------------
>
>
> DEFAULT_BUCKET_ID: VISTA_RC
>
> BUGCHECK_STR: 0x101
>
> PROCESS_NAME: System
>
> CURRENT_IRQL: 1c
>
> LAST_CONTROL_TRANSFER: from 81ca2f7a to 81cf16d9
>
> STACK_TEXT:
> 807809c0 81ca2f7a 00000101 00000061 00000000 nt!KeBugCheckEx+0x1e
> 807809f4 81ca469d 81c0a61b 000000d1 80780a88 nt!KeUpdateRunTime+0xd5
> 807809f4 81c70879 81c0a61b 000000d1 80780a88 nt!KeUpdateSystemTime+0xed
> 80780a88 81cc02d6 00000fff 00000000 81d245e8 nt!KxFlushEntireTb+0xba
> 80780aa0 81c7c6cd 00000000 00000001 a77fe000 nt!KeFlushTb+0x176
> 80780abc 81c7052f 81d246b4 00000000 00000001 nt!KeFlushMultipleRangeTb+0x91
> 80780c44 81c70066 81d44220 00000001 80780c80 nt!MiAgeWorkingSet+0x37c
> 80780c98 81c6bed1 00000002 80780cb4 00000001 nt!MiProcessWorkingSets+0x1ff
> 80780cd8 81c6bcda 00000000 83ca8870 00000000 nt!MmWorkingSetManager+0x19a
> 80780d7c 81dde6ad 00000000 86187273 00000000 nt!KeBalanceSetManager+0x12a
> 80780dc0 81cc5686 81c6bbb0 00000000 00000000 nt!PspSystemThreadStartup+0x9d
> 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
>
>
> STACK_COMMAND: kb
>
> FOLLOWUP_IP:
> nt!KxFlushEntireTb+ba
> 81c70879 f390 pause
>
> SYMBOL_STACK_INDEX: 3
>
> SYMBOL_NAME: nt!KxFlushEntireTb+ba
>
> FOLLOWUP_NAME: MachineOwner
>
> MODULE_NAME: nt
>
> IMAGE_NAME: ntkrnlmp.exe
>
> DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a
>
> FAILURE_BUCKET_ID: 0x101_nt!KxFlushEntireTb+ba
>
> BUCKET_ID: 0x101_nt!KxFlushEntireTb+ba
>
>
>
>
>
> any hints what could be the possible reason?
>
> how to go ahead.
>
> — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and
> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
> the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
> —
>
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
> — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and
> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
> the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

10

the zero’ed callstack on the current thread is either due to a wrong pointer being passed to the extension command or a clear sign of why that processor is not taking interrupts (b/c it’s stack has mysteriously been trashed). Do you have any SEH blocks in your driver which may be catching a structured exception that it should not be?

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of joyjit mullick
Sent: Wednesday, May 20, 2009 7:25 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] 0x101 dump on vista sp1

0: kd> !thread 806d51e0
THREAD 806d51e0 Cid 0000.0000 Teb: 00000000 Win32Thread: 00000000 RUNNING on processor 1
Not impersonating
DeviceMap 88c08d70
Owning Process 83c3c910 Image: System
Wait Start TickCount 0 Ticks: 12580201 (2:06:30:52.393)
Context Switch Count 24769841
UserTime 00:00:00.0000
KernelTime 12:21:27.0678
Win32 Start Address nt!KiIdleLoop (0x81c9f504)
Stack Init 806ed000 Current 806ecd4c Base 806ed000 Limit 806ea000 Call 0
Priority 0 BasePriority 0 PriorityDecrement 0
ChildEBP RetAddr Args to Child
00000000 00000000 00000000 00000000 00000000 0x0
0: kd> !thread 861f8030
THREAD 861f8030 Cid 0280.0338 Teb: 7ffda000 Win32Thread: ff8ad5a8 STANDBY
Not impersonating
DeviceMap 88c08d70
Owning Process 87191300 Image: csrss.exe
Wait Start TickCount 12579887 Ticks: 314 (0:00:00:04.898)
Context Switch Count 2309554
UserTime 00:00:00.0000
KernelTime 00:00:00.0093
Win32 Start Address 0x76119a30
Stack Init 95aa0000 Current 95a9fc28 Base 95aa0000 Limit 95a9d000 Call 0
Priority 15 BasePriority 13 PriorityDecrement 0
ChildEBP RetAddr Args to Child
95a9fc40 81ca1943 861f8030 00000000 861f80b8 nt!KiSwapContext+0x26 (FPO: [Uses EBP] [0,0,4])
95a9fc84 81c9e999 861f8030 00000001 81c8b9c4 nt!KiSwapThread+0x433
95a9fcd8 920de55c 00000004 861ea250 00000001 nt!KeWaitForMultipleObjects+0x53d
95a9fd34 920decc6 00000001 00000002 9450e450 win32k!RawInputThread+0x482 (FPO: [Non-Fpo])
95a9fd48 921a2002 00000004 00fffec8 95a9fd64 win32k!xxxCreateSystemThreads+0x4a (FPO: [Non-Fpo])
95a9fd58 81c8d9aa 00000004 00ffff08 77a19a94 win32k!NtUserCallNoParam+0x1b (FPO: [Non-Fpo])
95a9fd58 77a19a94 00000004 00ffff08 77a19a94 nt!KiFastCallEntry+0x12a (FPO: [0,3] TrapFrame @ 95a9fd64)
WARNING: Frame IP not in any known module. Following frames may be wrong.
00ffff08 00000000 00000000 00000000 00000000 0x77a19a94
doron,
it seems some user io happening in the context of the next thread
On Tue, May 19, 2009 at 10:28 PM, Doron Holan > wrote:

Based on this

CurrentThread: 806d51e0
NextThread: 861f8030
IdleThread: 806d51e0

Run

!thread 806d51e0

!thread 861f8030

And see if there is anything interesting going on

d

From: xxxxx@lists.osr.commailto:xxxxx [mailto:xxxxx@lists.osr.commailto:xxxxx] On Behalf Of joyjit mullick
Sent: Tuesday, May 19, 2009 2:03 AM

To: Windows System Software Devs Interest List
Subject: Re: [ntdev] 0x101 dump on vista sp1

0: kd> !pcr 0
KPCR for Processor 0 at 81d25800:
Major 1 Minor 1
NtTib.ExceptionList: 807805b0
NtTib.StackBase: 00000000
NtTib.StackLimit: 00000000
NtTib.SubSystemTib: 8013d000
NtTib.Version: 055dcc27
NtTib.UserPointer: 00000001
NtTib.SelfTib: 00000000

SelfPcr: 81d25800
Prcb: 81d25920
Irql: 0000001f
IRR: 00000000
IDR: ffffffff
InterruptMode: 00000000
IDT: 827f9400
GDT: 827f9000
TSS: 8013d000

CurrentThread: 83ca8870
NextThread: 00000000
IdleThread: 81d28e00

DpcQueue:
0: kd> !pcr 1
KPCR for Processor 1 at 806d1000:
Major 1 Minor 1
NtTib.ExceptionList: ffffffff
NtTib.StackBase: 00000000
NtTib.StackLimit: 00000000
NtTib.SubSystemTib: 806d3130
NtTib.Version: 060124b7
NtTib.UserPointer: 00000002
NtTib.SelfTib: 00000000

SelfPcr: 806d1000
Prcb: 806d1120
Irql: 00000002
IRR: 00000000
IDR: ffffffff
InterruptMode: 00000000
IDT: 806d8950
GDT: 806d8550
TSS: 806d3130

CurrentThread: 806d51e0
NextThread: 861f8030
IdleThread: 806d51e0

DpcQueue: 0x84acae08 0x87e576b9 [Normal] tcpip!TcpPeriodicTimeoutHandler

806d1120 00010001 806d51e0 861f8030 806d51e0
806d1130 00000001 00000002 0e080106 00000000
806d1140 00000000 00000000 00000000 00000000
806d1150 00000000 00000000 00000000 00000000
806d1160 00000000 00000000 00000000 00000000
806d1170 00000000 00000000 00000000 00000000
806d1180 00000000 00000000 00000000 00000000
806d1190 00000000 00000000 00000000 00000000
806d1120 00010001 806d51e0 861f8030 806d51e0
806d1130 00000001 00000002 0e080106 00000000
806d1140 00000000 00000000 00000000 00000000
806d1150 00000000 00000000 00000000 00000000
806d1160 00000000 00000000 00000000 00000000
806d1170 00000000 00000000 00000000 00000000
806d1180 00000000 00000000 00000000 00000000
806d1190 00000000 00000000 00000000 00000000

0: kd> dd 861f8030
861f8030 00780006 00000000 861f8038 861f8038
861f8040 140687db 00000009 00000009 00000000
861f8050 176cccc3 00000009 95aa0000 95a9d000
861f8060 95a9fc28 00000000 861f8068 861f8068
861f8070 861f8070 861f8070 87191300 0f000000
861f8080 00000001 00000000 00233db2 00000a03
861f8090 00000001 861b0e80 00000021 0000000d
861f80a0 00000000 806d2c78 00000000 00bff42f
861f8030 00780006 00000000 861f8038 861f8038
861f8040 140687db 00000009 00000009 00000000
861f8050 176cccc3 00000009 95aa0000 95a9d000
861f8060 95a9fc28 00000000 861f8068 861f8068
861f8070 861f8070 861f8070 87191300 0f000000
861f8080 00000001 00000000 00233db2 00000a03
861f8090 00000001 861b0e80 00000021 0000000d
861f80a0 00000000 806d2c78 00000000 00bff42f

0: kd> dps 861f8070
861f8070 861f8070
861f8074 861f8070
861f8078 87191300
861f807c 0f000000
861f8080 00000001
861f8084 00000000
861f8088 00233db2
861f808c 00000a03
861f8090 00000001
861f8094 861b0e80
861f8098 00000021
861f809c 0000000d
861f80a0 00000000
861f80a4 806d2c78
861f80a8 00000000
861f80ac 00bff42f
861f80b0 00000000
861f80b4 7ffda000
861f80b8 00750008
861f80bc 00000000
861f80c0 861f80c0
861f80c4 861f80c0
861f80c8 a5dddaec
861f80cc 000001c8
861f80d0 81d29a90 nt!KiTimerTableListHead+0x750
861f80d4 81d29a90 nt!KiTimerTableListHead+0x750
861f80d8 00000000
861f80dc 00000000
861f80e0 000000c0
861f80e4 00000000
861f80e8 861fc828
861f80ec 861fc828
861f8070 861f8070
861f8074 861f8070
861f8078 87191300
861f807c 0f000000
861f8080 00000001
861f8084 00000000
861f8088 00233db2
861f808c 00000a03
861f8090 00000001
861f8094 861b0e80
861f8098 00000021
861f809c 0000000d
861f80a0 00000000
861f80a4 806d2c78
861f80a8 00000000
861f80ac 00bff42f
861f80b0 00000000
861f80b4 7ffda000
861f80b8 00750008
861f80bc 00000000
861f80c0 861f80c0
861f80c4 861f80c0
861f80c8 a5dddaec
861f80cc 000001c8
861f80d0 81d29a90 nt!KiTimerTableListHead+0x750
861f80d4 81d29a90 nt!KiTimerTableListHead+0x750
861f80d8 00000000
861f80dc 00000000
861f80e0 000000c0
861f80e4 00000000
861f80e8 861fc828
861f80ec 861fc828

doron,

above is what i could see meaningful after dumping the stack of the prcb.

does it make any sense?

On Mon, May 18, 2009 at 7:47 PM, Doron Holan > wrote:

The prcb of the hung proc is given to you, look at that. For the N procs you have do the following

Foreach(proc from 0 to N-1)
~proc
k

This will switch to each processor and show you the stack. There may be enough context left to show you what hung the proc

d

Sent from my phone with no t9, all spilling mistakes are not intentional.

________________________________

From: joyjit mullick >
Sent: Monday, May 18, 2009 1:01 AM
To: Windows System Software Devs Interest List >
Subject: [ntdev] 0x101 dump on vista sp1

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: 00000061, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 806d1120, The PRCB address of the hung processor.
Arg4: 00000001, 0.

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

DEFAULT_BUCKET_ID: VISTA_RC

BUGCHECK_STR: 0x101

PROCESS_NAME: System

CURRENT_IRQL: 1c

LAST_CONTROL_TRANSFER: from 81ca2f7a to 81cf16d9

STACK_TEXT:
807809c0 81ca2f7a 00000101 00000061 00000000 nt!KeBugCheckEx+0x1e
807809f4 81ca469d 81c0a61b 000000d1 80780a88 nt!KeUpdateRunTime+0xd5
807809f4 81c70879 81c0a61b 000000d1 80780a88 nt!KeUpdateSystemTime+0xed
80780a88 81cc02d6 00000fff 00000000 81d245e8 nt!KxFlushEntireTb+0xba
80780aa0 81c7c6cd 00000000 00000001 a77fe000 nt!KeFlushTb+0x176
80780abc 81c7052f 81d246b4 00000000 00000001 nt!KeFlushMultipleRangeTb+0x91
80780c44 81c70066 81d44220 00000001 80780c80 nt!MiAgeWorkingSet+0x37c
80780c98 81c6bed1 00000002 80780cb4 00000001 nt!MiProcessWorkingSets+0x1ff
80780cd8 81c6bcda 00000000 83ca8870 00000000 nt!MmWorkingSetManager+0x19a
80780d7c 81dde6ad 00000000 86187273 00000000 nt!KeBalanceSetManager+0x12a
80780dc0 81cc5686 81c6bbb0 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KxFlushEntireTb+ba
81c70879 f390 pause

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!KxFlushEntireTb+ba

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a

FAILURE_BUCKET_ID: 0x101_nt!KxFlushEntireTb+ba

BUCKET_ID: 0x101_nt!KxFlushEntireTb+ba

any hints what could be the possible reason?

how to go ahead.

— NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

—

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

— NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

— NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer</mailto:xxxxx></mailto:xxxxx>