BugCheck 1000007E, {ffffffffc0000005, fffff80003d17184, fffff880035bd848, fffff880035bd0b0}
GetUlongPtrFromAddress: unable to read from fffff80003cb0300
Probably caused by : ntkrnlmp.exe ( nt!CmpDereferenceNameControlBlockWithLock+b8 )
Followup: MachineOwner
---------
nt!CmpDereferenceNameControlBlockWithLock+0xb8:
fffff800`03d17184 488b02 mov rax,qword ptr [rdx] ds:002b:00000000`b970d86c=????????????????
GetUlongPtrFromAddress: unable to read from fffff80003cf7300
Probably caused by : hardware ( fltmgr!DeleteStreamListCtrlCallback+9 )
Followup: MachineOwner
---------
nt!KeBugCheckEx:
fffff800`03aec9a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff880`071fce00=000000000000001e
BugCheck 10E, {1f, fffff8a008d20010, 1, 8bebe}
GetUlongPtrFromAddress: unable to read from fffff80003cff300
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+12b )
Followup: MachineOwner
---------
nt!KeBugCheckEx:
fffff800`03af49a0 48894c2408 mov qword ptr [rsp+8],rcx ss:fffff880`05dba630=000000000000010e
BugCheck 50, {fffff9a01ecb7b38, 0, fffff88004d6a2b5, 5}
Could not read faulting driver name
GetUlongPtrFromAddress: unable to read from fffff80003cb8300
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+1e5 )
Followup: MachineOwner
---------
nt!KeBugCheckEx:
fffff800`03aad9a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff880`02b38e10=0000000000000050
BugCheck 4E, {2, 156895, 1bf7ff, 8}
GetUlongPtrFromAddress: unable to read from fffff80003ced300
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+8d )
Followup: MachineOwner
---------
nt!KeBugCheckEx:
fffff800`03ae29a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff880`0372b980=000000000000004e