Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\122909-16270-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`02a1b000 PsLoadedModuleList = 0xfffff800`02c58e50
Debug session time: Tue Dec 29 14:07:11.414 2009 (GMT-5)
System Uptime: 0 days 0:21:11.882
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff880041247ac, fffff880031be788, fffff880031bdfe0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+fec )
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: fffff880041247ac, The address that the exception occurred at
Arg3: fffff880031be788, Exception Record Address
Arg4: fffff880031bdfe0, 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:
dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+fec
fffff880`041247ac 488b11 mov rdx,qword ptr [rcx]
EXCEPTION_RECORD: fffff880031be788 -- (.exr 0xfffff880031be788)
ExceptionAddress: fffff880041247ac (dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0x0000000000000fec)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff880031bdfe0 -- (.cxr 0xfffff880031bdfe0)
rax=0000000000000000 rbx=0000000000000000 rcx=2000000000000000
rdx=fffff8a0091386e0 rsi=fffff8a0091386e0 rdi=0000000000000000
rip=fffff880041247ac rsp=fffff880031be9c0 rbp=fffffa8003d2d000
r8=0000000000010000 r9=0000000000000000 r10=0000000000000001
r11=fffff8a0091387e8 r12=0000000000000000 r13=0000000000000001
r14=fffffa8003d3c6f0 r15=fffff8a0091387e8
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0xfec:
fffff880`041247ac 488b11 mov rdx,qword ptr [rcx] ds:002b:20000000`00000000=????????????????
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 fffff80002cc30e0
ffffffffffffffff
FOLLOWUP_IP:
dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+fec
fffff880`041247ac 488b11 mov rdx,qword ptr [rcx]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff8800411425d to fffff880041247ac
STACK_TEXT:
fffff880`031be9c0 fffff880`0411425d : fffffa80`03d3c6f0 fffff8a0`091386e0 fffffa80`02176400 fffffa80`03d2d000 : dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0xfec
fffff880`031beb30 fffff880`0410f358 : fffffa80`02af6cc0 00000000`00000000 00000000`00000000 fffff880`031beca0 : dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x96d
fffff880`031bec50 fffff880`0412d16d : fffffa80`00000000 fffffa80`03ced010 00000000`6d4d6956 fffff880`00000174 : dxgmms1!VidMmiProcessTerminationCommand+0x4c
fffff880`031beca0 fffff880`0412c3f8 : fffff800`00b96080 fffffa80`024b8200 00000000`00000000 fffffa80`03ced010 : dxgmms1!VidSchiSubmitDeviceCommand+0x39
fffff880`031becd0 fffff880`0412be96 : 00000000`00000000 fffffa80`024b8200 00000000`00000080 fffffa80`03ced010 : dxgmms1!VidSchiSubmitQueueCommand+0xb0
fffff880`031bed00 fffff800`02d30166 : 00000000`02e8de6a fffffa80`03d0c8c0 fffffa80`01848890 fffffa80`03d0c8c0 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`031bed40 fffff800`02a6b486 : fffff800`02c05e80 fffffa80`03d0c8c0 fffff800`02c13c40 fffff880`01258534 : nt!PspSystemThreadStartup+0x5a
fffff880`031bed80 00000000`00000000 : fffff880`031bf000 fffff880`031b9000 fffff880`031bd9b0 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+fec
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578
STACK_COMMAND: .cxr 0xfffff880031bdfe0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+fec
BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+fec
Followup: MachineOwner
---------
