[PC] DXGI_ERROR_DEVICE_RESET every 10 or so minutes
Hello, here are my specs:
Intel i7-5820k 6-core CPU @ 4.0 GHz
32 GB DDR4 RAM
GTX 970 4GB GPU
Corsair 750W PSU
Windows 10 Pro
150 MBit XFinity Down/20 Mb Up
When the error occurs, I get a gray screen, followed by both monitors getting signal back with the following error message:
Direct X Error
DXGI_ERROR_DEVICE_RESET ("The device failed due to a badly formed command. This is a run-time issue; the application should destroy and recreate the device.") GPU: "NVIDIA GeForce GTX 970", Driver: 37570
Origin is totally blacked out, and I have to close it with Task Manager because it won't close itself (says that Titanfall 2 is still running, it's trying to close too early.)
This happens no matter what graphics settings I use (even on Low.) It may not occur when playing in windowed, haven't had a chance to check since you guys are getting DDoSed at the moment.
Windows EventViewer has the following thing to say:
Display driver nvlddmkm stopped responding and has successfully recovered.
Here are the steps I've taken to try and solve the problem:
1. Doing a clean install of the latest drivers (currently 375.70.)
2. Down-clocking my GPU.
3. Verifying the Titanfall 2 install.
4. Changing my graphics settings.
5. Disabling my second monitor.
6. Turning off Origin's in-game overlay
7. Trying a different GTX 970 (I have multiple workstations at home.)
8. Trying it on a different PC with similar specs.
None of these resulted in a difference at all. Attached is a copy of my DxDiag.txt.
I believe I have found the solution to this problem (or so it seems so far.)
If you have an NVIDIA card, try opening the NVIDIA control panel and turning on debug mode. (Do this by opening the NVIDIA Control Panel, go to Help -> and check Debug Mode.) This will ignore the manufacturer's overclock settings and use the factory default stock clock. While it seems silly that this would make a difference when EVGA Precision X didn't, somehow it has been working without issue for the past few days. Of course, due to the random nature of this bug, it could easily just be chance that it hasn't crashed or caused any issues thus far.
I am not the only person that this has helped. However, it may not work for you.