BSOD playing CS:GO After Crash

masta518 · 25 Aug 2013

Hi,
I'm new to this forum and I hope I can get some help from you guys. I'm not computer literate so please bear with me :)

Yesterday my dad unplugged my desktop while it was hibernating and took it out to the garage to blow compressed air into the fans/motherboard/hardrive/DVD drives to get out all the dust. When I started my computer up this morning, the monitor displayed the exact same screen as I left it, but then froze. I hard rebooted with the power button in safe mode, but then it froze again before seeing the Windows logo. I had to hard reboot again, then it did some weird thing where it checked the integrity of the files on my system on a command line in 3 stages, deleted and restoring a whole bunch of files in the process. I didn't notice much once I was returned to the desktop.

When I tried to play CS:GO, I noticed the game was running slower and slower after every minute and eventually just crashed with a weird "brrrrrrrrrrrrrrrrrrrrrrrr" sound while the monitor says that it has no signal. The computer just freezes and I have to reboot through the power button. When I go back to the desktop, I get this:
--------------------------------------------------------------------
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 4105

Additional information about the problem:
BCCode: 116
BCP1: FFFFFA80083D14E0
BCP2: FFFFF880061BD700
BCP3: FFFFFFFFC000009A
BCP4: 0000000000000004
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\082513-17269-01.dmp
C:\Users\Vincent\AppData\Local\Temp\WER-51605-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
--------------------------------------------------------------------

I don't think it's my drivers/graphics card since I just updated all of them about a week ago. I'm really frustrated, so please help me if you can

Arc · 26 Aug 2013

Hello masta518.

A stop 0x116 is a graphics/display related error.

We know that the latest version of the nvidia display driver is buggy in some cases. So I would suggest you to install the 314.22 WHQL only.

Uninstall All nvidia items in Control Panel > Programs and features
- 3D Vision Control Driver
- 3D Vision Driver
- Graphics Driver
- HD Audio Driver
- PhysX
- nvidia Update
(Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
Now follow Drivers - Clean Left over Files after Uninstalling
Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:

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

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.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of the PSU.

Let us know the results.
________________________________________________________
BDOS ANALYSIS:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80083d14e0, fffff880061bd700, ffffffffc000009a, 4}

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+8ed700 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80083d14e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880061bd700, 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+8ed700
fffff880`061bd700 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`026d0a48 fffff880`04cfb054 : 00000000`00000116 fffffa80`083d14e0 fffff880`061bd700 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`026d0a50 fffff880`04cce867 : fffff880`061bd700 fffffa80`09ffd000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`026d0a90 fffff880`04cfae63 : fffffa80`ffffd84d 00000000`00000000 fffffa80`083d14e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`026d0b40 fffff880`04dca03d : fffffa80`0c21a550 00000000`00000080 00000000`00000000 fffffa80`09f363c0 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`026d0bc0 fffff800`03369bae : 00000000`024e15fb fffffa80`09f8b8b0 fffffa80`054ee040 fffffa80`09f8b8b0 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`026d0c00 fffff800`030bc8c6 : fffff800`03246e80 fffffa80`09f8b8b0 fffff800`03254cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`026d0c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+8ed700
fffff880`061bd700 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+8ed700

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  51c41788

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

3: kd> lmvm nvlddmkm
start             end                 module name
fffff880`058d0000 fffff880`063b5000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Fri Jun 21 14:36:16 2013 (51C41788)
    CheckSum:         00AB87FF
    ImageSize:        00AE5000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

masta518 · 26 Aug 2013

Hi Arc,

Thank you for responding. I have done all of the steps so far but then I get an incompatibility error like in my attached file. Can you please help?

masta518 · 26 Aug 2013

Hmm, should I just install the latest drivers instead?

Arc · 27 Aug 2013

If your GPU is a newer model, it may not support older drivers like 314.22.

You have the latest version of display driver installed, 320.49. Its buggy, but as you have no other way, stick with it.

Perform the other tests. Let us know the results.

masta518 · 27 Aug 2013

Hi Arc,

So I reinstalled the new drivers and everything and tried to run the burn-in test; the computer shutdown after 3~ minutes. I then figured that maybe that was a bit too stressing on the system, so opened CS:GO again and the same thing happened: after playing for 5 minutes or so the frame-rate steadily drops and it crashes with that weird sound and I have to manually reboot.

Do you think my graphics card is broken or something happened when we were blowing air into the desktop? Before that, I ran CS:GO just fine.

P.S. I don't know how to calculate my wattage, but I don't think that would be a big issue anyways. I've attached the speccy screenshot instead.

Arc · 28 Aug 2013

If the GPU cannot take the load of Furmark for more than 3 minutes, if is failing, for sure. But probably you are not ready to decide it based on furmark only? Then follow the process below:

Is it under load, or in normal running?

If not under load, Open the GPU. Clean the fan grills manually.....check if anything is broken there or not.

Clean the PCIe port with fresh and dry cotton cloth, clean the edge of the GPU too. Re-seat it. See if it is behaving the same or not.

If you dont see anything physically damaged in the GPU fans, and if it is behaving the same with the GPU on, do two different trial-and-error tests. Use another GPU in your computer and see how it goes. Put your GPU in another computer and see how it goes.