Solved BSOD Playing CS:GO error 0x00000116

[TobyL]

Hi everyone!

I recently completed my build and I am very satisfied with the result, it is my 7th build and everything went well.

However, when playing CS:GO I get huge lag-spikes about every 20-30 min - 1 hour. The computer almost never crashes it merely freezes for a while (10 sec maybe).

One time though, about a week ago it actually crashed giving me the opportunity to reach out to you guys with a BSOD dump:

==================================================
Dump File : 072814-6084-01.dmp
Crash Time : 2014-07-28 22:57:58
Bug Check String :
Bug Check Code : 0x00000116
Parameter 1 : fffffa80`0af2d4e0
Parameter 2 : fffff880`0f9f8d1c
Parameter 3 : ffffffff`c000009a
Parameter 4 : 00000000`00000004
Caused By Driver : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5d140
File Description : DirectX Graphics Kernel
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18228 (win7sp1_gdr.130731-2222)
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\072814-6084-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 804*832
Dump File Time : 2014-07-28 23:00:40
==================================================

I will also, as requested, attach my DM Log and a .txt copy of my dump log.

I have been researching this for about two weeks now and it is starting to get the better of me. Please tell me if you need any additional information from me and how I shall proceed to provide that for you.

Many thanks and best regards,
Toby

ps. system specs again:
Win 7 professional N x64
Asus Z97-A
SSD 250GB Samsung 840 EVO Basic
2TB Western DIgital Caviar Green WD20EZRX 64MB, SATA-600
Intel Core i5 4690K 3,5 GHz, 6MB
Corsair 8GB DDR3 VENGEANCE LP (2x4GB)
MSI GeForce GTX 770 GAMING 2GB (1098MHz)
Silverstone Argon AR01
Fractal Design Newton R3, 600W 80+ Platinum
All installed in a:
Kab Fractal Design Arc Midi R2 ATX
ds.

 

[Arc]

Hi TobyL.

If it is a stray BSOD only (as it is appearing), you may neglect it for the time being. But if the issue continues to occur, then troubleshooting is really needed.

To troubleshoot a stop 0x116 issue, the basic places that you need to observe is ....

• Overclocking. It may cause a stop 0x116.
• Power Supply. Make it sure that PSU is supplying adequate power.
• Temperature. Overheating may cause it. Monitor the temps using Speccy (Free).
• GPU. It may fail to take the stress. A Furmark stress test will tell you about it.
• Display driver. Observe the situation with different versions.

Sometimes some game settings may also cause it. A downgradation of the game preferences may also be helpful.

If the BSODs continue, we will start itemwise troubleshooting, OK?
__________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800af2d4e0, fffff8800f9f8d1c, 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+98bd1c )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800af2d4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f9f8d1c, 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+98bd1c
fffff880`0f9f8d1c 48ff25ddb9edff  jmp     qword ptr [nvlddmkm+0x867700 (fffff880`0f8d4700)]

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.16384 (debuggers(dbg).130821-1623) amd64fre

STACK_TEXT:  
fffff880`0234ea48 fffff880`0fd2e140 : 00000000`00000116 fffffa80`0af2d4e0 fffff880`0f9f8d1c ffffffff`c000009a : nt!KeBugCheckEx
fffff880`0234ea50 fffff880`0fd01867 : fffff880`0f9f8d1c fffffa80`0995a000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0234ea90 fffff880`0fd2df4f : fffffa80`ffffd84d 00000000`00000000 fffffa80`0af2d4e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`0234eb40 fffff880`0f03803d : fffffa80`0a104010 00000000`00000080 00000000`00000000 fffffa80`099492d0 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`0234ebc0 fffff800`02f1573a : 00000000`0127f28e fffffa80`09973760 fffffa80`069f0740 fffffa80`09973760 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`0234ec00 fffff800`02c6a8e6 : fffff800`02df4e80 fffffa80`09973760 fffff800`02e02cc0 fffff880`00fd43bb : nt!PspSystemThreadStartup+0x5a
fffff880`0234ec40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+98bd1c
fffff880`0f9f8d1c 48ff25ddb9edff  jmp     qword ptr [nvlddmkm+0x867700 (fffff880`0f8d4700)]

SYMBOL_NAME:  nvlddmkm+98bd1c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  537a8efc

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
---------

2: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f06d000 fffff880`0fcd1000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Tue May 20 04:38:44 2014 (537A8EFC)
    CheckSum:         00C1EA41
    ImageSize:        00C64000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[TobyL]

Thank you!

Thank you!

Furmark tests are flawless.

I will try the different steps that you suggests and get back asap!

Again thanks for your reply, much appreciated.

BR,
Toby

 

[Arc]

No problem mate.

Keep in touch, let us know about any further issue.

 

[TobyL]

No problem mate.

Keep in touch, let us know about any further issue.

Hi Arc!

Thank you so much I have been testing for a full month now (wanted to be completely sure before I celebrated)

I did flawless furmark, stresstests but failed in CS GO like the post indicated. Then I did as you suggested and rolled back to a previous release of my graphics driver.

For a month now I have had only had 1 crash and could find other issues that lead to that. So zero crashes due to this issue.

Conclusion: the driver was the problem, will wait a while before I update the driver and try again

Cheers to Arc! (marked as solved)

 

[Arc]

Good news.

Let us know for any further issue.