BSoD, 0x00000116 / 0x00000117

LeetZero · 26 May 2013

Hello,
I registered on this forum just for this issue that has been pestering me just recently.
I seem to receive random BSoDs, they happen randomly, but can be "forced" by playing a game or stress-testing.
The first time they happened they happened while purely searching on the web. I was in holiday this weekend, and it didn't happen before. Looking onto it, I noticed fixes regarding driver updates. I had a NVIDIA Driver 310.xx, I now updated to the latest 320, with no avail regarding the errors.
Using BlueScreenView, I seen the Drivers causing problems are nvlddmkm.sys, tdx.sys, ioTblMap.sys, NDProxy.sys, and at the first error, which is x117, CompositeBus.sys.
I searched my guts out on Google for every driver and error (116/117) to notice mostly about video drivers (which I did update, and nothing changed) and the only other thing I found was something regarding nvlddmkm, changing the file. Additionally I also considered overheating (also resulting from my searches), opening up a temperature program, I noticed my GPU was as much as 70*C on idle, which is absurd. I have 3 case fans (2 in 1 out) and they were full of dust, after dedusting I got about 40*C on idle. Reasonable for me, but nothing changed regarding BSoD.
I also, at first, received driver crashing error, but no BSoD or screen flicking, but after 5-10 minutes after the respective error.

The easiest way I can force into a BSoD (?) is to run BF3, in which I play about 1 minute onto when the game crashes down, the screen flicking, ending up in my screen going "off" state and nothing doable, the HDD led on my case also stopping, and my Numlock led, likewise stopping. Upon restart/forced shutdown, dmp's are created, too, under my assumption, when the screen goes black there's a BSoD happening.

If it matters anyhow, the cable is connected to DVI-D.

Thanks in advance. If there's anything I missed that would help troubleshooting let me know.

Arc · 26 May 2013

A stop 0x116 and a stop 0x117, both are display related errors.

Are you getting this BSOD after updating the display driver? The driver is latest and not widely tested, so we are not very aware of its performance till date. If it is happening only after the update, roll the display driver back to the earlier version that worked good there.

Device Manager - Roll Back Driver

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. Also set the BIOS to default, too.

How To Clear CMOS (Reset BIOS)

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.

Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark

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.

Let us know the results. Also let us know how old the build is.
________________________________________________________________________
BSOD ANALYSIS:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80089db010, fffff880059cb010, 0, d}

*** 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+13b010 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80089db010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880059cb010, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000d, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP: 
nvlddmkm+13b010
fffff880`059cb010 4055            push    rbp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`033e2888 fffff880`0548f000 : 00000000`00000116 fffffa80`089db010 fffff880`059cb010 00000000`00000000 : nt!KeBugCheckEx
fffff880`033e2890 fffff880`0548ed87 : fffff880`059cb010 fffffa80`089db010 fffffa80`095ac010 fffffa80`08b85010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`033e28d0 fffff880`05535f07 : fffffa80`089db010 00000000`00000000 fffffa80`095ac010 fffffa80`08b85010 : dxgkrnl!TdrIsRecoveryRequired+0x21f
fffff880`033e2900 fffff880`0555fb75 : 00000000`ffffffff 00000000`000016dc 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`033e29e0 fffff880`0555e2bb : 00000000`00000102 00000000`00000000 00000000`000016dc 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`033e2a10 fffff880`055312c6 : ffffffff`ff676980 fffffa80`08b85010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`033e2ab0 fffff880`0555de7a : 00000000`00000000 fffffa80`095ac010 00000000`00000080 fffffa80`08b85010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`033e2bc0 fffff800`02515e6a : 00000000`fffffc32 fffffa80`08c1f760 fffffa80`06990740 fffffa80`08c1f760 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`033e2c00 fffff800`0226fec6 : fffff800`023f1e80 fffffa80`08c1f760 fffff800`023ffcc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`033e2c40 00000000`00000000 : fffff880`033e3000 fffff880`033dd000 fffff880`0d3f6d70 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+13b010
fffff880`059cb010 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+13b010

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

2: kd> lmvm nvlddmkm
start             end                 module name
fffff880`05890000 fffff880`06371000   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

LeetZero · 26 May 2013

Arc said:

A stop 0x116 and a stop 0x117, both are display related errors.
-snip-

Minimum PSU Wattage: 310 W
Recommended
PSU Wattage: 360 W

I have a 500 W.

I have had overclocked in the past, I am on stock now.

The BSoD is not only after the display driver update, as I mentioned. The update was done because of the assumption that it's the fault of the BSoD. Downgrading will not solve the issue, unless I am going to downgrade even less than I had before, even if it worked 1 week earlier.

On an uptime of 1h and 30m now, surprisingly no BSoD or driver crash: GPU 45C, CPU 42C.

As I mentioned, any stress test is/will be followed by a BSoD regardless.

Also, the build dates around 2 years ago. The main components (PSU/HDD/MOBO/CPU/GPU) haven't been changed since. The RAM was.

Speccy:
Operating System
Microsoft Windows 7 Ultimate 64-bit SP1
CPU
Intel Core i5 2300 @ 2.80GHz 45 °C
Sandy Bridge 32nm Technology
RAM
8.00GB Dual-Channel DDR3 @ 532MHz (8-8-8-20)
Motherboard
ASRock H61M-VS (CPUSocket) 37 °C
Graphics
E2360 (1920x1080@60Hz)
1024MB GeForce GTX 460 (Undefined) 46 °C
Hard Drives
1863GB Western Digital WDC WD20EARX-00PASB0 ATA Device (SATA) 33 °C
Optical Drives
DTSOFT Virtual CdRom Device
Optiarc DVD RW AD-5260S ATA Device
Audio
VIA High Definition Audio
Though I am not sure what's up with the Speccy stuff as far as I have them listed.

Arc · 26 May 2013

We wanted the speccy screenshot for the heat report, not for the system details.... it is there in your original post :)

Stress test followed by BSOD. A good indicator of a failing GPU.
Try with onboard graphics and see if it is crashing with it in the same way or not.

Also make it sure that there is no dust allocation around the air vents and fan grills inside the computer.

LeetZero · 26 May 2013

I just played a full round of Battlefield 3 without interruptions. Something worked fine I guess, even if I didn't do anything.

Attempting a second round gave me this error

LeetZero · 28 May 2013

There seem to be random black screens now, even at startup sometimes. No BSoD is created but keyboard becomes unresponsive.

Just finished a FurMark, somehow, without crashing, even if about 10 crashes before it crashed about 1 second of starting it. Anyway, Temp was 42->85 (C). FPS 37-38.

Arc · 28 May 2013

The screenshot says it is a video memory error of the GPU.

Try another test .... NVIDIA/AMD Video Card - Test with OCCT. Take both the stress test and video memory test.

But, the most important test that is needed here is to observe the situation ... how it is working with the onboard graphics. Use the onboard graphics and observe if it is behaving the same there or not.

LeetZero · 28 May 2013

Hello. Here are the OCCT results for 30 minutes.
I am not sure how to Memory Stress.
The GPU pushed as far as 93C. For some reason, it didn't save it as a image log though, so I guess I could mention that it climbed quite quickly in the first 10 minutes from 40C to 80C, then it slowly 10-30 to 92C.

Arc · 28 May 2013

Stress test passed good. The video memory test is described in NVIDIA/AMD Video Card - Test with OCCT, Test 2: Video Memory Test

Also, observe the situation using onboard graphics.

LeetZero · 28 May 2013

Arc said:

Stress test passed good. The video memory test is described in NVIDIA/AMD Video Card - Test with OCCT, Test 2: Video Memory Test

Also, observe the situation using onboard graphics.

I'll attend the onboard graphics part a bit later, I have a wire party at the back of my PC. Affording to take out my PC 2 days consecutively is not of my ethics.

I will do it at the next crash or tomorrow morning, given my PC will be shut off anyway.

But yeah. The tutorial given is for v3 OCCT. I am using v4 OCCT, which no longer has memory test apparently.