Loading Dump File [C:\DUMPS\mainy\020711-31421-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x8280f000 PsLoadedModuleList = 0x8294e570
Debug session time: Mon Feb 7 17:31:43.345 2011 (UTC + 0:00)
System Uptime: 0 days 0:05:15.111
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c000001d, 8286f4f0, 8eed1c54, 0}
Probably caused by : hardware ( nt!KiTrap0E+dc )
Followup: MachineOwner
---------
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: 8286f4f0, The address that the exception occurred at
Arg3: 8eed1c54, 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!MmAccessFault+1967
8286f4f0 ff ???
TRAP_FRAME: 8eed1c54 -- (.trap 0xffffffff8eed1c54)
ErrCode = 00000000
eax=00000000 ebx=00000000 ecx=00000000 edx=80000000 esi=c00262a8 edi=84eb0418
eip=8286f4f0 esp=8eed1cc8 ebp=8eed1d1c iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!MmAccessFault+0x1967:
8286f4f0 ff ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
MISALIGNED_IP:
nt!MmAccessFault+1967
8286f4f0 ff ???
LAST_CONTROL_TRANSFER: from 82847968 to 8286f4f0
FAILED_INSTRUCTION_ADDRESS:
nt!MmAccessFault+1967
8286f4f0 ff ???
STACK_TEXT:
8eed1d1c 82847968 00000001 098aa000 00000001 nt!MmAccessFault+0x1967
8eed1d1c 6c90bb1f 00000001 098aa000 00000001 nt!KiTrap0E+0xdc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0462e984 00000000 00000000 00000000 00000000 0x6c90bb1f
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiTrap0E+dc
82847968 85c0 test eax,eax
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KiTrap0E+dc
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED
BUCKET_ID: IP_MISALIGNED
Followup: MachineOwner
