Windows 7, BSOD's, Stuttering, Black Screen, main devil culprit "Nvlddmkm"

ok this has been going for for FAR TOO long this is the final FUC*** moment

what i have found out/tried so far in my 2 years of observing/trying to solve this issue:

reseating the RAM results in 2-4 weeks of BSOD-Error free experience, but after that the "Nvlddmkm" BSOD/Freezing/Black screen RETURNS

purchased a new graphics card, this resulted in 2-3 MONTHS of BSOD-Error free experience but after that yes "Nvlddmkm" BSOD's etc RETURNED!

new ram also did NOT Help and i have run a memory test

system restored

old/new nvidia drivers with DDU

msconfig unchecked all startup items

tried safemode and it does not bsod

ran harddisk check

mbam full scan hasn't found anything and haven't been infected in years

Current Problems:

BSoD's (culprit being blamed on "nvlddmkm.sys"

Black Screen (This can sometimes happen instead of the BSoD) and might appear at startup too (not always)

Gaming / Audio STUTTERING /

SPECS:

nvidia gtx 960 / i7 950

windows 7 / 8gb ram

motherboard : GA-X58A-UD3R

MINOR PROBLEMS:

For some reason .DMP are NOT being produced!

HOWEVER they are available at C:\Windows\LiveKernelReports\WATCHDOG (which is what iv'e uploaded/attached)

either way i have now installed "kb2716542" which will hopefully fix the no dump issue from now

Edited by Pokoyo, 06 September 2016 - 11:17 AM.

Attached Sysnativefilecolletionapp logs

The WD dumps are usually reports that are going to Microsoft.

Most often I find that they are related to video errors.

In this case (as in most cases) they are reports of STOP 0x117 errors.

These errors are actually BSOD errors without the Blue Screen.

They are associated with the message (from the system tray) that the Display Driver has stopped responding and has recovered.

If it hadn't of recovered, you would have had a BSOD and the error would have been a STOP 0x116

Please follow these troubleshooting suggestions:  http://www.sysnative.com/forums/bsod-kernel-dump-analysis-debugging-information/35-video-tdr-timeout-0x116-0x117.html#post29532
Also, please monitor your temps with this free utility: 

SpeedFan v. 4.5.1 and later (free from here:  http://www.almico.com/sfdownload.php ) can log temperatures in a CSV file:

To make it work you have to do BOTH of the below:

1. Enable logging in general: Configure...Log...check "Enabled" then click on OK to save.

2. Enable logging for specific checks: Configure...Temperatures..left click on each sensor, then click on "Logged" at the bottom of the Window (for our purposes we want them all) then once you've selected "Logged" for all sensors, then click on OK to save.

The log will be located at C:\Program Files (x86)\SpeedFan

Naming: log files are named SFLogYYYYMMDD.csv, where YYYY is the year (four digits), MM is the month (2 digits, zero padded) and DD is the day (2 digits, zero padded). If a file already exists by that name, the file that already exists is renamed according to the following naming scheme: SFLogYYYYMMDD-CCCC.csv, where CCCC is a increasing number. The new file is then created with the standard file name scheme.

Notes: whenever you change the options related with logging, SpeedFan starts a new log file.

NOTE:You may want to turn logging off when we're done - as I don't know it's impact on performance or on the system.

More to follow, but I may get interrupted.

We just had a granddaughter and I'm waiting for my wife to pick me up to go to the hospital!!!

Analysis:

The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Tue Sep  6 08:20:59.233 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\WD-20160906-1320.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.23418.amd64fre.win7sp1_ldr.160408-2045
System Uptime:0 days 0:48:29.185
*** 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+14968c )
BugCheck 117, {fffffa8008df2010, fffff880057e768c, 0, 0}
BugCheck Info: VIDEO_TDR_TIMEOUT_DETECTED (117)
Arguments:
Arg1: fffffa8008df2010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880057e768c, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.
BUGCHECK_STR:  0x117
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: X64_0x117_IMAGE_nvlddmkm.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Sep  4 15:42:07.505 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\WD-20160904-2042.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.23418.amd64fre.win7sp1_ldr.160408-2045
System Uptime:0 days 2:54:13.474
*** 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+14968c )
BugCheck 117, {fffffa800b2a4010, fffff8800663d68c, 0, 0}
BugCheck Info: VIDEO_TDR_TIMEOUT_DETECTED (117)
Arguments:
Arg1: fffffa800b2a4010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800663d68c, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.
BUGCHECK_STR:  0x117
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: X64_0x117_IMAGE_nvlddmkm.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Sep  4 11:57:03.839 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\WD-20160904-1657.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.23418.amd64fre.win7sp1_ldr.160408-2045
System Uptime:0 days 0:00:29.807
*** 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+144684 )
BugCheck 117, {fffffa800b6664e0, fffff8800f1df684, 0, 0}
BugCheck Info: VIDEO_TDR_TIMEOUT_DETECTED (117)
Arguments:
Arg1: fffffa800b6664e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f1df684, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.
BUGCHECK_STR:  0x117
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: X64_0x117_IMAGE_nvlddmkm.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
The rest of the memory dump summaries are hidden in the Spoiler tag below.  Click on "Show" to reveal them.

The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Tue Sep  6 08:20:59.233 2016 (UTC - 4:00)**************************
hardlock.sys       Mon Feb  2 10:34:08 2009 (49871270)
intelppm.sys       Mon Jul 13 19:19:25 2009 (4A5BC0FD)
VClone.sys         Sun Aug  9 17:25:45 2009 (4A7F3ED9)
nusb3hub.sys       Fri Nov 20 05:15:57 2009 (4B066C5D)
nusb3xhc.sys       Fri Nov 20 05:16:01 2009 (4B066C61)
ElbyCDIO.sys       Thu Dec 17 17:25:16 2009 (4B2AAFCC)
Rt64win7.sys       Thu Mar  4 08:42:52 2010 (4B8FB8DC)
amdxata.sys        Fri Mar 19 12:18:18 2010 (4BA3A3CA)
aksdf.sys          Wed Jul 21 11:59:49 2010 (4C471975)
aksfridge.sys      Fri Sep 24 07:27:55 2010 (4C9C8B3B)
mvxxmm.sys         Thu Jun 16 05:54:34 2011 (4DF9D2DA)
mvs91xx.sys        Thu Jun 16 05:54:52 2011 (4DF9D2EC)
npf.sys            Thu Feb 28 20:31:24 2013 (513004EC)
LGSUsbFilt.Sys     Thu May 30 11:15:44 2013 (51A76D20)
LGSHidFilt.Sys     Thu May 30 11:16:33 2013 (51A76D51)
tap0901.sys        Wed Nov  5 08:16:32 2014 (545A2330)
LGJoyXlCore.sys    Fri Apr 24 17:20:57 2015 (553AB3B9)
LGBusEnum.sys      Fri Apr 24 17:21:00 2015 (553AB3BC)
lgcoretemp.sys     Tue Jun  9 12:52:10 2015 (557719BA)
RTKVHD64.sys       Thu Jun 18 06:45:05 2015 (5582A131)
nvlddmkm.sys       Wed Jul 22 20:15:54 2015 (55B0323A)
mbam.sys           Tue Aug 11 13:35:19 2015 (55CA3257)
idmwfp.sys         Wed Jan 27 11:45:02 2016 (56A8F40E)
SbieDrv.sys        Fri Feb 26 13:18:55 2016 (56D0970F)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Sep  4 15:42:07.505 2016 (UTC - 4:00)**************************
ezplay.sys         Mon Apr 30 06:08:55 2007 (4635C037)
Rt64win7.sys       Fri Jan 21 02:34:00 2011 (4D3936E8)
jraid.sys          Thu May 19 03:55:18 2011 (4DD4CCE6)
nvhda64v.sys       Thu Apr 16 15:03:16 2015 (55300774)
LGVirHid.sys       Fri Apr 24 17:20:53 2015 (553AB3B5)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Sep  4 11:57:03.839 2016 (UTC - 4:00)**************************
nvlddmkm.sys       Mon Feb  8 23:52:55 2016 (56B970A7)

Edited by usasma, 07 September 2016 - 01:34 PM.

After the most thorough and aggressive dust clean I have ever done, I am no longer getting any errors/problems

However I will report here if there are any new issues relating to the same BSoD. Thanks for the reply/useful info either way.

Edited by Pokoyo, 08 September 2016 - 04:35 PM.