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\121610-11278-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a09000 PsLoadedModuleList = 0xfffff800`02c46e50
Debug session time: Thu Dec 16 13:48:37.293 2010 (UTC - 5:00)
System Uptime: 0 days 0:53:02.337
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff880045b4cf7, fffff880042ad6a8, fffff880042acf10}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b )
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: fffff880045b4cf7, The address that the exception occurred at
Arg3: fffff880042ad6a8, Exception Record Address
Arg4: fffff880042acf10, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>
FAULTING_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b
fffff880`045b4cf7 0fba63540d bt dword ptr [rbx+54h],0Dh
EXCEPTION_RECORD: fffff880042ad6a8 -- (.exr 0xfffff880042ad6a8)
ExceptionAddress: fffff880045b4cf7 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x000000000000002b)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff880042acf10 -- (.cxr 0xfffff880042acf10)
rax=fffff8a00301aaf0 rbx=ff01f8a00312a350 rcx=fffffa8006109000
rdx=fffffa80041d3d30 rsi=fffffa8006109000 rdi=fffffa8006109000
rip=fffff880045b4cf7 rsp=fffff880042ad8e0 rbp=fffffa80051b1a78
r8=fffffa80049c6b01 r9=0000000000000000 r10=0000000000000000
r11=0000000000000158 r12=fffffa80041d3d30 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x2b:
fffff880`045b4cf7 0fba63540d bt dword ptr [rbx+54h],0Dh ds:002b:ff01f8a0`0312a3a4=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb10e0
ffffffffffffffff
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b
fffff880`045b4cf7 0fba63540d bt dword ptr [rbx+54h],0Dh
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff880045b1ed3 to fffff880045b4cf7
STACK_TEXT:
fffff880`042ad8e0 fffff880`045b1ed3 : 00000000`00000000 fffffa80`0500a8d0 00000000`0000003e 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x2b
fffff880`042ad910 fffff880`045cc65d : 00000000`00000000 fffff8a0`02281c50 fffffa80`00000000 fffffa80`049c6b20 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`042adae0 fffff880`045cc398 : fffff880`02f67f40 fffff880`045cbd00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`042adcd0 fffff880`045cbe96 : 00000000`00000000 fffffa80`03fb1b00 00000000`00000080 fffffa80`05f68370 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`042add00 fffff800`02d1dc06 : 00000000`017743e3 fffffa80`060caa10 fffffa80`03cce040 fffffa80`060caa10 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`042add40 fffff800`02a57c26 : fffff880`02f63180 fffffa80`060caa10 fffff880`02f6dfc0 fffff880`01226a90 : nt!PspSystemThreadStartup+0x5a
fffff880`042add80 00000000`00000000 : fffff880`042ae000 fffff880`042a8000 fffff880`042ad690 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578
STACK_COMMAND: .cxr 0xfffff880042acf10 ; kb
FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b
BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b
Followup: MachineOwner
---------
.