BSOD While playing Dota 2

Flamewall2 · 12 May 2015

They appear to be random. In an attempt to fix it I factory reset my computer and installed dota 2, steam, skype as well as all windows and driver updates. Here is what happens I play Dota comp freezes audio that was playing for about the past .5 seconds loops and then comp auto restarts. As far as I know it only happens about every 30 mins or so on dota.

Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\User\Desktop\051215-17082-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18798.amd64fre.win7sp1_gdr.150316-1654
Machine Name:
Kernel base = 0xfffff800`0340d000 PsLoadedModuleList = 0xfffff800`03652890
Debug session time: Tue May 12 00:37:11.802 2015 (UTC - 7:00)
System Uptime: 0 days 2:08:05.614
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800f9a04e0, fffff8800603ca08, ffffffffc000009a, 4}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+7aca08 )

Followup: MachineOwner
---------

7: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800f9a04e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800603ca08, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

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

FAULTING_IP:
nvlddmkm+7aca08
fffff880`0603ca08 48ff258126edff jmp qword ptr [nvlddmkm+0x67f090 (fffff880`05f0f090)]

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0x116

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_TEXT:
fffff880`07beea48 fffff880`0635b134 : 00000000`00000116 fffffa80`0f9a04e0 fffff880`0603ca08 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`07beea50 fffff880`0632e867 : fffff880`0603ca08 fffffa80`0c0c0000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`07beea90 fffff880`0635af43 : fffffa80`ffffd846 ffffffff`fffe7960 fffffa80`0f9a04e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`07beeb40 fffff880`0583803d : fffffa80`0e264320 00000000`00000080 00000000`00000000 fffffa80`0bf05010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`07beebc0 fffff800`03719aba : 00000000`039e1ef2 fffffa80`0a92b8b0 fffffa80`069a8b30 fffffa80`0a92b8b0 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`07beec00 fffff800`03471426 : fffff800`035ffe80 fffffa80`0a92b8b0 fffff800`0360dcc0 00000000`ffffffff : nt!PspSystemThreadStartup+0x5a
fffff880`07beec40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+7aca08
fffff880`0603ca08 48ff258126edff jmp qword ptr [nvlddmkm+0x67f090 (fffff880`05f0f090)]

SYMBOL_NAME: nvlddmkm+7aca08

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 55259065

FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x116_image_nvlddmkm.sys

FAILURE_ID_HASH: {1f9e0448-3238-5868-3678-c8e526bb1edc}

Followup: MachineOwner
---------

SGT Oddball · 12 May 2015

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa800f9a04e0, fffff8800603ca08, ffffffffc000009a, 4}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+7aca08 )
Followup: MachineOwner
---------

As you know the dump blames nvlddmkm.sys which is your NVidia graphics driver, see if you can find a newer driver or roll back to a previous version.

Flamewall2 · 12 May 2015

K I'll try rolling back graphics driver its currently up to date

Flamewall2 · 13 May 2015

Could this be caused by my graphics card overheating? Because I was just playing dota of making graphics card use an older driver and I didnt get a BSOD but my screen did temporarely die on me

Flamewall2 · 13 May 2015

????