VirtualBox

Ticket #523: WinDbg_Output.txt

File WinDbg_Output.txt, 23.6 KB (added by tpre, 17 years ago)

WinDbg-Output on Minidump

Line 
1
2Microsoft (R) Windows Debugger Version 6.7.0005.1
3Copyright (c) Microsoft Corporation. All rights reserved.
4
5
6Loading Dump File [C:\WINDOWS\Minidump\Mini072807-01.dmp]
7Mini Kernel Dump File: Only registers and stack trace are available
8
9Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
10Executable search path is:
11Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
12Product: WinNt, suite: TerminalServer SingleUserTS
13Built by: 2600.xpsp_sp2_qfe.070227-2300
14Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a820
15Debug session time: Sat Jul 28 10:36:14.241 2007 (GMT+2)
16System Uptime: 0 days 16:04:32.967
17Loading Kernel Symbols
18..................................................................................................................................................................................................
19Loading User Symbols
20Loading unloaded module list
21...............
22*******************************************************************************
23* *
24* Bugcheck Analysis *
25* *
26*******************************************************************************
27
28Use !analyze -v to get detailed debugging information.
29
30BugCheck 1000007E, {c0000005, 1, f790a8ec, f790a5e8}
31
32*** WARNING: Unable to verify timestamp for VBoxUSBFlt.sys
33*** ERROR: Module load completed but symbols could not be loaded for VBoxUSBFlt.sys
34Probably caused by : VBoxUSBFlt.sys ( VBoxUSBFlt+380 )
35
36Followup: MachineOwner
37---------
38
39kd> !analyze -v
40*******************************************************************************
41* *
42* Bugcheck Analysis *
43* *
44*******************************************************************************
45
46SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
47This is a very common bugcheck. Usually the exception address pinpoints
48the driver/function that caused the problem. Always note this address
49as well as the link date of the driver/image that contains this address.
50Some common problems are exception code 0x80000003. This means a hard
51coded breakpoint or assertion was hit, but this system was booted
52/NODEBUG. This is not supposed to happen as developers should never have
53hardcoded breakpoints in retail code, but ...
54If this happens, make sure a debugger gets connected, and the
55system is booted /DEBUG. This will let us see why this breakpoint is
56happening.
57Arguments:
58Arg1: c0000005, The exception code that was not handled
59Arg2: 00000001, The address that the exception occurred at
60Arg3: f790a8ec, Exception Record Address
61Arg4: f790a5e8, Context Record Address
62
63Debugging Details:
64------------------
65
66
67EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in "0x%08lx" verweist auf Speicher in "0x%08lx". Der Vorgang "%s" konnte nicht auf dem Speicher durchgef hrt werden.
68
69FAULTING_IP:
70+1
7100000001 ?? ???
72
73EXCEPTION_RECORD: f790a8ec -- (.exr 0xfffffffff790a8ec)
74ExceptionAddress: 00000001
75 ExceptionCode: c0000005 (Access violation)
76 ExceptionFlags: 00000000
77NumberParameters: 2
78 Parameter[0]: 00000000
79 Parameter[1]: 00000001
80Attempt to read from address 00000001
81
82CONTEXT: f790a5e8 -- (.cxr 0xfffffffff790a5e8)
83eax=00000004 ebx=8854ad50 ecx=00000000 edx=00220003 esi=87d00460 edi=8853a008
84eip=00000001 esp=f790a9b4 ebp=f790a9d8 iopl=0 nv up ei pl zr na pe nc
85cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
8600000001 ?? ???
87Resetting default scope
88
89CUSTOMER_CRASH_COUNT: 1
90
91DEFAULT_BUCKET_ID: DRIVER_FAULT
92
93PROCESS_NAME: System
94
95ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in "0x%08lx" verweist auf Speicher in "0x%08lx". Der Vorgang "%s" konnte nicht auf dem Speicher durchgef hrt werden.
96
97READ_ADDRESS: 00000001
98
99FAILED_INSTRUCTION_ADDRESS:
100+1
10100000001 ?? ???
102
103BUGCHECK_STR: 0x7E
104
105LAST_CONTROL_TRANSFER: from bac8fae1 to 00000001
106
107STACK_TEXT:
108WARNING: Frame IP not in any known module. Following frames may be wrong.
109f790a9b0 bac8fae1 00000040 68627375 64657621 0x1
110f790a9d8 bac8d1d8 8930d3b8 8853a008 f790aa0c usbhub!USBH_PdoDispatch+0x1e9
111f790a9e8 804e37f7 87d003a8 8853a008 8853a008 usbhub!USBH_HubDispatch+0x48
112f790a9f8 f77b7380 00000000 89962c58 87c43030 nt!IopfCallDriver+0x31
113f790aa0c 804e37f7 00000000 8853a008 892e9230 VBoxUSBFlt+0x380
114f790aa1c f77f04db 00220003 8853a12c 80000000 nt!IopfCallDriver+0x31
115f790aa38 f77ef76b 87c62410 8853a008 89e2fda8 usbccgp!ParentInternalDeviceControl+0xbb
116f790aa5c f77ef5d3 87c62408 8853a008 0000000f usbccgp!USBC_InternalDeviceControl+0x3b
117f790aa98 804e37f7 87c62350 8853a008 892e9230 usbccgp!USBC_Dispatch+0x183
118f790aaa8 f77f1231 80000000 00000002 00220003 nt!IopfCallDriver+0x31
119f790aad8 f77ef786 892d37f8 8853a008 892d37f8 usbccgp!FunctionInternalDeviceControl+0x1c1
120f790aafc f77ef5d3 892d37f0 8853a008 0000000f usbccgp!USBC_InternalDeviceControl+0x56
121f790ab38 804e37f7 892d3738 8853a008 8853a008 usbccgp!USBC_Dispatch+0x183
122f790ab48 ba8e2fd7 87c4327c 8930d3b8 87c43030 nt!IopfCallDriver+0x31
123f790ab74 ba8e3609 87c43030 8930d3b8 00000002 hidusb!HumCallUSB+0x71
124f790ab8c ba8e365a 87c43030 00000000 89c8d008 hidusb!HumAbortPendingRequests+0x4b
125f790aba4 ba8e376f 87c43030 89c8d008 87c43218 hidusb!HumRemoveDevice+0x32
126f790abd4 f7407e91 87c43030 89c8d008 87c430fc hidusb!HumPnP+0x45
127f790abe8 f740ea5f 87c43030 89c8d008 87c430fc HIDCLASS!HidpCallDriver+0x3f
128f790ac04 f740cf1c 87c430fc 89c8d008 89c8d1bc HIDCLASS!HidpRemoveDevice+0xa1
129f790ac20 f740d076 87c430e8 89c8d008 f790ac40 HIDCLASS!HidpFdoPnp+0x72
130f790ac30 f740892b 87c430e8 89c8d008 f790ac7c HIDCLASS!HidpIrpMajorPnp+0x1e
131f790ac40 804e37f7 87c43030 89c8d008 f790accc HIDCLASS!HidpMajorHandler+0x79
132f790ac50 8059df8f 892d3738 892d3738 00000002 nt!IopfCallDriver+0x31
133f790ac7c 8061ad54 87c43030 f790aca8 00000000 nt!IopSynchronousCall+0xb7
134f790acd0 80531683 892d3738 00000002 00000000 nt!IopRemoveDevice+0x93
135f790acf8 8061becf e2c65078 00000018 e12f4c50 nt!IopRemoveLockedDeviceNode+0x160
136f790ad10 8061bf3b 89c9ca38 00000002 e12f4c50 nt!IopDeleteLockedDeviceNode+0x34
137f790ad44 8061bfe6 87d003a8 022f4c50 00000002 nt!IopDeleteLockedDeviceNodes+0x3f
138f790ad74 804e426b 89c84da8 00000000 89e2fda8 nt!IopDelayedRemoveWorker+0x4b
139f790adac 8057cfce 89c84da8 00000000 00000000 nt!ExpWorkerThread+0x100
140f790addc 804f88fa 804e4196 00000001 00000000 nt!PspSystemThreadStartup+0x34
14100000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
142
143
144FOLLOWUP_IP:
145VBoxUSBFlt+380
146f77b7380 ?? ???
147
148SYMBOL_STACK_INDEX: 4
149
150SYMBOL_NAME: VBoxUSBFlt+380
151
152FOLLOWUP_NAME: MachineOwner
153
154MODULE_NAME: VBoxUSBFlt
155
156IMAGE_NAME: VBoxUSBFlt.sys
157
158DEBUG_FLR_IMAGE_TIMESTAMP: 45f6eb5d
159
160STACK_COMMAND: .cxr 0xfffffffff790a5e8 ; kb
161
162FAILURE_BUCKET_ID: 0x7E_BAD_IP_VBoxUSBFlt+380
163
164BUCKET_ID: 0x7E_BAD_IP_VBoxUSBFlt+380
165
166Followup: MachineOwner
167---------
168
169kd> !analyze -v
170*******************************************************************************
171* *
172* Bugcheck Analysis *
173* *
174*******************************************************************************
175
176SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
177This is a very common bugcheck. Usually the exception address pinpoints
178the driver/function that caused the problem. Always note this address
179as well as the link date of the driver/image that contains this address.
180Some common problems are exception code 0x80000003. This means a hard
181coded breakpoint or assertion was hit, but this system was booted
182/NODEBUG. This is not supposed to happen as developers should never have
183hardcoded breakpoints in retail code, but ...
184If this happens, make sure a debugger gets connected, and the
185system is booted /DEBUG. This will let us see why this breakpoint is
186happening.
187Arguments:
188Arg1: c0000005, The exception code that was not handled
189Arg2: 00000001, The address that the exception occurred at
190Arg3: f790a8ec, Exception Record Address
191Arg4: f790a5e8, Context Record Address
192
193Debugging Details:
194------------------
195
196
197EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in "0x%08lx" verweist auf Speicher in "0x%08lx". Der Vorgang "%s" konnte nicht auf dem Speicher durchgef hrt werden.
198
199FAULTING_IP:
200+1
20100000001 ?? ???
202
203EXCEPTION_RECORD: f790a8ec -- (.exr 0xfffffffff790a8ec)
204ExceptionAddress: 00000001
205 ExceptionCode: c0000005 (Access violation)
206 ExceptionFlags: 00000000
207NumberParameters: 2
208 Parameter[0]: 00000000
209 Parameter[1]: 00000001
210Attempt to read from address 00000001
211
212CONTEXT: f790a5e8 -- (.cxr 0xfffffffff790a5e8)
213eax=00000004 ebx=8854ad50 ecx=00000000 edx=00220003 esi=87d00460 edi=8853a008
214eip=00000001 esp=f790a9b4 ebp=f790a9d8 iopl=0 nv up ei pl zr na pe nc
215cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
21600000001 ?? ???
217Resetting default scope
218
219CUSTOMER_CRASH_COUNT: 1
220
221DEFAULT_BUCKET_ID: DRIVER_FAULT
222
223PROCESS_NAME: System
224
225ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in "0x%08lx" verweist auf Speicher in "0x%08lx". Der Vorgang "%s" konnte nicht auf dem Speicher durchgef hrt werden.
226
227READ_ADDRESS: 00000001
228
229FAILED_INSTRUCTION_ADDRESS:
230+1
23100000001 ?? ???
232
233BUGCHECK_STR: 0x7E
234
235LAST_CONTROL_TRANSFER: from bac8fae1 to 00000001
236
237STACK_TEXT:
238WARNING: Frame IP not in any known module. Following frames may be wrong.
239f790a9b0 bac8fae1 00000040 68627375 64657621 0x1
240f790a9d8 bac8d1d8 8930d3b8 8853a008 f790aa0c usbhub!USBH_PdoDispatch+0x1e9
241f790a9e8 804e37f7 87d003a8 8853a008 8853a008 usbhub!USBH_HubDispatch+0x48
242f790a9f8 f77b7380 00000000 89962c58 87c43030 nt!IopfCallDriver+0x31
243f790aa0c 804e37f7 00000000 8853a008 892e9230 VBoxUSBFlt+0x380
244f790aa1c f77f04db 00220003 8853a12c 80000000 nt!IopfCallDriver+0x31
245f790aa38 f77ef76b 87c62410 8853a008 89e2fda8 usbccgp!ParentInternalDeviceControl+0xbb
246f790aa5c f77ef5d3 87c62408 8853a008 0000000f usbccgp!USBC_InternalDeviceControl+0x3b
247f790aa98 804e37f7 87c62350 8853a008 892e9230 usbccgp!USBC_Dispatch+0x183
248f790aaa8 f77f1231 80000000 00000002 00220003 nt!IopfCallDriver+0x31
249f790aad8 f77ef786 892d37f8 8853a008 892d37f8 usbccgp!FunctionInternalDeviceControl+0x1c1
250f790aafc f77ef5d3 892d37f0 8853a008 0000000f usbccgp!USBC_InternalDeviceControl+0x56
251f790ab38 804e37f7 892d3738 8853a008 8853a008 usbccgp!USBC_Dispatch+0x183
252f790ab48 ba8e2fd7 87c4327c 8930d3b8 87c43030 nt!IopfCallDriver+0x31
253f790ab74 ba8e3609 87c43030 8930d3b8 00000002 hidusb!HumCallUSB+0x71
254f790ab8c ba8e365a 87c43030 00000000 89c8d008 hidusb!HumAbortPendingRequests+0x4b
255f790aba4 ba8e376f 87c43030 89c8d008 87c43218 hidusb!HumRemoveDevice+0x32
256f790abd4 f7407e91 87c43030 89c8d008 87c430fc hidusb!HumPnP+0x45
257f790abe8 f740ea5f 87c43030 89c8d008 87c430fc HIDCLASS!HidpCallDriver+0x3f
258f790ac04 f740cf1c 87c430fc 89c8d008 89c8d1bc HIDCLASS!HidpRemoveDevice+0xa1
259f790ac20 f740d076 87c430e8 89c8d008 f790ac40 HIDCLASS!HidpFdoPnp+0x72
260f790ac30 f740892b 87c430e8 89c8d008 f790ac7c HIDCLASS!HidpIrpMajorPnp+0x1e
261f790ac40 804e37f7 87c43030 89c8d008 f790accc HIDCLASS!HidpMajorHandler+0x79
262f790ac50 8059df8f 892d3738 892d3738 00000002 nt!IopfCallDriver+0x31
263f790ac7c 8061ad54 87c43030 f790aca8 00000000 nt!IopSynchronousCall+0xb7
264f790acd0 80531683 892d3738 00000002 00000000 nt!IopRemoveDevice+0x93
265f790acf8 8061becf e2c65078 00000018 e12f4c50 nt!IopRemoveLockedDeviceNode+0x160
266f790ad10 8061bf3b 89c9ca38 00000002 e12f4c50 nt!IopDeleteLockedDeviceNode+0x34
267f790ad44 8061bfe6 87d003a8 022f4c50 00000002 nt!IopDeleteLockedDeviceNodes+0x3f
268f790ad74 804e426b 89c84da8 00000000 89e2fda8 nt!IopDelayedRemoveWorker+0x4b
269f790adac 8057cfce 89c84da8 00000000 00000000 nt!ExpWorkerThread+0x100
270f790addc 804f88fa 804e4196 00000001 00000000 nt!PspSystemThreadStartup+0x34
27100000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
272
273
274FOLLOWUP_IP:
275VBoxUSBFlt+380
276f77b7380 ?? ???
277
278SYMBOL_STACK_INDEX: 4
279
280SYMBOL_NAME: VBoxUSBFlt+380
281
282FOLLOWUP_NAME: MachineOwner
283
284MODULE_NAME: VBoxUSBFlt
285
286IMAGE_NAME: VBoxUSBFlt.sys
287
288DEBUG_FLR_IMAGE_TIMESTAMP: 45f6eb5d
289
290STACK_COMMAND: .cxr 0xfffffffff790a5e8 ; kb
291
292FAILURE_BUCKET_ID: 0x7E_BAD_IP_VBoxUSBFlt+380
293
294BUCKET_ID: 0x7E_BAD_IP_VBoxUSBFlt+380
295
296Followup: MachineOwner
297---------
298
299kd> !analyze -v
300*******************************************************************************
301* *
302* Bugcheck Analysis *
303* *
304*******************************************************************************
305
306SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
307This is a very common bugcheck. Usually the exception address pinpoints
308the driver/function that caused the problem. Always note this address
309as well as the link date of the driver/image that contains this address.
310Some common problems are exception code 0x80000003. This means a hard
311coded breakpoint or assertion was hit, but this system was booted
312/NODEBUG. This is not supposed to happen as developers should never have
313hardcoded breakpoints in retail code, but ...
314If this happens, make sure a debugger gets connected, and the
315system is booted /DEBUG. This will let us see why this breakpoint is
316happening.
317Arguments:
318Arg1: c0000005, The exception code that was not handled
319Arg2: 00000001, The address that the exception occurred at
320Arg3: f790a8ec, Exception Record Address
321Arg4: f790a5e8, Context Record Address
322
323Debugging Details:
324------------------
325
326
327EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in "0x%08lx" verweist auf Speicher in "0x%08lx". Der Vorgang "%s" konnte nicht auf dem Speicher durchgef hrt werden.
328
329FAULTING_IP:
330+1
33100000001 ?? ???
332
333EXCEPTION_RECORD: f790a8ec -- (.exr 0xfffffffff790a8ec)
334ExceptionAddress: 00000001
335 ExceptionCode: c0000005 (Access violation)
336 ExceptionFlags: 00000000
337NumberParameters: 2
338 Parameter[0]: 00000000
339 Parameter[1]: 00000001
340Attempt to read from address 00000001
341
342CONTEXT: f790a5e8 -- (.cxr 0xfffffffff790a5e8)
343eax=00000004 ebx=8854ad50 ecx=00000000 edx=00220003 esi=87d00460 edi=8853a008
344eip=00000001 esp=f790a9b4 ebp=f790a9d8 iopl=0 nv up ei pl zr na pe nc
345cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
34600000001 ?? ???
347Resetting default scope
348
349CUSTOMER_CRASH_COUNT: 1
350
351DEFAULT_BUCKET_ID: DRIVER_FAULT
352
353PROCESS_NAME: System
354
355ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in "0x%08lx" verweist auf Speicher in "0x%08lx". Der Vorgang "%s" konnte nicht auf dem Speicher durchgef hrt werden.
356
357READ_ADDRESS: 00000001
358
359FAILED_INSTRUCTION_ADDRESS:
360+1
36100000001 ?? ???
362
363BUGCHECK_STR: 0x7E
364
365LAST_CONTROL_TRANSFER: from bac8fae1 to 00000001
366
367STACK_TEXT:
368WARNING: Frame IP not in any known module. Following frames may be wrong.
369f790a9b0 bac8fae1 00000040 68627375 64657621 0x1
370f790a9d8 bac8d1d8 8930d3b8 8853a008 f790aa0c usbhub!USBH_PdoDispatch+0x1e9
371f790a9e8 804e37f7 87d003a8 8853a008 8853a008 usbhub!USBH_HubDispatch+0x48
372f790a9f8 f77b7380 00000000 89962c58 87c43030 nt!IopfCallDriver+0x31
373f790aa0c 804e37f7 00000000 8853a008 892e9230 VBoxUSBFlt+0x380
374f790aa1c f77f04db 00220003 8853a12c 80000000 nt!IopfCallDriver+0x31
375f790aa38 f77ef76b 87c62410 8853a008 89e2fda8 usbccgp!ParentInternalDeviceControl+0xbb
376f790aa5c f77ef5d3 87c62408 8853a008 0000000f usbccgp!USBC_InternalDeviceControl+0x3b
377f790aa98 804e37f7 87c62350 8853a008 892e9230 usbccgp!USBC_Dispatch+0x183
378f790aaa8 f77f1231 80000000 00000002 00220003 nt!IopfCallDriver+0x31
379f790aad8 f77ef786 892d37f8 8853a008 892d37f8 usbccgp!FunctionInternalDeviceControl+0x1c1
380f790aafc f77ef5d3 892d37f0 8853a008 0000000f usbccgp!USBC_InternalDeviceControl+0x56
381f790ab38 804e37f7 892d3738 8853a008 8853a008 usbccgp!USBC_Dispatch+0x183
382f790ab48 ba8e2fd7 87c4327c 8930d3b8 87c43030 nt!IopfCallDriver+0x31
383f790ab74 ba8e3609 87c43030 8930d3b8 00000002 hidusb!HumCallUSB+0x71
384f790ab8c ba8e365a 87c43030 00000000 89c8d008 hidusb!HumAbortPendingRequests+0x4b
385f790aba4 ba8e376f 87c43030 89c8d008 87c43218 hidusb!HumRemoveDevice+0x32
386f790abd4 f7407e91 87c43030 89c8d008 87c430fc hidusb!HumPnP+0x45
387f790abe8 f740ea5f 87c43030 89c8d008 87c430fc HIDCLASS!HidpCallDriver+0x3f
388f790ac04 f740cf1c 87c430fc 89c8d008 89c8d1bc HIDCLASS!HidpRemoveDevice+0xa1
389f790ac20 f740d076 87c430e8 89c8d008 f790ac40 HIDCLASS!HidpFdoPnp+0x72
390f790ac30 f740892b 87c430e8 89c8d008 f790ac7c HIDCLASS!HidpIrpMajorPnp+0x1e
391f790ac40 804e37f7 87c43030 89c8d008 f790accc HIDCLASS!HidpMajorHandler+0x79
392f790ac50 8059df8f 892d3738 892d3738 00000002 nt!IopfCallDriver+0x31
393f790ac7c 8061ad54 87c43030 f790aca8 00000000 nt!IopSynchronousCall+0xb7
394f790acd0 80531683 892d3738 00000002 00000000 nt!IopRemoveDevice+0x93
395f790acf8 8061becf e2c65078 00000018 e12f4c50 nt!IopRemoveLockedDeviceNode+0x160
396f790ad10 8061bf3b 89c9ca38 00000002 e12f4c50 nt!IopDeleteLockedDeviceNode+0x34
397f790ad44 8061bfe6 87d003a8 022f4c50 00000002 nt!IopDeleteLockedDeviceNodes+0x3f
398f790ad74 804e426b 89c84da8 00000000 89e2fda8 nt!IopDelayedRemoveWorker+0x4b
399f790adac 8057cfce 89c84da8 00000000 00000000 nt!ExpWorkerThread+0x100
400f790addc 804f88fa 804e4196 00000001 00000000 nt!PspSystemThreadStartup+0x34
40100000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
402
403
404FOLLOWUP_IP:
405VBoxUSBFlt+380
406f77b7380 ?? ???
407
408SYMBOL_STACK_INDEX: 4
409
410SYMBOL_NAME: VBoxUSBFlt+380
411
412FOLLOWUP_NAME: MachineOwner
413
414MODULE_NAME: VBoxUSBFlt
415
416IMAGE_NAME: VBoxUSBFlt.sys
417
418DEBUG_FLR_IMAGE_TIMESTAMP: 45f6eb5d
419
420STACK_COMMAND: .cxr 0xfffffffff790a5e8 ; kb
421
422FAILURE_BUCKET_ID: 0x7E_BAD_IP_VBoxUSBFlt+380
423
424BUCKET_ID: 0x7E_BAD_IP_VBoxUSBFlt+380
425
426Followup: MachineOwner
427---------
428
429kd> !analyze -v
430*******************************************************************************
431* *
432* Bugcheck Analysis *
433* *
434*******************************************************************************
435
436SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
437This is a very common bugcheck. Usually the exception address pinpoints
438the driver/function that caused the problem. Always note this address
439as well as the link date of the driver/image that contains this address.
440Some common problems are exception code 0x80000003. This means a hard
441coded breakpoint or assertion was hit, but this system was booted
442/NODEBUG. This is not supposed to happen as developers should never have
443hardcoded breakpoints in retail code, but ...
444If this happens, make sure a debugger gets connected, and the
445system is booted /DEBUG. This will let us see why this breakpoint is
446happening.
447Arguments:
448Arg1: c0000005, The exception code that was not handled
449Arg2: 00000001, The address that the exception occurred at
450Arg3: f790a8ec, Exception Record Address
451Arg4: f790a5e8, Context Record Address
452
453Debugging Details:
454------------------
455
456
457EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in "0x%08lx" verweist auf Speicher in "0x%08lx". Der Vorgang "%s" konnte nicht auf dem Speicher durchgef hrt werden.
458
459FAULTING_IP:
460+1
46100000001 ?? ???
462
463EXCEPTION_RECORD: f790a8ec -- (.exr 0xfffffffff790a8ec)
464ExceptionAddress: 00000001
465 ExceptionCode: c0000005 (Access violation)
466 ExceptionFlags: 00000000
467NumberParameters: 2
468 Parameter[0]: 00000000
469 Parameter[1]: 00000001
470Attempt to read from address 00000001
471
472CONTEXT: f790a5e8 -- (.cxr 0xfffffffff790a5e8)
473eax=00000004 ebx=8854ad50 ecx=00000000 edx=00220003 esi=87d00460 edi=8853a008
474eip=00000001 esp=f790a9b4 ebp=f790a9d8 iopl=0 nv up ei pl zr na pe nc
475cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
47600000001 ?? ???
477Resetting default scope
478
479CUSTOMER_CRASH_COUNT: 1
480
481DEFAULT_BUCKET_ID: DRIVER_FAULT
482
483PROCESS_NAME: System
484
485ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in "0x%08lx" verweist auf Speicher in "0x%08lx". Der Vorgang "%s" konnte nicht auf dem Speicher durchgef hrt werden.
486
487READ_ADDRESS: 00000001
488
489FAILED_INSTRUCTION_ADDRESS:
490+1
49100000001 ?? ???
492
493BUGCHECK_STR: 0x7E
494
495LAST_CONTROL_TRANSFER: from bac8fae1 to 00000001
496
497STACK_TEXT:
498WARNING: Frame IP not in any known module. Following frames may be wrong.
499f790a9b0 bac8fae1 00000040 68627375 64657621 0x1
500f790a9d8 bac8d1d8 8930d3b8 8853a008 f790aa0c usbhub!USBH_PdoDispatch+0x1e9
501f790a9e8 804e37f7 87d003a8 8853a008 8853a008 usbhub!USBH_HubDispatch+0x48
502f790a9f8 f77b7380 00000000 89962c58 87c43030 nt!IopfCallDriver+0x31
503f790aa0c 804e37f7 00000000 8853a008 892e9230 VBoxUSBFlt+0x380
504f790aa1c f77f04db 00220003 8853a12c 80000000 nt!IopfCallDriver+0x31
505f790aa38 f77ef76b 87c62410 8853a008 89e2fda8 usbccgp!ParentInternalDeviceControl+0xbb
506f790aa5c f77ef5d3 87c62408 8853a008 0000000f usbccgp!USBC_InternalDeviceControl+0x3b
507f790aa98 804e37f7 87c62350 8853a008 892e9230 usbccgp!USBC_Dispatch+0x183
508f790aaa8 f77f1231 80000000 00000002 00220003 nt!IopfCallDriver+0x31
509f790aad8 f77ef786 892d37f8 8853a008 892d37f8 usbccgp!FunctionInternalDeviceControl+0x1c1
510f790aafc f77ef5d3 892d37f0 8853a008 0000000f usbccgp!USBC_InternalDeviceControl+0x56
511f790ab38 804e37f7 892d3738 8853a008 8853a008 usbccgp!USBC_Dispatch+0x183
512f790ab48 ba8e2fd7 87c4327c 8930d3b8 87c43030 nt!IopfCallDriver+0x31
513f790ab74 ba8e3609 87c43030 8930d3b8 00000002 hidusb!HumCallUSB+0x71
514f790ab8c ba8e365a 87c43030 00000000 89c8d008 hidusb!HumAbortPendingRequests+0x4b
515f790aba4 ba8e376f 87c43030 89c8d008 87c43218 hidusb!HumRemoveDevice+0x32
516f790abd4 f7407e91 87c43030 89c8d008 87c430fc hidusb!HumPnP+0x45
517f790abe8 f740ea5f 87c43030 89c8d008 87c430fc HIDCLASS!HidpCallDriver+0x3f
518f790ac04 f740cf1c 87c430fc 89c8d008 89c8d1bc HIDCLASS!HidpRemoveDevice+0xa1
519f790ac20 f740d076 87c430e8 89c8d008 f790ac40 HIDCLASS!HidpFdoPnp+0x72
520f790ac30 f740892b 87c430e8 89c8d008 f790ac7c HIDCLASS!HidpIrpMajorPnp+0x1e
521f790ac40 804e37f7 87c43030 89c8d008 f790accc HIDCLASS!HidpMajorHandler+0x79
522f790ac50 8059df8f 892d3738 892d3738 00000002 nt!IopfCallDriver+0x31
523f790ac7c 8061ad54 87c43030 f790aca8 00000000 nt!IopSynchronousCall+0xb7
524f790acd0 80531683 892d3738 00000002 00000000 nt!IopRemoveDevice+0x93
525f790acf8 8061becf e2c65078 00000018 e12f4c50 nt!IopRemoveLockedDeviceNode+0x160
526f790ad10 8061bf3b 89c9ca38 00000002 e12f4c50 nt!IopDeleteLockedDeviceNode+0x34
527f790ad44 8061bfe6 87d003a8 022f4c50 00000002 nt!IopDeleteLockedDeviceNodes+0x3f
528f790ad74 804e426b 89c84da8 00000000 89e2fda8 nt!IopDelayedRemoveWorker+0x4b
529f790adac 8057cfce 89c84da8 00000000 00000000 nt!ExpWorkerThread+0x100
530f790addc 804f88fa 804e4196 00000001 00000000 nt!PspSystemThreadStartup+0x34
53100000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
532
533
534FOLLOWUP_IP:
535VBoxUSBFlt+380
536f77b7380 ?? ???
537
538SYMBOL_STACK_INDEX: 4
539
540SYMBOL_NAME: VBoxUSBFlt+380
541
542FOLLOWUP_NAME: MachineOwner
543
544MODULE_NAME: VBoxUSBFlt
545
546IMAGE_NAME: VBoxUSBFlt.sys
547
548DEBUG_FLR_IMAGE_TIMESTAMP: 45f6eb5d
549
550STACK_COMMAND: .cxr 0xfffffffff790a5e8 ; kb
551
552FAILURE_BUCKET_ID: 0x7E_BAD_IP_VBoxUSBFlt+380
553
554BUCKET_ID: 0x7E_BAD_IP_VBoxUSBFlt+380
555
556Followup: MachineOwner
557---------
558

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