Windows 10 Crashes

I just started up over the weekend and was pretty content playing until I randomly started crashing.

The screen just went black and eventually the windows restart noise occurs... Unfortunately the system boots without any video. Unfortunately due to the nature of the crash, it doesn't appear to write much of anything in the event log.

On one of the few occasions something was written a bugcheck was written and from that I was able to load up the crash dump.

Basically it looks up the directx 12 driver is having issues managing the video ram. I'm not sure if this is a windows thing, an nvidia thing, or a FFXIV thing.

Due to the fact that everything else seems stable, GTAV, LoL, PoE, etc... i'm leaning towards a FFXIV issue.

I've attached the crash dump to see if anyone else has any ideas...

Code:

---


VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 000000000000002e, The subtype of the bugcheck:
Arg2: ffffc00177c892d0
Arg3: ffffc0017f9f6010
Arg4: ffffd0007c13c730

Debugging Details:
------------------


BUGCHECK_STR:  0x10e_2e

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

LAST_CONTROL_TRANSFER:  from fffff801df073c3d to fffff803173d6220

STACK_TEXT: 
ffffd000`7c13c6c8 fffff801`df073c3d : 00000000`0000010e 00000000`0000002e ffffc001`77c892d0 ffffc001`7f9f6010 : nt!KeBugCheckEx
ffffd000`7c13c6d0 fffff801`e1e61e61 : ffffc001`794cbda0 ffffc001`77c892d0 ffffc001`77c892d0 ffffe001`00000003 : watchdog!WdLogEvent5_WdCriticalError+0xcd
ffffd000`7c13c710 fffff801`e1ec0167 : ffffc001`77c892d0 ffffe001`fba24e40 ffffc001`8c760ba8 ffffc001`7f9f6010 : dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+0x121
ffffd000`7c13c760 fffff801`e1e9e885 : 00008086`000004b0 00000000`00000002 ffffd000`7c13c959 00000000`000000a1 : dxgmms2!VIDMM_SEGMENT::InvalidateAllVirtualAddress+0x19b
ffffd000`7c13c840 fffff801`df1bc486 : ffffe001`fb9bd3b0 00000000`00000000 ffffe169`a461b300 fffff801`e1eca9db : dxgmms2!VIDMM_GLOBAL::InvalidateAllVirtualAddresses+0x31
ffffd000`7c13c870 fffff801`df1d2255 : ffffe002`02de04c0 00000000`000000a1 ffffe002`02de04c0 00000000`00000000 : dxgkrnl!DXGADAPTER::PrepareToReset+0x76
ffffd000`7c13c8c0 fffff801`e1e6e3b1 : ffffe002`02de04c0 ffffd000`7c13c959 00000000`0002a121 00000000`00000008 : dxgkrnl!TdrIsRecoveryRequired+0x1c5
ffffd000`7c13c8f0 fffff801`e1e9b0cc : ffffe001`fba0b000 ffffd000`7c13cb00 ffffe001`fba0b000 ffffe001`fb9d6000 : dxgmms2!VidSchiReportHwHang+0x3fd
ffffd000`7c13c9c0 fffff801`e1e55c3c : ffffe001`fb9d6000 00000000`0000c002 00000000`00000001 00000000`00000002 : dxgmms2!VidSchiCheckHwProgress+0x137bc
ffffd000`7c13ca00 fffff801`e1e93403 : ffffe001`fb9d6000 ffffd000`7c13cbc8 ffffe002`02612c40 ffffe002`00000000 : dxgmms2!VidSchiScheduleCommandToRun+0x33c
ffffd000`7c13cb90 fffff801`e1e933e0 : ffffe001`fb9d6000 00000004`00000000 ffffe001`f62fe380 ffffe001`f62fe300 : dxgmms2!VidSchiRun_PriorityTable+0x1f
ffffd000`7c13cbc0 fffff803`1736e698 : ffffe001`f62fe380 ffffd000`7c13cc90 ffffd000`7a79c180 fffff803`173db230 : dxgmms2!VidSchiWorkerThread+0x80
ffffd000`7c13cc00 fffff803`173db306 : ffffd000`7a79c180 ffffe001`fb9d7780 ffffd000`7a7a8bc0 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd000`7c13cc60 00000000`00000000 : ffffd000`7c13d000 ffffd000`7c137000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP:
dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+121
fffff801`e1e61e61 488bcb          mov    rcx,rbx

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+121

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  55b99ee0

IMAGE_VERSION:  10.0.10240.16412

BUCKET_ID_FUNC_OFFSET:  121

FAILURE_BUCKET_ID:  0x10e_2e_dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange

BUCKET_ID:  0x10e_2e_dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x10e_2e_dxgmms2!vidmm_cpu_host_aperture::unmaprange

FAILURE_ID_HASH:  {ebf2c813-41e1-4d73-9be7-00c514787ed3}

---

The dump indicates that the graphics driver had a memory-related error. First thing to do is make sure you have the latest graphics driver for your card, for Windows 10. I'm not too familiar with Win10 error logs yet but the WIN8_DRIVER_FAULT line suggests that you're using a Windows 8 driver, which works but isn't ideal.

Ignore that line... That only exists because the debugging tools are for Windows 8.1 still. Graphics drivers are up to date with the latest and greatest, 355.60.