Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\DMP\011811-28392-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82a08000 PsLoadedModuleList = 0x82b50810
Debug session time: Tue Jan 18 15:39:43.378 2011 (UTC - 5:00)
System Uptime: 0 days 0:07:12.126
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 82ac7edd, ae6dfac0, 0}
Probably caused by : memory_corruption ( nt!MiCheckForConflictingNode+16 )
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: c0000005, The exception code that was not handled
Arg2: 82ac7edd, The address that the exception occurred at
Arg3: ae6dfac0, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!MiCheckForConflictingNode+16
82ac7edd 3b4810 cmp ecx,dword ptr [eax+10h]
TRAP_FRAME: ae6dfac0 -- (.trap 0xffffffffae6dfac0)
ErrCode = 00000000
eax=04465000 ebx=00017000 ecx=000742c0 edx=000742c0 esi=7ffdffff edi=742c0000
eip=82ac7edd esp=ae6dfb34 ebp=ae6dfb34 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!MiCheckForConflictingNode+0x16:
82ac7edd 3b4810 cmp ecx,dword ptr [eax+10h] ds:0023:04465010=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: WerFault.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82ac576c to 82ac7edd
STACK_TEXT:
ae6dfb34 82ac576c 000742c0 000742d6 ae6dfbe8 nt!MiCheckForConflictingNode+0x16
ae6dfb44 82c5d699 8571d840 88312a74 85729d48 nt!MiCheckForConflictingVadExistence+0x1a
ae6dfbe8 82c768e9 8888c080 8571d840 ae6dfce4 nt!MiMapViewOfImageSection+0x35c
ae6dfc58 82c871b1 8571d840 ae6dfce4 00000000 nt!MiMapViewOfSection+0x22e
ae6dfc88 82c870dc b19de4b8 8571d840 ae6dfce4 nt!MmMapViewOfSection+0x2a
ae6dfd04 82a4b42a 0000021c ffffffff 0019cdd0 nt!NtMapViewOfSection+0x204
ae6dfd04 76df64f4 0000021c ffffffff 0019cdd0 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0019cedc 00000000 00000000 00000000 00000000 0x76df64f4
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiCheckForConflictingNode+16
82ac7edd 3b4810 cmp ecx,dword ptr [eax+10h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiCheckForConflictingNode+16
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc007
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x8E_nt!MiCheckForConflictingNode+16
BUCKET_ID: 0x8E_nt!MiCheckForConflictingNode+16
Followup: MachineOwner
---------