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

Comments

  • Kirister
    189 postsMember, Battlefield, Battlefield 1 Member
    edited October 2016
    Kramun wrote: »
    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
    2 postsMember, Battlefield 3, Battlefield 4, Battlefield, Battlefield 1, CTE, BF1IncursionsAlpha Member
    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
    3 postsMember, Battlefield 3, Battlefield 4, Battlefield, Battlefield 1 Member
    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
    10 postsMember, Battlefield 3, Battlefield 4, Battlefield, Battlefield 1 Member
    edited October 2016
    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
    4 postsMember, Battlefield 3, Battlefield 4, Battlefield, Medal of Honor Warfighter, Battlefield 1 Member
    edited October 2016
    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 Contents
    The 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
    7 postsMember, Battlefield 3, Battlefield 4, Battlefield, Battlefield 1 Member
    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
    189 postsMember, Battlefield, Battlefield 1 Member
    edited October 2016
    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
    49 postsMember, Battlefield 3, Battlefield 4, Battlefield Member
    @ 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
    232 postsMember, Battlefield 3, Battlefield 4, Battlefield, Battlefield 1 Member
    @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
    29 postsMember, Battlefield 3, Battlefield 4, Battlefield, Battlefield 1 Member
    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.

  • Kirister
    189 postsMember, Battlefield, Battlefield 1 Member
    edited October 2016
    We are working with DICE to find the root cause. Unfortunately I don't have any further updates at the moment.
    Latest message from nVIDIA (posted <1hour ago).

    https://forums.geforce.com/default/topic/972627/geforce-drivers/battlefield-1-directx-crashes-mostly-gtx770-/post/5006414/#5006414

    @RedRiveRR_
  • Alabatross
    232 postsMember, Battlefield 3, Battlefield 4, Battlefield, Battlefield 1 Member
    edited October 2016
    Kirister wrote: »
    We are working with DICE to find the root cause. Unfortunately I don't have any further updates at the moment.
    Latest message from nVIDIA (posted <1hour ago).

    https://forums.geforce.com/default/topic/972627/geforce-drivers/battlefield-1-directx-crashes-mostly-gtx770-/post/5006414/#5006414

    @RedRiveRR_

    If this bug was in BF3/BF4/HL then hopefully the enormous popularity of BF1 (being called the best BF game of the decade according to many) is acting as a catalyst to actually solve this.


    Meanwhile I can only play my safe 3 (don't know the actual names) to avoid crashing
    - Forest
    - Amiens
    - Desert Castle

    If it's any others all my friends and I back out and I find us all a new one that is one of these. Otherwise ill get the full lock up and wince as I hold down my power button.
  • Kwobiwan
    6 postsMember, Battlefield 3, Battlefield 4, Battlefield, Battlefield 1 Member
    Alabatross wrote: »
    @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.

    Uh ? every Frostbite Engine Game?
    For me i Played BF Bad Company 2 ; BF 3 ; BF 4 ; Star Wars Battlefront; and i never ever had in this Frostbite Games this Dirext X error. So it is at least for me a BF 1 specific Problem.
    God Thanks im Going to vavation for a Week . Hopefully they fix somthing.

    MFG
  • Power69ful
    3 postsMember, Battlefield 3, Battlefield 4, Battlefield, Battlefield 1 Member
    Hi, I played four hours and again appears Dx problem

    directx.jpgsubirimagenes

    I made this and the problem continue:

    1. Disable Dx12
    2. Disable origin overlay
    3. repair the redists

    PC config:

    Windows 7 64 Bits
    Driver: Nvidia 375.63
    Intel Core i7 2600k Stock
    DDR3 8GB G.Skill Ripjaws 1600
    Nvidia GTX 670 V.Ram 2GB Stock
    Motherboard: ASRock Fatal1ty P67 Professional
    Creative Sound Blaster Audigy 2 ZS
    Psu: Cooler Master 850w


  • koweratus
    14 postsMember, Battlefield 3, Battlefield 4, Battlefield Hardline, Battlefield, Battlefield 1, CTE, Battlefield V Member
    Hello,

    The Dev team continues to investigate and work on this issue. Definitely understand how frustrating this is.
    One of our QA guys had the same issue with his GTX770 and tracked it down to an outdated Realtek Audio driver. He updated the driver and swapped Windows Power Settings from Balanced to High Performance and hasn't experienced a crash since.

    Those experiencing this issue, give that a try.
    I've also just drafted an email to the studio team to find the status of their investigation, any possible workarounds, and potential fix date.
    Will keep you posted.

    -Braddock512-

    Already had high power mode and updated driver... :/ cmon I cant even finish a single round
  • Neo_Bahamut_19
    109 postsMember, Battlefield 3, Battlefield 4, Battlefield, Battlefield 1 Member
    edited October 2016
    Kwobiwan wrote: »
    Alabatross wrote: »
    @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.

    Uh ? every Frostbite Engine Game?
    For me i Played BF Bad Company 2 ; BF 3 ; BF 4 ; Star Wars Battlefront; and i never ever had in this Frostbite Games this Dirext X error. So it is at least for me a BF 1 specific Problem.
    God Thanks im Going to vavation for a Week . Hopefully they fix somthing.

    MFG

    Why don't you look through the forums for the other games for similar issues, hrm? Ye ol' "didn't happen to me so it doesn't exist" logic you haz.

    I even plainly stated that I've had those issues, "across multiple GPUs, CPUs, motherboards, RAM, HDDs, SSDs, and OSs" and that "Only my Battlefield collection since Battlefield 3" and that "The ball has been in Dice's court ever since the emergence of the Frostbite 2.0 Engine"

    This issue started cropping up AFTER Bad Company 2, that was still on the Frostbite 1.0 Engine. BF3 was the first on the FB 2.0 E.


    Just a few threads:
    Battlefield 3: http://battlelog.battlefield.com/bf3/en/forum/threadview/2955065210854961836/
    Battlefield 4: https://battlelog.battlefield.com/bf4/forum/threadview/2955065240539392431/
    Hardline: https://talk.turtlerockstudios.com/t/tell-us-the-status-of-dxgi-device-hung-error/50487
    MoH Warfighter: https://battlelog.battlefield.com/mohw/forum/threadview/2832654625395259360/

    Took me a minute to find just 4 examples of other Frostbite 2.0 Engine games that have the Device Hung issue.
  • xX-ALeIaQ-Xx
    377 postsMember, Battlefield 3, Battlefield 4, Battlefield, Battlefield 1, CTE, BF1IncursionsAlpha, Battlefield V Member
    Can someone test this?
    Because after i have set up as i did, this config seems that works fine for me.


    My Rig
    CPU i5 4690k
    GPU gpu 770 (drv 375.63)
    RAM 8gb
    SND Creative SB-z

    Temp in game
    CPU
    Around 60°

    GPU°
    min 55°(all time is stable on it)
    max 68° (but idont see when i got this point)

    °Celsius scale



    In game the options are (with V-SYNC ON i tested also OFF)
    pGwn3yC.png

    as Global 3D settings in Control Panel i have this
    part I
    lAeq0Xt.png
    part II
    1GfSxZo.png

    Game runs smooth and stable, but maybe is just a singularity


    Tell me your feedback.

    I make some hard test this long week.... see you in game.
  • nty35
    8 postsMember, Battlefield 3, Battlefield 4, Battlefield, Battlefield 1 Member
    1976ramzes wrote: »
    I repeat - need to work on it: KernelBase.dll 6.1.7601.18015 (Win7 x64) This is a problem inside the code of the game, on video cards with factory overclocked frequencies (Boost). Game crushes driver. And nothing will not help, except for correction of this library "KernelBase.dll"

    did you try this method?

    http://powerglovestudio.com/battlefield-1-game-crash/
  • Neo_Bahamut_19
    109 postsMember, Battlefield 3, Battlefield 4, Battlefield, Battlefield 1 Member
    edited October 2016
    Can someone test this?

    Game runs smooth and stable, but maybe is just a singularity


    Tell me your feedback.

    I make some hard test this long week.... see you in game.

    That's exactly how my settings are but I'm running a GTX690, so it has multi-GPU rendering. Obviously processor, memory, and so on are different. Running Windows 10 as well.

    Still crashing.

    The fact that solutions are so inconsistent really leads me to believe it's not an issue with things external to the game, but to believe it's something wrong internally with the game, specifically the engine since this has been going on through multitudes of games using this engine.
This discussion has been closed.