Random BSOD and Crashes - VFX & Video diting, HD Video Playback, 3D

[Jalisco]

Random BSOD and Crashes - VFX & Video diting, HD Video Playback, 3D

Hello all,
I am looking for some assistance as to what is causing my computer to crash. It doesn't happen insanely often, but the way it crashes makes me think there's a hardware issue going on. I am mostly thinking it's either my CPU or one of my two graphics cards installed, but I'd be more inclined towards the GPU being faulty.

The reason being is that the crashes happen mostly when I'm doing HD video playback or editing video or visual effects. The software I use mostly is The Foundry's Nuke and Autodesk's Maya. I also experience video lag spikes during this, such as poor UI navigation within these software.

However, I have tried stress testing my CPU and graphics cards for hours without any crashes, and even performing fresh installs on the OS(Win7), so I'm not entirely sure which piece of hardware is causing me these crashes and spikes. Any and all help will be greatly appreciated.

Attached is the zip file including the dmp and driver information files as outlined in the forum. If you need any other information about my system, please let me know. Once again, thank you for all your help! Hope to hear from you all soon

 

[SGT Oddball]

Two of the three dumps blame your nVidia driver (the other dump is inconclusive), the first think to try would be going to NVidia's site and getting some different drivers and take it from there.

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa801d52e4e0, fffff8800f937340, ffffffffc000009a, 4}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
[B][COLOR="Red"]Probably caused by : nvlddmkm.sys ( nvlddmkm+921340 )[/COLOR][/B]

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: fffffa801d52e4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f937340, 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+921340
fffff880`0f937340 48ff25f9bfecff  jmp     qword ptr [nvlddmkm+0x7ed340 (fffff880`0f803340)]

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.17298 (debuggers(dbg).141024-1500) amd64fre

STACK_TEXT:  
fffff880`02935b88 fffff880`0fd53134 : 00000000`00000116 fffffa80`1d52e4e0 fffff880`0f937340 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`02935b90 fffff880`0fd26867 : fffff880`0f937340 fffffa80`1523b000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02935bd0 fffff880`0fd52f43 : 00000000`ffffd846 ffffffff`fffe7960 fffffa80`1d52e4e0 fffff880`02d6335a : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`02935c80 fffff880`02d6203d : fffffa80`1883f2d0 00000000`00000080 00000000`00000000 fffffa80`15090010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`02935d00 fffff800`0375c0ca : 00000000`02a89052 fffffa80`14c4ab50 fffffa80`12d839e0 fffffa80`14c4ab50 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`02935d40 fffff800`034b0be6 : fffff880`03331180 fffffa80`14c4ab50 fffff880`0333c1c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02935d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+921340
fffff880`0f937340 48ff25f9bfecff  jmp     qword ptr [nvlddmkm+0x7ed340 (fffff880`0f803340)]

SYMBOL_NAME:  nvlddmkm+921340

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  [B]nvlddmkm.sys[/B]

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_[B]nvlddmkm.sys[/B]

FAILURE_ID_HASH:  {1f9e0448-3238-5868-3678-c8e526bb1edc}

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

 

[Jalisco]

Two of the three dumps blame your nVidia driver (the other dump is inconclusive), the first think to try would be going to NVidia's site and getting some different drivers and take it from there.

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa801d52e4e0, fffff8800f937340, ffffffffc000009a, 4}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
[B][COLOR="Red"]Probably caused by : nvlddmkm.sys ( nvlddmkm+921340 )[/COLOR][/B]

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: fffffa801d52e4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f937340, 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+921340
fffff880`0f937340 48ff25f9bfecff  jmp     qword ptr [nvlddmkm+0x7ed340 (fffff880`0f803340)]

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.17298 (debuggers(dbg).141024-1500) amd64fre

STACK_TEXT:  
fffff880`02935b88 fffff880`0fd53134 : 00000000`00000116 fffffa80`1d52e4e0 fffff880`0f937340 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`02935b90 fffff880`0fd26867 : fffff880`0f937340 fffffa80`1523b000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02935bd0 fffff880`0fd52f43 : 00000000`ffffd846 ffffffff`fffe7960 fffffa80`1d52e4e0 fffff880`02d6335a : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`02935c80 fffff880`02d6203d : fffffa80`1883f2d0 00000000`00000080 00000000`00000000 fffffa80`15090010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`02935d00 fffff800`0375c0ca : 00000000`02a89052 fffffa80`14c4ab50 fffffa80`12d839e0 fffffa80`14c4ab50 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`02935d40 fffff800`034b0be6 : fffff880`03331180 fffffa80`14c4ab50 fffff880`0333c1c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02935d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+921340
fffff880`0f937340 48ff25f9bfecff  jmp     qword ptr [nvlddmkm+0x7ed340 (fffff880`0f803340)]

SYMBOL_NAME:  nvlddmkm+921340

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  [B]nvlddmkm.sys[/B]

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_[B]nvlddmkm.sys[/B]

FAILURE_ID_HASH:  {1f9e0448-3238-5868-3678-c8e526bb1edc}

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

Thank you for your reply SGT Oddball. I've tried upgrading and downgrading the drivers I'm using, and still getting the same BSOD. It's been very confusing because after changing drivers I did some stress tests on the cards to see if it was a heat problem or over stress, as I've read around the web that these may cause BSOD. Initially, the tests were running for a good amount of time and the marks were possitive with no BSOD. I felt like the driver updates had fixed it since there was no crashes during the stress testing, but not much long after this I started getting them again.

Most of my applications running consist in either Photoshop/Premiere/Nuke/Maya/Lightroom + either music(mixcloud/soundcloud) or video(YouTube, Netflix) player on the web browser(chrome).

I attached the new dmp files. I'm still new at reading these files, so I could only absorb certain things from them. After doing some research, it seems that all dump files point to dxgkrnl.sys which DirectX Graphics Kernel, and they all seem to point into my Nvidia drivers. With that said, what other type of testing could I do to discard faulty hardware issues?