This is a little messy
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffa8002effad0, 0, fffff880107a8e1d, 2}
Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19 )
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: fffffa8002effad0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff880107a8e1d, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003b03100
fffffa8002effad0
FAULTING_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19
fffff880`107a8e1d 488b02 mov rax,qword ptr [rdx]
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff880079df610 -- (.trap 0xfffff880079df610)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880079df7c8 rbx=0000000000000000 rcx=fffffa80115d4000
rdx=fffffa8002effad0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880107a8e1d rsp=fffff880079df7a0 rbp=fffffa8012ede290
r8=fffffa8014650900 r9=0000000000000000 r10=0000000000000000
r11=0000000000000039 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x19:
fffff880`107a8e1d 488b02 mov rax,qword ptr [rdx] ds:92fc:fffffa80`02effad0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800039485e4 to fffff800038cbbc0
STACK_TEXT:
fffff880`079df4a8 fffff800`039485e4 : 00000000`00000050 fffffa80`02effad0 00000000`00000000 fffff880`079df610 : nt!KeBugCheckEx
fffff880`079df4b0 fffff800`038c9cee : 00000000`00000000 fffffa80`02effad0 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x43836
fffff880`079df610 fffff880`107a8e1d : 00000000`ffffd94a 00000000`00000003 fffffa80`115c1000 fffffa80`115c2a90 : nt!KiPageFault+0x16e
fffff880`079df7a0 fffff880`107a5ff7 : 00000000`00000000 fffffa80`0cec80d8 00000000`0000001e 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x19
fffff880`079df7d0 fffff880`107c07d9 : 00000000`00000000 fffff8a0`0e276910 fffffa80`00000000 fffffa80`14650990 : dxgmms1!VIDMM_GLOBAL:
repareDmaBuffer+0x43f
fffff880`079df9a0 fffff880`107c0514 : fffff800`00b96080 fffff880`107bff00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`079dfb90 fffff880`107c0012 : 00000000`00000000 fffffa80`147b19b0 00000000`00000080 fffffa80`115b2410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`079dfbc0 fffff800`03b6773a : 00000000`01d47098 fffffa80`0d647b50 fffffa80`0c9e4890 fffffa80`0d647b50 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`079dfc00 fffff800`038bc8e6 : fffff800`03a46e80 fffffa80`0d647b50 fffff800`03a54cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`079dfc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19
fffff880`107a8e1d 488b02 mov rax,qword ptr [rdx]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5164dc13
FAILURE_BUCKET_ID: X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19
BUCKET_ID: X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19
Followup: MachineOwner
---------
0: kd> lmvm dxgmms1
start end module name
fffff880`10788000 fffff880`107ce000 dxgmms1 (pdb symbols) C:\Program Files\Debugging Tools for Windows (x64)\sym\dxgmms1.pdb\93AB163000A844D5BF442A979FB6FF991\dxgmms1.pdb
Loaded symbol image file: dxgmms1.sys
Mapped memory image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\dxgmms1.sys\5164DC1346000\dxgmms1.sys
Image path: \SystemRoot\System32\drivers\dxgmms1.sys
Image name: dxgmms1.sys
Timestamp: Tue Apr 09 23:27:15 2013 (5164DC13)
CheckSum: 00043C9B
ImageSize: 00046000
File version: 6.1.7601.18126
Product version: 6.1.7601.18126
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: dxgmms1.sys
OriginalFilename: dxgmms1.sys
ProductVersion: 6.1.7601.18126
FileVersion: 6.1.7601.18126 (win7sp1_gdr.130409-1534)
FileDescription: DirectX Graphics MMS
LegalCopyright: © Microsoft Corporation. All rights reserved.