Connected to Windows 7 7600 x86 compatible target at (Wed Sep 1 11:37:44.595 2010 (UTC + 2:00)), ptr64 FALSE Loading Kernel Symbols ............................................................... ................................................. Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 93, {1116fadf, 88c02d90, 0, 1} *** ERROR: Symbol file could not be found. Defaulted to export symbols for VBoxSF.sys - Probably caused by : VBoxSF.sys ( VBoxSF+265e ) Followup: MachineOwner --------- nt!RtlpBreakWithStatusInstruction: 827b821c cc int 3 kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* INVALID_KERNEL_HANDLE (93) This message occurs if kernel code (server, redirector, other driver, etc.) attempts to close a handle that is not a valid handle. Arguments: Arg1: 1116fadf, The handle that NtClose was called with. Arg2: 88c02d90, Arg3: 00000000 Arg4: 00000001 Debugging Details: ------------------ DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO BUGCHECK_STR: 0x93 PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from 82679a42 to 827b821c STACK_TEXT: 8078628c 82679a42 00000003 4b04299d 00000000 nt!RtlpBreakWithStatusInstruction 807862dc 8267a523 00000003 00000000 82606c94 nt!KiBugCheckDebugBreak+0x1c 807866a0 826798f2 00000093 1116fadf 88c02d90 nt!KeBugCheck2+0x6a1 807866c4 82db013d 00000093 1116fadf 88c02d90 nt!KeBugCheckEx+0x1e 807866ec 82cd1e9a 88c02d90 1116fadf 00000000 nt!ExMapHandleToPointerEx+0x10d 80786728 82cd215d 1116fadf 00000001 87f84af8 nt!ObReferenceObjectByHandleWithTag+0x20a 8078674c 82affbfd 9116fadf 00000001 87f84af8 nt!ObReferenceObjectByHandle+0x21 80786770 82abb874 9116fadf 00000001 00000000 nt!CmObReferenceObjectByHandle+0x21 80786814 827c6913 9116fadf 80786904 00000002 nt!NtQueryValueKey+0x172 80786814 827b5d01 9116fadf 80786904 00000002 nt!KiFastCallEntry+0x163 807868a4 9116f65e 9116fadf 80786904 00000002 nt!ZwQueryValueKey+0x11 WARNING: Stack unwind information not available. Following frames may be wrong. 8078690c 9116f6f9 9116fadf 91181c84 80786944 VBoxSF+0x265e 8078694c 9116fb02 0000006c 8263c178 00000000 VBoxSF+0x26f9 807869a8 82b345d2 8d1b1958 8d1c2000 8c09afc0 VBoxSF+0x2b02 80786ba4 82e94a0b 80000748 00000001 00000000 nt!IopLoadDriver+0x800 80786bf0 82e91658 00000000 808109f0 00000000 nt!IopInitializeSystemDrivers+0x16d 80786c6c 82e869ae 8080a098 849e2ab8 849e2748 nt!IoInitSystem+0x6ca 80786d4c 82ab2012 80786d90 82d2110c 8080a098 nt!Phase1InitializationDiscard+0xd5e 80786d54 82d2110c 8080a098 4b0426d1 00000000 nt!Phase1Initialization+0xd 80786d90 827cbcc5 82ab2005 8080a098 00000000 nt!PspSystemThreadStartup+0x178 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19 STACK_COMMAND: kb FOLLOWUP_IP: VBoxSF+265e 9116f65e 85c0 test eax,eax SYMBOL_STACK_INDEX: b SYMBOL_NAME: VBoxSF+265e FOLLOWUP_NAME: MachineOwner MODULE_NAME: VBoxSF IMAGE_NAME: VBoxSF.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4c5aa35c FAILURE_BUCKET_ID: 0x93_VRF_VBoxSF+265e BUCKET_ID: 0x93_VRF_VBoxSF+265e Followup: MachineOwner ---------