Titanfall 2 crashing to desktop repeatedly

Hey @ToneUsersRSimps. 

That's an error we were seeing for a while not long ago. NVIDIA put out a driver earlier this year that should have fixed it, but it sounds like it might be coming back up. 

If possible, can you try rolling back to an earlier driver to see if that helps at all? I've also heard from some players who said disabling "Full Screen Optimization" in Windows may also help with this error as well. 

/Kent

I have tried that and it isnt making a difference, I rolled back to the previous version where it wasnt crashing and it is still crashing, tried disabling fullscreen optimisation and running in admin mode, nothing is working. 

😢

@ToneUsersRSimps 

I appreciate you giving that a shot. 

What happens if you start up your PC in a Clean Boot before you launch the game? If there's anything else running at the same time that might be causing this error that might help to get around it. For more details on how to set one up check out the EA Help website. 

Let me know if you're still seeing the same error message afterward. Thanks!

/Kent

Did a clean boot and it still happened, managed to get one attrition game in, then it crashed to desktop on the second one. My GPU is factory overclocked, could this be causing the issue do you think?

@ToneUsersRSimps 

That could be a factor. When you have a chance could you pull up a DxDiag and share it here so we can take a look? For more info on how to pull one up check out the EA Help website. Once you have the text file please attach it to this thread. Thanks!

/Kent

The dx diag is attached. Its most certainly the GPU hanging error but the error message doesnt come up anymore.I reinstalled windows and redownloaded the game, it didnt crash for about 3 days then it started doing it again. 

My GPU is the aorus 2070 super, it comes factory overclocked with quite a high clock rate, I remember this game not  liking msi afterburner and crashing with any oc applied years ago, not sure if that has anything to do with it. 

@ToneUsersRSimps 

Thanks! I appreciate it. 

That particular error was something we were seeing for quite a while on RTX cards, but NVIDIA put out a driver update that should have fixed it earlier this year. I'm wondering if it might have resurfaced on more recent drivers. 

Would it be possible to try rolling back to an earlier version of the NVIDIA drivers to test and see if that makes any difference at all? 

/Kent

@ToneUsersRSimps 

Hmmm, interesting. That's definitely not what I'd expect to help, but I'm glad to hear it's working for you!

/Kent