id,summary,reporter,owner,description,type,status,component,version,resolution,keywords,cc,guest,host 10097,Win7 VM's crash when a debugger is connected via virtualized COM port pipe (ICH9 only),matthew.robben@gmail.com,,"I'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. {{{ Opened \.\pipe\vmcom Waiting to reconnect... Connected to Windows 7 7600 x64 target at (Wed Dec 28 10:26:18.444 2011 (UTC - 5:00)), ptr64 TRUE Kernel Debugger connection established. Symbol search path is: *** Invalid *** **************************************************************************** * Symbol loading may be unreliable without a symbol search path. * * Use .symfix to have the debugger choose a symbol path. * * After setting your symbol path, use .reload to refresh symbol locations. * **************************************************************************** Executable search path is: ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe - Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`0284a000 PsLoadedModuleList = 0xfffff800`02a87e50 Debug session time: Wed Dec 28 10:26:12.029 2011 (UTC - 5:00) System Uptime: 0 days 5:12:49.358 Break instruction exception - code 80000003 (first chance) ******************************************************************************* * * * You are seeing this message because you pressed either * * CTRL+C (if you run console kernel debugger) or, * * CTRL+BREAK (if you run GUI kernel debugger), * * on your debugger machine's keyboard. * * * * THIS IS NOT A BUG OR A SYSTEM CRASH * * * * If you did not intend to break into the debugger, press the ""g"" key, then * * press the ""Enter"" key now. This message might immediately reappear. If it * * does, press ""g"" and ""Enter"" again. * * * ******************************************************************************* nt!DbgBreakPointWithStatus: fffff800`028b3f60 cc int 3 1: kd> .symfix 1: kd> .reload Connected to Windows 7 7600 x64 target at (Wed Dec 28 10:33:42.784 2011 (UTC - 5:00)), ptr64 TRUE Loading Kernel Symbols . -- User interrupt 1: kd> g Break instruction exception - code 80000003 (first chance) ******************************************************************************* * * * You are seeing this message because you pressed either * * CTRL+C (if you run console kernel debugger) or, * * CTRL+BREAK (if you run GUI kernel debugger), * * on your debugger machine's keyboard. * * * * THIS IS NOT A BUG OR A SYSTEM CRASH * * * * If you did not intend to break into the debugger, press the ""g"" key, then * * press the ""Enter"" key now. This message might immediately reappear. If it * * does, press ""g"" and ""Enter"" again. * * * ******************************************************************************* nt!RtlpBreakWithStatusInstruction: fffff800`028b3f60 cc int 3 3: kd> !stack No export stack found 3: kd> !ps No export ps found 3: kd> !eip No export eip found 3: kd> !thread THREAD fffff88002f1dfc0 Cid 0000.0000 Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 3 Not impersonating DeviceMap fffff8a0000060c0 Owning Process fffff80002a43140 Image: Idle Attached Process fffffa8000c9e040 Image: System Wait Start TickCount 0 Ticks: 1203174 (0:05:12:49.634) Context Switch Count 1255366 IdealProcessor: 3 UserTime 00:00:00.000 KernelTime 05:11:32.149 Win32 Start Address nt!KiIdleLoop (0xfffff800028c46a0) Stack Init fffff88002f3bdb0 Current fffff88002f3bd40 Base fffff88002f3c000 Limit fffff88002f36000 Call 0 Priority 16 BasePriority 0 UnusualBoost 0 ForegroundBoost 0 IoPriority 0 PagePriority 0 Child-SP RetAddr : Args to Child : Call Site fffff880`02f3bac8 fffff800`02882d73 : 00000000`00000000 fffff880`02f13180 00000000`00000000 00000000`00026161 : nt!RtlpBreakWithStatusInstruction fffff880`02f3bad0 fffff800`028c8ba1 : 00000000`00000000 fffff880`02f3bb80 fffff880`02f13180 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x5dd4 fffff880`02f3bb00 fffff880`0450f9c2 : fffff800`028c9a3a 00000000`ffffffed fffffa80`0203b2b8 fffff880`02f1dfc0 : nt!KiSecondaryClockInterrupt+0x131 (TrapFrame @ fffff880`02f3bb00) fffff880`02f3bc98 fffff800`028c9a3a : 00000000`ffffffed fffffa80`0203b2b8 fffff880`02f1dfc0 00000000`00000001 : 0xfffff880`0450f9c2 fffff880`02f3bca0 fffff800`028c46cc : fffff880`02f13180 fffff880`00000000 00000000`00000000 fffff800`02950cf0 : nt!PoIdle+0x53a fffff880`02f3bd80 00000000`00000000 : fffff880`02f3c000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c 3: kd> g Break instruction exception - code 80000003 (first chance) ******************************************************************************* * * * You are seeing this message because you pressed either * * CTRL+C (if you run console kernel debugger) or, * * CTRL+BREAK (if you run GUI kernel debugger), * * on your debugger machine's keyboard. * * * * THIS IS NOT A BUG OR A SYSTEM CRASH * * * * If you did not intend to break into the debugger, press the ""g"" key, then * * press the ""Enter"" key now. This message might immediately reappear. If it * * does, press ""g"" and ""Enter"" again. * * * ******************************************************************************* nt!RtlpBreakWithStatusInstruction: fffff800`028b3f60 cc int 3 2: kd> g Break instruction exception - code 80000003 (first chance) nt!RtlpBreakWithStatusInstruction: fffff800`028b3f60 cc int 3 3: kd> !thread THREAD fffff88002f1dfc0 Cid 0000.0000 Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 3 Not impersonating DeviceMap fffff8a0000060c0 Owning Process fffff80002a43140 Image: Idle Attached Process fffffa8000c9e040 Image: System Wait Start TickCount 0 Ticks: 1204506 (0:05:13:10.414) Context Switch Count 1260552 IdealProcessor: 3 UserTime 00:00:00.000 KernelTime 05:11:52.335 Win32 Start Address nt!KiIdleLoop (0xfffff800028c46a0) Stack Init fffff88002f3bdb0 Current fffff88002f3bd40 Base fffff88002f3c000 Limit fffff88002f36000 Call 0 Priority 16 BasePriority 0 UnusualBoost 0 ForegroundBoost 0 IoPriority 0 PagePriority 0 Child-SP RetAddr : Args to Child : Call Site fffff880`02f1db58 fffff800`029b16d2 : fffff800`00000010 fffffa80`01be2a20 00000000`00000000 fffff800`029b17e2 : nt!RtlpBreakWithStatusInstruction fffff880`02f1db60 fffff800`028138da : fffff800`00000005 00000028`00000025 00000000`0000027f fffff800`028292b0 : nt!KiBugCheckDebugBreak+0x12 fffff880`02f1dbc0 fffff800`029d0513 : 00000000`00000001 fffff800`028292b0 00000000`00000000 00000000`0000005c : hal!HalBugCheckSystem+0x1ba fffff880`02f1dc00 fffff800`0280d6c1 : fffffa80`000006c0 fffff880`02f1de20 fffff880`02f1dcf0 fffff800`028292b0 : nt!WheaReportHwError+0x263 fffff880`02f1dc60 fffff800`02974311 : fffff880`02f1de30 00000000`00000001 00000000`00000001 fffffa80`0203b200 : hal!HalHandleNMI+0x149 fffff880`02f1dc90 fffff800`028b9202 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000003 : nt!KiProcessNMI+0x131 fffff880`02f1dcf0 fffff800`028b9063 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82 fffff880`02f1de30 fffff800`028c8acf : 00000000`00000000 fffff880`02f3bb80 fffff880`02f13180 00000000`00000001 : nt!KiNmiInterrupt+0x163 (TrapFrame @ fffff880`02f1de30) fffff880`02f3bb00 fffff880`0450f9c2 : fffff800`028c9a3a 00000000`ffffffed fffffa80`0203b2b8 fffff880`02f1dfc0 : nt!KiSecondaryClockInterrupt+0x5f (TrapFrame @ fffff880`02f3bb00) fffff880`02f3bc98 fffff800`028c9a3a : 00000000`ffffffed fffffa80`0203b2b8 fffff880`02f1dfc0 00000000`00000001 : 0xfffff880`0450f9c2 fffff880`02f3bca0 fffff800`028c46cc : fffff880`02f13180 fffff880`00000000 00000000`00000000 fffff800`02950cf0 : nt!PoIdle+0x53a fffff880`02f3bd80 00000000`00000000 : fffff880`02f3c000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c 3: kd> !analyze -v TRIAGER: Could not open triage file : C:\Program Files\Windows Kits\8.0\Debuggers\x64\triage\oca.ini, error 2 TRIAGER: Could not open triage file : C:\Program Files\Windows Kits\8.0\Debuggers\x64\winxp\triage.ini, error 2 TRIAGER: Could not open triage file : C:\Program Files\Windows Kits\8.0\Debuggers\x64\triage\user.ini, error 2 Connected to Windows 7 7600 x64 target at (Wed Dec 28 10:49:24.239 2011 (UTC - 5:00)), ptr64 TRUE Loading Kernel Symbols ............................................................... ................................................................ ............. Loading User Symbols Loading unloaded module list ................ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Unknown bugcheck code (111) Unknown bugcheck description Arguments: Arg1: 0000000000000000 Arg2: 0000000000000000 Arg3: 0000000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ *** ERROR: Module load completed but symbols could not be loaded for intelppm.sys TRIAGER: Could not open triage file : C:\Program Files\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0x111 PROCESS_NAME: System CURRENT_IRQL: f LAST_CONTROL_TRANSFER: from fffff800029b16d2 to fffff800028b3f60 STACK_TEXT: fffff880`02f1db58 fffff800`029b16d2 : fffff800`00000010 fffffa80`01be2a20 00000000`00000000 fffff800`029b17e2 : nt!RtlpBreakWithStatusInstruction fffff880`02f1db60 fffff800`028138da : fffff800`00000005 00000028`00000025 00000000`0000027f fffff800`028292b0 : nt!KiBugCheckDebugBreak+0x12 fffff880`02f1dbc0 fffff800`029d0513 : 00000000`00000001 fffff800`028292b0 00000000`00000000 00000000`0000005c : hal!HalBugCheckSystem+0x1ba fffff880`02f1dc00 fffff800`0280d6c1 : fffffa80`000006c0 fffff880`02f1de20 fffff880`02f1dcf0 fffff800`028292b0 : nt!WheaReportHwError+0x263 fffff880`02f1dc60 fffff800`02974311 : fffff880`02f1de30 00000000`00000001 00000000`00000001 fffffa80`0203b200 : hal!HalHandleNMI+0x149 fffff880`02f1dc90 fffff800`028b9202 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000003 : nt!KiProcessNMI+0x131 fffff880`02f1dcf0 fffff800`028b9063 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82 fffff880`02f1de30 fffff800`028c8acf : 00000000`00000000 fffff880`02f3bb80 fffff880`02f13180 00000000`00000001 : nt!KiNmiInterrupt+0x163 fffff880`02f3bb00 fffff880`0450f9c2 : fffff800`028c9a3a 00000000`ffffffed fffffa80`0203b2b8 fffff880`02f1dfc0 : nt!KiSecondaryClockInterrupt+0x5f fffff880`02f3bc98 fffff800`028c9a3a : 00000000`ffffffed fffffa80`0203b2b8 fffff880`02f1dfc0 00000000`00000001 : intelppm+0x39c2 fffff880`02f3bca0 fffff800`028c46cc : fffff880`02f13180 fffff880`00000000 00000000`00000000 fffff800`02950cf0 : nt!PoIdle+0x53a fffff880`02f3bd80 00000000`00000000 : fffff880`02f3c000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c STACK_COMMAND: kb FOLLOWUP_IP: intelppm+39c2 fffff880`0450f9c2 c3 ret SYMBOL_STACK_INDEX: 9 SYMBOL_NAME: intelppm+39c2 FOLLOWUP_NAME: MachineOwner MODULE_NAME: intelppm IMAGE_NAME: intelppm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc0fd FAILURE_BUCKET_ID: X64_0x111_intelppm+39c2 BUCKET_ID: X64_0x111_intelppm+39c2 Followup: MachineOwner --------- }}}[[BR]] ",defect,closed,other,VirtualBox 4.1.8,fixed,HAL,,Windows,Windows