Page MenuHomeFeedback Tracker

Cannot create DX11 device: E_INVALIDARG
New, NormalPublic

Description

I used to play the game and it was fine.
But recently the game began to give an error :
''Cannot create DX11 device:

Adapter (NVIDIA GeForce GT 630M) Fullscreen
Resolution 1366x768, format R8G8B8A8_UNORM. refresh 60 Hz
E_INVALIDARG ''

How can I fix this?

Details

Severity
Crash
Resolution
Open
Reproducibility
Always
Operating System
Windows 10 x64
Operating System Version
1709
Category
General
Steps To Reproduce

game start

Event Timeline

i am having the same problem and cant seem to fix it tried pretty much everythin only started when i done the windows updated so aint got a clue if u found a way please tell me some people said go bk on ur drivers to the one the drivers was working on but i cant lol it is a new laptop so i am stuck lol

Omery added a subscriber: Omery.EditedNov 26 2017, 2:08 AM

Hi,
Ive been facing the same issue, it seems like windows wont recognize the dedicated graphics card (gtx 1050 4gb), only the onboard intel gpu. Windows does show the nvidia card on the device manager, but i guess its not using it at all for some reason. I have already tried updating the video card drivers, and downgrading to an older version of them, but nothing seems to help. The problem started since windows got the 1709 build, up until then everything ran perfectly.

Hi.
Have you tried installing build 1703?

Omery added a comment.EditedNov 26 2017, 6:24 PM

Unfortunately, i cannot revert back to the old windows builds before 1709, since windows.old was deleted...

Likewise, have the same issue.
Interesting, also have the same graphics card in my laptop. Done the usual: graphics driver reinstall, verify game, etc., no luck. Does everyone else have a 630m?

Just did full reinstall of ARMA 3 – deleted all folders, cleaned APPDATA – bug still persists.
Think this is an actual bug now.

Wulf added a subscriber: Wulf.Nov 27 2017, 12:40 PM

Hello.

Thank you for the report. Could you please send us your Arma reports? Here's how to do that:
How to Guide

Troubleshooting report attached.
Had a quick look through, and this seemed notable –

'DX11 - Initializing DX11 engine.
15:43:11 DX11 - Detecting best GPU adapter.
15:43:21 DX11 - Detected best GPU adapter 0 : "NVIDIA GeForce GT 630M", benchmark result = 250394, level coef = 1, total result = 250394
15:43:21 DX11 - Using DXGI adapter 0.
15:43:21 - adapter description : NVIDIA GeForce GT 630M
15:43:21 - adapter vendor ID : 4318
15:43:21 - adapter device ID : 3561
15:43:21 - adapter subsys ID : 406261820
15:43:21 - adapter revision : 161
15:43:21 - dedicated video memory : 1027145728
15:43:21 - dedicated system memory : 0
15:43:21 - shared system memory : 4238342144
15:43:21 InitSound ...
15:43:22 InitSound - complete
15:43:24 DX11 error : Cannot create DX11 device : E_INVALIDARG
15:43:24 Resolution failed: 1366x768x (60 Hz)
ErrorMessage: Cannot create DX11 device:

Adapter (NVIDIA GeForce GT 630M) Fullscreen
Resolution 1366x768, format R8G8B8A8_UNORM, refresh 60 Hz
Error E_INVALIDARG'{F92989}

I do not see the report.

There we go second time lucky.

Update: just tried installing older version of Nvidia drivers, 387.92.
Error still present.

What is your version of Windows? what build?

Same as OP: 1709, Windows 10 x64.

I also have this version. Did you try to roll back the update?

Unfortunately I've deleted the previous version so I can't rollback.

Thanks to everyone helping out.

Omery added a comment.EditedNov 29 2017, 6:59 PM

hi,
I managed to solve the problem. what i did was I reinstalled windows with an earlier build (1511 i think). then, i installed the nvidia drivers i got with my laptop (asus gl553vd), and updated to the current 1709 build. im pretty certain its a compatebility problem between the new windows build and the nvidia drivers/ geforce experience app on certain systems. anyway, thats how i solved the problem. id suggest doing what i did, and if the problem reocurres after the 1709 update, just roll back to a previous build.

Hey Omery, congratulations in getting out of this hellhole :)

Just wondering if you then proceeded to update your Nvidia drivers after you updated windows?

thanks @AnEnglishmanSheIs :D . I havnt upgraded the nvidia drivers since. Personally, i wouldnt do that until the next fix/update is published by microsoft.

Omery added a comment.EditedNov 30 2017, 12:29 PM

P.S: you could also try updating the display driver (not the geforce experience) after updating windows as i have done, and if there are any problems use DDU (http://www.guru3d.com/files-details/display-driver-uninstaller-download.html) to completely remove the display driver, and install an older version of the display driver.

joaovitorpina added a subscriber: joaovitorpina.EditedDec 2 2017, 2:58 AM

I'm having the same problem, I just moved from windows 8.1 to 10. I did a full wipe so I'm stuck with the driver that Windows 10 automatically installed.Do any of you guys know what driver version do i need for Arma 3 to work in this current windows 10 build? Btw I have a Gt540m

Edit: I'm gonna try installing some old versions to see if I can make it work, if it works I get back here to say it what version for you to install, its the same driver for us @AnEnglishmanSheIs

joaovitorpina added a comment.EditedDec 2 2017, 3:50 AM

@AnEnglishmanSheIs I managed to find a working driver version that works with arma 3, use DDU to wipe your actual driver, then download driver 365.19(here is the link). If your computer turns off in the middle of the installation, its ok just check if it installed. I started installing the Driver then my pc turned off, but then when I turned on it was installed and Arma 3 was working. Hope I could help :)

@joaovitorpina Thanks a lot for the recommendation, I'll check it out. Only the thing is is that I'm reluctant to use DDU because I wouldn't want to delete all my display drivers – could you possibly confirm for me that DDU works with Nvidia Optimus?

Thanks a lot.

joaovitorpina added a comment.EditedDec 2 2017, 4:37 AM

It works, and you don't need to uninstall all your display drivers, just the Nvidia ones. When you open the program it shows the manufacturers, just select Nvidia and clear it, it will just uninstall the Nvidia, Intel HD graphics will remain the same. I have Nvidia Optimus and it just worked fine for me

Cheers man going to do it now; fingers crossed.

No luck chaps.
Ran DDU with a combination of driver versions and none of them worked.
@joaovitorpina the version you suggested wouldn't install for me for some reason.
Guess I'm just going to have to wait :(

Just wanted to weigh in, since I'm having the same problem with a different error.

After the Windows update, either:
a. Arma runs "fine" EXCEPT it runs on my integrated graphics with powerpoint FPS,
b. I roll back my drivers and Arma attempts to use my GPU but fails and crashes.

My laptop is an ASUS ROG G501VW with Intel HD Graphics 530 and a GTX 960m.

I do not get the same error. I cannot roll back to the previous version of Windows, so I settled on wiping both my Intel graphics drivers and Nvidia graphics drivers. I installed the latest ones from the Asus support page. The more recent version of the Intel driver results in Arma running off the integrated graphics card, so I decided not to update it as I prefer Arma crash on the correct graphics card rather than running poorly on the wrong graphics card. I also reinstalled Arma.

I get a window with text "bad_module_info error",
The next window shows:

Arma 3 exit code 0x000000FF-

And in the crash report when I scroll down through the logs I find that Arma successfully creates a DX11 device, but then crashed immediately after with

Exception code c0000005

which is noted in the logs essentially as a seg fault because it is treated as out of bounds memory. The underlying issue seems to be the same though.

Task manager data corroborates the log data because it shows a spike to 100% in Nvidia GPU usage right as the game opens, immediately followed by a drop to 0% after the crash.

joaovitorpina added a comment.EditedDec 2 2017, 8:31 PM

@AnEnglishmanSheIs Sorry mate that I couldnt help you. Try something, after I did what I said to you, I ran DDU again and installed the latest version of the drivers, and its working now, don't know why. Maybe a full wipe and reinstall of the display drivers did it. Maybe when Windows installed the display driver for me it corrupted something Idk, but it is working right now. Try it, maybe it works as we have similar graphic cards and use the same driver.

Update: I dont know why but it stopped working again, seems I will need to wait with you for a fix.

@aerophyle Did you try to run it on windowed mode? I did some searching on your error and it seems that after the last windows update a lot of people are having the same problem and the can "fix" it by playing in windowed, but it is not a fix because eventually it happens,

@joaovitorpina Na you did your best I'm just beyond the pale :)
Also just wondering did you use DDU while on Windows 1709? I just did a full wipe and reinstall of 388.43 and no luck.

Question for everyone: is this affecting all your games? For me, any game that uses DirectX 10 or above returns a similar error, around the lines of 'Cannot initialise DirectX 11 device'. Any DX9 games work fine on the Nvidia card though.

I've also submitted a support ticket to Nvidia on this.

@AnEnglishmanSheIs Yes, i did, I just installed windows 10 and updated it. I did a full wipe and installed 388.31, it worked for sometime then I restarted my pc and now its getting the same error.

I dont know if it is just arma 3 or every dx10 and above game, going to try now, as i said, i just installed arma 3 because I change from win 8.1 to win 10 yesterday.

And i will also submit a support ticket to nvidia, maybe they get more attention to it and fix it quickly.

@joaovitorpina Ah I see you have the same problem as me.
Games work first time, then afterwards stop working. Same thing happened to me with Bioshock Remastered.

Really strange. Yeah that would be great bring attention to the issue.

joaovitorpina added a comment.EditedDec 3 2017, 12:58 AM

@AnEnglishmanSheIs So I tried to run a dx11 game, Call to Arms, and it ran normally for me, I think for me its just an arma 3 bug who knows.

Edit: I really dont know anymore what is doing it kkkkkk, sometimes works sometimes don't, but its isolated only in arma 3.

Edit 2: It seems that even in my integrated graphics I cant run arma 3, so its not an nvidia problem for me, maybe directx came corrupt, but i dont I have a clue what it can be, because if it was a directx problem, I wouldnt be running other games.

@joaovitorpina I have not tried that, thanks for the suggestion. I'll give it a shot. I posted my error here because I think it is definitely the same issue, or at the very least the root cause of the problem is the same as the DX11 error. I guess BI and Microsoft have to coordinate their update cycles better, because every time they coincide things go wrong I fear the worst..

@AnEnglishmanSheIs my DX9 games work just fine as well. I don't have any other DX11 games on my laptop right now for space reasons, and I don't play many other games for time reasons. It really sucks not being able to play the only game I boot into Windows for :/


@joaovitorpina attempted to force window mode, but no luck. Black screen to error. Attached is a screenshot of the relevant bits in the error report. I guess we're all playing the waiting game.

joaovitorpina added a comment.EditedDec 3 2017, 5:23 PM

@aerophyle Indeed we are, and they sure need to coordinate better. I just installed windows 10 because everyone says it get more performance for everthing and indeed it gets. But the only game that I wanted to play on it, doesnt work so its dissapointing. Just going to need to wait with you guys for a fix. And it seems that we are not alone, I did some search and there is a lot of people that had the same problem, changed from windows 8.1 or lower to windows 10 and cant play arma 3.

Edit: I reinstalled windows, and on build 1703 it runs normally.

@joaovitorpina I can't roll back :/ my update was from some build of Windows 10 to build 16299. I'm not sure why I have such a weird build number, but since my Windows update, Arma update, and subsequent driver updates all took place in the same week I couldn't be sure which update was the cause. I am just gonna have to wait for the Arma update and hope it solves everything...it better be playable within the next two weeks, I'll rage at Bohemia's doorstep nonstop if I can't play Arma all winter break.

@aerophyle Anyways, the great windows update on win 10 tried to update to 1709 and my HD just fried don't know why, best week of the year. So I don't know if reinstalling would help. Now I don't even have a PC, but when I buy a new HD I will test it and see if it works

Sadly i've now also ran into this issue. ArmA ran very well up to now. I hadn't played in three days and apparently something happened in that timeframe that has resulted in ArmA no longer working. The Launcher works fine. The ArmA III loading screen with the loading bar becomes visible after pressing 'Play' and after the loading is complete, it dissapears. After a few moments a prompt appears stating a error has ocurred. I have attached a screenshot of said error-prompt.

I have tried several remedies, sadly none of which have worked.

  • I have updated my Nvidia drivers.
  • I have tried to update my Intel HD video drivers (apparantly already at the latest increment).
  • I have removed my Intel HD and Nvidia video drivers, after which i have installed their most recent versions.
  • I have System Restored my Windows to a point several weeks back, when ArmA still ran. To no avail.
  • I have removed my Intel HD and Nvidia video drivers and installed the (old) versions that came on CD when i got my system.
  • I have Steam verified the game files, all of which checked out.
  • I have tried different configurations in the launcher (Windowed yes / no, x64/x86, HT yes/no, etc.)
  • I have tried running the launcher and the two game executables in compatibility mode (Win. 8).

An interesting note is that forcing the game to run on my integrated graphics card does indeed start the game correctly, albeit at ~3fps (duh). As others have noted it probably does have something to do with a Intel HD / Nvidia Optimus driver conflict. However as ArmA seems to be the only game this is currently happening in (atleast on my system), there might be a problem on BI's side?

The system this occurs on (Clevo W150HRM):

  • i7 2720QM
  • Nvidia GT555M
  • 8GB DDR3 RAM
  • 7200RPM HDD

I have also attached the error log, in case it might offer a better view of the issues we all seem to be experiencing:

Kind regards,

Smooth

@aerophyle Anyways, the great windows update on win 10 tried to update to 1709 and my HD just fried don't know why, best week of the year. So I don't know if reinstalling would help. Now I don't even have a PC, but when I buy a new HD I will test it and see if it works

Did you ever get your rig fixed? Are you running 1703 or did you have to keep 1709? Still no one assigned to this ticket and it's been this way for weeks. I wonder how many game devs are actually contacting Microsoft about the problem, since this isn't an Arma specific issue...

@AnEnglishmanSheIs

Hi, Englishman could you please send your report once more? With recent dumps? Just trigger the error and upload the latest files.

Thank you.

No problem; I've attached my report once more.
However I don't think I can help you guys with diagnostics anymore – I solved my problem with a full WIndows reset and update. I was working through steps with Nvidia support, and they told me to update my Windows to Build 16299.98, which apparently included a fix to DirectX. My computer would not update, and that then became the final straw.

I'd suggest updating everything, and clearing your DirectX cache using Windows Disk Clean-up. Best of luck everyone.

SmoothOperator added a comment.EditedDec 18 2017, 3:55 AM

@Wulf I was hoping AnEnglishmanShels' solution would also solve the problem for me. I've completely reformatted and reinstalled my computer today. I've just finished completely updating and installing everything. however, I'm afraid this has not yet solved the problem, i'm seeing the exact same error every time i try to start the game. Both in x64 and in x86 versions... I'm at a loss here really.

My current Windows Build is: 16299.125.
My current Nvidia GPU driver Build is: 388.59 (GeForce Experience: 3.11.0.73, PhysX: 9.17.0524)

DxDiag is reporting i'm currently running DirectX 12.

Any help would be appreciated a lot, this is rather frustrating.

EDIT:

Here's the error i currently get:

SmoothOperator added a comment.EditedDec 18 2017, 3:30 PM

Okay, so i have contacted Nvidia Support. They have referred me to what was apparantly a Windows issue. They let me set the 'Force WARP' option in DirectX. This solved the issue with Geforce Experience only giving a black screen, but ArmA III still gave the same error. I was then advised to roll back to Windows build 1703. Which i did.

After having completed the restore, i tried starting ArmA again. I now suddenly get a different error:

This happens, after which i get 0xC0000135 - STATUS_DLL_NOT_FOUND stated in the error log.. Now this sucks, but atleast there is a little more information about this error on the Community Wiki. I have completed an integrity check on ArmA's files (125 missing, now restored), Yet the issue prevailed. Being at a loss for words here i have tried the Dependency Walker as suggested in the CW article. It has listed so many dependencies it's just ridicilous.. especially on this being a fresh Windows 10 install.

Screenshot of the Dependency Walker:

Attached error report of the 'new' error:

This is just is such a shame. I absolutely love ArmA and would love to play the new expansions i just bought. I'm at over 1900+ Hours in ArmA III on this same computer and it just suddenly broke. I'm really at a loss for what to do now.

I wanted to post a solution here that is working for me, though I don't know how much it will help others. I bought Squad recently and it was working, but it forced windowed mode and when I set the graphics to full screen the game was getting the same failure to start error. I took this as a clue and, under compatibility settings for the game, I checked the DPI scaling and full screen optimization boxes. For some reason, this got the game working for me. They do not open from Steam correctly, but I can finally play again. I hope this helps some of you guys, since it ties in with the forced windowed mode "fix."

I wanted to post a solution here that is working for me, though I don't know how much it will help others. I bought Squad recently and it was working, but it forced windowed mode and when I set the graphics to full screen the game was getting the same failure to start error. I took this as a clue and, under compatibility settings for the game, I checked the DPI scaling and full screen optimization boxes. For some reason, this got the game working for me. They do not open from Steam correctly, but I can finally play again. I hope this helps some of you guys, since it ties in with the forced windowed mode "fix."

Thank you! That actually seems to work! Must be a direct X issue somehow. I have noticed that the current install of the Geforce Experience has problems (black/grey application screen) that started after i installed ArmA III on my second reinstall, whereas it the Geforce Experience didn't before the installation. I checked this. Configuration issue somehow maybe?

Thank you Aerophyle!