Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\MEMORY.DMP] Kernel Summary Dump File: Only kernel address space is available Symbol search path is: http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16617.x86fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0x83049000 PsLoadedModuleList = 0x83191810 Debug session time: Fri Aug 27 23:50:27.008 2010 (GMT+2) System Uptime: 1 days 21:34:43.865 WARNING: Process directory table base 7D3BC600 doesn't match CR3 00185000 WARNING: Process directory table base 7D3BC600 doesn't match CR3 00185000 Loading Kernel Symbols ............................................................... ................................................................ ........................... Loading User Symbols PEB is paged out (Peb.Ldr = 7ffdf00c). Type ".hh dbgerr001" for details Loading unloaded module list ....................... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7F, {8, 807c7750, 0, 0} *** ERROR: Symbol file could not be found. Defaulted to export symbols for VMMR0.r0 - PEB is paged out (Peb.Ldr = 7ffdf00c). Type ".hh dbgerr001" for details PEB is paged out (Peb.Ldr = 7ffdf00c). Type ".hh dbgerr001" for details Probably caused by : VMMR0.r0 ( VMMR0!EMInterpretWrmsr+677 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 00000008, EXCEPTION_DOUBLE_FAULT Arg2: 807c7750 Arg3: 00000000 Arg4: 00000000 Debugging Details: ------------------ PEB is paged out (Peb.Ldr = 7ffdf00c). Type ".hh dbgerr001" for details PEB is paged out (Peb.Ldr = 7ffdf00c). Type ".hh dbgerr001" for details BUGCHECK_STR: 0x7f_8 TSS: 00000028 -- (.tss 0x28) eax=fffffb84 ebx=92ec4000 ecx=00000000 edx=92ec5054 esi=92edf900 edi=92ee1388 eip=9c6fc3d7 esp=00067d48 ebp=00067d48 iopl=0 nv up ei ng nz ac pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010296 VMMR0!EMInterpretWrmsr+0x677: 9c6fc3d7 5d pop ebp Resetting default scope DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: VirtualBox.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from 00000000 to 9c6fc3d7 STACK_TEXT: 00067d48 00000000 00000000 00000000 00000000 VMMR0!EMInterpretWrmsr+0x677 STACK_COMMAND: .tss 0x28 ; kb FOLLOWUP_IP: VMMR0!EMInterpretWrmsr+677 9c6fc3d7 5d pop ebp SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: VMMR0!EMInterpretWrmsr+677 FOLLOWUP_NAME: MachineOwner MODULE_NAME: VMMR0 IMAGE_NAME: VMMR0.r0 DEBUG_FLR_IMAGE_TIMESTAMP: 4c5aa99e FAILURE_BUCKET_ID: 0x7f_8_VMMR0!EMInterpretWrmsr+677 BUCKET_ID: 0x7f_8_VMMR0!EMInterpretWrmsr+677 Followup: MachineOwner ---------