VirtualBox

Ticket #9508: vboxdisp-memdump.txt

File vboxdisp-memdump.txt, 10.2 KB (added by Diego, 13 years ago)
Line 
1Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
2Copyright (c) Microsoft Corporation. All rights reserved.
3
4
5Loading Dump File [C:\Windows\MEMORY.DMP]
6Kernel Summary Dump File: Only kernel address space is available
7
8Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
9Executable search path is:
10Windows 7 Kernel Version 7601 (Service Pack 1) UP Free x64
11Product: WinNt, suite: TerminalServer SingleUserTS
12Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
13Machine Name:
14Kernel base = 0xfffff800`02c52000 PsLoadedModuleList = 0xfffff800`02e97670
15Debug session time: Thu Aug 25 16:44:11.518 2011 (UTC - 6:00)
16System Uptime: 0 days 0:04:17.136
17Loading Kernel Symbols
18...............................................................
19................................................................
20..................................
21Loading User Symbols
22PEB is paged out (Peb.Ldr = 000007ff`fffd6018). Type ".hh dbgerr001" for details
23Loading unloaded module list
24.......
25*******************************************************************************
26* *
27* Bugcheck Analysis *
28* *
29*******************************************************************************
30
31Use !analyze -v to get detailed debugging information.
32
33BugCheck 50, {fffff901c203bfb8, 0, fffff9600095cf70, 5}
34
35Page 5693c not present in the dump file. Type ".hh dbgerr004" for details
36Page 5693c not present in the dump file. Type ".hh dbgerr004" for details
37*** ERROR: Module load completed but symbols could not be loaded for VBoxDisp.dll
38Page 5666b not present in the dump file. Type ".hh dbgerr004" for details
39Page 560e1 not present in the dump file. Type ".hh dbgerr004" for details
40Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
41Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
42Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
43Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
44Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
45Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
46Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
47Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
48Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
49Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
50Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
51Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
52Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
53Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
54Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
55Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
56Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
57Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
58Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
59Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
60Probably caused by : VBoxDisp.dll ( VBoxDisp+cf70 )
61
62Followup: MachineOwner
63---------
64
65kd> !analyze -v
66*******************************************************************************
67* *
68* Bugcheck Analysis *
69* *
70*******************************************************************************
71
72PAGE_FAULT_IN_NONPAGED_AREA (50)
73Invalid system memory was referenced. This cannot be protected by try-except,
74it must be protected by a Probe. Typically the address is just plain bad or it
75is pointing at freed memory.
76Arguments:
77Arg1: fffff901c203bfb8, memory referenced.
78Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
79Arg3: fffff9600095cf70, If non-zero, the instruction address which referenced the bad memory
80 address.
81Arg4: 0000000000000005, (reserved)
82
83Debugging Details:
84------------------
85
86Page 560e1 not present in the dump file. Type ".hh dbgerr004" for details
87Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
88Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
89Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
90Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
91Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
92Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
93Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
94Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
95Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
96Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
97Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
98Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
99Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
100Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
101Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
102Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
103Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
104Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
105Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
106Page 5663e not present in the dump file. Type ".hh dbgerr004" for details
107
108READ_ADDRESS: fffff901c203bfb8
109
110FAULTING_IP:
111VBoxDisp+cf70
112fffff960`0095cf70 488b040a mov rax,qword ptr [rdx+rcx]
113
114MM_INTERNAL_CODE: 5
115
116IMAGE_NAME: VBoxDisp.dll
117
118DEBUG_FLR_IMAGE_TIMESTAMP: 4e4913e3
119
120MODULE_NAME: VBoxDisp
121
122FAULTING_MODULE: fffff96000950000 VBoxDisp
123
124DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
125
126BUGCHECK_STR: 0x50
127
128PROCESS_NAME: SnippingTool.e
129
130CURRENT_IRQL: 0
131
132TRAP_FRAME: fffff88006624960 -- (.trap 0xfffff88006624960)
133NOTE: The trap frame does not contain all registers.
134Some register values may be zeroed or incorrect.
135rax=fffff900c00cc040 rbx=0000000000000000 rcx=fffff900c00cc060
136rdx=0000000101f6ff58 rsi=0000000000000000 rdi=0000000000000000
137rip=fffff9600095cf70 rsp=fffff88006624af8 rbp=0000000000000020
138 r8=0000000000000020 r9=0000000000000001 r10=0000000000000000
139r11=fffff900c00cc060 r12=0000000000000000 r13=0000000000000000
140r14=0000000000000000 r15=0000000000000000
141iopl=0 nv up ei ng nz na pe cy
142VBoxDisp+0xcf70:
143fffff960`0095cf70 488b040a mov rax,qword ptr [rdx+rcx] ds:d248:bfb8=????????????????
144Resetting default scope
145
146LAST_CONTROL_TRANSFER: from fffff80002c793bf to fffff80002ccec40
147
148STACK_TEXT:
149fffff880`066247f8 fffff800`02c793bf : 00000000`00000050 fffff901`c203bfb8 00000000`00000000 fffff880`06624960 : nt!KeBugCheckEx
150fffff880`06624800 fffff800`02cccd6e : 00000000`00000000 fffff901`c203bfb8 00000000`00000a00 fffff900`c00cc020 : nt! ?? ::FNODOBFM::`string'+0x44791
151fffff880`06624960 fffff960`0095cf70 : fffff960`009531f8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
152fffff880`06624af8 fffff960`009531f8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : VBoxDisp+0xcf70
153fffff880`06624b00 fffff960`0095341d : fffff900`c00c8020 fffff900`c00c0cd8 fffff900`c00c8020 00000000`00000000 : VBoxDisp+0x31f8
154fffff880`06624b80 fffff960`0027c7af : fffff900`c00c0cd8 00000000`00000000 00000000`00000000 00000004`00000008 : VBoxDisp+0x341d
155fffff880`06624bd0 fffff960`000754be : fffff900`c00da010 fffff900`c00c0cd8 fffff900`c203bcc0 fffff900`c201ecc0 : win32k!WatchdogDrvSetPointerShape+0xa7
156fffff880`06624c50 fffff960`00074d77 : 00000000`000001bc fffffa80`02d59030 00000000`00000000 fffff900`00000000 : win32k!vSetPointer+0x5be
157fffff880`06624d70 fffff960`000e40f6 : fffff900`c00c6000 fffff900`c1db3450 fffff900`c1d52d00 fffff960`00000000 : win32k!GreSetPointer+0x177
158fffff880`06624e20 fffff960`000c5acb : fffff900`c1efcc20 fffff880`06624f60 00000000`00000000 fffff900`c01a5010 : win32k!zzzUpdateCursorImage+0x28e
159fffff880`06624e60 fffff960`0010c363 : 00000000`00000000 fffff880`06624f60 00000000`00000000 00000000`00000000 : win32k!zzzSetCursor+0x77
160fffff880`06624eb0 fffff800`02ccded3 : fffffa80`013ae8e0 fffff880`06624f60 00000000`0185000f 00000000`02010ad5 : win32k!NtUserSetCursor+0x4b
161fffff880`06624ee0 00000000`7713c93a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
16200000000`0022f4f8 fffff800`02cc6210 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7713c93a
163fffff880`066252d0 fffff880`066252e8 : 00000000`01c801ba fffff880`066252f8 fffff900`00000018 ffff01e0`064dd2f6 : nt!KiCallUserMode
164fffff880`066252d8 00000000`01c801ba : fffff880`066252f8 fffff900`00000018 ffff01e0`064dd2f6 fffff880`06625db0 : 0xfffff880`066252e8
165fffff880`066252e0 fffff880`066252f8 : fffff900`00000018 ffff01e0`064dd2f6 fffff880`06625db0 00000000`00000000 : 0x1c801ba
166fffff880`066252e8 fffff900`00000018 : ffff01e0`064dd2f6 fffff880`06625db0 00000000`00000000 00000000`00000000 : 0xfffff880`066252f8
167fffff880`066252f0 ffff01e0`064dd2f6 : fffff880`06625db0 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff900`00000018
168fffff880`066252f8 fffff880`06625db0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffff01e0`064dd2f6
169fffff880`06625300 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`06625db0
170
171
172STACK_COMMAND: kb
173
174FOLLOWUP_IP:
175VBoxDisp+cf70
176fffff960`0095cf70 488b040a mov rax,qword ptr [rdx+rcx]
177
178SYMBOL_STACK_INDEX: 3
179
180SYMBOL_NAME: VBoxDisp+cf70
181
182FOLLOWUP_NAME: MachineOwner
183
184FAILURE_BUCKET_ID: X64_0x50_VBoxDisp+cf70
185
186BUCKET_ID: X64_0x50_VBoxDisp+cf70
187
188Followup: MachineOwner
189---------

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