VirtualBox

Ticket #3697: clock-interrupt-bsod.txt

File clock-interrupt-bsod.txt, 15.6 KB (added by Paul, 15 years ago)

Debugged Memory.dmp file of the problem.

Line 
1
2Loading Dump File [C:\Windows\MEMORY.DMP]
3Kernel Summary Dump File: Only kernel address space is available
4
5Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
6Executable search path is:
7Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
8Product: WinNt, suite: TerminalServer SingleUserTS Personal
9Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
10Machine Name:
11Kernel base = 0x81c41000 PsLoadedModuleList = 0x81d58c70
12Debug session time: Fri Apr 10 12:40:58.763 2009 (GMT-5)
13System Uptime: 0 days 14:15:56.185
14Loading Kernel Symbols
15...............................................................
16................................................................
17.......................
18Loading User Symbols
19PEB is paged out (Peb.Ldr = 7ffda00c). Type ".hh dbgerr001" for details
20Loading unloaded module list
21.........
22*******************************************************************************
23* *
24* Bugcheck Analysis *
25* *
26*******************************************************************************
27
28Use !analyze -v to get detailed debugging information.
29
30BugCheck 101, {61, 0, 803d1120, 1}
31
32PEB is paged out (Peb.Ldr = 7ffda00c). Type ".hh dbgerr001" for details
33PEB is paged out (Peb.Ldr = 7ffda00c). Type ".hh dbgerr001" for details
34Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
35
36Followup: MachineOwner
37---------
38
390: kd> !analyze -v
40*******************************************************************************
41* *
42* Bugcheck Analysis *
43* *
44*******************************************************************************
45
46CLOCK_WATCHDOG_TIMEOUT (101)
47An expected clock interrupt was not received on a secondary processor in an
48MP system within the allocated interval. This indicates that the specified
49processor is hung and not processing interrupts.
50Arguments:
51Arg1: 00000061, Clock interrupt time out interval in nominal clock ticks.
52Arg2: 00000000, 0.
53Arg3: 803d1120, The PRCB address of the hung processor.
54Arg4: 00000001, 0.
55
56Debugging Details:
57------------------
58
59PEB is paged out (Peb.Ldr = 7ffda00c). Type ".hh dbgerr001" for details
60PEB is paged out (Peb.Ldr = 7ffda00c). Type ".hh dbgerr001" for details
61
62BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_2_PROC
63
64DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
65
66PROCESS_NAME: SearchIndexer.e
67
68CURRENT_IRQL: 1c
69
70STACK_TEXT:
71986e1840 81cf9271 00000101 00000061 00000000 nt!KeBugCheckEx+0x1e
72986e1874 81cf8f7d 855fdc1b 000000d1 986e1908 nt!KeUpdateRunTime+0xd5
73986e1874 81c8055e 855fdc1b 000000d1 986e1908 nt!KeUpdateSystemTime+0xed
74986e1908 81ce6bec a6e6b808 00000001 a6e6b808 nt!KeFlushSingleTb+0xc8
75986e1970 81c9bb54 00000001 a6e6b808 00000000 nt!MmAccessFault+0xc03
76986e1970 872b34f2 00000001 a6e6b808 00000000 nt!KiTrap0E+0xdc
77986e1a10 872b2711 841c3658 855810d8 0000000a Ntfs!NtfsInitializeMftRecord+0x5d
78986e1c04 8729ad01 841c3658 855f8b80 973ef358 Ntfs!NtfsCreateNewFile+0x715
79986e1cec 872202aa 841c3658 855f8b80 968ef96c Ntfs!NtfsCommonCreate+0xca2
80986e1d2c 81cfa288 968ef904 00000000 ffffffff Ntfs!NtfsCommonCreateCallout+0x20
81986e1d2c 81cfa381 968ef904 00000000 ffffffff nt!KiSwapKernelStackAndExit+0x118
82968ef894 81c7f7cd 968ef904 8722028a 986e2000 nt!KiSwitchKernelStackAndCallout+0x31
83968ef8e0 8722033a 8722028a 968ef904 00000000 nt!KeExpandKernelStackAndCalloutEx+0x1e7
84968ef914 8729c1fb 841c3658 855f8b80 968ef96c Ntfs!NtfsCommonCreateOnNewStack+0x3c
85968efa10 81cfcfd3 85581020 855f8b80 855f8b80 Ntfs!NtfsFsdCreate+0x1f1
86968efa28 80745ba7 855f8b80 00000000 855f8d34 nt!IofCallDriver+0x63
87968efa4c 80758643 968efa6c 85569488 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x251
88968efa98 81cfcfd3 85569488 8555ea48 871fdba4 fltmgr!FltpCreate+0x2a1
89968efab0 81e61d11 2a6b2fa3 85602314 848d69b8 nt!IofCallDriver+0x63
90968efb80 81e873ff 848d69d0 00000000 85602270 nt!IopParseDevice+0xf61
91968efc10 81e5f0f6 00000000 968efc68 00000040 nt!ObpLookupObjectName+0x5a8
92968efc70 81e60bf3 06e1ea58 00000000 00000001 nt!ObOpenObjectByName+0x13c
93968efce4 81e67fea 06e1eabc c0100080 06e1ea58 nt!IopCreateFile+0x63b
94968efd30 81c98a1a 06e1eabc c0100080 06e1ea58 nt!NtCreateFile+0x34
95968efd30 774c9a94 06e1eabc c0100080 06e1ea58 nt!KiFastCallEntry+0x12a
96WARNING: Frame IP not in any known module. Following frames may be wrong.
9706e1eab4 00000000 00000000 00000000 00000000 0x774c9a94
98
99
100STACK_COMMAND: kb
101
102SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
103
104FOLLOWUP_NAME: MachineOwner
105
106MODULE_NAME: Unknown_Module
107
108IMAGE_NAME: Unknown_Image
109
110DEBUG_FLR_IMAGE_TIMESTAMP: 0
111
112FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
113
114BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
115
116Followup: MachineOwner
117---------
118
1190: kd> !analyze -v
120*******************************************************************************
121* *
122* Bugcheck Analysis *
123* *
124*******************************************************************************
125
126CLOCK_WATCHDOG_TIMEOUT (101)
127An expected clock interrupt was not received on a secondary processor in an
128MP system within the allocated interval. This indicates that the specified
129processor is hung and not processing interrupts.
130Arguments:
131Arg1: 00000061, Clock interrupt time out interval in nominal clock ticks.
132Arg2: 00000000, 0.
133Arg3: 803d1120, The PRCB address of the hung processor.
134Arg4: 00000001, 0.
135
136Debugging Details:
137------------------
138
139PEB is paged out (Peb.Ldr = 7ffda00c). Type ".hh dbgerr001" for details
140PEB is paged out (Peb.Ldr = 7ffda00c). Type ".hh dbgerr001" for details
141
142BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_2_PROC
143
144DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
145
146PROCESS_NAME: SearchIndexer.e
147
148CURRENT_IRQL: 1c
149
150STACK_TEXT:
151986e1840 81cf9271 00000101 00000061 00000000 nt!KeBugCheckEx+0x1e
152986e1874 81cf8f7d 855fdc1b 000000d1 986e1908 nt!KeUpdateRunTime+0xd5
153986e1874 81c8055e 855fdc1b 000000d1 986e1908 nt!KeUpdateSystemTime+0xed
154986e1908 81ce6bec a6e6b808 00000001 a6e6b808 nt!KeFlushSingleTb+0xc8
155986e1970 81c9bb54 00000001 a6e6b808 00000000 nt!MmAccessFault+0xc03
156986e1970 872b34f2 00000001 a6e6b808 00000000 nt!KiTrap0E+0xdc
157986e1a10 872b2711 841c3658 855810d8 0000000a Ntfs!NtfsInitializeMftRecord+0x5d
158986e1c04 8729ad01 841c3658 855f8b80 973ef358 Ntfs!NtfsCreateNewFile+0x715
159986e1cec 872202aa 841c3658 855f8b80 968ef96c Ntfs!NtfsCommonCreate+0xca2
160986e1d2c 81cfa288 968ef904 00000000 ffffffff Ntfs!NtfsCommonCreateCallout+0x20
161986e1d2c 81cfa381 968ef904 00000000 ffffffff nt!KiSwapKernelStackAndExit+0x118
162968ef894 81c7f7cd 968ef904 8722028a 986e2000 nt!KiSwitchKernelStackAndCallout+0x31
163968ef8e0 8722033a 8722028a 968ef904 00000000 nt!KeExpandKernelStackAndCalloutEx+0x1e7
164968ef914 8729c1fb 841c3658 855f8b80 968ef96c Ntfs!NtfsCommonCreateOnNewStack+0x3c
165968efa10 81cfcfd3 85581020 855f8b80 855f8b80 Ntfs!NtfsFsdCreate+0x1f1
166968efa28 80745ba7 855f8b80 00000000 855f8d34 nt!IofCallDriver+0x63
167968efa4c 80758643 968efa6c 85569488 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x251
168968efa98 81cfcfd3 85569488 8555ea48 871fdba4 fltmgr!FltpCreate+0x2a1
169968efab0 81e61d11 2a6b2fa3 85602314 848d69b8 nt!IofCallDriver+0x63
170968efb80 81e873ff 848d69d0 00000000 85602270 nt!IopParseDevice+0xf61
171968efc10 81e5f0f6 00000000 968efc68 00000040 nt!ObpLookupObjectName+0x5a8
172968efc70 81e60bf3 06e1ea58 00000000 00000001 nt!ObOpenObjectByName+0x13c
173968efce4 81e67fea 06e1eabc c0100080 06e1ea58 nt!IopCreateFile+0x63b
174968efd30 81c98a1a 06e1eabc c0100080 06e1ea58 nt!NtCreateFile+0x34
175968efd30 774c9a94 06e1eabc c0100080 06e1ea58 nt!KiFastCallEntry+0x12a
176WARNING: Frame IP not in any known module. Following frames may be wrong.
17706e1eab4 00000000 00000000 00000000 00000000 0x774c9a94
178
179
180STACK_COMMAND: kb
181
182SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
183
184FOLLOWUP_NAME: MachineOwner
185
186MODULE_NAME: Unknown_Module
187
188IMAGE_NAME: Unknown_Image
189
190DEBUG_FLR_IMAGE_TIMESTAMP: 0
191
192FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
193
194BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
195
196Followup: MachineOwner
197---------
198
1990: kd> !analyze -v
200*******************************************************************************
201* *
202* Bugcheck Analysis *
203* *
204*******************************************************************************
205
206CLOCK_WATCHDOG_TIMEOUT (101)
207An expected clock interrupt was not received on a secondary processor in an
208MP system within the allocated interval. This indicates that the specified
209processor is hung and not processing interrupts.
210Arguments:
211Arg1: 00000061, Clock interrupt time out interval in nominal clock ticks.
212Arg2: 00000000, 0.
213Arg3: 803d1120, The PRCB address of the hung processor.
214Arg4: 00000001, 0.
215
216Debugging Details:
217------------------
218
219PEB is paged out (Peb.Ldr = 7ffda00c). Type ".hh dbgerr001" for details
220PEB is paged out (Peb.Ldr = 7ffda00c). Type ".hh dbgerr001" for details
221
222BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_2_PROC
223
224DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
225
226PROCESS_NAME: SearchIndexer.e
227
228CURRENT_IRQL: 1c
229
230STACK_TEXT:
231986e1840 81cf9271 00000101 00000061 00000000 nt!KeBugCheckEx+0x1e
232986e1874 81cf8f7d 855fdc1b 000000d1 986e1908 nt!KeUpdateRunTime+0xd5
233986e1874 81c8055e 855fdc1b 000000d1 986e1908 nt!KeUpdateSystemTime+0xed
234986e1908 81ce6bec a6e6b808 00000001 a6e6b808 nt!KeFlushSingleTb+0xc8
235986e1970 81c9bb54 00000001 a6e6b808 00000000 nt!MmAccessFault+0xc03
236986e1970 872b34f2 00000001 a6e6b808 00000000 nt!KiTrap0E+0xdc
237986e1a10 872b2711 841c3658 855810d8 0000000a Ntfs!NtfsInitializeMftRecord+0x5d
238986e1c04 8729ad01 841c3658 855f8b80 973ef358 Ntfs!NtfsCreateNewFile+0x715
239986e1cec 872202aa 841c3658 855f8b80 968ef96c Ntfs!NtfsCommonCreate+0xca2
240986e1d2c 81cfa288 968ef904 00000000 ffffffff Ntfs!NtfsCommonCreateCallout+0x20
241986e1d2c 81cfa381 968ef904 00000000 ffffffff nt!KiSwapKernelStackAndExit+0x118
242968ef894 81c7f7cd 968ef904 8722028a 986e2000 nt!KiSwitchKernelStackAndCallout+0x31
243968ef8e0 8722033a 8722028a 968ef904 00000000 nt!KeExpandKernelStackAndCalloutEx+0x1e7
244968ef914 8729c1fb 841c3658 855f8b80 968ef96c Ntfs!NtfsCommonCreateOnNewStack+0x3c
245968efa10 81cfcfd3 85581020 855f8b80 855f8b80 Ntfs!NtfsFsdCreate+0x1f1
246968efa28 80745ba7 855f8b80 00000000 855f8d34 nt!IofCallDriver+0x63
247968efa4c 80758643 968efa6c 85569488 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x251
248968efa98 81cfcfd3 85569488 8555ea48 871fdba4 fltmgr!FltpCreate+0x2a1
249968efab0 81e61d11 2a6b2fa3 85602314 848d69b8 nt!IofCallDriver+0x63
250968efb80 81e873ff 848d69d0 00000000 85602270 nt!IopParseDevice+0xf61
251968efc10 81e5f0f6 00000000 968efc68 00000040 nt!ObpLookupObjectName+0x5a8
252968efc70 81e60bf3 06e1ea58 00000000 00000001 nt!ObOpenObjectByName+0x13c
253968efce4 81e67fea 06e1eabc c0100080 06e1ea58 nt!IopCreateFile+0x63b
254968efd30 81c98a1a 06e1eabc c0100080 06e1ea58 nt!NtCreateFile+0x34
255968efd30 774c9a94 06e1eabc c0100080 06e1ea58 nt!KiFastCallEntry+0x12a
256WARNING: Frame IP not in any known module. Following frames may be wrong.
25706e1eab4 00000000 00000000 00000000 00000000 0x774c9a94
258
259
260STACK_COMMAND: kb
261
262SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
263
264FOLLOWUP_NAME: MachineOwner
265
266MODULE_NAME: Unknown_Module
267
268IMAGE_NAME: Unknown_Image
269
270DEBUG_FLR_IMAGE_TIMESTAMP: 0
271
272FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
273
274BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
275
276Followup: MachineOwner
277---------
278
2790: kd> !analyze -v
280*******************************************************************************
281* *
282* Bugcheck Analysis *
283* *
284*******************************************************************************
285
286CLOCK_WATCHDOG_TIMEOUT (101)
287An expected clock interrupt was not received on a secondary processor in an
288MP system within the allocated interval. This indicates that the specified
289processor is hung and not processing interrupts.
290Arguments:
291Arg1: 00000061, Clock interrupt time out interval in nominal clock ticks.
292Arg2: 00000000, 0.
293Arg3: 803d1120, The PRCB address of the hung processor.
294Arg4: 00000001, 0.
295
296Debugging Details:
297------------------
298
299PEB is paged out (Peb.Ldr = 7ffda00c). Type ".hh dbgerr001" for details
300PEB is paged out (Peb.Ldr = 7ffda00c). Type ".hh dbgerr001" for details
301
302BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_2_PROC
303
304DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
305
306PROCESS_NAME: SearchIndexer.e
307
308CURRENT_IRQL: 1c
309
310STACK_TEXT:
311986e1840 81cf9271 00000101 00000061 00000000 nt!KeBugCheckEx+0x1e
312986e1874 81cf8f7d 855fdc1b 000000d1 986e1908 nt!KeUpdateRunTime+0xd5
313986e1874 81c8055e 855fdc1b 000000d1 986e1908 nt!KeUpdateSystemTime+0xed
314986e1908 81ce6bec a6e6b808 00000001 a6e6b808 nt!KeFlushSingleTb+0xc8
315986e1970 81c9bb54 00000001 a6e6b808 00000000 nt!MmAccessFault+0xc03
316986e1970 872b34f2 00000001 a6e6b808 00000000 nt!KiTrap0E+0xdc
317986e1a10 872b2711 841c3658 855810d8 0000000a Ntfs!NtfsInitializeMftRecord+0x5d
318986e1c04 8729ad01 841c3658 855f8b80 973ef358 Ntfs!NtfsCreateNewFile+0x715
319986e1cec 872202aa 841c3658 855f8b80 968ef96c Ntfs!NtfsCommonCreate+0xca2
320986e1d2c 81cfa288 968ef904 00000000 ffffffff Ntfs!NtfsCommonCreateCallout+0x20
321986e1d2c 81cfa381 968ef904 00000000 ffffffff nt!KiSwapKernelStackAndExit+0x118
322968ef894 81c7f7cd 968ef904 8722028a 986e2000 nt!KiSwitchKernelStackAndCallout+0x31
323968ef8e0 8722033a 8722028a 968ef904 00000000 nt!KeExpandKernelStackAndCalloutEx+0x1e7
324968ef914 8729c1fb 841c3658 855f8b80 968ef96c Ntfs!NtfsCommonCreateOnNewStack+0x3c
325968efa10 81cfcfd3 85581020 855f8b80 855f8b80 Ntfs!NtfsFsdCreate+0x1f1
326968efa28 80745ba7 855f8b80 00000000 855f8d34 nt!IofCallDriver+0x63
327968efa4c 80758643 968efa6c 85569488 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x251
328968efa98 81cfcfd3 85569488 8555ea48 871fdba4 fltmgr!FltpCreate+0x2a1
329968efab0 81e61d11 2a6b2fa3 85602314 848d69b8 nt!IofCallDriver+0x63
330968efb80 81e873ff 848d69d0 00000000 85602270 nt!IopParseDevice+0xf61
331968efc10 81e5f0f6 00000000 968efc68 00000040 nt!ObpLookupObjectName+0x5a8
332968efc70 81e60bf3 06e1ea58 00000000 00000001 nt!ObOpenObjectByName+0x13c
333968efce4 81e67fea 06e1eabc c0100080 06e1ea58 nt!IopCreateFile+0x63b
334968efd30 81c98a1a 06e1eabc c0100080 06e1ea58 nt!NtCreateFile+0x34
335968efd30 774c9a94 06e1eabc c0100080 06e1ea58 nt!KiFastCallEntry+0x12a
336WARNING: Frame IP not in any known module. Following frames may be wrong.
33706e1eab4 00000000 00000000 00000000 00000000 0x774c9a94
338
339
340STACK_COMMAND: kb
341
342SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
343
344FOLLOWUP_NAME: MachineOwner
345
346MODULE_NAME: Unknown_Module
347
348IMAGE_NAME: Unknown_Image
349
350DEBUG_FLR_IMAGE_TIMESTAMP: 0
351
352FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
353
354BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
355
356Followup: MachineOwner
357---------

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy