I got this error all the time. Using dual NVIDIA GeForce GTX 770 SLI
DirectX Error DirectX function “GetDeviceRemovedReason” failed with DXGI_ERROR_DEVICE_HUNG. GPU: “NVIDIA GeForce GTX 770”, Driver: 37557 OK
Ok so I was also getting this error. I spent months trying to understand what the problem is. I had triple SLI and it caused me nothing but headaches. I spent more time trying to sort out the problems than I did playing games.
My solution at first was to unplug the power from two of my cards and just play the game on one card. What a difference that made. A whole nights gaming without ANY problems.
I then sold my cards and bought the biggest single card I could afford. I then had the FPS on the monitor and adjusted the graphics settings until I was the 80 - 100 FPS all the time and left it at that.
I know this is not an ideal solution I used to play with 3 x swifts in surround which was awesome but as Nvidia seem to be dropping 3 X SLI the writing has been on the wall for some time :(, but I’m having soooooo much more fun.
I bought a Maxwell Titan X for £400 on gumtree and play on 3440 x 1440 monitor at 100 FPS with settings on Ultra / High with HBAO off. Looks great 
Hope you find your solution !!!
Disabling DX12 fixed it for me. Since my game would not launch, I had to edit the following file to disable DX12:
Documents\Battlefield 1\settings\PROFSAVE_profile
In this file, find the line that says: GstRender.Dx12Enabled 1
Change the 1 to a 0 (zero)
Hope that helps some of you!
I have the same error but putting the game to use single card from 3d options doesn’t work I will try to disable SLI as whole to see if it helps I too have dual 770.
Please help i still getting the same error over and over again
@Eclipse4349 tried doing that but the problem still persists. Really frustrating especially when in multiplayer. If anyone finds a solutions please post it.
here is the screenshot of my error. I did some checking and it seems that a lot of GTX 670,680,770 users are facing the same problem.
one time this happened:
Problem signature:
Problem Event Name: APPCRASH
Application Name: bf1.exe
Application Version: 1.0.9.53998
Application Timestamp: 58077d90
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7601.17932
Fault Module Timestamp: 503285c2
Exception Code: 887a0006
Exception Offset: 000000000000caed
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: dbf0
Additional Information 2: dbf0e7e3eede1751a3bea8a1a43721a6
Additional Information 3: 7b37
Additional Information 4: 7b37a11bec1e3fd5d53a4fa9c774ed48
@D4nyMX @MrcZ_zed026
There is already a topic with over 100 pages of replies, use this one instead. No need to flood the forum with new topics about the same issue.
DirectX Function Error (Nvidia) - Are you actually serious EA? ( 28.03.17 - 21:34 CEST )
Also I will save you some time. This crash is not fixable by end users. You have to wait for Dice to release a patch.
Have had the same problems since day one, today I tried windowed-borderless and have been able to play without interruptions (crashes).
I had the same issue and i havent had a crash in a good long while after i turned on dx12 and turned off origin in game
I still got this problem, running GTX770, ant news on this?
No. Last week a DICE dev posted here that they’re working on it: DirectX Function Error (Nvidia) - Are you actually serious EA? ( 28.03.17 - 21:34 CEST )
don’t know if they’re really working on it. Since a few days no reaction …
Sory buddy. we can only hope
Im pretty sure they will fix it. But it takes sometime, and if they have found a fix, they need to test it, and make sure it doesn’t break other things.
Does everyone still have this problem? just started to encounter the issue and I have a gtx 770. Any news on a fix?
Yep, I just had it happen, using a 770 as well.
Still no fix for it but in the meantime just play the Sinai Desert, Suez, Argonne Forest, Amiens and Fao Fortress maps. They seem to be unaffected.
this keeps happening to me but i have an rx 480
Still same Prob here. Using 2xGTX780Ti
closing this as there is a whole thread for this.
@Kebno - amd released a new driver, others have reported this solves their issue