BSOD/'No-display' crashes when any nVidia driver is installed

Sethmetal Kukri · 01 Aug 2014

Hello, I need help with understanding the exact problem with my desktop that I thought I had fixed. My 0x117 crashes never recovered, leading to the 'no-display' situation where I had to do a hard shutdown, sometimes 0x116 occurred instead but I see no 'blue screens' before rebooting.

When I thought I have solved a major problem in booting to windows with a nVidia driver installed by installing a new pair of Gskill 2x 8GB module ram, after a month or so I crashed while watching youtube videos (and loading a game), and thereafter my crashes begin a few minutes after logging into Windows, while playing a game or even checking my email on Firefox.

Crashes will only happen when a nVidia driver is installed, I had brought my 560 GTX to the servicing center to check for any issues quite some time ago but there isn't any problems with it. I even reinstalled OS suspecting my hard shutdowns had corrupted my OS somehow, but the crashes still occurred in a few minutes after logging into Windows.

Arc · 01 Aug 2014

Hi Sethmetal Kukri.

Click on the 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

Sethmetal Kukri · 01 Aug 2014

Done.

Arc · 02 Aug 2014

The thread title says ....

crashes when any nVidia driver is installed

So we may assume that you have tried different versions of the display driver already and nothing changed. The stop 0x116 (or 0x117) BSOD continues to occur. Is it the fact? let us know.

Are you overclocking?

Code:

MaxSpeed:     2800
CurrentSpeed: 2808

As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

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 .

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.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark
If you cannot perform the stress test in your computer, you may try to attach the GPU in any other computer and run the stress test there.

Let us know the results.
____________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8010fea4e0, fffff8800fc21f14, 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+98df14 )

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: fffffa8010fea4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fc21f14, 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+98df14
fffff880`0fc21f14 803dce15efff00  cmp     byte ptr [nvlddmkm+0x87f4e9 (fffff880`0fb134e9)],0

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`025f5b88 fffff880`04ab0140 : 00000000`00000116 fffffa80`10fea4e0 fffff880`0fc21f14 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`025f5b90 fffff880`04a83867 : fffff880`0fc21f14 fffffa80`105df000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`025f5bd0 fffff880`04aaff4f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`10fea4e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`025f5c80 fffff880`04b7f03d : fffffa80`10b29160 00000000`00000080 00000000`00000000 fffffa80`105c8410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`025f5d00 fffff800`0317273a : 00000000`08117fba fffffa80`105da060 fffffa80`0c775040 fffffa80`105da060 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`025f5d40 fffff800`02ec78e6 : fffff800`03051e80 fffffa80`105da060 fffff800`0305fcc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`025f5d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+98df14
fffff880`0fc21f14 803dce15efff00  cmp     byte ptr [nvlddmkm+0x87f4e9 (fffff880`0fb134e9)],0

SYMBOL_NAME:  nvlddmkm+98df14

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  525da526

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

3: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f294000 fffff880`0fec1000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Wed Oct 16 01:57:18 2013 (525DA526)
    CheckSum:         00C04839
    ImageSize:        00C2D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Sethmetal Kukri · 02 Aug 2014

1. I have tried the latest, and the driver nVidia specifically made for 460 & 560 series drivers to deal with the TDR issues while surfing the web. My assumption that all drivers could not work was before I changed my RAM to the Gskill 2x 8GB modules where any driver could prevent me from logging in to windows at all. When the special driver nVidia made for 560 series failed, I assumed the rest wouldn't work.

2. My MSI Twin Frozr II GTX 560 is factory overclocked, I have no idea how to underclock it permanently nor do I know what else is overclocked.

3. I had recently re-applied the thermal compound and I had monitored it for a while, sits at around 80C max while gaming.

4. I am away from home at the moment, so I'm unable to access my desktop to do the tests. My wattage of the PSU is 750W by the way, some of the specs I have are listed in 'My System Specs'.

Arc · 02 Aug 2014

OK, we may wait for the results of the tests and then continue.

Sethmetal Kukri · 02 Aug 2014

Just gonna reattach the LiveKernelReports dump files in zip again since the first one was in rar.

Sethmetal Kukri · 04 Aug 2014

Arc said:

OK, we may wait for the results of the tests and then continue.

Hmm, I have a problem here.

I can't run the Furmark test without a driver, I installed a 2 year old nVidia driver and I cannot even get to the windows login screen without hanging indefinitely for no reason. (could get past 'Starting Windows', but hanged and all I saw was my mouse cursor)

This time it provided no dmp files on the hanging, like it did when it was issues before I changed my RAM sticks.

I have provided the dmp files from Windows\LiveKernelReports in the above post just in case you missed it.

Edit: Also today I have tried installing the same driver again after doing a little tweak to the TdrDelay, crashed while going into Control Panel to change some nVidia settings. Attached in this posts are the dmp files from LiveKernelReports and Minidump.

Arc · 04 Aug 2014

It is the same stop 0x116 BSOD, with the same driver installed as detected in post #4.

If it had been a different driver version, that would have been an information. Can you install the latest one, 340.52 WHQL? Drivers | GeForce

From whatever you stated, it indicates to a GPU failure, but it is better to take a stress test before deciding about it. If you cannot take a stress test, can you apply any other GPU there as a test basis, just to see how the computer reacts with another GPU?

And please follow post #2 to report a BSOD. It gives us a better visibility to the situation.
_______________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800cbb04e0, fffff8800fc57f14, 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+98df14 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800cbb04e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fc57f14, 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+98df14
fffff880`0fc57f14 803dce15efff00  cmp     byte ptr [nvlddmkm+0x87f4e9 (fffff880`0fb494e9)],0

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`053fdb88 fffff880`0ff54140 : 00000000`00000116 fffffa80`0cbb04e0 fffff880`0fc57f14 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`053fdb90 fffff880`0ff27867 : fffff880`0fc57f14 fffffa80`1038c000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`053fdbd0 fffff880`0ff53f4f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`0cbb04e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`053fdc80 fffff880`0f23803d : fffffa80`0df22330 00000000`00000080 00000000`00000000 fffffa80`102f1410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`053fdd00 fffff800`0312e73a : 00000000`fffffc32 fffffa80`10398a00 fffffa80`0c775040 fffffa80`10398a00 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`053fdd40 fffff800`02e838e6 : fffff800`0300de80 fffffa80`10398a00 fffff800`0301bcc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`053fdd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+98df14
fffff880`0fc57f14 803dce15efff00  cmp     byte ptr [nvlddmkm+0x87f4e9 (fffff880`0fb494e9)],0

SYMBOL_NAME:  nvlddmkm+98df14

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  525da526

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

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f2ca000 fffff880`0fef7000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Wed Oct 16 01:57:18 2013 (525DA526)
    CheckSum:         00C04839
    ImageSize:        00C2D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Sethmetal Kukri · 05 Aug 2014

Well, as I'd have guessed, the 340 driver didn't work either. I could get to the point of being able to change some settings in nVidia control panel and starting the Furmark test which didn't last beyond 3 seconds before the no-display crash kicked in. (After restarting, it didn't allow me to see my desktop either)

I have no other GPU to test with unfortunately, but I do not think the issue is with my GPU.

I ran the dm log thingy again, I don't think it copied any of the dmp files from LiveKernelReports so I attached those along.