BSOD - BCCODE 116 - random resets when browsing or gaming

mjordan7 · 04 Mar 2015

Hi, first time posting here. Would really appreciate any help you guys could offer.

I've been having some issues with my desktop recently. It seems to reset randomly up to 2-3 times per day. My monitor goes to black screen and then computer restarts. This doesn't occur in any predictable time frame when doing something, but so far it's only seemed to occur when I'm browsing chrome or playing various video games (far cry 4, hearthstone, sc2, eq1). Once it reboots, everything works as it did before it reset, but it gives the error BC CODE 116.

Problem signature: Problem Event
Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: 116
BCP1: FFFFFA800CFF24E0
BCP2: FFFFF88005252F38
BCP3: FFFFFFFFC000009A
BCP4: 0000000000000004
OS Version: 6_1_7601
Service Pack: 1_0 Product: 768_1

The other thing that I've noticed is that whenever I have a browser or game running, I'll see flickering horizontal static lines at various points on the screen. These lines never occur on the desktop (black solid), and will not occur above or below the vertical span of the browser window or windowed game that is running. Resizing the browser or game window causes the lines to occur only to the left and right of the resized smaller window, never above the window's vertical span. I would really appreciate any suggestions on how to try to fix this. I'll list my specs and what I've tried below.

operating system: Windows 7 premium home 64bit
Monitor: dell u3011
computer: Alienware Aurora r4 desktop from 2011
cpu: Intel i7-3930K @ 3.20GHz not overclocked
memory: 16gb ram
gpu: geforce gtx 980 not overclocked (previously geforce 560 ti)

I upgraded the stock 550w power supply and previous graphics card approximately 2 months ago when I noticed the horizontal lines described above. I assumed my graphics card was failing. I was not having bluescreen/resets at that time. Upgrading the card did not change the horizontal lines, and the bluescreen/resets happened within 2 weeks of the upgrade.

Things I have tried:
1) reinstall windows completely
2) ensure most updated bios
3) ensure most up to date video card driver
4) check gpu and cpu temperatures
5) open side of case and have box-fan blowing into PC

I've purchased a replacement motherboard online and have that on the way. In researching the BCCODE116, one of the posts finished with the person saying he fixed it after replacing his motherboard.

The only other thing I could think of trying is to buy a new monitor and see if that changes anything.

Anything you guys can think of to try I would really appreciate it. Trying to make this computer last as long as it can.

Thanks for reading

Arc · 05 Mar 2015

A stop 0x116 is a display related issue.

As the display driver is latest, not paying attention on it right now (may be later).

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. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.

eXtreme Power Supply Calculator - The only power supply calculator trusted by PSU manufacturers and computer enthusiasts

Also let us know the wattage of your PSU.

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

Code:

BugCheck 116, {fffffa800cfd54e0, fffff88006684f38, 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+7a3f38 )

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: fffffa800cfd54e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88006684f38, 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+7a3f38
fffff880`06684f38 48ff25f192edff  jmp     qword ptr [nvlddmkm+0x67d230 (fffff880`0655e230)]

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`0b14ba48 fffff880`058d0134 : 00000000`00000116 fffffa80`0cfd54e0 fffff880`06684f38 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`0b14ba50 fffff880`058a3867 : fffff880`06684f38 fffffa80`157de000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0b14ba90 fffff880`058cff43 : 00000000`ffffd846 ffffffff`fffe7960 fffffa80`0cfd54e0 fffff880`0599ff3c : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`0b14bb40 fffff880`059a003d : fffffa80`18f685e0 00000000`00000080 00000000`00000000 fffffa80`157d2410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`0b14bbc0 fffff800`0331ab8a : 00000000`028ad588 fffffa80`157c1760 fffffa80`0cd8bae0 fffffa80`157c1760 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`0b14bc00 fffff800`0306d8e6 : fffff800`031f8e80 fffffa80`157c1760 fffff800`03206cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0b14bc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+7a3f38
fffff880`06684f38 48ff25f192edff  jmp     qword ptr [nvlddmkm+0x67d230 (fffff880`0655e230)]

SYMBOL_NAME:  nvlddmkm+7a3f38

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  54d3b001

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`05ee1000 fffff880`068f3000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu Feb 05 23:31:37 2015 (54D3B001)
    CheckSum:         009D4DDE
    ImageSize:        00A12000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

mjordan7 · 05 Mar 2015

Thanks for the reply!

The power supply is a Corsair RM Series 750 Watt ATX/EPS - CP-9020055-NA RM750

I downloaded furmark and ran it. I noticed the horizontal display artifacts on the test, but no system resets/bluescreens. I've posted a picture of what I saw on the test as well as speccy screenshot.

I attempted the power supply calculator but I don't know about a lot of the info it's asking for.

The computer doesn't seem to overheat. I have the case open and a boxfan blowing inside it currently and it's still having the display artifacts with gaming/browsing and bluescreen/resets several times daily.

Please let me know if there is anything else you need or that I can do.

Thanks a lot for helping me

Arc · 05 Mar 2015

Display artifacts are strong indication of a failing graphics card. It would be better if you apply any other card or onboard graphics and see how it goes.