DirectX Function Error (Nvidia) - Are you actually serious EA? ( 28.03.17 - 21:34 CEST )

[xeimonster]

I’ve managed to fix my game (so far) by doing the following;

Re-installing Windows 7
Re-installing Origin
Re-installing my Microsoft Visual C++ Redistrutables - particually the 2015 redists - however you need all of them.
https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads

Updating Windows 7 to the latest release
Updating nVidia graphics drivers to 378.49

I no longer get the DirectX function crash (well, after one hour of playing that is).

I’ll keep you posted if it crashes again.

[Klootgieter123]

Lol still no fix for BF1? sad… No BF5 for me…

[Contayjen]

I just spent a grand on PC upgrades to play this game and a week in, this is where I end up. The BF1 crash club

[OP_Glitchmobile]

‘‘I just spent a grand on PC upgrades to play this game’’

hu…hue…huehue…HAHHAHAHAHAHAHAAHH

This will get you in a good mood again:

Gramatik - Tearin It Up

[GRABibus]

I experiment in BF1 random crashes with message (See here the EVGA realted post, which is also for BF5) :

https://forums.evga.com/Battlefield-V-DirectX-crasherror-with-any-amount-of-OC-on-GTX-1080-Ti-SC-Black-m2881989.aspx#2927315

I have an overclock on my GTX 1080Ti which is perfectly stable in all my games and all benchmark tests :
COD BO3, COD BO4, Overwatch, Titanfall 2, SWBF, SWBF 2, DOOM, CS GO, Time Spy, HEaven Benchmarks, Superposition.

BUT, for BF1 and BF5, no way. Random crashes with the message DXGI_ERROR_DEVICE_REMOVED (see enclosed EVGA link).
It can occur after minutes of games, or 1 hour…

As soon as I add only 10MHz on my GTX 1080 Ti, those randow crashes occur.

I have tested roughly all I could, except trying stock frequencies…

Are some of you get he same issues and do we know where those crashes could come from ?
Because I can’t believe that adding 10MHz only on GPU frequency makes those 2 games crashw hile, from my side, adding 126MHz on the GPU Frequency is perfectly stale in all games and benchmark tests I listed above.

My card is a Gigabyte GTX 1080 Ti Gaming OC flashed with Bios EVG FTW3 358W => Base clock = 1569MHz for the GPU.

So, 1695MHz base clock (1569MHz + 126MHz) stable in COD BO3, COD BO4, Overwatch, Titanfall 2, SWBF, SWBF 2, DOOM, CS GO, Time Spy, HEaven Benchmarks, Superposition.
So, 1579 MHz base clock (1569MHz + 10MHz) crahes in BF1 and BF5 as explained…

I didn’t test yet at 1569MHz as I want to be sure first there is not a fix somewhere or an explanation.

Thank you.

[EdwinSpangler]

@GRABibus

Random crashes with the message DXGI_ERROR_DEVICE_REMOVED

What PSU do you have? Thats what it was for me after ruling out that to be the cause…

Was using a bronze certified corsair 750 and changed to a seasonic 850 platinum and it fixed that “GPU physically removed from system error”..

[GRABibus]

@EdwinSpangler

@GRABibus

Random crashes with the message DXGI_ERROR_DEVICE_REMOVED

What PSU do you have? Thats what it was for me after ruling out that to be the cause…

Was using a bronze certified corsair 750 and changed to a seasonic 850 platinum and it fixed that “GPU physically removed from system error”..

I have a Cooler Master Silent Pro M2 1000W

[EdwinSpangler]

@GRABibus

@EdwinSpangler

@GRABibus

Random crashes with the message DXGI_ERROR_DEVICE_REMOVED

What PSU do you have? Thats what it was for me after ruling out that to be the cause…

Was using a bronze certified corsair 750 and changed to a seasonic 850 platinum and it fixed that “GPU physically removed from system error”..

I have a Cooler Master Silent Pro M2 1000W

Im wondering if this has anything to do with the bronze/silver/gold/plat rating of the PSUs…?

[TehDatsun]

I get the same video card removed message multiple times a day, sometimes every game, sometimes after a couple of hours. The usual start Task Manager and end process, etc. So frustrating.

But now it’s got even worse, the game has the black background, spinning white wheel thing coming up every 10 seconds or so, can’t customize solider in or out of game, can’t use any of the Options settings as it returns you back to the More menu, etc. The list of bugs is endless. Done everything suggested that you can find on the net bar starting from scratch again. Update drivers, turn off Origin in-game overlay, turn off cloud save, delete BF1 folder, repair game, blah, blah, blah…

Combined with the hacking of some of those well known names that must not be named who I and others have reported multiple times over months now, that is it for me. Played it today for the last time.

And BFV? You have to be joking. After this experience, I wouldn’t go near it.

[Kirister]

@Kramun

This happened with my GTX770, Win7(64b), 16gb, AMD6350 when I played Hardline so stopped playing it when they never fixed it. Never happened once when playing BF4. Now it’s happening in BF1.

Seems the best bet is a card upgrade to a 10 series. Is that a guarantee fix to this? I have tried everything posted here and willing to try that if it does guarantee the crashing stops. Otherwise it’s a refund on the game.

Hardline and BF1 are the only two BF games that I have ever had graphics or sound problems with and I played all PC releases since 1942 came out.

Upgrading to 10 series or even AMD cards does NOT guarantee you a crash free experience.

Here’s an example of a guy crashing on an AMD RX 480: https://www.reddit.com/r/battlefield_one/comments/59skxo/game_crash_error_directx

And there has been plenty of examples of 1060/70/80 crashes if you browse the thread.

@JanneAir
Single monitor and I still get crashes. It’s not related.

[kikazz123]

i found out that turning off your origin overlay seems to fix it for me, right click on the game and go to game properties and un check the box https://gyazo.com/9ed4aebea46158df1321fb2fe7b18ad6

[bali_meister]

DX12 works for me as well. Playing on low now for an average of about 80FPS until they fix it with DX11. For me it’s absolutely playable with DX12 on Low

[DunyunRings]

I found a fix that worked for me, thought i would share.

http://powerglovestudio.com/battlefield-1-game-crash/

Very simple fix and it somehow worked perfectly for me. Played 5 hours last night, rotated thru every map.

Hope it helps someone else.

[Razor2K18]

It’s a new AMD driver out. But they wrote nothing about BF1…

Radeon Software Crimson Edition 16.10.3 Highlights
​Fixed Issues
Fixed an issue for Titanfall 2™ where a limited set of Graphics Core Next products may experience an intermittent game crash.
Known Issues
1.A few game titles may fail to launch, experience performance issues or crash if the third party application “Raptr” has its game overlay enabled. A workaround is to disable the overlay if this is experienced.
2.H.264 content playback may experience playback issues on internet browsers with hardware acceleration when also running gaming applications or content.
3.The Division™ may experience checkered corruption when using character model overlays or the game menu.
4.Some users without the Radeon WattMan feature may experience a Radeon Software popup error regarding Radeon WattMan.
5.FIFA 17™ may experience an application hang or black screen on launch for some select Hybrid Graphics or AMD PowerXpress mobile configurations.
6.H.264 content may experience blocky corruption when streaming using P2P content players on some Radeon RX 400 series graphics products.
Package ContentsThe Radeon Software Crimson Edition 16.10.3 installation package contains the following:
Radeon Software Crimson Edition 16.10.3 Driver Version 16.40.2911.1001

[GoGoGadgetJimbo]

Funny. I’ve been playing without a single problem for 26 hours on my AMD Sapphire 6950. Swapped to my buddies GTX 770 and can’t get it to run longer than 15 minutes now…I guess I’ll just keep using the card released in 2010…

[Kirister]

@JCrushfield

I found a fix that worked for me, thought i would share.

http://powerglovestudio.com/battlefield-1-game-crash/

Very simple fix and it somehow worked perfectly for me. Played 5 hours last night, rotated thru every map.

Hope it helps someone else.

Doesn’t work for me. Created a new session and crashed 10s into St Quentin.

[BatIIeth]

@ Solidhammer
Having multiple versions of that kernal driver nvlddmkm.sys in windows/system32/driverstore/filerepository has been attributed to improper driver updates from nvidia in the past. Something to do with not reading the right file version, and registry keys having the wrong value . Before you try my fix . Go look in that directory, search box. nvlddmkm . then see how many versions of that file exist . Then you decide if you want to clean things up and start with a clean driver install. I have been playing all maps , more than 5 or 6 times now and , all is well . I think those steps are important cause once you get rid of all the older nvidia folders and files, then the registry cleaner should delete all keys and values for them.

@Braddock512
Although I think this is a Nvidia problem, thanks for giving this attention and showing support in efforts to find a simple fix.
I been reporting on Nvidia’s driver bug forums for release 375.63 , and so far no response from them at all .
Rolling back the drivers is one thing I have not tried because BF1 prompts you to update driver in order to continue .
I wanted to use the driver I used for the beta but dont know a work around to that message that pops up when you start BF1.

Moving West…

Testing another fix ATM much simpler . The user.cfg maxvariableframerate idea posted by McClane13

-Go into bf1 directory and create a notpad file . copy and paste this to it

Perfoverlay.drawfps 1
gametime.maxvariablefps 90

-Now save as all files. name it user.cfg

-Nvidia control panel, manage 3D settings , program settings tab , chose bf1.exe from drop down box , if not there add it .
then set maximum pre-rendered frames to 1
I also set Maximum performance , this way the GPU clock speed stays constant.

It’s Practical to think cause we have systems these days that use power saving , and overclocking features all in one package.
In addition to the kernal driver mess . It is possible that BF1 is sensitive to fluctuating clock speeds , It was more stable when I down clocked to stock on my GPU with MSI . but still crashed. Now I got full throttle both in windows power setting, cause my CPU uses speed stepping, and the gpu, cause it will fluctuate with demand, stability seems to help with the clean driver install . So now , Im reverting my Nvidia Services to start. and enabling GFE . Back stepping to see what may cause the crash. but also to see if I can now run the game stable with GFE and all Nvidia features on while using this user.cfg .

[Alabatross]

@GrateFuIlDead

@Braddock512
Although I think this is a Nvidia problem, thanks for giving this attention and showing support in efforts to find a simple fix.
I been reporting on Nvidia’s driver bug forums for release 375.63 , and so far no response from them at all .
Rolling back the drivers is one thing I have not tried because BF1 prompts you to update driver in order to continue .
I wanted to use the driver I used for the beta but dont know a work around to that message that pops up when you start BF1.

Nvidia already said they can reproduce the crash on non-Nvidia cards, ball is in DICE’s court.

[FistyMcBeef]

@GrateFuIlDead

Testing another fix ATM much simpler . The user.cfg maxvariableframerate idea posted by McClane13

-Go into bf1 directory and create a notpad file . copy and paste this to it

Perfoverlay.drawfps 1
gametime.maxvariablefps 90

-Now save as all files. name it user.cfg

-Nvidia control panel, manage 3D settings , program settings tab , chose bf1.exe from drop down box , if not there add it .
then set maximum pre-rendered frames to 1
I also set Maximum performance , this way the GPU clock speed stays constant.

perfoverlay.drawfps 1 only turns on a brief fps monitoring.
changing the maxvariablefps has already been tried (as noted in the main post.)
setting to max performance has already been tried.

[Neo_Bahamut_19]

@Alabatross

@GrateFuIlDead

@Braddock512
Although I think this is a Nvidia problem, thanks for giving this attention and showing support in efforts to find a simple fix.
I been reporting on Nvidia’s driver bug forums for release 375.63 , and so far no response from them at all .
Rolling back the drivers is one thing I have not tried because BF1 prompts you to update driver in order to continue .
I wanted to use the driver I used for the beta but dont know a work around to that message that pops up when you start BF1.

Nvidia already said they can reproduce the crash on non-Nvidia cards, ball is in DICE’s court.

The ball has been in Dice’s court ever since the emergence of the Frostbite 2.0 Engine. These issues have been plaguing every Battlefield game that has used it. Instead of looking at their own code they like to point fingers and blame everyone else. They’ll never own up to it until people file a class action lawsuit against them for selling a faulty product.

I’ve literally tried everything that has ever been suggested to fix this issue for any Frostbite Engine game. The only game that doesn’t have remotely the issues has been Battlefield 4 ever since the “third string” or “life support” team took over patching, which was after all the DLC was released and they shifted everyone over to Battlefield 1 development. Says a lot that those guys are actually capable of fixing issues, says a lot about the incompetence of the initial dev teams.

At first my crashes were every hour or two, maybe 3. Now I can’t play a single ¯_(ツ)/¯ round without crashing, sometimes locking things up so bad I have to hard shutdown. This is literally the only game engine that does this crap too. I have a Steam library of around 200+ games, not a single one has stability issues that I’ve seen. Only my Battlefield collection since Battlefield 3 (Frostbite “2.0”, more like "¯_(ツ)/¯.0") has had these issues with the Device Error. This error has been across multiple GPUs, CPUs, motherboards, RAM, HDDs, SSDs, and OSs.

Every single time they try to pass the buck to Nvidia/AMD, or other driver manufacturers and deny all responsibility. Then, once that “third string” gets involved, they magically start to disappear. I think a lot of it is developer pride and arrogance. They refuse to look into their own product. We won’t get a fix for this for another year or two, and then it’ll just silently stop happening.