If you're running an Nvidia card and drivers past 350.12(And even this version, albeit less so) and are suffering from the "Displayer Driver has stopped responding and recovered..." error, you're not alone.
In fact, it's a massively widespread issue among many nvidia users.
https://forums.geforce.com/default/t...dmkm-stopped-/
Figuring out what's causing it is a very painful and drawn out process, and your mileage will vary in any kind of attempt to fix it.
In my case, I was having HD audio device conflicts and had to disable the HD audio drivers for nvidia entirely. I only ended up on that particular solution after hours of benchmarking, burn testing, fiddling with overclocks, and even going through the hassle of trying to sort out WMI errors.
Seriously. It's a major issue for nvidia and has been for a while, due to the really poor quality of their drivers as of late.
The best place to start in dealing with that particular error is to get Display Driver Uninstaller from
https://forums.geforce.com/default/t...d-07-10-2015-/
Use it after booting into safemode. Restart, and then install driver version 347.88 with a clean install, selecting only the Driver and PhysX. Nothing else. Make sure to go into the nvidia control panel and set your power management mode to "Prefer Maximum."
If that resolves your issue, you're good to go.
If it doesn't, then you've got a long, long journey of sorting out what's causing it. Could be anything from bad DRAM, PCI-E bus going out, or even a file corruption in windows.
Despite that issue, though, I still get the DX11 crashes on loads, though. That generally appears to be entirely unrelated to hardware, and something client-side. It's definitely not my video card if 4 hours of Furmark and Heaven/Valley are stable at a core clock boosted to 1400mhz.
Running an MSI GTX 970 Gaming 100me.