BSOD playing League of Legends (Error 0x116, nvlddmkm.sys)

stepberg · 31 Jan 2013

Hi guys,

please see my zip file from the SF Diagnostic Tool for details but basically I get the BSOD occuring (randomly?) while playing League of Legends and I cannot for the life of it figure out what exactly the problem is or even better, how to fix it.

Google sent me here and I really hope that anyone can help me a bit with this issue. :) Every tiny bit of help is deeply appreciated.

If I need to post different or additional information, please let me know (I presume everything important is covered in the SF diag tool). Thank you!

Arc · 31 Jan 2013

Hello stepberg.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80065743f0, fffff88006160adc, 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+929adc )

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: fffffa80065743f0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88006160adc, 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+929adc
fffff880`06160adc 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`02ad1a48 fffff880`06332000 : 00000000`00000116 fffffa80`065743f0 fffff880`06160adc ffffffff`c000009a : nt!KeBugCheckEx
fffff880`02ad1a50 fffff880`06305867 : fffff880`06160adc fffffa80`0a155000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02ad1a90 fffff880`06331e0f : 00000000`ffffd84d fffffa80`0a094010 fffffa80`065743f0 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`02ad1b40 fffff880`04b90ec1 : fffffa80`0b669d50 00000000`00000080 00000000`00000000 fffffa80`0a094010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`02ad1bc0 fffff800`03522e5a : 00000000`0279612e fffffa80`0a16f610 fffffa80`05aeb740 fffffa80`0a16f610 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`02ad1c00 fffff800`0327cd26 : fffff800`033fee80 fffffa80`0a16f610 fffff800`0340ccc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02ad1c40 00000000`00000000 : fffff880`02ad2000 fffff880`02acc000 fffff880`02ad14d0 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+929adc
fffff880`06160adc 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+929adc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50de9218

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

7: kd> lmvm nvlddmkm
start             end                 module name
fffff880`05837000 fffff880`062d5000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sat Dec 29 12:17:52 2012 (50DE9218)
    CheckSum:         00A7F96C
    ImageSize:        00A9E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

A stop 0x116 is a display related error, and the version of display driver is known to be a buggy one. So first roll it back to a known stable version.

Download and install Driver Fusion.
Reboot the computer in Advanced Boot Options, safe mode. Search Driver Fusion in your start menu, and remove all components of your nVidia display driver.
Boot normally now. Go to Drivers - Download NVIDIA Drivers, Drivers > Beta and Legacy; search there with your cards particulars for GeForce 306.23 Driver, dated 13.9.2012 and install it.

If the issue continues, follow the guide: STOP 0x116: VIDEO_TDR_ERROR troubleshooting

Let us know the results.

stepberg · 31 Jan 2013

Dear Arc,

I removed and re-installed the drivers as per your instruction. I will update my progress accordingly. =)

stepberg · 01 Feb 2013

Update: My system still crashed, so the re-installation of the drivers did not solve this issue. I have attached a new SF diag tool zip-archive to this post, but according to whocrashed, it is still the same error. May installing a very old driver help?

I am now reading through the thread "STOP 0x116: VIDEO_TDR_ERROR troubleshooting" and am trying out some stuff mentioned in there.

- I have elevated my laptop to improve cooling
- I have run Furmark stress test but did not encounter any issues
- I have run sfc.exe - no problems found

So far, this issue only occurs while playing League of Legends, every other game works fine (including Diablo 3, Starcraft 2, Path of Exile...). Does anybody have any ideas on what the cause of this error could be or more importantly, how to fix it?

Arc · 02 Feb 2013

Same situation.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800a7544e0, fffff8800fd5f004, 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+ad6004 )

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

How old the GPU is?

If you are sure that the crashes are occurring for a particular game only, get into that games settings, change the preferences (texture etc) to medium or low. It may help a bit. Also, try to measure the memory usage during that very game.

stepberg · 02 Feb 2013

The GPU is a Nvidia GeForce GT 540M and as I bought the laptop in 2010, I'd presume this is how old it is. This is the laptop: EasyNote TS11HR-122GE | Product Model (it is in German though).

Arc · 02 Feb 2013

Sometimes an older GPU causes problems with newer graphics rich games.

Go for the alteration in the game's settings; it might make the situation a bit better.

stepberg · 24 Feb 2013

Currently I have been issue free for some time now but I am not sure if this will last or if the error sooner or later will come back. I have achieved this by installing the very old Nvidia driver provided by the notebook manufacturer (ver. 285.90) specifically for my model. This basically means that I can never update my gpu drivers unless I want to risk crashes again.

Thank you very much for your help Arc!!! I will mark this tentatively as solved under the assumption that my crash will not come back again (which I am uncertain of).

Arc · 24 Feb 2013

Not a perfectly good news, mate.

Still, if it is not crashing with the old driver, use it. If there is any further issue, let us know.