Mark_1970 :
I would suggest you post up the Dump file from C:\Windows\Minidump\041616-49389-01.dmp for us to inspect
So I ran WinDbg(x64) on that dump file and analyzed it. This is what I got:
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800cb414e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88005be0978, 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:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 7601.19160.amd64fre.win7sp1_gdr.160211-0600
SYSTEM_MANUFACTURER: System manufacturer
SYSTEM_PRODUCT_NAME: System Product Name
SYSTEM_SKU: To be filled by O.E.M.
SYSTEM_VERSION: System Version
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: 2001
BIOS_DATE: 09/20/2011
BASEBOARD_MANUFACTURER: ASUSTeK Computer INC.
BASEBOARD_PRODUCT: SABERTOOTH P67
BASEBOARD_VERSION: Rev 1.xx
DUMP_TYPE: 2
BUGCHECK_P1: fffffa800cb414e0
BUGCHECK_P2: fffff88005be0978
BUGCHECK_P3: 0
BUGCHECK_P4: 2
FAULTING_IP:
nvlddmkm+13e978
fffff880`05be0978 48ff25c1e85300 jmp qword ptr [nvlddmkm+0x67d240 (fffff880`0611f240)]
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CPU_COUNT: 8
CPU_MHZ: d53
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 2a
CPU_STEPPING: 7
CPU_MICROCODE: 6,2a,7,0 (F,M,S,R) SIG: 1A'00000000 (cache) 1A'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: DREW-PC
ANALYSIS_SESSION_TIME: 04-16-2016 12:26:41.0123
ANALYSIS_VERSION: 10.0.10586.567 amd64fre
STACK_TEXT:
fffff880`096c2888 fffff880`06511134 : 00000000`00000116 fffffa80`0cb414e0 fffff880`05be0978 00000000`00000000 : nt!KeBugCheckEx
fffff880`096c2890 fffff880`06510e3e : fffff880`05be0978 fffffa80`0cb414e0 fffffa80`0c8cb810 fffffa80`0c8a3010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`096c28d0 fffff880`065b8f13 : fffffa80`0cb414e0 00000000`00000000 fffffa80`0c8cb810 fffffa80`0c8a3010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`096c2900 fffff880`065e2cf1 : 00000000`ffffffff 00000000`00000dce 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`096c29e0 fffff880`065e1437 : 00000000`00000102 00000000`00000006 00000000`00000dce 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`096c2a10 fffff880`065b42d2 : ffffffff`ff676980 fffffa80`0c8a3010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`096c2ab0 fffff880`065e0ff6 : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`0c439168 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`096c2bc0 fffff800`0396ac6a : 00000000`0ad1e856 fffffa80`0c8cc760 fffffa80`069f79c0 fffffa80`0c8cc760 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`096c2c00 fffff800`036c1086 : fffff800`0384fe80 fffffa80`0c8cc760 fffff800`0385dcc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`096c2c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 9331cc480a76056907c83df5b44cbb124b171c6b
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: f1f802c820bc41a812114d7cbbe2a09449e9d75f
THREAD_SHA1_HASH_MOD: 8a8b82c1b789d2b57d111dee06f2d5d20bb3d242
FOLLOWUP_IP:
nvlddmkm+13e978
fffff880`05be0978 48ff25c1e85300 jmp qword ptr [nvlddmkm+0x67d240 (fffff880`0611f240)]
FAULT_INSTR_CODE: c125ff48
SYMBOL_NAME: nvlddmkm+13e978
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 54d3b001
FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
PRIMARY_PROBLEM_CLASS: X64_0x116_IMAGE_nvlddmkm.sys
TARGET_TIME: 2016-04-16T01:13:55.000Z
OSBUILD: 7601
OSSERVICEPACK: 1000
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
OSEDITION: Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2016-02-11 11:40:22
BUILDDATESTAMP_STR: 160211-0600
BUILDLAB_STR: win7sp1_gdr
BUILDOSVER_STR: 6.1.7601.19160.amd64fre.win7sp1_gdr.160211-0600
ANALYSIS_SESSION_ELAPSED_TIME: a6d
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x116_image_nvlddmkm.sys
FAILURE_ID_HASH: {1f9e0448-3238-5868-3678-c8e526bb1edc}
Followup: MachineOwner
---------
I assume it has something to do with the nvlddmkm.sys file, but I'm not really sure what to do. Any suggestions from here?
Thanks!!