bsod when starting up games

ruan1998

Honorable
Jun 10, 2016
2
0
10,510
hi guys this is my first post here and i really found some solid advice from this site hope you guys can help
everytime i start up a game wether it be ark survival evolved spore or metro last light i keep getting a bsod
here is my dump analasis
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`0340d000 PsLoadedModuleList = 0xfffff800`036506d0
Debug session time: Fri Jun 10 01:52:31.237 2016 (UTC - 4:00)
System Uptime: 0 days 0:05:31.127
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8005d6e010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f7c2c2c, 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:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

FAULTING_IP:
nvlddmkm+162c2c
fffff880`0f7c2c2c 48ff2565666100 jmp qword ptr [nvlddmkm+0x779298 (fffff880`0fdd9298)]

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0x116

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`05c064f8 fffff880`102fe000 : 00000000`00000116 fffffa80`05d6e010 fffff880`0f7c2c2c 00000000`00000000 : nt!KeBugCheckEx
fffff880`05c06500 fffff880`102fdd0a : fffff880`0f7c2c2c fffffa80`05d6e010 fffffa80`08d31160 fffffa80`08d0e3c0 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`05c06540 fffff880`103a4f13 : fffffa80`05d6e010 00000000`00000000 fffffa80`08d31160 fffffa80`08d0e3c0 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`05c06570 fffff880`103d2ed6 : fffffa80`ffffffff 00000000`0000516c fffff880`05c066c0 00000000`00000006 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`05c06650 fffff880`103b8ce9 : fffffa80`08d34000 ffffffff`ff676980 00000000`00000006 fffffa80`08d34000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`05c06690 fffff880`103b6184 : 00000000`00000001 fffff8a0`0d8cc5d0 fffffa80`08d34000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x1e9
fffff880`05c06790 fffff880`103b3927 : 00000000`00000000 fffffa80`05ca0000 00000000`0000000f fffff8a0`0d8cc5d0 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xfc
fffff880`05c067d0 fffff880`103cd7d9 : 00000000`00000000 fffff8a0`044ae0e0 fffffa80`00000000 fffffa80`05c7e290 : dxgmms1!VIDMM_GLOBAL:😛repareDmaBuffer+0xd6f
fffff880`05c069a0 fffff880`103cd514 : fffff800`00b96080 fffff880`103ccf00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`05c06b90 fffff880`103cd012 : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`08118c58 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`05c06bc0 fffff800`0371f2ea : 00000000`02f12114 fffffa80`08d33760 fffffa80`054d9040 fffffa80`08d33760 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`05c06c00 fffff800`034738e6 : fffff800`035fde80 fffffa80`08d33760 fffff800`0360bcc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`05c06c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+162c2c
fffff880`0f7c2c2c 48ff2565666100 jmp qword ptr [nvlddmkm+0x779298 (fffff880`0fdd9298)]

SYMBOL_NAME: nvlddmkm+162c2c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 573115e3

FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

Followup: MachineOwner
 
Solution
video stopped responding. Happens with overclocked GPU and with sound driver conflicts between the GPU sound support for HDMI and the motherboard sound drivers. Also tends to happen a lot on nvidia cards that have shadowplay active. Shadowplay depend on the network card driver. outdated network card drivers bog down the GPU until it can not respond within its required 2 second timeout window and this bugcheck can be generated.

You also see this bugcheck on software overclocked GPU, or if the PCI/e bus timings are not correct (should be 100MHz not overclocked in bios)
video stopped responding. Happens with overclocked GPU and with sound driver conflicts between the GPU sound support for HDMI and the motherboard sound drivers. Also tends to happen a lot on nvidia cards that have shadowplay active. Shadowplay depend on the network card driver. outdated network card drivers bog down the GPU until it can not respond within its required 2 second timeout window and this bugcheck can be generated.

You also see this bugcheck on software overclocked GPU, or if the PCI/e bus timings are not correct (should be 100MHz not overclocked in bios)
 
Solution

TRENDING THREADS