Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\031810-31515-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*F:\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.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a5d000 PsLoadedModuleList = 0xfffff800`02c9ae50
Debug session time: Thu Mar 18 06:54:34.514 2010 (GMT-4)
System Uptime: 0 days 0:08:16.452
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff88004ba8ce5, fffff880043416a8, fffff88004340f00}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19 )
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: fffff88004ba8ce5, The address that the exception occurred at
Arg3: fffff880043416a8, Exception Record Address
Arg4: fffff88004340f00, 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+19
fffff880`04ba8ce5 488b02 mov rax,qword ptr [rdx]
EXCEPTION_RECORD: fffff880043416a8 -- (.exr 0xfffff880043416a8)
ExceptionAddress: fffff88004ba8ce5 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x0000000000000019)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88004340f00 -- (.cxr 0xfffff88004340f00)
rax=fffff88004341908 rbx=0000000000000000 rcx=fffffa800f2b0000
rdx=58fffa800fd68690 rsi=fffffa800acd0880 rdi=fffffa800f2b0000
rip=fffff88004ba8ce5 rsp=fffff880043418e0 rbp=fffffa800af7e988
r8=fffffa800ae3c401 r9=0000000000000000 r10=0000000000000000
r11=0000000000000137 r12=0000000000000027 r13=0000000000000000
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+0x19:
fffff880`04ba8ce5 488b02 mov rax,qword ptr [rdx] ds:002b:58fffa80`0fd68690=????????????????
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 fffff80002d050e0
ffffffffffffffff
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19
fffff880`04ba8ce5 488b02 mov rax,qword ptr [rdx]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff88004ba5ed3 to fffff88004ba8ce5
STACK_TEXT:
fffff880`043418e0 fffff880`04ba5ed3 : 00000000`00000000 fffffa80`0acd0880 00000000`00000027 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x19
fffff880`04341910 fffff880`04bc065d : 00000000`00000000 fffff8a0`06a07ad0 fffffa80`00000000 fffffa80`0ae3c4a0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`04341ae0 fffff880`04bc0398 : fffff800`00b96080 fffff880`04bbfd00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`04341cd0 fffff880`04bbfe96 : 00000000`00000000 fffffa80`108dfd50 00000000`00000080 fffffa80`0f2a7010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`04341d00 fffff800`02d72166 : 00000000`037f2181 fffffa80`0f294770 fffffa80`0a949040 fffffa80`0f294770 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`04341d40 fffff800`02aad486 : fffff800`02c47e80 fffffa80`0f294770 fffff800`02c55c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`04341d80 00000000`00000000 : fffff880`04342000 fffff880`0433c000 fffff880`04341690 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578
STACK_COMMAND: .cxr 0xfffff88004340f00 ; kb
FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19
BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19
Followup: MachineOwner
---------
