DPC WATCHDOG VIOLATION

[yure]

· OS - Windows 10, 8.1, 8, 7, Vista ? w10
· x86 (32-bit) or x64 ? x64
· What was original installed OS on system? w10
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? full retail
· Age of system (hardware) 1 year / CPU < 3 months / gpu < 4 months
· Age of OS installation - have you re-installed the OS? 1 year - nope


· CPU - intel i7 4790k/ not oced
· Video Card - evga gtx 1070 sc
· MotherBoard - (if NOT a laptop) msi z97 gaming 7
· Power Supply - brand & wattage 650w gold evga g1


· System Manufacturer /na
· Laptop or Desktop? desktop


no perflog as it was stuck on collecting data for 60 seconds for about 5 mins
most if not all of my bsods started happening after the anniversary update, but this is the recently one
whocrashed me says it was nvlddmkm.sys nvidia driver along with ntoskrnl.exe so memory or just buggy nvidia driver ? lol
note: i was able to recreate the bsod

 

[yure]

i was able to recreate once more the bsod , i think its indeed the nvidia drivers anything above 372.XX made some games to crash into a bsod ( tried from 372.54 - 373.06 (372.90 was by far the worst of them all, i do know 375.63/375.70 are out but after a quick peek in to geforce community forums a lot of errors still persist or its even gotten worst than the previous drivers lol ) , 369.09 was the driver that the pc updated itself after the au update ( that's when the funkyness started , didn't know microsoft provided drivers like that since its not listed on the nvidia site ), i went back to 368.81 and so far no bsod's in a multitude of different games. maybe it has something to do with the pascal cards 1000 series and the au update ? any older game that uses directx 9 just dies/crashes with any of the 372.xx drivers