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.

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

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.
 

Sajin

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.

Aero is on, no worries there.
 
I used DDU to once again wipe all the drivers I could find and performed a clean installation. Back up and running again and I hope it will last this time. Fingers crossed.
 

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

How old is your psu?

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

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.  

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.
 

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?