Returning BSOD after getting laptop "fixed" ; nvlddmkm.sys 0x00000116

cnmartinez11 · 06 Jul 2013

This issue first came up a couple months ago when I was in school. I can remember exactly where it started too. I opened up an image file a professor sent us of scanned notes, and my laptop crashed. I don't recall if I got the BSOD that time, but after that whenever I tried to do anything that used the nvidia GPU instead of the integrated chip, I'd get this BSOD (I even forced simple programs like Chrome to run with the nvidia GPU and indeed it would crash). I googled around then, did as much as could which mostly amounted to trying stock drivers, newest drivers, and the last stable drivers I had, as well as rebuilding the nvlddmkm.sys file. None of it helped whatsoever.

Luckily I had a squaretrade warranty that wasn't up, but I couldn't afford to lose my computer for 5+ days during school, so I waited til summer to send it in. I got it back and the problem was gone! The invoice said they replaced the VGA. That was a few weeks ago, but on the 4th of July the problem came back again! It's the same deal: anytime I use the nvidia card it'll BSOD. I've done a clean install of the latest drivers which didn't help. Any insight would be appreciated. Thanks!

This is the laptop:
http://us.toshiba.com/computers/lapt...70/X775-Q7272/

Arc · 07 Jul 2013

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

It occurs due to various reasons. Let us discuss.

1. An outdated display driver.

Code:

fffff880`08286000 fffff880`08d67000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Mon May 13 00:39:45 2013 (518FE8F9)
    CheckSum:         00AB6DED
    ImageSize:        00AE1000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Install the NVIDIA DRIVERS 320.49WHQL

2. A failing GPU.
Stress test the Graphics Card (NVIDIA GeForce GTX 560M) using Furmark.
Video Card - Stress Test with Furmark

3. Overheating.
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.

There are some other things like inadequate power supply, dust allocation, etc; which are difficult to test on a laptop.

And some graphics hungry program/game may cause this error, too.

So let us know these three results at first.
______________________________________________________________________
BSOD ANALYSIS:

Code:

...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8005880010, fffff880083c1010, 0, 2}

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+13b010 )

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: fffffa8005880010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880083c1010, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

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


FAULTING_IP: 
nvlddmkm+13b010
fffff880`083c1010 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`02b904f8 fffff880`0714b054 : 00000000`00000116 fffffa80`05880010 fffff880`083c1010 00000000`00000000 : nt!KeBugCheckEx
fffff880`02b90500 fffff880`0714ad5e : fffff880`083c1010 fffffa80`05880010 fffffa80`0920bd50 fffffa80`098f5410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02b90540 fffff880`0700ff13 : fffffa80`05880010 00000000`00000000 fffffa80`0920bd50 fffffa80`098f5410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`02b90570 fffff880`0703ded6 : fffffa80`ffffffff 00000000`00003172 fffff880`02b906c0 00000000`00000006 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`02b90650 fffff880`07023ce9 : fffffa80`099bf000 ffffffff`feced300 00000000`00000006 fffffa80`099bf000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`02b90690 fffff880`07021184 : 00000000`00000001 fffff8a0`0476f670 fffffa80`099bf000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x1e9
fffff880`02b90790 fffff880`0701e927 : 00000000`00000000 fffffa80`05933000 00000000`00000012 fffff8a0`0476f670 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xfc
fffff880`02b907d0 fffff880`070387d9 : 00000000`00000000 fffff8a0`049f8820 fffffa80`00000000 fffffa80`058f1e40 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xd6f
fffff880`02b909a0 fffff880`07038514 : fffff800`00b96080 fffff880`07037f00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`02b90b90 fffff880`07038012 : 00000000`00000000 fffffa80`05917c70 00000000`00000080 fffffa80`098f5410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`02b90bc0 fffff800`03575ede : 00000000`01dfd7bf fffffa80`0920eb50 fffffa80`054eb040 fffffa80`0920eb50 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`02b90c00 fffff800`032c8906 : fffff800`03452e80 fffffa80`0920eb50 fffff800`03460cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02b90c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+13b010
fffff880`083c1010 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+13b010

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  518fe8f9

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

2: kd> lmvm nvlddmkm
start             end                 module name
fffff880`08286000 fffff880`08d67000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Mon May 13 00:39:45 2013 (518FE8F9)
    CheckSum:         00AB6DED
    ImageSize:        00AE1000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

cnmartinez11 · 11 Jul 2013

Thanks for the quick reply! Here are the results:

1) Clean installed, no change
2) Can't stress test the GPU. Any program that actually uses the GPU sends the computer to a BSOD immediately. Even if I launch Chrome with it instead of the integrated card - instant crash. I ran the test with the integrated card and it was fine (albeit very sluggish, of course).
3) Attached screenshot. Where I'm currently at it gets very hot, so I keep my laptop running on a cooler. Back where this problem first happened, it stayed pretty chilly so I never ran a cooler but it was much cooler than what it is now.

Do you know of any hardware/software fault that could cause a hardware malfunction like this? As mentioned, when it was repaired they replaced the GPU. After that it ran fine for awhile but then took another dive. This leads me to believe it's a hardware issue (but not directly the GPU itself) or a deeply rooted software issue. I'm wondering if something like a bad battery could mess up the GPU, and hence the problem would arise again even if the GPU was replaced. Just speculating.

Arc · 11 Jul 2013

cnmartinez11 said:

2) Can't stress test the GPU. Any program that actually uses the GPU sends the computer to a BSOD immediately. Even if I launch Chrome with it instead of the integrated card - instant crash. I ran the test with the integrated card and it was fine (albeit very sluggish, of course).

It is either the GPU, or the PCIe slot used by the GPU if it is th same crash with more than one GPU.