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 (3)\041010-18439-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c67000 PsLoadedModuleList = 0xfffff800`02ea4e50
Debug session time: Sun Apr 11 00:02:21.328 2010 (GMT-4)
System Uptime: 0 days 0:10:53.030
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002d1fe89, fffff880009a99d8, fffff880009a9230}
Probably caused by : memory_corruption ( nt!MmZeroPageThread+3d4 )
Followup: MachineOwner
---------
0: 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: fffff80002d1fe89, The address that the exception occurred at
Arg3: fffff880009a99d8, Exception Record Address
Arg4: fffff880009a9230, 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!MmZeroPageThread+3d4
fffff800`02d1fe89 f0410fba6d1000 lock bts dword ptr [r13+10h],0
EXCEPTION_RECORD: fffff880009a99d8 -- (.exr 0xfffff880009a99d8)
ExceptionAddress: fffff80002d1fe89 (nt!MmZeroPageThread+0x00000000000003d4)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff880009a9230 -- (.cxr 0xfffff880009a9230)
rax=0000000000000046 rbx=fffbffffffffffff rcx=0000000000000000
rdx=0000000000000000 rsi=fffffa8003f032f0 rdi=0000000000000046
rip=fffff80002d1fe89 rsp=fffff880009a9c10 rbp=00000000000000ff
r8=0000000000000000 r9=0000058000000000 r10=0000000000000002
r11=fffff880009a9c08 r12=0000000000000004 r13=ff3ffa7fffffffd0
r14=0000000000000100 r15=fffff80002e51e80
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
nt!MmZeroPageThread+0x3d4:
fffff800`02d1fe89 f0410fba6d1000 lock bts dword ptr [r13+10h],0 ds:002b:ff3ffa7f`ffffffe0=????????
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 fffff80002f0f0e0
ffffffffffffffff
FOLLOWUP_IP:
nt!MmZeroPageThread+3d4
fffff800`02d1fe89 f0410fba6d1000 lock bts dword ptr [r13+10h],0
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff80002f7c166 to fffff80002d1fe89
STACK_TEXT:
fffff880`009a9c10 fffff800`02f7c166 : fffffa80`03ff1040 00000000`00000080 fffffa80`03f72890 fffff800`02cb7479 : nt!MmZeroPageThread+0x3d4
fffff880`009a9d40 fffff800`02cb7486 : fffff800`02e51e80 fffffa80`03ff1040 fffff800`02e5fc40 00002640`e8000000 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d80 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a99b0 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MmZeroPageThread+3d4
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
STACK_COMMAND: .cxr 0xfffff880009a9230 ; kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x7E_nt!MmZeroPageThread+3d4
BUCKET_ID: X64_0x7E_nt!MmZeroPageThread+3d4
Followup: MachineOwner
---------