Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\101211-13494-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 7601 (Service Pack 1) MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c13000 PsLoadedModuleList = 0xfffff800`02e58670
Debug session time: Wed Oct 12 13:56:26.618 2011 (UTC - 7:00)
System Uptime: 0 days 2:45:27.054
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff880053afcf7, fffff880021bd6a8, fffff880021bcf00}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b )
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: fffff880053afcf7, The address that the exception occurred at
Arg3: fffff880021bd6a8, Exception Record Address
Arg4: fffff880021bcf00, 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_GLOBAL::ReferenceAllocationForPreparation+2b
fffff880`053afcf7 0fba63540d bt dword ptr [rbx+54h],0Dh
EXCEPTION_RECORD: fffff880021bd6a8 -- (.exr 0xfffff880021bd6a8)
ExceptionAddress: fffff880053afcf7 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x000000000000002b)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000780001b8
Attempt to read from address 00000000780001b8
CONTEXT: fffff880021bcf00 -- (.cxr 0xfffff880021bcf00)
rax=fffff8a00dadca30 rbx=0000000078000164 rcx=fffffa8005a37000
rdx=fffffa8005a88290 rsi=fffffa8005a37000 rdi=fffffa8005a37000
rip=fffff880053afcf7 rsp=fffff880021bd8e0 rbp=fffffa80046f26b0
r8=fffffa8006463601 r9=0000000000000000 r10=0000000000000000
r11=0000000000000048 r12=fffffa8005a88290 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`053afcf7 0fba63540d bt dword ptr [rbx+54h],0Dh ds:002b:00000000`780001b8=????????
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: 00000000780001b8
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec2100
00000000780001b8
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b
fffff880`053afcf7 0fba63540d bt dword ptr [rbx+54h],0Dh
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff880053aced3 to fffff880053afcf7
STACK_TEXT:
fffff880`021bd8e0 fffff880`053aced3 : 00000000`00000000 fffffa80`0662f238 00000000`00000001 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x2b
fffff880`021bd910 fffff880`053c765d : 00000000`00000000 fffff8a0`0b1d7780 fffffa80`00000000 fffffa80`06463640 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`021bdae0 fffff880`053c7398 : fffff880`02f67f00 fffff880`053c6d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`021bdcd0 fffff880`053c6e96 : 00000000`00000000 fffffa80`03ca9010 00000000`00000080 fffffa80`058ba410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`021bdd00 fffff800`02f2afee : 00000000`01fa247f fffffa80`05597b60 fffffa80`03670b30 fffffa80`05597b60 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`021bdd40 fffff800`02c815e6 : fffff880`02f63180 fffffa80`05597b60 fffff880`02f6df80 fffff880`0124ecb0 : nt!PspSystemThreadStartup+0x5a
fffff880`021bdd80 00000000`00000000 : fffff880`021be000 fffff880`021b8000 fffff880`021bd680 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: 4ce799c1
STACK_COMMAND: .cxr 0xfffff880021bcf00 ; kb
FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b
BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b
Followup: MachineOwner
---------