BSOD on nvidia 555m optimus

Hi I have a laptop with gt 555m (optimus). Suddently my laptop crash with blue screen when i tried to play league of legend or pes 2015. i check with who crash and the result is :

crash dump file: C:\Windows\Minidump\123014-45302-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x13EBFC)
Bugcheck code: 0x116 (0xFFFFFA8006195010, 0xFFFFF88008420BFC, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 347.09
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 347.09
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 347.09 , NVIDIA Corporation).
Google query: NVIDIA Corporation VIDEO_TDR_ERROR


After some time any program that i put to execute with the nvidia card give the crash. Everything is fine in the integrated graphic card, so I taught nvidia died but when i try to update the intel card it give the same crash which is weird. Thank you for your help

Hi.

Click on button below ....

It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip.
Screenshots and Files - Upload and Post in Seven Forums

We need to see the info before we suggest you about how to deal with the issue.

The zip you uploaded does not contain any crash dump.

Follow it: Dump Files - Configure Windows to Create on BSOD
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Dont run any disc cleanup tool before you upload another zip.

Still there is no crash dump; and without checking a crash dump nothing can be said precisely about a BSOD.

If you are sure that you have done it already ....

Follow it: Dump Files - Configure Windows to Create on BSOD
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

and still the dumps are not being recorded, take a camera snap of the next BSOD screen and let us see it? Perhaps the onboard codes will give some hints about whats going on there.

A stop 0x116 is a display/graphics related issue. The failing driver is the nvidia display driver.

Update it to the latest. Drivers - Download NVIDIA Drivers

When done, Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark

Take a screenshot of the furmark window before closing it. Upload the screenshot for us.

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. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

Let us know the results.
___________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80065f94e0, fffff8800f57a4ac, 0, 2}

*** 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+1584ac )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80065f94e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f57a4ac, 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+1584ac
fffff880`0f57a4ac 48ff251d4f6900  jmp     qword ptr [nvlddmkm+0x7ed3d0 (fffff880`0fc0f3d0)]

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.17237 (debuggers(dbg).140716-0327) amd64fre

STACK_TEXT:  
fffff880`02ecb4f8 fffff880`1015f134 : 00000000`00000116 fffffa80`065f94e0 fffff880`0f57a4ac 00000000`00000000 : nt!KeBugCheckEx
fffff880`02ecb500 fffff880`1015ee3e : fffff880`0f57a4ac fffffa80`065f94e0 fffffa80`0a6abc00 fffffa80`05561010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02ecb540 fffff880`07667f13 : fffffa80`065f94e0 00000000`00000000 fffffa80`0a6abc00 fffffa80`05561010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`02ecb570 fffff880`07695ed6 : fffffa80`ffffffff 00000000`00003a0a fffff880`02ecb6c0 00000000`00000006 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`02ecb650 fffff880`0767bce9 : fffffa80`0a6ee000 ffffffff`feced300 00000000`00000006 fffffa80`0a6ee000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`02ecb690 fffff880`07679184 : 00000000`00000001 fffff8a0`0dcc78d0 fffffa80`0a6ee000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x1e9
fffff880`02ecb790 fffff880`07676927 : 00000000`00000000 fffffa80`055a7000 00000000`0000000e fffff8a0`0dcc78d0 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xfc
fffff880`02ecb7d0 fffff880`076907d9 : 00000000`00000000 fffff8a0`0dc8d800 fffffa80`00000000 fffffa80`0b09cbd0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xd6f
fffff880`02ecb9a0 fffff880`07690514 : fffff800`00b94080 fffff880`0768ff00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`02ecbb90 fffff880`07690012 : 00000000`00000000 fffffa80`09891d50 00000000`00000080 fffffa80`05561010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`02ecbbc0 fffff800`03363b8a : 00000000`04bfdfa0 fffffa80`0a6ac200 fffffa80`054ec040 fffffa80`0a6ac200 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`02ecbc00 fffff800`030b68e6 : fffff800`03241e80 fffffa80`0a6ac200 fffff800`0324fcc0 00000000`00000001 : nt!PspSystemThreadStartup+0x5a
fffff880`02ecbc40 00000000`00000000 : fffff880`02ecc000 fffff880`02ec6000 fffff880`0d4ffd40 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+1584ac
fffff880`0f57a4ac 48ff251d4f6900  jmp     qword ptr [nvlddmkm+0x7ed3d0 (fffff880`0fc0f3d0)]

SYMBOL_NAME:  nvlddmkm+1584ac

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5463c853

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

4: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f422000 fffff880`10102000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu Nov 13 02:21:31 2014 (5463C853)
    CheckSum:         00CA4D59
    ImageSize:        00CE0000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

darkcode said:

hi I update to the latest drivers then when i started the furmark program i got the bsod...

Apparentlythe system is not overheating. In this situation when the computer crashes with a stop 0x116 during furmark, it is a fair indication that the graphics card is failing to take loads.

Better you replace the graphics card. If the computer is within warranty, ask teh vendor for a replacement.