VirtualBox

Ticket #7930: minidump-windbg.txt

File minidump-windbg.txt, 24.6 KB (added by Hector, 14 years ago)
Line 
1
2Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
3Copyright (c) Microsoft Corporation. All rights reserved.
4
5
6Loading Dump File [C:\Windows\Minidump\020711-38360-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:
11Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
12*** WARNING: Unable to verify timestamp for ntoskrnl.exe
13*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
14Windows 7 Kernel Version 7601 (Service Pack 1.178) MP (8 procs) Free x64
15Product: WinNt, suite: TerminalServer SingleUserTS
16Built by: 7601.16562.amd64fre.win7sp1_beta.100603-1800
17Machine Name:
18Kernel base = 0xfffff800`02c06000 PsLoadedModuleList = 0xfffff800`02e46e90
19Debug session time: Mon Feb 7 15:10:47.058 2011 (UTC - 8:00)
20System Uptime: 0 days 0:06:00.854
21Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
22*** WARNING: Unable to verify timestamp for ntoskrnl.exe
23*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
24Loading Kernel Symbols
25...............................................................
26................................................................
27............................................................
28Loading User Symbols
29Loading unloaded module list
30...
31*******************************************************************************
32* *
33* Bugcheck Analysis *
34* *
35*******************************************************************************
36
37Use !analyze -v to get detailed debugging information.
38
39BugCheck 7F, {8, 80050031, 26f8, fffff8800df067cd}
40
41Unable to load image \??\C:\PROGRA~1\Oracle\VIRTUA~1\VMMR0.r0, Win32 error 0n2
42*** WARNING: Unable to verify timestamp for VMMR0.r0
43*** ERROR: Module load completed but symbols could not be loaded for VMMR0.r0
44***** Kernel symbols are WRONG. Please fix symbols to do analysis.
45
46*************************************************************************
47*** ***
48*** ***
49*** Your debugger is not using the correct symbols ***
50*** ***
51*** In order for this command to work properly, your symbol path ***
52*** must point to .pdb files that have full type information. ***
53*** ***
54*** Certain .pdb files (such as the public OS symbols) do not ***
55*** contain the required information. Contact the group that ***
56*** provided you with these symbols if you need this command to ***
57*** work. ***
58*** ***
59*** Type referenced: nt!_KPRCB ***
60*** ***
61*************************************************************************
62*************************************************************************
63*** ***
64*** ***
65*** Your debugger is not using the correct symbols ***
66*** ***
67*** In order for this command to work properly, your symbol path ***
68*** must point to .pdb files that have full type information. ***
69*** ***
70*** Certain .pdb files (such as the public OS symbols) do not ***
71*** contain the required information. Contact the group that ***
72*** provided you with these symbols if you need this command to ***
73*** work. ***
74*** ***
75*** Type referenced: nt!KPRCB ***
76*** ***
77*************************************************************************
78*************************************************************************
79*** ***
80*** ***
81*** Your debugger is not using the correct symbols ***
82*** ***
83*** In order for this command to work properly, your symbol path ***
84*** must point to .pdb files that have full type information. ***
85*** ***
86*** Certain .pdb files (such as the public OS symbols) do not ***
87*** contain the required information. Contact the group that ***
88*** provided you with these symbols if you need this command to ***
89*** work. ***
90*** ***
91*** Type referenced: nt!_KPRCB ***
92*** ***
93*************************************************************************
94*************************************************************************
95*** ***
96*** ***
97*** Your debugger is not using the correct symbols ***
98*** ***
99*** In order for this command to work properly, your symbol path ***
100*** must point to .pdb files that have full type information. ***
101*** ***
102*** Certain .pdb files (such as the public OS symbols) do not ***
103*** contain the required information. Contact the group that ***
104*** provided you with these symbols if you need this command to ***
105*** work. ***
106*** ***
107*** Type referenced: nt!KPRCB ***
108*** ***
109*************************************************************************
110*************************************************************************
111*** ***
112*** ***
113*** Your debugger is not using the correct symbols ***
114*** ***
115*** In order for this command to work properly, your symbol path ***
116*** must point to .pdb files that have full type information. ***
117*** ***
118*** Certain .pdb files (such as the public OS symbols) do not ***
119*** contain the required information. Contact the group that ***
120*** provided you with these symbols if you need this command to ***
121*** work. ***
122*** ***
123*** Type referenced: nt!_KPRCB ***
124*** ***
125*************************************************************************
126*************************************************************************
127*** ***
128*** ***
129*** Your debugger is not using the correct symbols ***
130*** ***
131*** In order for this command to work properly, your symbol path ***
132*** must point to .pdb files that have full type information. ***
133*** ***
134*** Certain .pdb files (such as the public OS symbols) do not ***
135*** contain the required information. Contact the group that ***
136*** provided you with these symbols if you need this command to ***
137*** work. ***
138*** ***
139*** Type referenced: nt!_KPRCB ***
140*** ***
141*************************************************************************
142*************************************************************************
143*** ***
144*** ***
145*** Your debugger is not using the correct symbols ***
146*** ***
147*** In order for this command to work properly, your symbol path ***
148*** must point to .pdb files that have full type information. ***
149*** ***
150*** Certain .pdb files (such as the public OS symbols) do not ***
151*** contain the required information. Contact the group that ***
152*** provided you with these symbols if you need this command to ***
153*** work. ***
154*** ***
155*** Type referenced: nt!_KPRCB ***
156*** ***
157*************************************************************************
158*************************************************************************
159*** ***
160*** ***
161*** Your debugger is not using the correct symbols ***
162*** ***
163*** In order for this command to work properly, your symbol path ***
164*** must point to .pdb files that have full type information. ***
165*** ***
166*** Certain .pdb files (such as the public OS symbols) do not ***
167*** contain the required information. Contact the group that ***
168*** provided you with these symbols if you need this command to ***
169*** work. ***
170*** ***
171*** Type referenced: nt!_KPRCB ***
172*** ***
173*************************************************************************
174Probably caused by : VMMR0.r0 ( VMMR0+e7cd )
175
176Followup: MachineOwner
177---------
178
1792: kd> !analyze -vv
180*******************************************************************************
181* *
182* Bugcheck Analysis *
183* *
184*******************************************************************************
185
186UNEXPECTED_KERNEL_MODE_TRAP (7f)
187This means a trap occurred in kernel mode, and it's a trap of a kind
188that the kernel isn't allowed to have/catch (bound trap) or that
189is always instant death (double fault). The first number in the
190bugcheck params is the number of the trap (8 = double fault, etc)
191Consult an Intel x86 family manual to learn more about what these
192traps are. Here is a *portion* of those codes:
193If kv shows a taskGate
194 use .tss on the part before the colon, then kv.
195Else if kv shows a trapframe
196 use .trap on that value
197Else
198 .trap on the appropriate frame will show where the trap was taken
199 (on x86, this will be the ebp that goes with the procedure KiTrap)
200Endif
201kb will then show the corrected stack.
202Arguments:
203Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
204Arg2: 0000000080050031
205Arg3: 00000000000026f8
206Arg4: fffff8800df067cd
207
208Debugging Details:
209------------------
210
211***** Kernel symbols are WRONG. Please fix symbols to do analysis.
212
213*************************************************************************
214*** ***
215*** ***
216*** Your debugger is not using the correct symbols ***
217*** ***
218*** In order for this command to work properly, your symbol path ***
219*** must point to .pdb files that have full type information. ***
220*** ***
221*** Certain .pdb files (such as the public OS symbols) do not ***
222*** contain the required information. Contact the group that ***
223*** provided you with these symbols if you need this command to ***
224*** work. ***
225*** ***
226*** Type referenced: nt!_KPRCB ***
227*** ***
228*************************************************************************
229*************************************************************************
230*** ***
231*** ***
232*** Your debugger is not using the correct symbols ***
233*** ***
234*** In order for this command to work properly, your symbol path ***
235*** must point to .pdb files that have full type information. ***
236*** ***
237*** Certain .pdb files (such as the public OS symbols) do not ***
238*** contain the required information. Contact the group that ***
239*** provided you with these symbols if you need this command to ***
240*** work. ***
241*** ***
242*** Type referenced: nt!KPRCB ***
243*** ***
244*************************************************************************
245*************************************************************************
246*** ***
247*** ***
248*** Your debugger is not using the correct symbols ***
249*** ***
250*** In order for this command to work properly, your symbol path ***
251*** must point to .pdb files that have full type information. ***
252*** ***
253*** Certain .pdb files (such as the public OS symbols) do not ***
254*** contain the required information. Contact the group that ***
255*** provided you with these symbols if you need this command to ***
256*** work. ***
257*** ***
258*** Type referenced: nt!_KPRCB ***
259*** ***
260*************************************************************************
261*************************************************************************
262*** ***
263*** ***
264*** Your debugger is not using the correct symbols ***
265*** ***
266*** In order for this command to work properly, your symbol path ***
267*** must point to .pdb files that have full type information. ***
268*** ***
269*** Certain .pdb files (such as the public OS symbols) do not ***
270*** contain the required information. Contact the group that ***
271*** provided you with these symbols if you need this command to ***
272*** work. ***
273*** ***
274*** Type referenced: nt!KPRCB ***
275*** ***
276*************************************************************************
277*************************************************************************
278*** ***
279*** ***
280*** Your debugger is not using the correct symbols ***
281*** ***
282*** In order for this command to work properly, your symbol path ***
283*** must point to .pdb files that have full type information. ***
284*** ***
285*** Certain .pdb files (such as the public OS symbols) do not ***
286*** contain the required information. Contact the group that ***
287*** provided you with these symbols if you need this command to ***
288*** work. ***
289*** ***
290*** Type referenced: nt!_KPRCB ***
291*** ***
292*************************************************************************
293*************************************************************************
294*** ***
295*** ***
296*** Your debugger is not using the correct symbols ***
297*** ***
298*** In order for this command to work properly, your symbol path ***
299*** must point to .pdb files that have full type information. ***
300*** ***
301*** Certain .pdb files (such as the public OS symbols) do not ***
302*** contain the required information. Contact the group that ***
303*** provided you with these symbols if you need this command to ***
304*** work. ***
305*** ***
306*** Type referenced: nt!_KPRCB ***
307*** ***
308*************************************************************************
309*************************************************************************
310*** ***
311*** ***
312*** Your debugger is not using the correct symbols ***
313*** ***
314*** In order for this command to work properly, your symbol path ***
315*** must point to .pdb files that have full type information. ***
316*** ***
317*** Certain .pdb files (such as the public OS symbols) do not ***
318*** contain the required information. Contact the group that ***
319*** provided you with these symbols if you need this command to ***
320*** work. ***
321*** ***
322*** Type referenced: nt!_KPRCB ***
323*** ***
324*************************************************************************
325*************************************************************************
326*** ***
327*** ***
328*** Your debugger is not using the correct symbols ***
329*** ***
330*** In order for this command to work properly, your symbol path ***
331*** must point to .pdb files that have full type information. ***
332*** ***
333*** Certain .pdb files (such as the public OS symbols) do not ***
334*** contain the required information. Contact the group that ***
335*** provided you with these symbols if you need this command to ***
336*** work. ***
337*** ***
338*** Type referenced: nt!_KPRCB ***
339*** ***
340*************************************************************************
341
342BUILD_VERSION_STRING: 7601.16562.amd64fre.win7sp1_beta.100603-1800
343
344SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.
345
346SYSTEM_PRODUCT_NAME: Gigabyte Technology Co., Ltd.
347
348BIOS_VENDOR: Award Software International, Inc.
349
350BIOS_VERSION: F13
351
352BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.
353
354ADDITIONAL_DEBUG_TEXT:
355Use '!findthebuild' command to search for the target build information.
356If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
357
358MODULE_NAME: VMMR0
359
360FAULTING_MODULE: fffff80002c06000 nt
361
362DEBUG_FLR_IMAGE_TIMESTAMP: 4d35ba56
363
364BUGCHECK_STR: 0x7f_8
365
366CPU_MICROCODE: 0,0,0,0 (F,M,S,R) SIG: 11'00000000 (cache) 0'00000000 (init)
367
368CUSTOMER_CRASH_COUNT: 1
369
370DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
371
372CURRENT_IRQL: 0
373
374ANALYSIS_SESSION_HOST: Q6600
375
376ANALYSIS_SESSION_TIME: 02-07-2011 15:56:15.0887
377
378LAST_CONTROL_TRANSFER: from fffff80002c8c6e9 to fffff80002c8d140
379
380STACK_TEXT:
381fffff880`0376ade8 fffff800`02c8c6e9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000026f8 : nt+0x87140
382fffff880`0376adf0 00000000`0000007f : 00000000`00000008 00000000`80050031 00000000`000026f8 fffff880`0df067cd : nt+0x866e9
383fffff880`0376adf8 00000000`00000008 : 00000000`80050031 00000000`000026f8 fffff880`0df067cd 00000000`00000000 : 0x7f
384fffff880`0376ae00 00000000`80050031 : 00000000`000026f8 fffff880`0df067cd 00000000`00000000 00000000`00000000 : 0x8
385fffff880`0376ae08 00000000`000026f8 : fffff880`0df067cd 00000000`00000000 00000000`00000000 00000000`00000000 : 0x80050031
386fffff880`0376ae10 fffff880`0df067cd : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x26f8
387fffff880`0376ae18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : VMMR0+0xe7cd
388
389
390STACK_COMMAND: kb
391
392FOLLOWUP_IP:
393VMMR0+e7cd
394fffff880`0df067cd e87effffff call VMMR0+0xe750 (fffff880`0df06750)
395
396FAULT_INSTR_CODE: ffff7ee8
397
398SYMBOL_STACK_INDEX: 6
399
400SYMBOL_NAME: VMMR0+e7cd
401
402FOLLOWUP_NAME: MachineOwner
403
404IMAGE_NAME: VMMR0.r0
405
406BUCKET_ID: WRONG_SYMBOLS
407
408ANALYSIS_SESSION_ELAPSED_TIME: 1653
409
410Followup: MachineOwner
411---------
412

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