Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini061410-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\Symbole*http://msdl.microsoft.com/download/symbols Executable search path is: Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 2600.xpsp_sp3_gdr.100216-1514 Machine Name: Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720 Debug session time: Mon Jun 14 09:21:02.828 2010 (GMT+2) System Uptime: 0 days 0:02:15.561 Loading Kernel Symbols ............................................................... ......................................................... Loading User Symbols Loading unloaded module list ........ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, 80637625, b60b78dc, 0} Unable to load image aswSP.SYS, Win32 error 0n2 *** WARNING: Unable to verify timestamp for aswSP.SYS *** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS Probably caused by : memory_corruption Followup: memory_corruption --------- 1: 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: c0000005, The exception code that was not handled Arg2: 80637625, The address that the exception occurred at Arg3: b60b78dc, Trap Frame Arg4: 00000000 Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod "0x%08lx" odwo FAULTING_IP: nt!HvpGetCellMapped+5f 80637625 8b4304 mov eax,dword ptr [ebx+4] TRAP_FRAME: b60b78dc -- (.trap 0xffffffffb60b78dc) ErrCode = 00000000 eax=00001bb0 ebx=00001bb0 ecx=8a5ef488 edx=000003fb esi=e1743b60 edi=00000dc7 eip=80637625 esp=b60b7950 ebp=b60b7998 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!HvpGetCellMapped+0x5f: 80637625 8b4304 mov eax,dword ptr [ebx+4] ds:0023:00001bb4=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0x8E PROCESS_NAME: lsass.exe LAST_CONTROL_TRANSFER: from 8062f490 to 80637625 STACK_TEXT: b60b7998 8062f490 e1743b60 ff7bbdc7 8a3c22e4 nt!HvpGetCellMapped+0x5f b60b7b6c 805bf434 ff7bbdc7 ff7bbdc7 8a3c2240 nt!CmpParseKey+0x42e b60b7be4 805bb9c0 00000000 b60b7c24 00000040 nt!ObpLookupObjectName+0x53c b60b7c38 80624d6e 00000000 8a6eb418 00000001 nt!ObOpenObjectByName+0xea b60b7d34 b5ec867a 00d3fa30 00000001 00d3f9cc nt!NtOpenKey+0x1c8 WARNING: Stack unwind information not available. Following frames may be wrong. b60b7d50 8054163c 00d3fa30 00000001 00d3f9cc aswSP+0x867a b60b7d50 7c90e514 00d3fa30 00000001 00d3f9cc nt!KiFastCallEntry+0xfc 00d3fb64 00000000 00000000 00000000 00000000 0x7c90e514 STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt 806378f7 - nt!HvpIsFreeNeighbor+25 [ 39:31 ] 1 error : !nt (806378f7) MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: ONE_BIT FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT Followup: memory_corruption ---------