Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\051210-21403-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*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
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x83038000 PsLoadedModuleList = 0x83177570
Debug session time: Tue May 11 23:29:58.128 2010 (GMT-4)
System Uptime: 0 days 3:06:04.907
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c000001d, 8306f697, 88ff2cc0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiTrap07+cf )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c000001d, The exception code that was not handled
Arg2: 8306f697, The address that the exception occurred at
Arg3: 88ff2cc0, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
FAULTING_IP:
nt!KiTrap07+cf
8306f697 0fae29 xrstor [ecx]
TRAP_FRAME: 88ff2cc0 -- (.trap 0xffffffff88ff2cc0)
ErrCode = 00000000
eax=00000007 ebx=80010031 ecx=88ff2dc0 edx=00000000 esi=0305fd04 edi=85506030
eip=8306f697 esp=88ff2d34 ebp=88ff2d34 iopl=0 nv up di pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010006
nt!KiTrap07+0xcf:
8306f697 0fae29 xrstor [ecx]
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: audiodg.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 703b7a89 to 8306f697
FAILED_INSTRUCTION_ADDRESS:
nt!KiTrap07+cf
8306f697 0fae29 xrstor [ecx]
STACK_TEXT:
88ff2d34 703b7a89 badb0d00 00000000 00000000 nt!KiTrap07+0xcf
WARNING: Frame IP not in any known module. Following frames may be wrong.
0305fc7c 00000000 00000000 00000000 00000000 0x703b7a89
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiTrap07+cf
8306f697 0fae29 xrstor [ecx]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiTrap07+cf
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbffc
FAILURE_BUCKET_ID: 0x8E_BAD_IP_nt!KiTrap07+cf
BUCKET_ID: 0x8E_BAD_IP_nt!KiTrap07+cf
Followup: MachineOwner
---------