BSOD 0x116 (stop error) Replaced GPU, replaced RAM, replaced PSU

Zuriel · 30 Jun 2014

My monitor goes black and I am forced to reboot. After rebooting I get a blue screen prompt telling me that i've recovered from a BSOD. I've been monitoring them since October.

In October, I RMA'd my graphics card. Oct 27. You can see that after I got a new GPU, my BSOD's halted... so obviously its the GPU right? if you look at my BSOD dumps the last one is OCT 27, new gpu, and i don't get one until Feb 7.

So on Feb 7 I call up eVGA again and say, ok so my GPU is bad again and I wonder if its something im doing to kill them.

So I am going to get a second RMA and the tech tells me that they received my first card and they ran it for over a hour in a diagnostic app and didn't have a single problem... aka my card was fine...

so i explain my BSOD issues and the tech tells me that it may be a voltage issue and that it may be my power supply... soooooooooo

I goto Tiger Direct down the street and buy a "whatever i can get" thats over 1000 watts supply because I have a 850 watt PSU and obviously its not enough power so i go big... and guess what... My last BSOD dump before the PSU is 3/18 March 18. So new PSU and I don't get a single BSOD until 6/14/2014.

So I have attached "All" of my dumps and all my info with the issues.

My problem is... if its "not" my GPU, why did getting a new one give me no BSOD for 3 months.

my problem is... if its "not" my PSU why did getting a new one march 18 let my PC run till 6/14 with no BSOD's.. again 3 months...

is this not randomly coincidentally off? i mean.. why would a new GPU make it work for 3 months, then find out from eVGA my old GPU was fine. then why did a new PSU make it work, when my old one "was" working fine minus the BSOD's.. which make me wonder if the PSU is the issue.. again, why would it magically just work with no setting changes for 3 months?

or is there something coincidental about my issues??? like maybe something im missing?

also... my motherboard is out of warranty by a few months, so Gigabyte said too bad... but they said "oh well a stop error like that sounds like RAM"... but i replaced my Ram with Corsair all new sticks...

i also set up my voltages in my BIOS to the right voltages, the right RAM timings, the right everything... i think...

I have a liquid cooled PC so its hard to just pull a CPU or pull a GPU and swap it around :\

Also, my BSOD's happen randomly.. usually in the first 10 minutes, then usually not again for hours or days... its rare that i have 2 BSOD dumps in 1 day and after it BSOD's i reboot and run it all day.. so its not like i keep it off... and my temps are stupid sexy... 30 - 40c for CPU under full load, and GPU sits at 40 - 50 all day long. its not a temp issue, because if it was, why would it happen instantly, then not again, and i can game all day and night with no issues.. its just a SUPER RANDOM thing to me... also if i dual boot into mac (like a hacintosh) my mac also black screens and reboots, so its the same stop video issue thats happening.

Also im a MSDN subscriber so i have tried a fresh ISO of win 8.1 and 2 or 3 win 7 64's (different media 1x burn speed, the works). thinking that maybe its OS related... (which im pretty dang sure its not).

if anyone can give me some better insight that would be really helpful. Don't wanna dump $ into a 3rd PSU or RMA my GPU again (but eVGA said i can). so please give me some solid advice, thanks!

Arc · 01 Jul 2014

Hi Zuriel.

I read your OP. I would suggest you to have an open mind; and dont decide that it is not it. Because during troubleshooting you have to get everything tested.

The BSOD is a stop 0x116. That is an error from the part of the display environment. That means ....

The GPU itself
The display driver
The PSU
The system temps and dust allocation inside the computer
The hardware parts like GPU fans
Overclocking failure

And etc. I would suggest you to go through a thorough troubleshooting, whatever may be the idea you may have about those.

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

Check if the Power Supply Unit (PSU, 850 watts you said) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator v2.5

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 .

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Install the NVIDIA DRIVERS 314.22WHQL only, at least as a test. Because it never fails on itself.

Uninstall All nvidia items in Control Panel > Programs and features
- 3D Vision Control Driver
- 3D Vision Driver
- Graphics Driver
- HD Audio Driver
- PhysX
- nvidia Update
(Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
Now follow Drivers - Clean Left over Files after Uninstalling
Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:

Let us know the results.
_____________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80132af4e0, fffff880101fb608, 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+9a3608 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80132af4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880101fb608, 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+9a3608
fffff880`101fb608 48ff258159edff  jmp     qword ptr [nvlddmkm+0x878f90 (fffff880`100d0f90)]

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`09ff7b88 fffff880`10541140 : 00000000`00000116 fffffa80`132af4e0 fffff880`101fb608 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`09ff7b90 fffff880`10514867 : fffff880`101fb608 fffffa80`171ca000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`09ff7bd0 fffff880`10540f4f : fffff800`ffffd84d ffffffff`fffe7960 fffffa80`132af4e0 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`09ff7c80 fffff880`0f83803d : fffffa80`17268850 00000000`00000080 00000000`00000000 fffffa80`171c9410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`09ff7d00 fffff800`0376673a : 00000000`04614bb4 fffffa80`17197610 fffffa80`12aeb040 fffffa80`17197610 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`09ff7d40 fffff800`034bb8e6 : fffff800`03645e80 fffffa80`17197610 fffff800`03653cc0 fffff880`09ff7e40 : nt!PspSystemThreadStartup+0x5a
fffff880`09ff7d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+9a3608
fffff880`101fb608 48ff258159edff  jmp     qword ptr [nvlddmkm+0x878f90 (fffff880`100d0f90)]

SYMBOL_NAME:  nvlddmkm+9a3608

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  539a4345

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

11: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f858000 fffff880`104e4000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Fri Jun 13 05:48:13 2014 (539A4345)
    CheckSum:         00C4CA14
    ImageSize:        00C8C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Zuriel · 07 Jul 2014

Clean installed the NVIDIA DRIVERS 314.22WHQL only.

Ran FurMark for 30 minutes. Temps never went over 65c at 2560x1600 using the exact settings listed in the forum post you linked to set it up (burnin, fx, logging, etc). No issues, no artifcats, I am writing this post after the 30 minutes of running it with no issues.

Like i suspected... its not a temperature issue... its not... I turn the PC on today, got a blue screens within 4 minutes of running the PC. Rebooted after BS0D #1 and got the second within 1 minute of BSOD #1. Rebooted again and haven't gotten a BSOD yet, and I ran the 30 minute furmark test....

both BSOD's were stop 16, same error as always. Drivers have no chanage. stress test has no change.

Going to pull all the sticks but 1 stick and run a memtest64 on it. Then i'll run it with the solo stick and see, but its looking more and more like a power supply / motherboard issue...

any thoughts?

Arc · 07 Jul 2014

You havent reported about the temperature and the PSU yet?

And, for reporting the BSOD, upload the data as per the Blue Screen of Death (BSOD) Posting Instructions in your reply post alongwith the two missing reports.