Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\DMP\021811-19702-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02c1d000 PsLoadedModuleList = 0xfffff800`02e5ae50
Debug session time: Fri Feb 18 11:01:23.958 2011 (UTC - 5:00)
System Uptime: 0 days 20:08:51.285
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff88004f33c70, fffff8800ab00da0, 0}
Probably caused by : dxgmms1.sys ( dxgmms1!VidMmTerminateAllocation+154 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff88004f33c70, Address of the instruction which caused the bugcheck
Arg3: fffff8800ab00da0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
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!VidMmTerminateAllocation+154
fffff880`04f33c70 498b7d20 mov rdi,qword ptr [r13+20h]
CONTEXT: fffff8800ab00da0 -- (.cxr 0xfffff8800ab00da0)
rax=fffffa80047d1050 rbx=fffffa8005b6c000 rcx=fffffa8003eae3e0
rdx=0000000000000000 rsi=fffffa800408e360 rdi=fffff8a00e76fac8
rip=fffff88004f33c70 rsp=fffff8800ab01770 rbp=fffffa8006d47d50
r8=0000000000000000 r9=0000000000000000 r10=fffff80002e08760
r11=fffff8800ab01740 r12=fffff8a00e76fba0 r13=000000000204001c
r14=0000000000000001 r15=0000000000000001
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
dxgmms1!VidMmTerminateAllocation+0x154:
fffff880`04f33c70 498b7d20 mov rdi,qword ptr [r13+20h] ds:002b:00000000`0204003c=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: Wow.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff88004f33c70
STACK_TEXT:
fffff880`0ab01770 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VidMmTerminateAllocation+0x154
FOLLOWUP_IP:
dxgmms1!VidMmTerminateAllocation+154
fffff880`04f33c70 498b7d20 mov rdi,qword ptr [r13+20h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VidMmTerminateAllocation+154
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d3fa174
STACK_COMMAND: .cxr 0xfffff8800ab00da0 ; kb
FAILURE_BUCKET_ID: X64_0x3B_dxgmms1!VidMmTerminateAllocation+154
BUCKET_ID: X64_0x3B_dxgmms1!VidMmTerminateAllocation+154
Followup: MachineOwner
---------