VirtualBox

Ticket #10097: output.txt

File output.txt, 14.3 KB (added by matthew.robben@gmail.com, 13 years ago)

pretty printed text of the debugger

Line 
1I've got a 64 bit win7 box running latest version of VirtualBox. I have a Win7 x64 VM that I'd like to use for development of kernel drivers. The VM has a virtualized COM port that creates a host pipe called VMCOM. Whenever I connect a kernel debugger (in this case WINDBG) to the VM over that pipe, after breaking and continuing execution a few times I see the VM crash in HALHandleNMI after a secondaryclockinterrupt occurs. The bugcheck details given via !analyze are also given.
2
3
4###DEBUGGER SESSION COPIED BELOW
5Opened \\.\pipe\vmcom
6Waiting to reconnect...
7Connected to Windows 7 7600 x64 target at (Wed Dec 28 10:26:18.444 2011 (UTC - 5:00)), ptr64 TRUE
8Kernel Debugger connection established.
9Symbol search path is: *** Invalid ***
10****************************************************************************
11* Symbol loading may be unreliable without a symbol search path. *
12* Use .symfix to have the debugger choose a symbol path. *
13* After setting your symbol path, use .reload to refresh symbol locations. *
14****************************************************************************
15Executable search path is:
16*********************************************************************
17* Symbols can not be loaded because symbol path is not initialized. *
18* *
19* The Symbol Path can be set by: *
20* using the _NT_SYMBOL_PATH environment variable. *
21* using the -y <symbol_path> argument when starting the debugger. *
22* using .sympath and .sympath+ *
23*********************************************************************
24*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
25Windows 7 Kernel Version 7600 MP (4 procs) Free x64
26Product: WinNt, suite: TerminalServer SingleUserTS
27Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
28Machine Name:
29Kernel base = 0xfffff800`0284a000 PsLoadedModuleList = 0xfffff800`02a87e50
30Debug session time: Wed Dec 28 10:26:12.029 2011 (UTC - 5:00)
31System Uptime: 0 days 5:12:49.358
32Break instruction exception - code 80000003 (first chance)
33*******************************************************************************
34* *
35* You are seeing this message because you pressed either *
36* CTRL+C (if you run console kernel debugger) or, *
37* CTRL+BREAK (if you run GUI kernel debugger), *
38* on your debugger machine's keyboard. *
39* *
40* THIS IS NOT A BUG OR A SYSTEM CRASH *
41* *
42* If you did not intend to break into the debugger, press the "g" key, then *
43* press the "Enter" key now. This message might immediately reappear. If it *
44* does, press "g" and "Enter" again. *
45* *
46*******************************************************************************
47nt!DbgBreakPointWithStatus:
48fffff800`028b3f60 cc int 3
491: kd> .symfix
501: kd> .reload
51Connected to Windows 7 7600 x64 target at (Wed Dec 28 10:33:42.784 2011 (UTC - 5:00)), ptr64 TRUE
52Loading Kernel Symbols
53. -- User interrupt
541: kd> g
55Break instruction exception - code 80000003 (first chance)
56*******************************************************************************
57* *
58* You are seeing this message because you pressed either *
59* CTRL+C (if you run console kernel debugger) or, *
60* CTRL+BREAK (if you run GUI kernel debugger), *
61* on your debugger machine's keyboard. *
62* *
63* THIS IS NOT A BUG OR A SYSTEM CRASH *
64* *
65* If you did not intend to break into the debugger, press the "g" key, then *
66* press the "Enter" key now. This message might immediately reappear. If it *
67* does, press "g" and "Enter" again. *
68* *
69*******************************************************************************
70nt!RtlpBreakWithStatusInstruction:
71fffff800`028b3f60 cc int 3
723: kd> !stack
73No export stack found
743: kd> !ps
75No export ps found
763: kd> !eip
77No export eip found
783: kd> !thread
79THREAD fffff88002f1dfc0 Cid 0000.0000 Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 3
80Not impersonating
81DeviceMap fffff8a0000060c0
82Owning Process fffff80002a43140 Image: Idle
83Attached Process fffffa8000c9e040 Image: System
84Wait Start TickCount 0 Ticks: 1203174 (0:05:12:49.634)
85Context Switch Count 1255366 IdealProcessor: 3
86UserTime 00:00:00.000
87KernelTime 05:11:32.149
88Win32 Start Address nt!KiIdleLoop (0xfffff800028c46a0)
89Stack Init fffff88002f3bdb0 Current fffff88002f3bd40
90Base fffff88002f3c000 Limit fffff88002f36000 Call 0
91Priority 16 BasePriority 0 UnusualBoost 0 ForegroundBoost 0 IoPriority 0 PagePriority 0
92Child-SP RetAddr : Args to Child : Call Site
93fffff880`02f3bac8 fffff800`02882d73 : 00000000`00000000 fffff880`02f13180 00000000`00000000 00000000`00026161 : nt!RtlpBreakWithStatusInstruction
94fffff880`02f3bad0 fffff800`028c8ba1 : 00000000`00000000 fffff880`02f3bb80 fffff880`02f13180 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x5dd4
95fffff880`02f3bb00 fffff880`0450f9c2 : fffff800`028c9a3a 00000000`ffffffed fffffa80`0203b2b8 fffff880`02f1dfc0 : nt!KiSecondaryClockInterrupt+0x131 (TrapFrame @ fffff880`02f3bb00)
96fffff880`02f3bc98 fffff800`028c9a3a : 00000000`ffffffed fffffa80`0203b2b8 fffff880`02f1dfc0 00000000`00000001 : 0xfffff880`0450f9c2
97fffff880`02f3bca0 fffff800`028c46cc : fffff880`02f13180 fffff880`00000000 00000000`00000000 fffff800`02950cf0 : nt!PoIdle+0x53a
98fffff880`02f3bd80 00000000`00000000 : fffff880`02f3c000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c
99
1003: kd> g
101Break instruction exception - code 80000003 (first chance)
102*******************************************************************************
103* *
104* You are seeing this message because you pressed either *
105* CTRL+C (if you run console kernel debugger) or, *
106* CTRL+BREAK (if you run GUI kernel debugger), *
107* on your debugger machine's keyboard. *
108* *
109* THIS IS NOT A BUG OR A SYSTEM CRASH *
110* *
111* If you did not intend to break into the debugger, press the "g" key, then *
112* press the "Enter" key now. This message might immediately reappear. If it *
113* does, press "g" and "Enter" again. *
114* *
115*******************************************************************************
116nt!RtlpBreakWithStatusInstruction:
117fffff800`028b3f60 cc int 3
1182: kd> g
119Break instruction exception - code 80000003 (first chance)
120nt!RtlpBreakWithStatusInstruction:
121fffff800`028b3f60 cc int 3
1223: kd> !thread
123THREAD fffff88002f1dfc0 Cid 0000.0000 Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 3
124Not impersonating
125DeviceMap fffff8a0000060c0
126Owning Process fffff80002a43140 Image: Idle
127Attached Process fffffa8000c9e040 Image: System
128Wait Start TickCount 0 Ticks: 1204506 (0:05:13:10.414)
129Context Switch Count 1260552 IdealProcessor: 3
130UserTime 00:00:00.000
131KernelTime 05:11:52.335
132Win32 Start Address nt!KiIdleLoop (0xfffff800028c46a0)
133Stack Init fffff88002f3bdb0 Current fffff88002f3bd40
134Base fffff88002f3c000 Limit fffff88002f36000 Call 0
135Priority 16 BasePriority 0 UnusualBoost 0 ForegroundBoost 0 IoPriority 0 PagePriority 0
136Child-SP RetAddr : Args to Child : Call Site
137fffff880`02f1db58 fffff800`029b16d2 : fffff800`00000010 fffffa80`01be2a20 00000000`00000000 fffff800`029b17e2 : nt!RtlpBreakWithStatusInstruction
138fffff880`02f1db60 fffff800`028138da : fffff800`00000005 00000028`00000025 00000000`0000027f fffff800`028292b0 : nt!KiBugCheckDebugBreak+0x12
139fffff880`02f1dbc0 fffff800`029d0513 : 00000000`00000001 fffff800`028292b0 00000000`00000000 00000000`0000005c : hal!HalBugCheckSystem+0x1ba
140fffff880`02f1dc00 fffff800`0280d6c1 : fffffa80`000006c0 fffff880`02f1de20 fffff880`02f1dcf0 fffff800`028292b0 : nt!WheaReportHwError+0x263
141fffff880`02f1dc60 fffff800`02974311 : fffff880`02f1de30 00000000`00000001 00000000`00000001 fffffa80`0203b200 : hal!HalHandleNMI+0x149
142fffff880`02f1dc90 fffff800`028b9202 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000003 : nt!KiProcessNMI+0x131
143fffff880`02f1dcf0 fffff800`028b9063 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82
144fffff880`02f1de30 fffff800`028c8acf : 00000000`00000000 fffff880`02f3bb80 fffff880`02f13180 00000000`00000001 : nt!KiNmiInterrupt+0x163 (TrapFrame @ fffff880`02f1de30)
145fffff880`02f3bb00 fffff880`0450f9c2 : fffff800`028c9a3a 00000000`ffffffed fffffa80`0203b2b8 fffff880`02f1dfc0 : nt!KiSecondaryClockInterrupt+0x5f (TrapFrame @ fffff880`02f3bb00)
146fffff880`02f3bc98 fffff800`028c9a3a : 00000000`ffffffed fffffa80`0203b2b8 fffff880`02f1dfc0 00000000`00000001 : 0xfffff880`0450f9c2
147fffff880`02f3bca0 fffff800`028c46cc : fffff880`02f13180 fffff880`00000000 00000000`00000000 fffff800`02950cf0 : nt!PoIdle+0x53a
148fffff880`02f3bd80 00000000`00000000 : fffff880`02f3c000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c
149
150
1513: kd> !analyze -v
152TRIAGER: Could not open triage file : C:\Program Files\Windows Kits\8.0\Debuggers\x64\triage\oca.ini, error 2
153TRIAGER: Could not open triage file : C:\Program Files\Windows Kits\8.0\Debuggers\x64\winxp\triage.ini, error 2
154TRIAGER: Could not open triage file : C:\Program Files\Windows Kits\8.0\Debuggers\x64\triage\user.ini, error 2
155Connected to Windows 7 7600 x64 target at (Wed Dec 28 10:49:24.239 2011 (UTC - 5:00)), ptr64 TRUE
156Loading Kernel Symbols
157...............................................................
158................................................................
159.............
160Loading User Symbols
161
162Loading unloaded module list
163................
164*******************************************************************************
165* *
166* Bugcheck Analysis *
167* *
168*******************************************************************************
169
170Unknown bugcheck code (111)
171Unknown bugcheck description
172Arguments:
173Arg1: 0000000000000000
174Arg2: 0000000000000000
175Arg3: 0000000000000000
176Arg4: 0000000000000000
177
178Debugging Details:
179------------------
180
181*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
182TRIAGER: Could not open triage file : C:\Program Files\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
183
184DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
185
186BUGCHECK_STR: 0x111
187
188PROCESS_NAME: System
189
190CURRENT_IRQL: f
191
192LAST_CONTROL_TRANSFER: from fffff800029b16d2 to fffff800028b3f60
193
194STACK_TEXT:
195fffff880`02f1db58 fffff800`029b16d2 : fffff800`00000010 fffffa80`01be2a20 00000000`00000000 fffff800`029b17e2 : nt!RtlpBreakWithStatusInstruction
196fffff880`02f1db60 fffff800`028138da : fffff800`00000005 00000028`00000025 00000000`0000027f fffff800`028292b0 : nt!KiBugCheckDebugBreak+0x12
197fffff880`02f1dbc0 fffff800`029d0513 : 00000000`00000001 fffff800`028292b0 00000000`00000000 00000000`0000005c : hal!HalBugCheckSystem+0x1ba
198fffff880`02f1dc00 fffff800`0280d6c1 : fffffa80`000006c0 fffff880`02f1de20 fffff880`02f1dcf0 fffff800`028292b0 : nt!WheaReportHwError+0x263
199fffff880`02f1dc60 fffff800`02974311 : fffff880`02f1de30 00000000`00000001 00000000`00000001 fffffa80`0203b200 : hal!HalHandleNMI+0x149
200fffff880`02f1dc90 fffff800`028b9202 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000003 : nt!KiProcessNMI+0x131
201fffff880`02f1dcf0 fffff800`028b9063 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82
202fffff880`02f1de30 fffff800`028c8acf : 00000000`00000000 fffff880`02f3bb80 fffff880`02f13180 00000000`00000001 : nt!KiNmiInterrupt+0x163
203fffff880`02f3bb00 fffff880`0450f9c2 : fffff800`028c9a3a 00000000`ffffffed fffffa80`0203b2b8 fffff880`02f1dfc0 : nt!KiSecondaryClockInterrupt+0x5f
204fffff880`02f3bc98 fffff800`028c9a3a : 00000000`ffffffed fffffa80`0203b2b8 fffff880`02f1dfc0 00000000`00000001 : intelppm+0x39c2
205fffff880`02f3bca0 fffff800`028c46cc : fffff880`02f13180 fffff880`00000000 00000000`00000000 fffff800`02950cf0 : nt!PoIdle+0x53a
206fffff880`02f3bd80 00000000`00000000 : fffff880`02f3c000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c
207
208
209STACK_COMMAND: kb
210
211FOLLOWUP_IP:
212intelppm+39c2
213fffff880`0450f9c2 c3 ret
214
215SYMBOL_STACK_INDEX: 9
216
217SYMBOL_NAME: intelppm+39c2
218
219FOLLOWUP_NAME: MachineOwner
220
221MODULE_NAME: intelppm
222
223IMAGE_NAME: intelppm.sys
224
225DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc0fd
226
227FAILURE_BUCKET_ID: X64_0x111_intelppm+39c2
228
229BUCKET_ID: X64_0x111_intelppm+39c2
230
231Followup: MachineOwner
232---------

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