BSOD randomly occurs, BCCode 116

NZCoyote · 22 Nov 2014

Thanks to anyone that looks at this.

I've had a random bluescreen and reboot problem on my PC since a couple of months ago, happens at random, sometimes within 15 minutes, other times not for days. Before the blue screens started the system was rock solid.

I have completed a fresh install of Windows and a few other required software programs, and the random crashes are still occurring with the fresh install.

I've attached the log/dump files that were collated by Dm Log Collector.

PC Specs:

Processor - Intel Core i7-960
Motherboard - Gigabyte X58-UD5
RAMM - 6X 2GB Corsair DDR3 CMX6GX3M3A2000C9
GPU - 2x Gigabyte Geforce GTX680
OS - Windows 7 (6.1) Ultimate Edition 64-bit
OS Drive - OCZ Vertex 3 SSD
Storage Drive - 3x Western Digital1TB Green WD10EADS

Regards,
Nigel

Arc · 22 Nov 2014

Multiple bugcheck codes are there, giving a hint of display failure. Despite of having multiple versions of the display driver installed.
A stop 0x116 is a display/graphics related BSOD. The most possible causes are:

Overclocking;
Inadequate power supply;
System overheat and dust allocation;
A failing display driver; and
A failing graphics card.

Let us check them, one by one. Do the following things with proper documentation.

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) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator - The most trusted PSU Wattage Calculator
Also let us know the wattage of the 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 .

Uninstall the latest version of the display driver that you have installed. Use Display Driver uninstaller to do it. Then apply 340.52 WHQL there. To have a trouble free driver installation, follow NVIDIA Drivers - Avoid Problems.

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.

Let us know the results.
____________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80105674e0, fffff8800f401288, ffffffffc00000b5, a}

Unable to load image \SystemRoot\system32\DRIVERS\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+158288 )

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: fffffa80105674e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f401288, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc00000b5, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000a, Optional internal context dependent data.

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


FAULTING_IP: 
nvlddmkm+158288
fffff880`0f401288 48ff25c1506900  jmp     qword ptr [nvlddmkm+0x7ed350 (fffff880`0fa96350)]

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`0230da58 fffff880`046f3134 : 00000000`00000116 fffffa80`105674e0 fffff880`0f401288 ffffffff`c00000b5 : nt!KeBugCheckEx
fffff880`0230da60 fffff880`046f2f0f : fffff880`0f401288 fffffa80`105674e0 fffffa80`0c8fe740 fffffa80`0c5b4410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0230daa0 fffff880`0479af13 : fffffa80`105674e0 00000000`c00000b5 fffffa80`0c8fe740 fffffa80`0c5b4410 : dxgkrnl!TdrIsRecoveryRequired+0x273
fffff880`0230dad0 fffff880`047c8ed6 : fffffa80`ffffffff 00000000`0000c4f6 fffff880`0230dc30 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`0230dbb0 fffff880`047962aa : fffffa80`0c5b4410 ffffffff`feced300 fffffa80`0c8fe740 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`0230dbf0 fffff880`047c2ff6 : 00000000`00000000 fffffa80`0c8fe740 00000000`00000080 fffffa80`0c5b4410 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2
fffff880`0230dd00 fffff800`0312673a : 00000000`0394f93f fffffa80`0c1e0760 fffffa80`099e0990 fffffa80`0c1e0760 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`0230dd40 fffff800`02e7b8e6 : fffff800`03005e80 fffffa80`0c1e0760 fffff800`03013cc0 fffff880`03576701 : nt!PspSystemThreadStartup+0x5a
fffff880`0230dd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+158288
fffff880`0f401288 48ff25c1506900  jmp     qword ptr [nvlddmkm+0x7ed350 (fffff880`0fa96350)]

SYMBOL_NAME:  nvlddmkm+158288

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5457e833

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

2: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f2a9000 fffff880`0ff89000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Tue Nov 04 02:10:19 2014 (5457E833)
    CheckSum:         00CA351E
    ImageSize:        00CE0000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8800f3b84e0, fffff88007b54288, fffff88007b53ae0}

Probably caused by : nvlddmkm.sys ( nvlddmkm+1534e0 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800f3b84e0, The address that the exception occurred at
Arg3: fffff88007b54288, Exception Record Address
Arg4: fffff88007b53ae0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nvlddmkm+1534e0
fffff880`0f3b84e0 48397908        cmp     qword ptr [rcx+8],rdi

EXCEPTION_RECORD:  fffff88007b54288 -- (.exr 0xfffff88007b54288)
ExceptionAddress: fffff8800f3b84e0 (nvlddmkm+0x00000000001534e0)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000008
Attempt to read from address 0000000000000008

CONTEXT:  fffff88007b53ae0 -- (.cxr 0xfffff88007b53ae0;r)
rax=0000000000000000 rbx=fffff8a00ce56a68 rcx=0000000000000000
rdx=0000000000000000 rsi=fffff8a00ce56a50 rdi=fffffa800c5fe010
rip=fffff8800f3b84e0 rsp=fffff88007b544c0 rbp=fffff88007b54619
 r8=0000000000000000  r9=0000000000000000 r10=fffff80002e4d000
r11=0000000000000352 r12=0000000000000001 r13=0000000000000001
r14=0000000000000001 r15=fffffa800b62ce98
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nvlddmkm+0x1534e0:
fffff880`0f3b84e0 48397908        cmp     qword ptr [rcx+8],rdi ds:002b:00000000`00000008=????????????????
Last set context:
rax=0000000000000000 rbx=fffff8a00ce56a68 rcx=0000000000000000
rdx=0000000000000000 rsi=fffff8a00ce56a50 rdi=fffffa800c5fe010
rip=fffff8800f3b84e0 rsp=fffff88007b544c0 rbp=fffff88007b54619
 r8=0000000000000000  r9=0000000000000000 r10=fffff80002e4d000
r11=0000000000000352 r12=0000000000000001 r13=0000000000000001
r14=0000000000000001 r15=fffffa800b62ce98
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nvlddmkm+0x1534e0:
fffff880`0f3b84e0 48397908        cmp     qword ptr [rcx+8],rdi ds:002b:00000000`00000008=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000008

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fa100
GetUlongFromAddress: unable to read from fffff800030fa1c0
 0000000000000008 Nonpaged pool

FOLLOWUP_IP: 
nvlddmkm+1534e0
fffff880`0f3b84e0 48397908        cmp     qword ptr [rcx+8],rdi

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

LAST_CONTROL_TRANSFER:  from fffffa800c5c9640 to fffff8800f3b84e0

STACK_TEXT:  
fffff880`07b544c0 fffffa80`0c5c9640 : fffffa80`0b622db0 ffffd319`484c764e 00000000`00000001 fffffa80`0c5fe000 : nvlddmkm+0x1534e0
fffff880`07b544c8 fffffa80`0b622db0 : ffffd319`484c764e 00000000`00000001 fffffa80`0c5fe000 fffff880`0f3b8402 : 0xfffffa80`0c5c9640
fffff880`07b544d0 ffffd319`484c764e : 00000000`00000001 fffffa80`0c5fe000 fffff880`0f3b8402 fffffa80`0c600018 : 0xfffffa80`0b622db0
fffff880`07b544d8 00000000`00000001 : fffffa80`0c5fe000 fffff880`0f3b8402 fffffa80`0c600018 fffff8a0`0ce56a80 : 0xffffd319`484c764e
fffff880`07b544e0 fffffa80`0c5fe000 : fffff880`0f3b8402 fffffa80`0c600018 fffff8a0`0ce56a80 fffffa80`0ea37590 : 0x1
fffff880`07b544e8 fffff880`0f3b8402 : fffffa80`0c600018 fffff8a0`0ce56a80 fffffa80`0ea37590 fffffa80`0b62c168 : 0xfffffa80`0c5fe000
fffff880`07b544f0 fffffa80`0c600018 : fffff8a0`0ce56a80 fffffa80`0ea37590 fffffa80`0b62c168 00000000`00000001 : nvlddmkm+0x153402
fffff880`07b544f8 fffff8a0`0ce56a80 : fffffa80`0ea37590 fffffa80`0b62c168 00000000`00000001 fffff880`0f36f36e : 0xfffffa80`0c600018
fffff880`07b54500 fffffa80`0ea37590 : fffffa80`0b62c168 00000000`00000001 fffff880`0f36f36e fffffa80`0b622000 : 0xfffff8a0`0ce56a80
fffff880`07b54508 fffffa80`0b62c168 : 00000000`00000001 fffff880`0f36f36e fffffa80`0b622000 fffff880`0f2d1e3e : 0xfffffa80`0ea37590
fffff880`07b54510 00000000`00000001 : fffff880`0f36f36e fffffa80`0b622000 fffff880`0f2d1e3e fffffa80`0ea37a80 : 0xfffffa80`0b62c168
fffff880`07b54518 fffff880`0f36f36e : fffffa80`0b622000 fffff880`0f2d1e3e fffffa80`0ea37a80 fffffa80`0b622000 : 0x1
fffff880`07b54520 fffffa80`0b622000 : fffff880`0f2d1e3e fffffa80`0ea37a80 fffffa80`0b622000 fffffa80`0b622db0 : nvlddmkm+0x10a36e
fffff880`07b54528 fffff880`0f2d1e3e : fffffa80`0ea37a80 fffffa80`0b622000 fffffa80`0b622db0 00000000`00000001 : 0xfffffa80`0b622000
fffff880`07b54530 fffffa80`0ea37a80 : fffffa80`0b622000 fffffa80`0b622db0 00000000`00000001 00000000`0000000b : nvlddmkm+0x6ce3e
fffff880`07b54538 fffffa80`0b622000 : fffffa80`0b622db0 00000000`00000001 00000000`0000000b fffff880`0f2d1ca8 : 0xfffffa80`0ea37a80
fffff880`07b54540 fffffa80`0b622db0 : 00000000`00000001 00000000`0000000b fffff880`0f2d1ca8 00000000`0000000b : 0xfffffa80`0b622000
fffff880`07b54548 00000000`00000001 : 00000000`0000000b fffff880`0f2d1ca8 00000000`0000000b fffffa80`0b622db0 : 0xfffffa80`0b622db0
fffff880`07b54550 00000000`0000000b : fffff880`0f2d1ca8 00000000`0000000b fffffa80`0b622db0 fffffa80`0b622db0 : 0x1
fffff880`07b54558 fffff880`0f2d1ca8 : 00000000`0000000b fffffa80`0b622db0 fffffa80`0b622db0 fffff880`07b54619 : 0xb
fffff880`07b54560 00000000`0000000b : fffffa80`0b622db0 fffffa80`0b622db0 fffff880`07b54619 fffffa80`00000000 : nvlddmkm+0x6cca8
fffff880`07b54568 fffffa80`0b622db0 : fffffa80`0b622db0 fffff880`07b54619 fffffa80`00000000 fffffa80`00000000 : 0xb
fffff880`07b54570 fffffa80`0b622db0 : fffff880`07b54619 fffffa80`00000000 fffffa80`00000000 fffffa80`0c42e600 : 0xfffffa80`0b622db0
fffff880`07b54578 fffff880`07b54619 : fffffa80`00000000 fffffa80`00000000 fffffa80`0c42e600 fffffa80`0b0cbc58 : 0xfffffa80`0b622db0
fffff880`07b54580 fffffa80`00000000 : fffffa80`00000000 fffffa80`0c42e600 fffffa80`0b0cbc58 00000000`00000000 : 0xfffff880`07b54619
fffff880`07b54588 fffffa80`00000000 : fffffa80`0c42e600 fffffa80`0b0cbc58 00000000`00000000 fffff880`0f372645 : 0xfffffa80`00000000
fffff880`07b54590 fffffa80`0c42e600 : fffffa80`0b0cbc58 00000000`00000000 fffff880`0f372645 fffffa80`0b62ce98 : 0xfffffa80`00000000
fffff880`07b54598 fffffa80`0b0cbc58 : 00000000`00000000 fffff880`0f372645 fffffa80`0b62ce98 fffffa80`0b62ce98 : 0xfffffa80`0c42e600
fffff880`07b545a0 00000000`00000000 : fffff880`0f372645 fffffa80`0b62ce98 fffffa80`0b62ce98 fffffa80`0b622000 : 0xfffffa80`0b0cbc58


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nvlddmkm+1534e0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  543fbaa0

STACK_COMMAND:  .cxr 0xfffff88007b53ae0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_nvlddmkm+1534e0

BUCKET_ID:  X64_0x7E_nvlddmkm+1534e0

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x7e_nvlddmkm+1534e0

FAILURE_ID_HASH:  {4b9f3413-6484-7841-c582-d8e2bd9c7688}

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

2: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f265000 fffff880`0ff41000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu Oct 16 18:01:28 2014 (543FBAA0)
    CheckSum:         00C97F5B
    ImageSize:        00CDC000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

NZCoyote · 22 Nov 2014

Hi Arc,

Thanks for looking at this.

1. Overclocking
Haven't bothered with overclocking for a long time now, everything is set to factory default.

2. Power Supply
PSU is a Silverstone Strider ST1500 - 1500W, would hope this is adequate!

3. System Overheat
Speccy screenshot attached of temps during everyday computing.
Link to Speccy Snapshot http://speccy.piriform.com/results/q...cJ1sTxFHZP87yV
Note the Snapshot is after running the Furmark Stress Test, so the temps are still stabilising.

4. Display Drivers
Uninstalled the version 344.48 Geforce drivers using the Display Driver Uninstaller and installed a clean copy of the 340.52 version.

5. Failing Graphics Card
Ran the Furmark stress test a couple of times for ~20minutes, screen shot from the second run attached. Also a Speccy screenshot while Furmark was running attached.

Regards,
Nigel

Arc · 22 Nov 2014

Everything is too good for a system having multiple bugchecks pointing to display failure.

Anyway, now let us observe how it runs with 340.52 WHQL driver. Let us know for any further BSOD.

NZCoyote · 27 Nov 2014

Morning,

I've just had the same crash again. The computer had been fine for a few days and appeared to be fixed.

Today when loading up a Youtube video, that was embedded in a website, the computer crashed and restarted.

Screenshot of windows action center screen and log/dump files attached.

Cheers,
Nigel

NZCoyote · 28 Nov 2014

Had another crash this morning, this time will trying to open a Jpeg file.

Updated crash/dump files attached.

Regards,
Nigel

Arc · 30 Nov 2014

Display crash continues, even after applying a known stable version of the display driver.

Code:

BugCheck 116, {fffffa800cf054e0, fffff8800f40d93c, ffffffffc00000b5, a}

*** 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+15393c )

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

Apparently we are not finding a ground to blame the graphics card, but we should take some alternative tests. Break the SLI. Apply a single card. See how it goes. It it BSODs, apply the other card and see how it works.

Let us know.

NZCoyote · 24 Dec 2014

Merry Christmas,

I've broken the SLi and the system seemed stable while running under each single card only.

I've left the SLi disabled but re-enabled both graphics cards and more crashes happening over the last day, seemed to be worse while making a Skype call.

Starting to think I should have had new PC hardware on my Christmas wish list!

Regards,
Nigel

Arc · 02 Jan 2015

I think you should stress test both the graphics cards individually, with furmark.