Regular BSODs related to Kernal Crashes

I've had my computer a few months now, and since about a month after installing my SSD (clean install, wiped my old 640gb WD HD before hand) i've gotten random BSOD's

These continued about once every week or so for a while, and always would happen in this order:
Usually something flash related would be open in a browser
Sudden crash of Video driver, and a notification that the kernal crashed and recovered
Continued crashing and recovering until the system BSOD's and reboots

Then everything's fine.

Recently, in the past 2 weeks i've started getting more frequent BSOD's without the previously mentioned set up and kernal crashses. I'm kind of at a loss her. I may end up just wiping and reinstalling again, but i'd like to know what's actually going on and if i can fix it.

These new random BSOD's sometimes happen when playing a game League of Legends, but also just during random browsing. As does the Kernal crash, which happened not 30 minutes ago with no flash pages open and working on a text document!

I'm using Avast! newest version btw, although the windows health report didnt say i was for some reason.

Also superfetch is disabled intentionally for my SSD, but im unsure what device drivers could be uninstalled. Maybe my SSD's drivers?

Basically this is a TDR error with your graphic card. Either you RAM of GPU is defective
Are you overclocking any components?
STOP 0x116: VIDEO_TDR_ERROR troubleshooting
Do Tests:
RAM - Test with Memtest86+
Nvidia Video Card - Test with OCCT
Remove any Avast software

   Information

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
You can use MagicDisc as an alternative.

Code:

sptd.sys        fffff880`01086000    fffff880`011ac000    0x00126000    0x4ad24632    12/10/2009 00:55:14

Code:

aswFsBlk.SYS        fffff880`05e5d000    fffff880`05e66000    0x00009000    0x4d651fc0    23/02/2011 18:54:56                
aswMonFlt.sys        fffff880`05e23000    fffff880`05e5d000    0x0003a000    0x4d651fc8    23/02/2011 18:55:04                
aswRdr.SYS        fffff880`02fe7000    fffff880`02ff1000    0x0000a000    0x4d651fcf    23/02/2011 18:55:11                
aswSnx.SYS        fffff880`02e18000    fffff880`02e98000    0x00080000    0x4d65203b    23/02/2011 18:56:59                
aswSP.SYS        fffff880`04a09000    fffff880`04a54000    0x0004b000    0x4d65203e    23/02/2011 18:57:02                
aswTdi.SYS        fffff880`02f4d000    fffff880`02f5d000    0x00010000    0x4d651ff7    23/02/2011 18:55:51

Thanks for the quick reply Yowanvista, i have to crash as it's 6am but i'll be running those tests on my memory tomorrow morning.

I'll uninstall alcohol 120% and make sure to run the tool as well, but what is wrong with Avast software? I'm not sure what problems that is causing if any..

I did some base overclocks on the GPU originally, but have since reverted them since i was hearing a lot of capacitor whine. I had a feeling these BSOD's might be related but i've been avoiding it since i am going to have to drain/disassemble my entire system now it seems

I dont think it would even be the best idea to run the tests on my GPU as it seems to have enough problems as is too.

but what is wrong with Avast software? I'm not sure what problems that is causing if any..

Avast has been causing a lot of issues recently on Windows 7

I dont think it would even be the best idea to run the tests on my GPU as it seems to have enough problems as is too.

Tests won't do any harm, do have any other PC just to replicate the issues with the GPU?

On the avast side that sucks, i guess i'll move to ESET or something since work gave me a free year of it. Hopefully that isnt having the same issues?

And no, this is my only water cooled system and it's difficult to swap parts when it's within my loop. I filed an RMA with EVGA a few minutes ago and will be shipping it back to them on the 20th when i have the time to disassemble and drain my system. Ugh.

Are there any other discrepancies that were noticeable in my logs that i should pay attention to? And thank you again! I really appreciate the help!

Ataraxey said:

On the avast side that sucks, i guess i'll move to ESET or something since work gave me a free year of it. Hopefully that isnt having the same issues?

ESET is good (for me!!). Never had an issue with it yet in (a total of) six years. Just make sure you have the latest version.

Got the new hardware, keep getting more crashes. Attached the logs, it seems like either an overheating issue because it will start up, be ok, crash and then not want to start up again with any video signal for a bit until it cools down or something.

Maybe the PSU isnt giving enough power?

Ataraxey said:

Got the new hardware, keep getting more crashes. Attached the logs, it seems like either an overheating issue because it will start up, be ok, crash and then not want to start up again with any video signal for a bit until it cools down or something.

Maybe the PSU isnt giving enough power?

Did you test your RAM? Its still the same TDR 0x116 error

Code:

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8009381010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880107c663c, 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+7b763c
fffff880`107c663c 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`0294cb88 fffff880`10cc9ef8 : 00000000`00000116 fffffa80`09381010 fffff880`107c663c ffffffff`c000009a : nt!KeBugCheckEx
fffff880`0294cb90 fffff880`10c9d867 : fffff880`107c663c fffffa80`07e55000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0294cbd0 fffff880`10cc9d07 : 00000000`ffffd87b ffffffff`fffe7960 fffffa80`09381010 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`0294cc80 fffff880`10d98ec1 : fffffa80`0913c010 00000000`00000080 00000000`00000000 fffffa80`07d9c410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`0294cd00 fffff800`033307c6 : 00000000`0379533a fffffa80`07db04d0 fffffa80`055099e0 fffffa80`07db04d0 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`0294cd40 fffff800`0306bc26 : fffff880`03531180 fffffa80`07db04d0 fffff880`0353c1c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0294cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+7b763c
fffff880`107c663c 4883ec28        sub     rsp,28h

SYMBOL_NAME:  nvlddmkm+7b763c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d64bb6c

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

I cant really test the ram now since it keeps crashing, even when i have no HDD plugged in and am just trying to get to the BIOS it crashes. My motherboard has warning LEDs that are supposed to show if there is an issue with specific components and it keeps saying my GPU is having an issue...but this is a brand new one from EVGA.

I'm starting to think it's my Motherboard now. I got another PSU and plugged it in JUST powering the GPU/Motherboard and had my other one powering my pump and fans and the crash still happened, so that rules that out. Brand new GPU from EVGA so it SHOULD be ok even if the mobo's warning light says otherwise.

The DRAM light has never come on, but i'll have my friend bring an extra stick over tomorrow before we disassemble it again and see if that clears things up. And thank you for all the help thus far, i really appreciate it.

But at this point im just frustrated to all hell. christ.

Used my friend's RAM tonight and it seemed to solve everything, but after an hour or so of uptime i got ANOTHER BSOD and crash. Here's the crash dump files again. Is it still the same thing?

If so maybe my GPU or motherboard have more issues...