BSOD while playing GPU intensive programs, Common 0xC000000D error

Zietlogik · 03 Jun 2013

This has begun happening roughly 1-2 weeks ago, prior to this the system ran flawlessly (never had a BSOD)

The strangest thing is that the BSOD started happening right after a windows update, and an install of MSE (never had it before this)

I have tried many different tests and fixes to try and solve this issue myself, but to no avail.

-Ran Memtest with 2x2Gb 1600 + 2x4Gb 1066 \ no errors
-Removed 2x4Gb 1066 \ no errors
(current modules are 2×2 Corsair DDR3 1600 (installed) / 2×4 G.Skill DDR3 1066 (removed))
-Ran Chkdsk \ complete
-Installed new Heatsink (Speedfan was giving me false temp readings, the CPU temp was not the issue / Current temps are roughly min:36 max:69 per Prime95)
-Several clean installs of various recent video drivers
-Checked PSU connections to hardware
-Cleaned dust from hardware

All-in-all the BSOD issue takes longer after troubleshooting to occur, but still occurs very frequently. I am wondering if my Raidmax 680w PSU is to blame, but I cannot be sure because I have no replacement hardware to test this.

Zietlogik · 04 Jun 2013

I would like to add an additional note here, that now it would seem that when the computer freezes/hangs, the system is still functioning (sounds/keypresses (i know because i had a VoiP program running and it was still working and responding when the screen was black), the system DOES manage to recover the video driver for roughly 1-5 seconds before completely freezing (no sound, frozen screen and requires force restart)

The strange part of this is that when the system prompts me prior to loading windows for the typical Safe Mode, start normally etc. that entire screen is messed up, flashing, going black, and distorted and not properly displaying.

Arc · 04 Jun 2013

Both the crash dumps you uploaded indicates to a stop 0x116, video TDR failure. It is graphics/display related, and includes a wide area of the computer's hardware-software environment in its scope.

Is it started to appear after you updated the display driver to the latest? If so, roll it back to the earlier version that worked good there.
Device Manager - Roll Back Driver

You are Overclocking, and it is one of the reasons of a stop 0x116.

Code:

CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3399

As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
How To Clear CMOS (Reset BIOS)

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

Let us know about your PSU wattage. Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
At least 30% extra is safe.

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.

And, I am guessing that the system is not an old one. How old it is actually? Have you cleaned the air vents and fan frills too?

Let us know.
___________________________________________________________________________________
BSOD ANALYSIS:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80039cf110, fffff88007dd5ed0, ffffffffc000009a, 4}

Unable to load image 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+8e9ed0 )

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: fffffa80039cf110, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88007dd5ed0, 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+8e9ed0
fffff880`07dd5ed0 4055            push    rbp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`06779a48 fffff880`06f36054 : 00000000`00000116 fffffa80`039cf110 fffff880`07dd5ed0 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`06779a50 fffff880`06f09867 : fffff880`07dd5ed0 fffffa80`05d85000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`06779a90 fffff880`06f35e63 : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`039cf110 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`06779b40 fffff880`0743803d : fffffa80`06648160 00000000`00000080 00000000`00000000 fffffa80`05132410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`06779bc0 fffff800`0331aede : 00000000`02dc35d5 fffffa80`05b2db50 fffffa80`0369f5f0 fffffa80`05b2db50 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`06779c00 fffff800`0306d906 : fffff800`031f7e80 fffffa80`05b2db50 fffff800`03205cc0 fffff800`00000003 : nt!PspSystemThreadStartup+0x5a
fffff880`06779c40 00000000`00000000 : fffff880`0677a000 fffff880`06774000 fffff880`067794d0 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+8e9ed0
fffff880`07dd5ed0 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+8e9ed0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  518fe8f9

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

3: kd> lmvm nvlddmkm
start             end                 module name
fffff880`074ec000 fffff880`07fcd000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Mon May 13 00:39:45 2013 (518FE8F9)
    CheckSum:         00AB6DED
    ImageSize:        00AE1000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

SCSI?

Zietlogik · 04 Jun 2013

Is it started to appear after you updated the display driver to the latest? If so, roll it back to the earlier version that worked good there.

I have done clean installs of various drivers, including the latest drivers as well as the last known good drivers I was using prior to the crashes (tested all drivers all the way back down to 310.90)

You are Overclocking, and it is one of the reasons of a stop 0x116.
Code:
CPUID: "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed: 3300
CurrentSpeed: 3399
As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
How To Clear CMOS (Reset BIOS)

Yes, I have only started running an OC recently, and the issues were appearing prior to the OC. TBH the reason I still have the OC settings is because the system is running for longer before crashing than on stock settings oddly enough :S

I used the basic Asus onboard Oc tool and normally 90% of the time I keep my settings on the F5 defaults.

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

Standard 1080 benchmark gives me temps of 73 max
1920x1200 burn-in gave me 87 max

Let us know about your PSU wattage. Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
At least 30% extra is safe.

According to eXtreme PSU Calculator, Minimum: 425, Recommended: 475
Currnently installed 680 Raidmax

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.

http://imgur.com/pWtFpvr.jpg

Note: I also have a saved screenshot of the false readings Speedfan was giving me (the entire reason I bought a brand new heatsink in the first place D: )

https://i.imgur.com/ovwBAur.jpg

And, I am guessing that the system is not an old one. How old it is actually? Have you cleaned the air vents and fan frills too?

I have recently done a complete clean of everything I could even see dust in, replaced the heatsink, cleaned out all fans, GPU had alot hidden in its casing but has been removed. This was done about a week ago

Thank you for your reply so far, I would love to get this resolved :)

Note: Also notice you are on some kind of GFX team? I used to be quite the signature enthusiast myself when I was still working in PS :P

Arc · 04 Jun 2013

OK... before suggesting the next things, I have a question for you. Can you tell me about the source of the SCSI you have installed?

No code has to be inserted here.

Can you disable it?

Zietlogik · 04 Jun 2013

Arc said:

OK... before suggesting the next things, I have a question for you. Can you tell me about the source of the SCSI you have installed?

No code has to be inserted here.

Can you disable it?

I do not see that particular device in my device manager, but I do have AVFT4YZP IDE Controller...perhaps the name is somehow a variable that keeps changing but...that is strange either way.

Should I try and disable that device?

EDIT: And still every single time i get the crash that I need to manual restart from, I still get "Session "Microsoft Security Client OOBE" stopped due to the following error: 0xC000000D"

EDIT 2: Adding a Diagnostic Tool zip from just after a crash

Arc · 05 Jun 2013

No new crash dump in the zip. Anyway, can you disable that aforesaid IDE controller and uninstall the program (I failed to get an idea about it) associated with it? I think it is needed.

Zietlogik · 05 Jun 2013

I disabled AVFT4YZP IDE Controller (the only one I could find in the device manager), but I have no idea what software might be associated with it, because i'm not even entirely certain what it is.

I disabled it yesterday and still get crashes, so if it is that software/program connected to it, I have no clue what it is.

EDIT: Just had another crash and it does not create a dump file, Screen went black, computer still running, sound disappears. But it never restarts, so I have to hit the reset button.

EDit2: I may just buy a new Vid Card and PSU.......

"Display driver nvlddmkm stopped responding and has successfully recovered."

Arc · 06 Jun 2013

If you plan to buy a new GPU, that is the best idea in this case. It is mostly a hardware issue, but too random to be caught by the GPU stress test.

Zietlogik · 06 Jun 2013

I am hoping that it alone is the cause, but you can never be too sure. Also would my current 680 PSU still be sufficient if I upgraded from my current 570 to a 680? (one on sale im looking at, almost seems too good to be true)

But the entire issue is so strange, just popping up out of nowhere and just doing all kinds of crazy things.

Now one thing I have noticed is that when the drivers crash, the screen goes black and the monitor goes into sleep mode, turning it off and back on then causes the drivers to recover (normally just a black screen and sound loop/frozen sound)