BSOD playing Dota 2

[Dennisingemarss]

Hello!
This is my first time doing this so sorry if any information is missing. When i play Dota 2 the computer often shuts down, restart but nothing is happening, it´s not really a BSOD but the information after says it is. This problem only occurs while playing Dota 2. I have searched for information on millions of forums but cant find any solution to this problem. I have done the regular things:

- Defraggler
- CCleaner
- Reinstall dota
- Uppdate my graphic drivers
- Play on minimal settings in game.
- Clean inside computer for dust.
- I have also reset the computer.
- Also tried a bunch of diffrent stuff that other persons said would work. Steamrelated.

In addition a electronic company tried to solve the problem but they couldnt find anything. I think they did a "stresstest" and so on.

I dont think its the hardware since I can play Battlefield 3 without any issues. I were about to post the error message but it dissapered after doing these BSOD steps to upload file. Would appreciate help!

 

[Arc]

Hi Dennisingemarss.

A stop 0x116 is a display related BSOD, and I am seeing that the display driver in use is nvidia 314.22 WHQL, which cannot fail at its own.

You have done a lot already, but still try these:

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Do it two times. During normal usage and during playing DOTA2 for a reasonable time.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

If any component of the laptop is overclocked, revert it back to default settings.

And, if the statement is true ......

This problem only occurs while playing Dota 2.

..... then the problem is with the game only. You need to contract th game developer in their forum, and ask for custom settings or patches for your system.

Finally, it is a branded desktop, 3 years old. What is the wattage of the PSU? Let us know.
Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
_________________________________________________________________________________________________

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8006afb010, fffff880061ae668, ffffffffc000000d, 3}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** 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+933668 )

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

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

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

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


FAULTING_IP: 
nvlddmkm+933668
fffff880`061ae668 4055            push    rbp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`0949aa18 fffff880`04686140 : 00000000`00000116 fffffa80`06afb010 fffff880`061ae668 ffffffff`c000000d : nt!KeBugCheckEx
fffff880`0949aa20 fffff880`04659569 : fffff880`061ae668 fffffa80`069a8000 00000000`00000000 fffffa80`0699e010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0949aa60 fffff880`04685eed : fffffa80`06afb010 fffffa80`06afb010 fffffa80`06afb010 fffffa80`0699e010 : dxgkrnl!DXGADAPTER::PrepareToReset+0x109
fffff880`0949aaa0 fffff880`0472cf13 : fffffa80`06afb010 00000000`00000000 fffffa80`07cadd50 fffffa80`0699e010 : dxgkrnl!TdrIsRecoveryRequired+0x245
fffff880`0949aad0 fffff880`0475aed6 : fffffa80`ffffffff 00000000`000b04cb fffff880`0949ac30 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`0949abb0 fffff880`047282aa : fffffa80`0699e010 ffffffff`feced300 fffffa80`07cadd50 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`0949abf0 fffff880`04754ff6 : 00000000`00000000 fffffa80`07cadd50 00000000`00000080 fffffa80`0699e010 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2
fffff880`0949ad00 fffff800`035132ea : 00000000`0291d2d8 fffffa80`069a2b50 fffffa80`03b66040 fffffa80`069a2b50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`0949ad40 fffff800`032678e6 : fffff800`033f1e80 fffffa80`069a2b50 fffff800`033ffcc0 000e6b76`ffffffd8 : nt!PspSystemThreadStartup+0x5a
fffff880`0949ad80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+933668
fffff880`061ae668 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+933668

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  51427b3c

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0587b000 fffff880`06326000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Fri Mar 15 07:07:00 2013 (51427B3C)
    CheckSum:         00A8D47C
    ImageSize:        00AAB000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[Dennisingemarss]

Hello and thanks for answering!

I decided to reboot the whole system, just to run the tests when the computer was clean. In addition, perhaps the BSOD occurs in other games as well, I cant just recall any specific game.

However I tried to do everything you asked for. Firstly a checked the temperature of normal usage of the computer which I have uploaded. I couldnt upload the temprature after playing Dota 2 for a while ince when I checked the graphics was over 100 degrees and a short moment after that the computer crashed. So well, that is perhaps the problem I guess?

I was unable to fullfill the stress test since it started to alert me when the maximum tempreature level was reached (around 100 degrees).

Lastly I really dont know what PSU I have. I googled a lot and searched for the computer manual and so on. Im sorry, and I dont know exactly the prestanda so I cant fill the data in "eXtreme Power Supply Calculator".

So, what do you suggest that I do now?

 

[Arc]

Well, dismantle the computer. Clean all the fan grills and air vents (dont remove the heat sneak, otherwise it will increase the workload and expenditure) so that the computer can blow the hot air out efficiently. Clean the GPU fans, too; but without breaking anything.

Then afford some additional cooler. Or leave one side of the case open and point a fan through it.

BTW, how old the GPU is? And, is it within warranty?

If you cannot control the heat, it may harm other components too. 100 degrees is not a matter of joke :shock:

So, if the GPU is old, replace it .... as the last option.

 

[Dennisingemarss]

Alright, I will try that!

That is the funny part. Its almost exactly three years old and I had an extra warranty on it.. So I went to the company and explained the problem just days before the warranty expired. As I said in the first post, they didnt find anything weird (which I think is bullshit) so I got it back and now there is no warranty = I turned to forums.

Nono, I know. Its crazy, I never actually checked the temperature before, I just felt on fans and didnt notice anything. Its just weird that it started so suddenly since it worked without any problems for so many years. Anyway, I will try to clean it and report the results!