Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\031412-7113-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: C:\Windows\System32
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03053000 PsLoadedModuleList = 0xfffff800`03298670
Debug session time: Wed Mar 14 14:33:00.808 2012 (GMT+1)
System Uptime: 0 days 2:36:28.978
Loading Kernel Symbols
...............................................................
................................................................
..............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use [COLOR="#0000FF"]!analyze -v[/COLOR] to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff88010160cee, fffff880069b9568, fffff880069b8dc0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22 )
Followup: MachineOwner
---------
0: 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: fffff88010160cee, The address that the exception occurred at
Arg3: fffff880069b9568, Exception Record Address
Arg4: fffff880069b8dc0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
FAULTING_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22
fffff880`10160cee 488b18 mov rbx,qword ptr [rax]
EXCEPTION_RECORD: fffff880069b9568 -- [COLOR="#0000FF"](.exr 0xfffff880069b9568)[/COLOR]
ExceptionAddress: fffff88010160cee (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x0000000000000022)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff880069b8dc0 -- [COLOR="#0000FF"](.cxr 0xfffff880069b8dc0)[/COLOR]
rax=fffdf8a010c2f6b0 rbx=0000000000000000 rcx=fffffa800c3a2000
rdx=fffffa800e2e0e00 rsi=fffffa800e198118 rdi=fffffa800c3a2000
rip=fffff88010160cee rsp=fffff880069b97a0 rbp=fffffa800e1b6350
r8=fffffa800779a801 r9=0000000000000000 r10=0000000000000000
r11=0000000000000001 r12=0000000000000132 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
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::ReferenceAllocationForPreparation+0x22:
fffff880`10160cee 488b18 mov rbx,qword ptr [rax] ds:002b:fffdf8a0`10c2f6b0=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003302100
ffffffffffffffff
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22
fffff880`10160cee 488b18 mov rbx,qword ptr [rax]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff8801015ded3 to fffff88010160cee
STACK_TEXT:
fffff880`069b97a0 fffff880`1015ded3 : 00000000`00000000 fffffa80`0e198118 00000000`00000132 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x22
fffff880`069b97d0 fffff880`1017865d : 00000000`00000000 fffff8a0`112241d0 fffffa80`00000000 fffffa80`0779a810 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`069b99a0 fffff880`10178398 : fffff800`00b96080 fffff880`10177d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`069b9b90 fffff880`10177e96 : 00000000`00000000 fffffa80`0e102010 00000000`00000080 fffffa80`0c386010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`069b9bc0 fffff800`0336afee : 00000000`01789a49 fffffa80`0c3878c0 fffffa80`06cf79e0 fffffa80`0c3878c0 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`069b9c00 fffff800`030c15e6 : fffff800`03245e80 fffffa80`0c3878c0 fffff800`03253cc0 fffff880`01621cb0 : nt!PspSystemThreadStartup+0x5a
fffff880`069b9c40 00000000`00000000 : fffff880`069ba000 fffff880`069b4000 fffff880`069b9540 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: [COLOR="#0000FF"]dxgmms1[/COLOR]
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1
STACK_COMMAND: .cxr 0xfffff880069b8dc0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22
BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22
Followup: MachineOwner
---------
0: kd> .cxr 0xfffff880069b8dc0
rax=fffdf8a010c2f6b0 rbx=0000000000000000 rcx=fffffa800c3a2000
rdx=fffffa800e2e0e00 rsi=fffffa800e198118 rdi=fffffa800c3a2000
rip=fffff88010160cee rsp=fffff880069b97a0 rbp=fffffa800e1b6350
r8=fffffa800779a801 r9=0000000000000000 r10=0000000000000000
r11=0000000000000001 r12=0000000000000132 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
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::ReferenceAllocationForPreparation+0x22:
fffff880`10160cee 488b18 mov rbx,qword ptr [rax] ds:002b:fffdf8a0`10c2f6b0=????????????????
