Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\BSODDmpFiles\BeKure\Windows_NT6_BSOD_jcgriff2\020712-10623-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 (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a5d000 PsLoadedModuleList = 0xfffff800`02ca2670
Debug session time: Tue Feb 7 14:35:02.257 2012 (GMT-7)
System Uptime: 0 days 0:49:27.989
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff880053d4d78, fffff880021c4688, fffff880021c3ee0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4c )
Followup: MachineOwner
---------
5: 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: fffff880053d4d78, The address that the exception occurred at
Arg3: fffff880021c4688, Exception Record Address
Arg4: fffff880021c3ee0, 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::IsPagingOperationPending+4c
fffff880`053d4d78 4939040a cmp qword ptr [r10+rcx],rax
EXCEPTION_RECORD: fffff880021c4688 -- (.exr 0xfffff880021c4688)
ExceptionAddress: fffff880053d4d78 (dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+0x000000000000004c)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff880021c3ee0 -- (.cxr 0xfffff880021c3ee0)
rax=000000000000ed31 rbx=fffff8a00c2896e0 rcx=bffff8a0015d8a38
rdx=0000000000000001 rsi=0000000000000001 rdi=0000000000000003
rip=fffff880053d4d78 rsp=fffff880021c48c8 rbp=0000000000000000
r8=0000000000000001 r9=0000000000000003 r10=0000000000000008
r11=fffffa80081473b0 r12=0000000000000114 r13=0000000000000000
r14=fffffa8009866720 r15=000000000000056b
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+0x4c:
fffff880`053d4d78 4939040a cmp qword ptr [r10+rcx],rax ds:002b:bffff8a0`015d8a40=????????????????
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 fffff80002d0c100
ffffffffffffffff
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4c
fffff880`053d4d78 4939040a cmp qword ptr [r10+rcx],rax
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff880053d202a to fffff880053d4d78
STACK_TEXT:
fffff880`021c48c8 fffff880`053d202a : fffff8a0`0c2896e0 fffffa80`09ac9960 fffffa80`08146000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+0x4c
fffff880`021c48d0 fffff880`053cf8af : 00000000`00000000 fffffa80`098148a0 00000000`00000145 fffffa80`097ff9e8 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xda
fffff880`021c4910 fffff880`053e965d : 00000000`00000000 fffff8a0`0adfa280 fffffa80`00000000 fffffa80`09866720 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
fffff880`021c4ae0 fffff880`053e9398 : fffff880`0308cfc0 fffff880`053e8d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`021c4cd0 fffff880`053e8e96 : 00000000`00000000 fffffa80`081dc8d0 00000000`00000080 fffffa80`08133410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`021c4d00 fffff800`02d74fee : 00000000`01e79a61 fffffa80`08137b60 fffffa80`069a6890 fffffa80`08137b60 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`021c4d40 fffff800`02acb5e6 : fffff880`03088180 fffffa80`08137b60 fffff880`03093040 fffff880`0122b384 : nt!PspSystemThreadStartup+0x5a
fffff880`021c4d80 00000000`00000000 : fffff880`021c5000 fffff880`021bf000 fffff880`021c4680 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1
STACK_COMMAND: .cxr 0xfffff880021c3ee0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4c
BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4c
Followup: MachineOwner
---------
