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: 82a99317, The address that the exception occurred at
Arg3: 9ecb4cc0, 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
82a99317 0fae29          xrstor  [ecx]
TRAP_FRAME:  9ecb4cc0 -- (.trap 0xffffffff9ecb4cc0)
ErrCode = 00000000
eax=00000007 ebx=80010031 ecx=9ecb4dc0 edx=00000000 esi=11cc42f0 edi=84c3b938
eip=82a99317 esp=9ecb4d34 ebp=9ecb4d34 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:
82a99317 0fae29          xrstor  [ecx]
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x8E
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from 6cc05792 to 82a99317
FAILED_INSTRUCTION_ADDRESS: 
nt!KiTrap07+cf
82a99317 0fae29          xrstor  [ecx]
STACK_TEXT:  
9ecb4d34 6cc05792 badb0d00 77db6344 00000000 nt!KiTrap07+0xcf
WARNING: Frame IP not in any known module. Following frames may be wrong.
1329fefc 00000000 00000000 00000000 00000000 0x6cc05792
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!KiTrap07+cf
82a99317 0fae29          xrstor  [ecx]
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  nt!KiTrap07+cf
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fd915
FAILURE_BUCKET_ID:  0x8E_BAD_IP_nt!KiTrap07+cf
BUCKET_ID:  0x8E_BAD_IP_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: 82a99317, The address that the exception occurred at
Arg3: 9ecb4cc0, 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
82a99317 0fae29          xrstor  [ecx]
TRAP_FRAME:  9ecb4cc0 -- (.trap 0xffffffff9ecb4cc0)
ErrCode = 00000000
eax=00000007 ebx=80010031 ecx=9ecb4dc0 edx=00000000 esi=11cc42f0 edi=84c3b938
eip=82a99317 esp=9ecb4d34 ebp=9ecb4d34 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:
82a99317 0fae29          xrstor  [ecx]
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x8E
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from 6cc05792 to 82a99317
FAILED_INSTRUCTION_ADDRESS: 
nt!KiTrap07+cf
82a99317 0fae29          xrstor  [ecx]
STACK_TEXT:  
9ecb4d34 6cc05792 badb0d00 77db6344 00000000 nt!KiTrap07+0xcf
WARNING: Frame IP not in any known module. Following frames may be wrong.
1329fefc 00000000 00000000 00000000 00000000 0x6cc05792
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!KiTrap07+cf
82a99317 0fae29          xrstor  [ecx]
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  nt!KiTrap07+cf
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fd915
FAILURE_BUCKET_ID:  0x8E_BAD_IP_nt!KiTrap07+cf
BUCKET_ID:  0x8E_BAD_IP_nt!KiTrap07+cf
Followup: MachineOwner
---------