Re: 0x887A0006 - DXGI_ERROR_Device_Hung

This does not work for me. The game crashes as soon as a match starts. 

 +1 to this issue.  The accepted solution is hot garbage, is anyone actually looking in to fixing this?

same issue, the game runs perfectly fine and then just crashes out of nowhere, DXGI_ERROR_RESET and Engine Error constantly showing up.

seems like playing windowed mode gets rid of the crashes but then you get the fps drops that come with windowed mode...

nothing in this thread has worked at all 

Win10

GTX 970

i5-6500

8GB ram

Logitech G600 mouse

update on this, I downclocked my gpu by 50mhz, no crashes at all now. Somewhat strange but the game still runs perfectly fine.

@Toxinia

That is good to know.

Which card do you have - was it factory OC'd? Did you do any additional OC'ing to it yourself?

Hey All.. I think Toxinia may have nailed it. I have an eVGA GTX 970 - FTW Edition, which means they're factory "OC'd" = (Overclocked).. I was routinely having either the Device_Hung or Device_Reset issue, but almost always by my 4-6th game.

Using eVGA Precision XOC software (free) to manage the "clock" speeds, I under-clocked my graphics card .. I brought the GPU "base" clock to its factory specs per nVidia: 1050 MHZ for GPU clock offset (-166 MHZ, down from "0", which is actually 1216 MHZ due to factory OC), leaving all other settings in the Precision software untouched, and applied those settings.  I did not change any other Origin, or TitanFall 2 in-game graphics settings (and my framerate is still hovering @ 60 FPS), and have played maybe 20 games now without the game crashing (at all) either due to the Device_Hung or Device_Reset errors. No other changes were made to my system, so process-of-elimination stands firm with the clock speeds being a potential issue.

Not sure if this will need fixing on nVidia's side or Respawn's, but it seems that any clock speeds above factory (original) nVidia GPU-specs for the card might be the issue. 

Thanks Toxinia!

@HeyRobFL Hi, that's certainly interesting. I was under the impression that factory overclocks are generally very stable, but this might be a new thing to keep an eye on. 

Thanks for the post. 

Hey @EA_David,

   Yes, I have always known them to be as well.. Unfortunately, I (highly) doubt it's the "stability" of the card as much as it is the software (driver, game engine, Origin software)'s interaction with the hardware. That error isn't the result of a video card failing (no video driver "crash", it's not over-heating, there's never any signs of in-game artifacts, and all other applications and games interact with the factory overclock correctly). 

The problem is almost definitely software related. 

@EA_David I tried underclocking the GPU by the maximum of -90MHz and the memory frequency by the maximum of -201MHz (Neither EVGA Precision nor MSI Afterburner let me go lower), but it didn't fix it.

Hey @cheaterll,

    Sorry the fix didn't work for you.. =( Did you by any chance, while using eVGA's Precision software, try manually typing -178 MHZ ? I had to do that to get mine to underclock that much.. I left the memory speed alone, because it wasn't overclocked by the factory. The MSI 980 Ti (I'm assuming you have the Gaming Edition) appears to have a base GPU overclock of 178 MHZ over nVidia's reference 980 Ti. 

@HeyRobFL Reverts back to -90.

@EA_David I have an EVGA GTX 970 SSC, it comes with a factory overclock, maybe that's related to the issue? I don't do any extra overclocking to it. I used MSI Afterburner to downclock it.

To set your GPU to the default factory speeds (undoes any factory overclock,)

Open up NVIDIA control panel

Go to Help -> Debug Mode

check that box. You may or may not have to do this every time you boot your PC.

It solved my crash, which was similar.

A few more steps to try here: https://forums.titanfall.com/en-us/discussion/5166/titanfall-2-troubleshooting-faq#latest