Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Jonathan\Desktop\minidumps_ao032710\032710-21808-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 (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02851000 PsLoadedModuleList = 0xfffff800`02a8ee50
Debug session time: Sat Mar 27 00:32:05.386 2010 (GMT-4)
System Uptime: 0 days 7:11:11.399
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff800028b7a3c, fffff88002dcba38, fffff88002dcb290}
Probably caused by : memory_corruption ( nt!MmInPageKernelStack+48 )
Followup: MachineOwner
---------
2: 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: fffff800028b7a3c, The address that the exception occurred at
Arg3: fffff88002dcba38, Exception Record Address
Arg4: fffff88002dcb290, 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!MmInPageKernelStack+48
fffff800`028b7a3c 49894308 mov qword ptr [r11+8],rax
EXCEPTION_RECORD: fffff88002dcba38 -- (.exr 0xfffff88002dcba38)
ExceptionAddress: fffff800028b7a3c (nt!MmInPageKernelStack+0x0000000000000048)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88002dcb290 -- (.cxr 0xfffff88002dcb290)
rax=fffff880020ec000 rbx=fffffa8006531b60 rcx=0000000000000002
rdx=0000000000017fe9 rsi=fffffa80036cd740 rdi=0000000000000000
rip=fffff800028b7a3c rsp=fffff88002dcbc70 rbp=0000000000000080
r8=0000000000000001 r9=0000000000095ebd r10=00000000000011a4
r11=effff880020f1db0 r12=0000000000000000 r13=fffff800028b75e8
r14=0000000000000000 r15=fffff80003959080
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nt!MmInPageKernelStack+0x48:
fffff800`028b7a3c 49894308 mov qword ptr [r11+8],rax ds:002b:effff880`020f1db8=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
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 fffff80002af90e0
ffffffffffffffff
FOLLOWUP_IP:
nt!MmInPageKernelStack+48
fffff800`028b7a3c 49894308 mov qword ptr [r11+8],rax
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff800028b79cf to fffff800028b7a3c
STACK_TEXT:
fffff880`02dcbc70 fffff800`028b79cf : fffffa80`06539060 00000000`00000080 fffffa80`036cd740 fffffa80`06531c00 : nt!MmInPageKernelStack+0x48
fffff880`02dcbcd0 fffff800`028b766c : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`036cd700 : nt!KiInSwapKernelStacks+0x1f
fffff880`02dcbd00 fffff800`02b66166 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSwapProcessOrStack+0x84
fffff880`02dcbd40 fffff800`028a1486 : fffff800`02a3be80 fffffa80`036f3680 fffff800`02a49c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02dcbd80 00000000`00000000 : fffff880`02dcc000 fffff880`02dc6000 fffff880`02dcba50 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MmInPageKernelStack+48
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
STACK_COMMAND: .cxr 0xfffff88002dcb290 ; kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x7E_nt!MmInPageKernelStack+48
BUCKET_ID: X64_0x7E_nt!MmInPageKernelStack+48
Followup: MachineOwner
---------
