Solved BSOD Most likely GPU-related

[Lavos]

Getting BSODs where the screen goes black, fans go crazy and computer restarts. I can only speculate on why it's happening but either it's completely random or it's got something to do with me using Google Chrome. I've tried rolling my GPU drivers back to last stable build but that did not fix the problem. Also tried re-installing OS, but no luck.

The problem is fairly recent. Only been happening for the last 3-4 weeks.

Please see attached archive.

 

[Arc]

There is a nice chance that the GPU is failing, as you are thinking. But before saying it, try another version of the display driver.

Neither of the drivers 340.52 WHQL and 337.88 WHQL are very stable. Try any other WHQL of the following ....

Drivers | GeForce

View attachment 332373
​

When done, Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark
​

Let us know the results.
___________________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800f22f4e0, fffff8800fa52d1c, 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
---------

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

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

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`085e9a48 fffff880`044ea134 : 00000000`00000116 fffffa80`0f22f4e0 fffff880`0fa52d1c ffffffff`c000009a : nt!KeBugCheckEx
fffff880`085e9a50 fffff880`044bd867 : fffff880`0fa52d1c fffffa80`0de5c000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`085e9a90 fffff880`044e9f43 : fffff800`ffffd846 ffffffff`fffe7960 fffffa80`0f22f4e0 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`085e9b40 fffff880`045ba03d : fffffa80`0e3e7d50 00000000`00000080 00000000`00000000 fffffa80`0dd89410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`085e9bc0 fffff800`02d1773a : 00000000`033c0c5a fffffa80`0dd32b50 fffffa80`0c749040 fffffa80`0dd32b50 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`085e9c00 fffff800`02a6c8e6 : fffff800`02bf6e80 fffffa80`0dd32b50 fffff800`02c04cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`085e9c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

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

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

7: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f0c7000 fffff880`0fd2b000   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

 

[Lavos]

Downgraded to 334.89 and ran the stress-test.
No artefacting and the temp leveled out at like 75 degrees didn't BSOD or anything.

 

[Arc]

Now give it some more time and see how it goes. Let us know for any further BSOD.

 

[Lavos]

BSOD'd again after about a day.

Am I right in assuming there is a hardware problem?

I made another info zip but I assume it's the same info as last time.

 

[Arc]

It is still the stop 0x116 continuing, despite of changing the display driver version. So there is a possibility of hardware failure. But as the furmark stress test ran without any issue, it is difficult to blame the hardware right now.

I will ask for hardware help for you.

 

[essenbe]

Lavos, are you overclocking either the card or CPU? if you are, set everything back to defaults and see if the problem continues. I am not opposed to overclocking as you will notice below my signature. But it can sometimes lead to instability. It won't hurt to try and see, if you are in fact overclocking. I would also make sure my firmware was up to date on my SSD.

 

[ICIT2LOL]

I might throw in my two cents worth with testing out that PSU too see my ditty

Using HW Info PSU

Download HW Info and pick the right bit version - HWiNFO, HWiNFO32/64 -Download -(copy and paste thissite into the search bar) If you do not need the running information in thesmaller right hand panel close it. In the left hand window click on the + forthe individual device groupings and they will open out to the variouscomponents.

Go on opening out further until you get to the device itself. click on it andit will highlight. In the right hand window there will be a very detaileddescription of that device as in brand, speeds model number etc etc These arevery detailed and are just what is needed for searching for drivers etc.

To get the PSU volts you need to select the Sensor buttoncircled in yellow in the pic for PSU testing do the same and scroll down thereadout as in my pic to where it has Nuvoton = yours might be a differentsection name / title. Post back a pic of that please.

If you want a more definitive test see this http://www.sevenforums.com/tutorials/301799-psu-test-dc-output-voltage.html but lease only use a digital multimeter and not ananalogue as they inject typically 9v into a circuit to test and into a 3.3v or5v rail - not a good idea!! see the partial pic of the correct sort of meter inthat tutorial. details if you scroll down that listing.

 

[Lavos]

No overclocking and the firmware is updated to the newest version.

Here's the screenshot.

 

[essenbe]

Lavos, We're just trying, as best we can, to make sure it is the card. I would hate for you to RMA the card and have the same problems with the new one. The definitive test for me, is if you have a friend with a similar card who would swap cards with you for a day or so, just to see. If he has the same problems as you, but you have none, then it is pretty certain it is the card. If he has no problems but you do, it is either your PSU or Motherboard. Hopefully, you could swap with a card with a similar power draw to your card. That would be the ideal test. You would have a pretty darn good idea when finished.

 

[Lavos]

Alright I'll give it a shot. Thanks for the help!

 

[ICIT2LOL]

No overclocking and the firmware is updated to the newest version.

Here's the screenshot.

Well at least the PSU checks out good so it isn't lack of supply

 

[essenbe]

Alright I'll give it a shot. Thanks for the help!

Be sure and let us know how it goes. maybe Arc or me or John will come up with something.

 

[Lavos]

Switched GPUs with my brother. He uses the exact same model and neither of us have any problems. I use a triple monitor setup while he only uses one, so that might be related somehow. I can't say for sure whether the problem actually was the GPU or if the PSU wasn't properly connected or something like that, but as long as it now works properly I'm fine with not knowing what the problem was.
Thanks for the help guys!

 

[ICIT2LOL]

Ok mate it could possibly have been something as simply reseating the GPU's or the PSU leads if you did that as well, but in any case best left alone and not try any more to fix the unbroken