Also I have been having BSODs with windows 10 on each build, i get the DPC_WATCHDOG_VIOLATION everytime. The output of my debugger shows this:
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\SymCache*
http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*
http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 10240 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10240.16393.amd64fre.th1_st1.150717-1719
Machine Name:
Kernel base = 0xfffff802`68a8e000 PsLoadedModuleList = 0xfffff802`68db3030
Debug session time: Fri Jul 31 12:34:23.193 2015 (UTC - 4:00)
System Uptime: 2 days 20:07:10.812
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
No .natvis files found at C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {0, 501, 500, 0}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )
Followup: MachineOwner
---------
*** Memory manager detected 48 instance(s) of page corruption, target is likely to have memory corruption.
I just made ANOTHER post in nvidia forums about this, and submitted another response to their feedback thread as well. All their windows 10 drivers to date have had botched memory management, and until they get it right I really don't think using different drivers will help.