Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\New folder\022510-20607-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c65000 PsLoadedModuleList = 0xfffff800`02ea2e50
Debug session time: Thu Feb 25 08:46:35.923 2010 (GMT-5)
System Uptime: 0 days 1:25:39.765
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002cc55fe, fffff88003124788, fffff88003123fe0}
Probably caused by : memory_corruption ( nt!MiFlushSectionInternal+e95 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002cc55fe, The address that the exception occurred at
Arg3: fffff88003124788, Exception Record Address
Arg4: fffff88003123fe0, Context Record Address
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!MiFlushSectionInternal+e95
fffff800`02cc55fe 4d8b7908 mov r15,qword ptr [r9+8]
EXCEPTION_RECORD: fffff88003124788 -- (.exr 0xfffff88003124788)
ExceptionAddress: fffff80002cc55fe (nt!MiFlushSectionInternal+0x0000000000000e95)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88003123fe0 -- (.cxr 0xfffff88003123fe0)
rax=0000000000000000 rbx=fffffa80045bb200 rcx=fffffa80045bb300
rdx=fffff80002ea3600 rsi=fffff880009ea180 rdi=0000000000000002
rip=fffff80002cc55fe rsp=fffff880031249c0 rbp=0000000000000000
r8=fffffa80045bb2b0 r9=0100000000000000 r10=fffffa80045bb278
r11=00000000001fe000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
nt!MiFlushSectionInternal+0xe95:
fffff800`02cc55fe 4d8b7908 mov r15,qword ptr [r9+8] ds:002b:01000000`00000008=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f0d0e0
ffffffffffffffff
FOLLOWUP_IP:
nt!MiFlushSectionInternal+e95
fffff800`02cc55fe 4d8b7908 mov r15,qword ptr [r9+8]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff80002dd8df5 to fffff80002cc55fe
STACK_TEXT:
fffff880`031249c0 fffff800`02dd8df5 : 00000000`00000000 00000000`00000008 fffffa80`045bb2b0 00000000`00000000 : nt!MiFlushSectionInternal+0xe95
fffff880`03124c00 fffff800`02dfd483 : 00000000`00000080 00000000`00000000 00000000`00000001 fffff800`02dfd4d0 : nt!MiDeleteCachedSegment+0x295
fffff880`03124c90 fffff800`02dfd5d3 : 00000000`00000005 fffff880`03124d00 fffffa80`00000001 ffffffff`00000012 : nt!MiRemoveUnusedSegments+0x73
fffff880`03124cc0 fffff800`02f7a166 : ffffffff`ffffffff ffffffff`ffffffff ffffffff`ffffffff ffffffff`ffffffff : nt!MiDereferenceSegmentThread+0x103
fffff880`03124d40 fffff800`02cb5486 : fffff800`02e4fe80 fffffa80`039ebb60 fffff800`02e5dc40 ffffffff`ffffffff : nt!PspSystemThreadStartup+0x5a
fffff880`03124d80 00000000`00000000 : fffff880`03125000 fffff880`0311f000 fffff880`03124800 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiFlushSectionInternal+e95
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
STACK_COMMAND: .cxr 0xfffff88003123fe0 ; kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x7E_nt!MiFlushSectionInternal+e95
BUCKET_ID: X64_0x7E_nt!MiFlushSectionInternal+e95
Followup: MachineOwner
---------
