Forum Discussion

Re: Battlefield 1 DirectX Memory Error

Problem still exists. People have basically tried everything possible on their end. To no avail. This is a list of things that have been tried already:

- Repaired BF1.
- Deleted, re-downloaded and reinstalled BF1 completely.
- Deleted settings (BF1 Folder in Documents).
- Updated Windows 10
- Ran the game as Admin.
- Installed newest drivers (375.63).
- Tested previous drivers (375.57).
- Tested previous drivers (373.03).
- Tested previous drivers (372.90).
- Cleaned drivers before each new install (Display Driver Uninstaller Safe Mode).
- Disabled DX12.
- Toggled GPU Memory Restriction ON/OFF.
- Tried lowest settings.
- Switched from Fullscreen to Borderless.
- Greatly underclocked GPU Core (-105Mhz) / Mem (-628Mhz).
- Overvolted (+12.5mV), raised max power and temp target of GPU.
- Reinstalled VC Redist.
- Checked GPU temp (65°C full load ingame, so not really hot).
- Stress tested my GPU using Furmark: no issue.
- Set gametime.maxvariablefps 60 (and 61, 80, etc...)
- No MSI Afterburner or any similar program running in the background.
- Very clean Windows 10 install with minimal programs running in the background.
- Disabled Origin in-game.
- Uninstalled Geforce Experience.
- nVIDIA control panel: Power management mode – prefer maximum performance
- nVIDIA control panel: Threaded optimization – off
- nVIDIA control panel: Triple buffering – off
- nVIDIA control panel: Vertical sync – off
- nVIDIA control panel: Maximum pre rendered frames – 3
- Removed my GPU physically for 30s and cleaned the dust.
- Updated motherboard bios, drivers and reset bios settings.
- Disabled Intel SpeedStep/EIST in BIOS.
- Turned off DVR in Windows 10's XBox App.
- Disabled Memory XMP profile in Bios.
- Did a MemTest, found no error.
- Applied the Regedit Fix

So far, hundreds of people came into the thread to inform they also have this problem. People with all kinds of rigs, operating systems and graphics cards. 600 series, 700 series, 900 series, even brand new cards like 1080s. And it's not even just Nvidia cards, there are people with AMD cards as well (which makes some of us doubt that it's the Nvidia driver's fault). And as usual people who find their way into the forum and actually reply are just the tip of the iceberg. So I guess it's safe to assume that literally thousands over thousands of your customers encounter this error. We tried everything, even things no user should ever do to an otherwise stable system (e.g. tampering with BIOS settings, clockings, voltages and the registry - personally, I'm not willing to do any of that), just to get BF1 to run stable. Nothing could solve it. We're really at the end of our wits and possibilities here.

Yesterday, I didn't even simply get the usual application crash and error message that would just require me to forcefully end the processes in the task manager and restart Origin and the game, it would even hard crash heavily, giving me a black screen for several seconds until throwing me back to the boot sequence. This cannot be healthy for the PC. I'm actually worried to play your game! Please investigate and try to fix it. We can't. No one has a clue what is going on or causing this. It might happen after 3 seconds or 3 hours. It's completely random from what we know.

And please communicate this to your customers wherever you can. And if playing the game possibly damages our PCs, then please warn us about it! Also inform your customers to not tinker about their BIOS, clockings, voltages or registry. There are lots of people out there that might try this in hopes of a solution, but have no clue what they're doing, because they're so eager to play the game properly.

1 Reply

  • Anonymous's avatar
    Anonymous
    9 years ago

    Hi, I'm having the exact same problem with a gtx 770. The game runs perfectly but randomly the game crash for the 'getDevice removed reason' error. Everything is up to date, but nothing solved this.

About Battlefield Franchise Discussion

Discuss the Battlefield games in this community forum.133,371 PostsLatest Activity: 2 years ago