Topic: nvlddmkm stopped responding, Windows 10 - page 2. (Read 804 times)
Are you overclocking your cpu by any chance? The only times I was having BSODs with clock watchdog timeouts was when I was trying to push my cpu too much.
Trying 385.41
Its telling me that those drivers are not compatible with the 1080 ti's
Change to 372.70 and see how you get on. Ive found those drivers the most stable.
Changing them now
Change to 372.70 and see how you get on. Ive found those drivers the most stable.
This time I received a blue screen with CLOCK_WATCHDOG_TIMEOUT as the stop code
Changed the drivers to 385.28 and then this happened about 30 mins later
https://ibb.co/geT8tk
another nvlddmkm error that caused a reboot
https://ibb.co/geT8tk
another nvlddmkm error that caused a reboot
5x 1080 ti on Windows 10
What cards are you running?
I'm currently using Windows 10, and after several hours of mining my rig will usually go offline for some nvlddmkm related issue. It will either stops responding, recover and reboot itself, or just freeze up (not 100% sure if its nvlddmkm, event viewer just says it recovered from a BugCheck). I've tried reinstalling the drivers - version 385.69 .. Getting really frustrated as I stay up most of the night seeing if the fix i applied changes anything and then a few hours later it crashes but I wake up several hours after that.. Getting really annoyed, any suggestions would be appreciated.
Jump to: