Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\032811-14601-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c63000 PsLoadedModuleList = 0xfffff800`02ea0e50
Debug session time: Mon Mar 28 10:10:01.737 2011 (UTC - 4:00)
System Uptime: 0 days 0:17:25.610
Loading Kernel Symbols
...............................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff88010bb7d90, fffff88002e3e6a8, fffff88002e3df00}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4 )
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: fffff88010bb7d90, The address that the exception occurred at
Arg3: fffff88002e3e6a8, Exception Record Address
Arg4: fffff88002e3df00, 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+c4
fffff880`10bb7d90 8b4810 mov ecx,dword ptr [rax+10h]
EXCEPTION_RECORD: fffff88002e3e6a8 -- (.exr 0xfffff88002e3e6a8)
ExceptionAddress: fffff88010bb7d90 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x00000000000000c4)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88002e3df00 -- (.cxr 0xfffff88002e3df00)
rax=108d56b7108d5697 rbx=fffff8a006552e50 rcx=fffffa8007c4b000
rdx=fffffa8004222220 rsi=fffffa8007c4b000 rdi=fffffa8007c4b000
rip=fffff88010bb7d90 rsp=fffff88002e3e8e0 rbp=fffffa8004470c38
r8=fffffa800445ee01 r9=0000000000000000 r10=0000000000000000
r11=0000000000000086 r12=fffffa8004222220 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010202
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0xc4:
fffff880`10bb7d90 8b4810 mov ecx,dword ptr [rax+10h] ds:002b:108d56b7`108d56a7=????????
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 fffff80002f0b0e0
ffffffffffffffff
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
fffff880`10bb7d90 8b4810 mov ecx,dword ptr [rax+10h]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff88010bb4ed3 to fffff88010bb7d90
STACK_TEXT:
fffff880`02e3e8e0 fffff880`10bb4ed3 : 00000000`00000000 fffffa80`0446e410 00000000`00000004 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0xc4
fffff880`02e3e910 fffff880`10bcf65d : 00000000`00000000 fffff8a0`06390390 fffffa80`00000000 fffffa80`0445ee70 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`02e3eae0 fffff880`10bcf398 : fffff880`02fd7f40 fffff880`10bced00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`02e3ecd0 fffff880`10bcee96 : 00000000`00000000 fffffa80`040e4180 00000000`00000080 fffffa80`07bc00f0 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`02e3ed00 fffff800`02f78166 : 00000000`01af8d92 fffffa80`07c25b60 fffffa80`03c6a990 fffffa80`07c25b60 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`02e3ed40 fffff800`02cb3486 : fffff880`02fd3180 fffffa80`07c25b60 fffff880`02fddfc0 fffff880`01227534 : nt!PspSystemThreadStartup+0x5a
fffff880`02e3ed80 00000000`00000000 : fffff880`02e3f000 fffff880`02e39000 fffff880`02e3e690 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578
STACK_COMMAND: .cxr 0xfffff88002e3df00 ; kb
FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
Followup: MachineOwner
---------
