Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\121610-33228-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c1a000 PsLoadedModuleList = 0xfffff800`02e57e50
Debug session time: Thu Dec 16 06:01:54.515 2010 (UTC - 5:00)
System Uptime: 0 days 0:26:08.561
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff8a04cd1e6c0, 0, fffff88004820fe8, 5}
Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+98 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8a04cd1e6c0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88004820fe8, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec20e0
fffff8a04cd1e6c0
FAULTING_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+98
fffff880`04820fe8 48035020 add rdx,qword ptr [rax+20h]
MM_INTERNAL_CODE: 5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff880078b7740 -- (.trap 0xfffff880078b7740)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a04cd1e6a0 rbx=0000000000000000 rcx=fffffa8009719100
rdx=0000000000000090 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004820fe8 rsp=fffff880078b78d0 rbp=0000000000000003
r8=fffffa8009989130 r9=fffff880078b7901 r10=0000000000000000
r11=fffffa800851a010 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x98:
fffff880`04820fe8 48035020 add rdx,qword ptr [rax+20h] ds:fffff8a0`4cd1e6c0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002d098c1 to fffff80002c8a740
STACK_TEXT:
fffff880`078b75d8 fffff800`02d098c1 : 00000000`00000050 fffff8a0`4cd1e6c0 00000000`00000000 fffff880`078b7740 : nt!KeBugCheckEx
fffff880`078b75e0 fffff800`02c8882e : 00000000`00000000 fffff8a0`0fed2b40 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40e8b
fffff880`078b7740 fffff880`04820fe8 : fffff8a0`11f6b850 fffff880`04820d4b 00000000`00000844 00000000`00000003 : nt!KiPageFault+0x16e
fffff880`078b78d0 fffff880`0481e8af : 00000000`00000000 fffffa80`0a3564e8 00000000`0000017a fffffa80`0a357ec0 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x98
fffff880`078b7910 fffff880`0483865d : 00000000`00000000 fffff8a0`0cd1e6a0 fffffa80`00000003 fffffa80`08a86dc0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
fffff880`078b7ae0 fffff880`04838398 : fffff880`009ed040 fffff880`04837d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`078b7cd0 fffff880`04837e96 : 00000000`00000000 fffffa80`087657e0 00000000`00000080 fffffa80`0851a010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`078b7d00 fffff800`02f2ec06 : 00000000`042e2bf8 fffffa80`0862ab60 fffffa80`057ef040 fffffa80`0862ab60 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`078b7d40 fffff800`02c68c26 : fffff880`009e8180 fffffa80`0862ab60 fffff880`009f30c0 00000000`000c2bb3 : nt!PspSystemThreadStartup+0x5a
fffff880`078b7d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+98
fffff880`04820fe8 48035020 add rdx,qword ptr [rax+20h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+98
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578
FAILURE_BUCKET_ID: X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+98
BUCKET_ID: X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+98
Followup: MachineOwner
---------
