Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\043010-18688-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
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x81e3e000 PsLoadedModuleList = 0x81f86810
Debug session time: Fri Apr 30 00:18:27.509 2010 (UTC + 8:00)
System Uptime: 0 days 0:07:08.337
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 81f5e943, a187aaac, 0}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+2e3 )
Followup: Pool_corruption
---------
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: c0000005, The exception code that was not handled
Arg2: 81f5e943, The address that the exception occurred at
Arg3: a187aaac, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx
FAULTING_IP:
nt!ExDeferredFreePool+2e3
81f5e943 894604 mov dword ptr [esi+4],eax
TRAP_FRAME: a187aaac -- (.trap 0xffffffffa187aaac)
ErrCode = 00000002
eax=a40068d0 ebx=000001ff ecx=000001ff edx=84032138 esi=00000000 edi=84032000
eip=81f5e943 esp=a187ab20 ebp=a187ab58 iopl=0 nv up ei ng nz ac po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010292
nt!ExDeferredFreePool+0x2e3:
81f5e943 894604 mov dword ptr [esi+4],eax ds:0023:00000004=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: SearchIndexer.
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 81f5d8aa to 81f5e943
STACK_TEXT:
a187ab58 81f5d8aa 84032000 00000000 00000000 nt!ExDeferredFreePool+0x2e3
a187abc0 8206fa7c a3b76810 00000000 846403a8 nt!ExFreePoolWithTag+0x8a4
a187abf4 81e7ad11 846403a8 81f67d20 846403d0 nt!MiSegmentDelete+0x1d8
a187ac20 81eafa73 846403a8 00000000 a7df8c58 nt!MiCheckControlArea+0x202
a187ac40 8206f483 846403a8 00000001 840e43a8 nt!MiDereferenceControlAreaBySection+0x87
a187ac64 8205f73c 846403a8 a7df8c58 a7df8c40 nt!MiSectionDelete+0x103
a187ac7c 81ea6f60 00000000 862c8d48 a7df8c40 nt!ObpRemoveObjectRoutine+0x59
a187ac90 81ea6ed0 a7df8c58 820837cc a05ee3c0 nt!ObfDereferenceObjectWithTag+0x88
a187ac98 820837cc a05ee3c0 862c8d48 00000c9c nt!ObfDereferenceObject+0xd
a187acdc 82084fb2 a05ee3c0 a094b938 8652f030 nt!ObpCloseHandleTableEntry+0x21d
a187ad0c 8208512a 8652f030 851c0001 04bef0c0 nt!ObpCloseHandle+0x7f
a187ad28 81e8144a 00000c9c 04bef0c4 77cb64f4 nt!NtClose+0x4e
a187ad28 77cb64f4 00000c9c 04bef0c4 77cb64f4 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
04bef0c4 00000000 00000000 00000000 00000000 0x77cb64f4
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ExDeferredFreePool+2e3
81f5e943 894604 mov dword ptr [esi+4],eax
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ExDeferredFreePool+2e3
FOLLOWUP_NAME: Pool_corruption
IMAGE_NAME: Pool_Corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: Pool_Corruption
FAILURE_BUCKET_ID: 0x8E_nt!ExDeferredFreePool+2e3
BUCKET_ID: 0x8E_nt!ExDeferredFreePool+2e3
Followup: Pool_corruption
---------
