Thanks, I would check for any additional Windows Updates, I have around 200+ Windows Updates installed and the average at the moment, I think is around 180+ Windows Updates.
Code:
BugCheck A, {fffffab005ecea60, 2, 1, fffff800030b7c0e}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::Free+a2 )
Code:
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
Code:
fffff880058a6960 -- (.trap 0xfffff880058a6960)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880058a6a60 rbx=0000000000000000 rcx=fffff880058a6a60
rdx=0000000000133b77 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030b7c0e rsp=fffff880058a6af0 rbp=fffffa8000025650
r8=fffffa800c15c410 r9=0000000000000000 r10=0000000000000000
r11=fffff880058a6ac0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!MiDeletePteRun+0x504:
fffff800`030b7c0e f0410fba6e1000 lock bts dword ptr [r14+10h],0 ds:00000000`00000010=????????
Code:
0: kd> !thread
GetPointerFromAddress: unable to read from fffff800032bd000
THREAD fffffa800bac9990 Cid 13fc.0724 Teb: 00000000fffdb000 Win32Thread: fffff900c2134c20 RUNNING on processor 0
IRP List:
Unable to read nt!_IRP @ fffffa800ba5e2e0
Not impersonating
GetUlongFromAddress: unable to read from fffff800031fcba4
Owning Process fffffa800c15c410 Image: Rome2.exe
Attached Process N/A Image: N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount 303981
Context Switch Count 2108863 IdealProcessor: 0 LargeStack
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime 00:00:00.000
KernelTime 00:00:00.000
Win32 Start Address 0x00000000013514ed
Stack Init fffff880058a7c70 Current fffff880058a77c0
Base fffff880058a8000 Limit fffff8800589f000 Call 0
Priority 11 BasePriority 8 UnusualBoost 0 ForegroundBoost 2 IoPriority 2 PagePriority 5
Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours: