Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\082710-25630-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols ;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e1c000 PsLoadedModuleList = 0xfffff800`03059e50
Debug session time: Thu Aug 26 21:30:49.222 2010 (GMT-4)
System Uptime: 0 days 5:44:53.298
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff8800fe20ff3, fffff8800599c698, fffff8800599bf00}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3 )
Followup: MachineOwner
---------
4: 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: fffff8800fe20ff3, The address that the exception occurred at
Arg3: fffff8800599c698, Exception Record Address
Arg4: fffff8800599bf00, 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+a3
fffff880`0fe20ff3 48894108 mov qword ptr [rcx+8],rax
EXCEPTION_RECORD: fffff8800599c698 -- (.exr 0xfffff8800599c698)
ExceptionAddress: fffff8800fe20ff3 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x00000000000000a3)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff8800599bf00 -- (.cxr 0xfffff8800599bf00)
rax=fffffa8008c6e9e0 rbx=fffff8a001c0d610 rcx=7ffffa8008c25370
rdx=fffff8a001b1a700 rsi=fffffa8008c18680 rdi=fffffa8008563000
rip=fffff8800fe20ff3 rsp=fffff8800599c8d0 rbp=0000000000000000
r8=fffffa8008c186d0 r9=fffff8800599c901 r10=0000000000000000
r11=fffffa800843f1e0 r12=0000000000000008 r13=0000000000000000
r14=fffffa8008bf7860 r15=000000000000001b
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xa3:
fffff880`0fe20ff3 48894108 mov qword ptr [rcx+8],rax ds:002b:7ffffa80`08c25378=????????????????
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 fffff800030c40e0
ffffffffffffffff
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3
fffff880`0fe20ff3 48894108 mov qword ptr [rcx+8],rax
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff8800fe1e8af to fffff8800fe20ff3
STACK_TEXT:
fffff880`0599c8d0 fffff880`0fe1e8af : 00000000`00000000 fffffa80`08b8f040 00000000`0000001b fffffa80`08c0d0c8 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xa3
fffff880`0599c910 fffff880`0fe3865d : fffffa80`00000000 fffff8a0`01b32ac0 fffffa80`00000000 fffffa80`08bf7860 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
fffff880`0599cae0 fffff880`0fe38398 : fffff800`00b96080 fffff880`0fe37d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`0599ccd0 fffff880`0fe37e96 : 00000000`00000000 fffffa80`085a9d50 00000000`00000080 fffffa80`0843f1e0 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`0599cd00 fffff800`03130c06 : 00000000`033792a2 fffffa80`08446770 fffffa80`055719e0 fffffa80`08446770 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`0599cd40 fffff800`02e6ac26 : fffff800`03006e80 fffffa80`08446770 fffff800`03014c40 fffff880`01254534 : nt!PspSystemThreadStartup+0x5a
fffff880`0599cd80 00000000`00000000 : fffff880`0599d000 fffff880`05997000 fffff880`0599c690 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578
STACK_COMMAND: .cxr 0xfffff8800599bf00 ; kb
FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3
BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3
Followup: MachineOwner
---------
