BSOD starting, playing, internet explorer and in idle. Error 116

[gunner38]

Hello, I am having tons of problems with my computer regarding BSOD BCCode 116.

A couple of months ago, I bought a new graphics card: a Nvidia 560GTX (Gigabyte GV-NV56GOC) and a new PSU (Corsair CX500 V2 Builder Series, 500 W) to run it and after 3 weeks the PC began to fail with the 116 error.

At the begining it crashed only at Windows 7 blue starting screen (after the loading screen with win logo and a progress bar). It happened once every 4 or 5 days.
After a month it was almost imposible to run unless starting in "FailSafe Mode" and began to crash in the desktop in idle. I tested it with another drivers, clean installs, changing cabes, etc... and nothing worked, only with another graphics card (an old nvidia 220GT wich came with the PC) and worked properly so I decided so send the card in RMA.

A couple of days ago the seller sent me an email saying that they couldn't find any issue with the 560GTX and they sent the card to Gigabyte to further testing (I wil have to wait 20-30 days to have more info). Yesterday my PC with the old card (the 220GT) began to fail while playing Skyrim with a grey screen and a strange buzz in the speakers. After 2 seconds it restarts saying that there was an system error bccode 116. Today it has crashed 4 times in 5 hours while playing (same as yesterday), "youtubbing" or (I think, but not sure than) in idle with a white screen and a strange buzz in the speakers, but not starting like with the 560GTX.

I had to change my HDD a month ago too so I tested in 2 diferent HDDs, drivers are OK and I guess that the PSU is enough for the new card and more than enough with the old one. I also ran sfc.exe /scannow witho no problems.


I'm running Windows Home Premium x64 (Service Pack 1) OEM, reinstalled one or 2 months ago. I will attach minidump files with errors of both cards.

 

[JaidynM]

The BCCode 116 is usually a problem with the graphics card.

Run a GPU stress test with Furmark. If it reports any errors you might want to give it back to the seller. If it's still under warranty, they should at least replace it.
http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

Also try and update your graphics drivers. The newest ones can be found below.
NVIDIA Driver Downloads - Advanced Search

Where did you purchase the card from? This definitely looks more like a hardware problem.

 

[gunner38]

Well, I already sent the 560GTX under warranty and the seller (www.pccomponentes.com) said taht the card passed those tests:
- Furmark 2 Hours
- Unigine Heaven 6 Hours
- OCCT 5 Hours

They sent it 10 days ago to the manufacturer (Gigabyte) to further testing and I have no news of it yet. The seller said that it would last around 20-30 days.

The card I'm using now is the old one, a 220GT with a very low power requirement and performance.
I did the Furmark test 30-40 min this morning and it didn't found any problems:
- No crashes.
- No overheating (stable since minute 5 around 45% fan speed at 67ºC/153ºF).
- 99% of GPU usage at 6 FPS (like I said a very low performance card).

Any ideas based in the .dmp files?

Thanks for you help!

 

[gunner38]

Really, I don't know what is going on. It crashed again while playing Skyrim and says something about X64_0x116 and Tdr:2_IMAGE_nvlddmkm.sys

In case it helps I'm adding a new .dmp file for the last error.

 

[JaidynM]

Unfortunately, I cannot read dump files. However, I can get someone who can to help you. This being said, I don't think there's much to be found in a dump files as it looks like a hardware problem.

In the meantime, try installing the latest drivers from the link I provided above (if you haven't done so already).

Also, have a look at the following troubleshooting thread...
http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html

...as well as this post:

If playing with video driver versions hasn't helped, make sure the box is not overheating. Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU. Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference. If so, it might be as simple as dust buildup and subsequently inadequate cooling.

Finally, if Gigabyte still have it, I'm sure they'll find something or have already found something. The actual vendor can often find a lot more problems than the dealer.

 

[Dave76]

First, go to this link and follow the instructions.
Blue Screen of Death (BSOD) Posting Instructions
Post all the info requested at the 'BSOD posting instructions' thread.
This information will give us the details that will help us to find the cause of your crashes.


If you are having crashes with both Graphics cards, there is a good chance these are not the cause.

Go to the links posted by JaidynM, run all of the tests and be sure to monitor your CPU core temps when running Prime95.

D/L Real Temp and keep it running during the test.

Don't go over 76.4°C, this is the max temp for your CPU.
Intel® Core™2 Quad Processor Q8300

Let us know the results of the tests.

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8008cae4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88010057ae4, 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+c3bae4
fffff880`10057ae4 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`04181b48 fffff880`100f5000 : 00000000`00000116 fffffa80`08cae4e0 fffff880`10057ae4 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`04181b50 fffff880`100c8867 : fffff880`10057ae4 fffffa80`09fc2000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`04181b90 fffff880`100f4e0f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`08cae4e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`04181c40 fffff880`101c3ec1 : fffffa80`0aa87200 00000000`00000080 00000000`00000000 fffffa80`0a003010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`04181cc0 fffff800`0311afee : 00000000`01b0d29b fffffa80`09fc7b60 fffffa80`057eb040 fffffa80`09fc7b60 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`04181d00 fffff800`02e715e6 : fffff800`02ff5e80 fffffa80`09fc7b60 fffff800`03003cc0 fffff880`01417384 : nt!PspSystemThreadStartup+0x5a
fffff880`04181d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+c3bae4
fffff880`10057ae4 4883ec28        sub     rsp,28h

SYMBOL_NAME:  nvlddmkm+c3bae4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e99233b

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

STOP 0x00000116: VIDEO_TDR_ERROR
Usual causes: Video driver, overheating, bad video card, ?BIOS, ?Power to card.

Have you updated the Graphics card driver?
Which version are you using now?

Your dump file is showing a lot of older drivers, go to your OEM driver site and look for any drivers newer that 2009, install them.

Have you installed all the Windows updates?
If not, install them.

This BSOD is difficult to analyze, we will need this information from the 'BSOD posting instructions' thread, listed above in order to proceed.

This is a Windows 7 Canonical display driver, you can get it from a Windows update.

fffff960`00760000 fffff960`00787000   cdd      cdd.dll      [COLOR="Red"]unavailable[/COLOR] (00000000)

This is a Windows 7 Frame buffer display driver, you can get it from a Windows update.

fffff960`00400000 fffff960`0040a000   TSDDD    TSDDD.dll    [COLOR="red"]unavailable[/COLOR] (00000000)

This is a Windows7 Multi-user Win32 driver, you can get it from a Windows update.

fffff960`000c0000 fffff960`003d4000   win32k   win32k.sys   [COLOR="red"]unavailable[/COLOR] (00000000)

 

[gunner38]

Allright, I am attaching all the info required (somethings might be in spanish inside the files, sorry).

1-I did the Furmark test again and results are OK both in GPU and CPU temperatures.

2- The video driver is ForceWare 285.62. If I see any newer in nvidia.com I will update it now.

3- I had almost all the updates, 4 optionals have been installed after making the tests. I have Service Pack 1 fully updated now.

4- I checked Medion page and I downloaded 4 drivers (I had 3 of them already installed when I started the topic).

One question, there is a specific way to download these drivers?

This is a Windows 7 Canonical display driver, you can get it from a Windows update.

Code:
fffff960`00760000 fffff960`00787000 cdd cdd.dll unavailable (00000000)
This is a Windows 7 Frame buffer display driver, you can get it from a Windows update.

Code:
fffff960`00400000 fffff960`0040a000 TSDDD TSDDD.dll unavailable (00000000)
This is a Windows7 Multi-user Win32 driver, you can get it from a Windows update.

Code:
fffff960`000c0000 fffff960`003d4000 win32k win32k.sys unavailable (00000000)

I used "seach for updates" option inside "windows update" and I don't know if they are installed right now.

Thank you for the help.

 

[Dave76]

For this type of debugging I'll need to go through your event logs, since they are in spanish, there is not much I can do.

Try running the System File Checker at the elevated command prompt, this tutorial will explain how to do this, use 'Option Two' Scan and Repair.
Run this a minimum of three times with re-boots after each run, even if it says it has found files it cannot fix.

How to Repair Windows 7 System Files with System File Checker


What RAM do you have installed?
Run memtest86+ with all four of your RAM cards installed.
If you get an error, you can stop the test and let us know.
RAM - Test with Memtest86+


If that doesn't work you can try a Repair Install.

How to Do a Repair Install to Fix Windows 7


Same as the last one.

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800a3734e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880100d8ae4, 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+c3bae4
fffff880`100d8ae4 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`03735b48 fffff880`07086000 : 00000000`00000116 fffffa80`0a3734e0 fffff880`100d8ae4 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`03735b50 fffff880`07059867 : fffff880`100d8ae4 fffffa80`09f6f000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`03735b90 fffff880`07085e0f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`0a3734e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`03735c40 fffff880`07154ec1 : fffffa80`05e1e1b0 00000000`00000080 00000000`00000000 fffffa80`09ee3010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`03735cc0 fffff800`03324fee : 00000000`01e2b251 fffffa80`09f55210 fffffa80`057eb040 fffffa80`09f55210 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`03735d00 fffff800`0307b5e6 : fffff800`031ffe80 fffffa80`09f55210 fffff800`0320dcc0 fffff880`0143fa20 : nt!PspSystemThreadStartup+0x5a
fffff880`03735d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+c3bae4
fffff880`100d8ae4 4883ec28        sub     rsp,28h

SYMBOL_NAME:  nvlddmkm+c3bae4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e99233b

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

 

[JMH]

Following on from the other good advice from my friends Jaidyn & Dave...

It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash.

As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.

If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

If playing with video driver versions hasn't helped, make sure the box is not overheating.

Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.

Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.

If so, it might be as simple as dust buildup and subsequently inadequate cooling.

I would download cpu-z and gpu-z (both free) and keep an eye on the video temps.

http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html