Hello there,
 
Today I had a BSoD out of the blue (heh). The BSoD mentioned "nvlddmkm.sys". So I looked it up and found many people having issues dating back to 2009 and sometimes even earlier. Even found some threads on this message board about it. So I set out to try some of the (least extreme) fixes that have been suggested over the years. I did not manage to get the entire error code but if the BSoD happens again I'll be sure to write it down.
 
I uninstalled all Nvidia drivers, then used driver sweeper to clean the remnants and reinstalled the latest Nvidia GPU drivers (375.70, Release date: 10/28/2016). Sadly I got another BSoD shortly after performing the clean installation of the drivers and now I'm getting what appears to be tearing when scrolling up or down or watching moving images.
 
Here is an example of the what I assume to be tearing during a video:

 
Things of note:
The BSoDs happened at seemingly random times but possibly always while a video was playing.
 
The GPU temperature, usage or fan speed did not spike when the BSoDs happened.
 
I also wanted to try: ccm.net/faq/6210-how-to-fix-an-nvlddmkm-sys-error-message
but not only do I not have c:\Nvidia I also do not have (or at least cannot find) the "nvlddmkm.sy" file described in that post.
 
The most recent changes I have made to the PC are getting this GPU in September and disabling the nasty Nvidia telemetry processes described here: majorgeeks.com/news/story/nvidia_adds_telemetry_to_latest_drivers_heres_how_to_disable_it.html
 
That's about all I can think of.
 
Additional info:

• OS: Windows 7 Ultimate
• Mobo: Asus P8Z68-V PRO
• GPU driver: 375.70 - Stock settings, no overclock.
• CPU: i7 2600K @4.2GHz
• PSU: Seasonic X-760
• RAM: 16GB Corsair Vengeance DDR3

DeathAngel74
you could try 375.76 hotfix:
 
or 373.06, it was the last before they added telemetry.

I don't own a high refresh rate monitor though. This is a Dell U2311H (1080p 60Hz).
And I've been using those 375.70 drivers since they were released in October but only today did it all go sideways. All this makes me doubt this is the root of the issue.
 
Nevertheless I suppose it's worth a try.

DeathAngel74
IDK then. I remember reading that one of the recent drivers was causing issues while watching videos/youtube. I may be wrong though. Do you get bsod while gaming? I remember when I build my first pc, it would randomly shutdownrestart/loud sound, followed by bsod while watching movies. It turned out to be the crappy Thermaltake TR-2 600W PSU I bought from BBY that was the problem. Any other time its been drivers and/or unstable overclock. Is your CPU overclocked?

Haven't spent much time playing video games today but the BSoDs have happened during normal usage. Just browsing the internet really.
The CPU has a stable overclock of 4.2GHz (used to be 4.5GHz but I eventually lowered it to 4.2GHz for lower voltage requirements).

DeathAngel74
Has anything changed in the last day or two? There has to be a reason, especially if all was stable yesterday.

Not to my knowledge. I mentioned the most recent changes in the original post.
The only other thing that has updated or changed is that Adobe Flash updated I think.

DeathAngel74
I'm using chrome, maybe its a browser issue?

Possibly? I'm seeing it on Firefox. Just tried a chrome based browser and internet explorer and they don't seem to suffer from the scrolling tearing at least. That or I'm just not able to see it.
Not sure what the cause could be though, Firefox' most recent update was October 20, 2016.
 

d0zer44
please keep this thread updated since i got 2 days ago the same crash cause of nvlddmkm.sys.
monday will my replacement 1070 ftw arrive and i will know if its the card or drivers

Make sure you have no overclocking of any components when testing the new card.

DrPhD
I guess I'll try deleting all the drivers again and reinstalling again?

#1 Run your cpu at stock clocks.
#2 Try running the card in debug mode.
#3 Make sure windows aero is enabled. Disabling aero can cause tearing in videos/images. 
#4 Report the bug check code (aka stop code) for the BSOD if it happens again.
 

UPDATE:
 
Alas, bad news. I thought the problem was fixed but I just had another BSoD. On the bright side, I managed to get the BSoD info this time using Bluescreenview.
 
==================================================
Dump File         : 111516-15459-01.dmp
Crash Time        : 15/11/2016 03:22:57
Bug Check String  :
Bug Check Code    : 0x00000116
Parameter 1       : fffffa80`169ba4e0
Parameter 2       : fffff880`0f95e0a8
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`0000000d
Caused By Driver  : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5d1f0
File Description  : DirectX Graphics Kernel
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.23418 (win7sp1_ldr.160408-2045)
Processor         : x64
Crash Address     : ntoskrnl.exe+70400
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\111516-15459-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 702,891
Dump File Time    : 15/11/2016 03:25:00
==================================================

Sajin
How old is your psu?

Same age as the rest of the PC other than the GPU and the CPU cooler. Built it in 2011 so 5-6 years old now.
It's a "Seasonic SS-760KM Active PFC F3" also known as the X760.
http://www.jonnyguru.com/modules.php?name=NDReviews&op=Story&reid=235

Sajin
5-6 year old psu? Time to get a new psu. Card could be blue screening because the card isn't getting enough power. Best advice I can give you would be to to test your card in another computer, try a different set of pci-e power cables (the ones you're currently using may be faulty), check your psu voltages to make sure they're within spec.
 
PSU Testing: http://www.jonnyguru.com/...;ndfaq_id=28 (You will need a Digital Multimeter for testing your PSU. You want all three rails to be within ATX spec, ATX Specification: 12V: 11.40 to 12.60,  5V: 4.75 to 5.25,  3V: 3.135 to 3.465. If any of your rails hit the minimum spec I would replace the PSU with a new one.)   

HOW TO: Properly load your system when checking PSU voltages.    
#1 Download & Install Prime95   
#2 Download & Install Unigine Heaven 4.0.   
#3 Open both Prime95 & Heaven 4.0 Run Small FFT test for Prime95. Run Heaven 4.0 @ max settings. Run both of these tests at the same time while checking voltages.
 
NOTE: Always check your hardware with your motherboards BIOS set to default settings.  

Is there any indication you're getting that this is due to the GPU not being able to draw enough power? And if so, what is it?
I ask because I've never had any issues with power. (I used to run a a Radeon HD6970 x2 in CrossfireX and my CPU used to run at 4.5GHz.)


I checked the Cooler Master PSU power draw calculator (http://www.coolermaster.com/power-supply-calculator/) and the result was:

• Load Wattage: 470 W
• Recommended PSU Wattage: 520 W

I don't have another PC I can test the card on and I also don't have a multimeter and the only way I could get my hands on one is to buy it so let's just say I'm currently not extremely inclined to go that route.
 
As an added note: I have not had any crashes during demanding tasks like video games. I've played through all of Titanfall 2 at 140fps without any issues and all my crashes so far have happened while browsing the internet/watching videos.
 

Sajin
BSOD 0x116 causes:

#1 Bad video driver or corrupt video driver.
#2 Defective video card.
#3 Insufficient power to gpu or defective psu.
 
Since you have no problems in games maybe your problem is related to the power management mode inside the nvidia control panel. Under manage 3d settings inside the nvidia control panel change power management mode (global settings) from optimal to adaptive. Reboot pc & retest the system for the blue screen. Did you set your cpu back to stock clocks like I suggested in post #13?

What does the adaptive setting do? Or rather what is the difference between optimal and adaptive? I thought optimal was the most economical...
And no I have not touched my CPU clock or any other setting.

Look this Thread for same issues -> https://forums.geforce.com/default/topic/955527/geforce-drivers/windows-10-build-1607-randomly-black-screens-nvlddmkm-/
It seems, its something with anniversary update in windows 10

Your bios should allow you to save the current settings to a profile so you won't have to manually change all the settings back later.
 
My suggestions at this time would be to...
 
#1 Reset cpu to default clock speeds.
#2 Change nvidia control panel global power management mode to adaptive. Reboot PC.
#3 Retest the system for awhile to make sure bsod is fixed.

I think I can now say I have definitively ruled out the RAM as a potential cause.
First I ran Windows Memory Diagnostic and received 0 errors.
Then I ran a full MemTest86 test, you can see the results of it below.
 
So now that the RAM is off the list of possible problems (and have sadly sacrificed a big chunk of productivity because these tests take a very long time) I think I can move onto the next possibility.
 
Because removing the CPU overclock and then just hoping for the best cannot give me any immediate or definite results I'm thinking about performing a CPU stress test as well. Maybe that way I can definitely confirm the OC is the actual problem or not. What do you think?
 
 
 
 

Sajin
Running a stress test on the cpu is a good idea, however, I would recommend testing the computer under the conditions that caused the bsod in the first place, but this time without the overclock applied.

That's kind of the problem. I have no idea what caused the BSoDs in the first place. Even with the BlueScreenView info nobody seems to be able to pinpoint the source of the issue so far.I also changed the Power Management settings to Adaptive and received the new Nvidia drivers today so who knows if that will affect anything.
 
I need to be able to definitively find out if something is not working right so my line of thought is that if there is truly something wrong with the CPU OC then a stress test should cause that issue to reveal itself. What do people use for CPU OC stability testing these days? Do people still use Prime95 for that? AIDA64? Geekbench? Realbench? x264?
I think I'll run x264 overnight and see if it holds up.