test content
What is the Arc Client?
Install Arc

Fatal Error: Direct3D driver returned error code (E_INV

This error has occurred after the latest update in Window 10
Asks to verify install files and does so.
The receive the following error code after hitting "ENGAGE"
Fatal Error: Direct3D driver returned error code (E_INVALIDARG) while creating D3D device.-d3d9

I have un-checked safe mode and added "-d3d9" to the command line within launcher.
I have also attempted to run in compatibility mode as windows 7.
These actions have made no difference.

Comments

  • starstream#1503 starstream Member Posts: 3 Arc User
    Is no one else experiencing this? I thought there would be loads after the latest Windows update
  • raddicalrabbitraddicalrabbit Member Posts: 2 Arc User
    I am also experiencing this issue. Any work around?

    I've tried same steps you have, as well as a complete fresh install of the game and nothing has worked yet.
  • sotsogmsotsogm Member Posts: 67 Arc User
    Having the same problem. It's bumming me out terribly--would love to get some playing in through the holidays. I've tried making sure I have everything updated, no luck.
  • kaithan1975kaithan1975 Member Posts: 947 Arc User
    edited December 2017
    Try uninstalling the latest Win10 update (rollback). The command d3d9 will do nothing.
    Post edited by kaithan1975 on
  • sotsogmsotsogm Member Posts: 67 Arc User
    edited December 2017
    Try uninstalling the latest Win10 update (rollback). The command d3d9 will do nothing.

    Regrettably, rolling back the Win10 update worked--soooo... my other stability issues are back, but I can play STO again. :/

    Thank you for the solution, though.
  • langat#7511 langat Member Posts: 3 Arc User
    Any other solutions? for me it seems that it was not cause of win update. though same error
  • kaithan1975kaithan1975 Member Posts: 947 Arc User
    edited December 2017
    There's a couple solutions floating around, although I can't seem to find them atm. You could try rolling your video card driver back to a older version. You can also try renaming the dx9 dll to like olddx9 to force dx11 load or change the game resolution to a lower setting. I would try the resolution change first then driver rollback.
    Post edited by kaithan1975 on
  • langat#7511 langat Member Posts: 3 Arc User
    Sorry, for silly questions, but how can i change resolution for STO or where do i find dx9 dll file?
    thanks a lot in advance!
  • jordan3550jordan3550 Member Posts: 328 Arc User
    ill give a roll back a try, ive been getting this error aswell
  • raddicalrabbitraddicalrabbit Member Posts: 2 Arc User
    Haven't tried the rollback yet - but may have to as no other fixes I've found have worked.

    I've currently logged a ticket with Support and they are currently looking into the matter as well. Not sure how long that'll take them though, so may have to rollback Win 10 :/ not an ideal solution.
  • jordan3550jordan3550 Member Posts: 328 Arc User
    not done the roll back yet, im hoping this weeks maintance will have a fix for it
  • jordan3550jordan3550 Member Posts: 328 Arc User
    tried roll back but hat didnt complete and the crashes are happening more frequent now i can log in move around for a few seconds then i get a black screen follower with the same error code and crypic crash reporting
  • malic232malic232 Member Posts: 12 Arc User
    I'm having the same issue. I just re downloaded the game this morning was hopping to return to the game but doesn't look like it's going to happen. also noted the rollback didn't work for me..
  • langat#7511 langat Member Posts: 3 Arc User
    Guys, i've found solution, encountering other problem with one more game - it was "lack of operational memory" problem. Soultion is to go to windows -> paramters -> games -> game menu and turn off 'capture games while playing' and both checkmarks below it as apparently it was using tonne of operational memory during loading for some weird reason after the win patch.
  • starstream#1503 starstream Member Posts: 3 Arc User
    I eventually resolved the issue with a completely clean install of windows 10
Sign In or Register to comment.