*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff8800537ffe8, fffff88002591698, fffff88002590ef0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+98 )
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: fffff8800537ffe8, The address that the exception occurred at
Arg3: fffff88002591698, Exception Record Address
Arg4: fffff88002590ef0, 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::ReferenceAllocationForSubmission+98
fffff880`0537ffe8 48035020 add rdx,qword ptr [rax+20h]
EXCEPTION_RECORD: fffff88002591698 -- (.exr 0xfffff88002591698)
ExceptionAddress: fffff8800537ffe8 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x0000000000000098)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88002590ef0 -- (.cxr 0xfffff88002590ef0)
rax=ff02f8a002f58df0 rbx=fffff8a011e96010 rcx=fffffa8004512e70
rdx=0000000000000060 rsi=fffffa80044b0bd0 rdi=fffffa8005926000
rip=fffff8800537ffe8 rsp=fffff880025918d0 rbp=0000000000000000
r8=fffffa80044b0c20 r9=0000000000000001 r10=0000000000000000
r11=fffffa80059273c0 r12=000000000000004b r13=0000000000000000
r14=fffffa8004d1de10 r15=00000000000000d5
iopl=0 nv up ei pl nz ac po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010216
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x98:
fffff880`0537ffe8 48035020 add rdx,qword ptr [rax+20h] ds:002b:ff02f8a0`02f58e10=????????????????
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 fffff800030c6100
ffffffffffffffff
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+98
fffff880`0537ffe8 48035020 add rdx,qword ptr [rax+20h]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff8800537d8af to fffff8800537ffe8
STACK_TEXT:
fffff880`025918d0 fffff880`0537d8af : 00000000`00000000 fffffa80`0659a258 00000000`000000d3 fffffa80`06f5f710 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x98
fffff880`02591910 fffff880`0539765d : 00000000`00000000 fffff8a0`02f58df0 fffffa80`00000000 fffffa80`04d1de10 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
fffff880`02591ae0 fffff880`05397398 : fffff880`009edf40 fffff880`05396d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`02591cd0 fffff880`05396e96 : 00000000`00000000 fffffa80`04d03470 00000000`00000080 fffffa80`057e0010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`02591d00 fffff800`0312efee : 00000000`0b353799 fffffa80`05900b60 fffffa80`039d4040 fffffa80`05900b60 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`02591d40 fffff800`02e855e6 : fffff880`009e9180 fffffa80`05900b60 fffff880`009f3fc0 00000001`00000001 : nt!PspSystemThreadStartup+0x5a
fffff880`02591d80 00000000`00000000 : fffff880`02592000 fffff880`0258c000 fffff880`02591680 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+98
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1
STACK_COMMAND: .cxr 0xfffff88002590ef0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+98
BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+98
Followup: MachineOwner
