Hello Jeremy and welcome to Seven Forums.
From the dump file you provided it appears there are three
drivers causing issues: igdkmd64.sys, dxgkrnl.sys, and dxgmms1.sys
The first is an Intel Graphics
driver and can be found/updated at the Intel Download Center.
Intel Download Center
The "dxg" drivers are the DirectX Graphics Kernel and the DirectX Graphics MMS. Both of these are typically updated through Windows Updates.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8004380010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004c36cb0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.
Debugging Details:
------------------
FAULTING_IP:
igdkmd64+23cb0
fffff880`04c36cb0 4889542410 mov qword ptr [rsp+10h],rdx
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`05438988 fffff880`04718000 : 00000000`00000116 fffffa80`04380010 fffff880`04c36cb0 00000000`00000000 : nt!KeBugCheckEx
fffff880`05438990 fffff880`04717d0a : fffff880`04c36cb0 fffffa80`04380010 fffffa80`060294f0 fffffa80`062f5010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`054389d0 fffff880`047bef07 : fffffa80`04380010 00000000`00000000 fffffa80`060294f0 fffffa80`062f5010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`05438a00 fffff880`047e8b75 : 00000000`ffffffff 00000000`0002631d 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`05438ae0 fffff880`047e72bb : 00000000`00000102 00000000`00000000 00000000`0002631d 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`05438b10 fffff880`047ba2c6 : ffffffff`ff676980 fffffa80`062f5010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`05438bb0 fffff880`047e6e7a : 00000000`00000000 fffffa80`0730a940 00000000`00000080 fffffa80`062f5010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`05438cc0 fffff800`03132e5a : 00000000`fffffc32 fffffa80`06008060 fffffa80`036cc740 fffffa80`06008060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`05438d00 fffff800`02e8cd26 : fffff880`009e9180 fffffa80`06008060 fffff880`009f3f40 fffffa80`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`05438d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
igdkmd64+23cb0
fffff880`04c36cb0 4889542410 mov qword ptr [rsp+10h],rdx
SYMBOL_NAME: igdkmd64+23cb0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: igdkmd64
IMAGE_NAME: igdkmd64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a01d55b
FAILURE_BUCKET_ID: X64_0x116_IMAGE_igdkmd64.sys
BUCKET_ID: X64_0x116_IMAGE_igdkmd64.sys
Followup: MachineOwner
Run a full scan with your resident anti-virus suite. Since no anti-malware product will be 100% effective 100% of the time, follow up with a couple more free on-demand scanners such as:
Malwarebytes ESET Online Scanner
I would next run a system file checker scan from an elevated command prompt (option two.) If any problems are found, run the scan 3 times and reboot th computer after each scan.
SFC /SCANNOW Command - System File Checker
Please post back the results of the anti-malware scans, results of the SFC scan, and your success at updating the drivers.