Liner Pools

Battlefield 1 – DirectX Error “GetDeviceRemovedReason” [Workaround]

At first, because of the phrasing of the error, I thought it might be Hardware, namely my GPU (Graphics Processing Unit, the Videocard); but since that was working fine with literally, all other games – playing in longer gaming sessions even [and I know for sure that I wasn’t actually physically pulling out my videocard while playing …I think] – I omitted that possibility (for now) and focused on a potential Software approach, which meant checking configuration…

Looking at the Settings for the game then, I tried reducing everything down to the Lowest Possible Settings; to reduce the load on the GPU and the load in the processing of the game itself. (With lowered settings, there would be less data being streamed from the game, less being extracted from the compressed/encrypted files of the game, less being calculated and drawn, less everything). If there was a problem with how game data was being handled, this might being it to light [note: an issue with integrity of the files would not be detected this way, this is more of a data handling troubleshooting step; integrity of the game files can usually be checked/verified with a Repair/Verify through the game client or if that doesn’t help, a Reinstall of the game usually assures accurate game files (barring Drive/RAM file handling (Hardware) issues – which is another tangent/issue altogether, heh) – screenshot of where to run a Repair/Verify of the game files for BF1, below].

Example of the Location of where to Repair the game files in the Origin Game Client, showing Battlefield 1 in 2017
(Click to see Full Size)

Nope. Crash. Error [which I lost the clean Screenshot of, of course – but a version of it is in the Header for this posting – I will add a clear Screenshot of the error window to this post when I can capture it again, if it occurs]. Hmmm…. Since it was a DirectX error (and I am 93.33-repeating-percent-sure that I did not “remove the video card” while playing..), I tried one last thing. Instead of swapping out the GPU to try with something else (a GPU from a friend’s PC, for example), which is approaching a Hardware type issue; I tried something else: I changed the DirectX level in the game from DirectX 12 to DirectX11 [this may not have been solely ‘my idea’ – although I am sure I would have eventually arrived at it as a troubleshooting step, I looked up this error and found many, many locations and sources of others stating they have this issue and encountered this error and I may have read it somewhere, for it to have come up – merely mentioning because I just don’t want to take sole credit for something I may not have come up with entirely by myself…].

Example of where to ‘Disable DirectX 12’ and ‘Enable DirectX 11’ in the Video Settings, in Battlefield 1
[Hmm, this is more of a Workaround than a ‘Fix’ for this issue…]
(Click to see Full Size)

Success! I played a good couple of hours this way, with no crashing, closing, freezing, or errors at all – great! After trying it after re-opening the game, rebooting and playing some more, testing it the next day or two after as well, it seemed ‘solidified’; changing the DirectX level/version from 12 to 11 seemed to ‘solve’ the issue [for me, for now].

I think this is more of a ‘Workaround’ than a ‘Fix’, since it doesn’t solve the issue permanently… there is still something in the game engine or how it communicates with DirectX/Windows/theGPU, which is causing something that is not ‘fixed’ by this step; but, since it does work to get past the issue, I thought I would share, to help others that may be running into this seemingly-popular problem (‘popular’ judging from the queries I found about this issue on both the Battlelog forum and EA Support Forums, spanning a few years now..). I hope this works for you, dear reader, as it seems to have done, for me.

[Since this is not a true ‘fix’ (I do not know if this is permanent nor do I know the actual source/nature of the issue, therefore I cannot say this is a ‘fix’, imo); I will post this with the title “workaround”…]

Addendum:

Other helpful tips/steps that can possibly help, if the above step does not work (and some additional information), can be found in multiple places on the Battlefield and EA forums, such as this list by a helpful poster named STEEiL:
https://forums.battlefield.com/en-us/discussion/54605/directx-function-error-amd-getdeviceremovedreason-error-in-battlefield-1

Good Luck – I hope it gets working for you soon – and See You In The Game!