game crash since the last arma update! v.1.78.143717

0x00000001 - UNABLE_TO_INIT_DXGI

0xC0000005 - STATUS_ACCESS_VIOLATION

Well After a last update without any mod my game crush for a same problem .status_access_violation. 3 times ı removed a game and install again but doesnt work. I search for a solution . ı tried every way ı can but still Same problem.

Hello.

Thank you for the report. Indeed it is caused by the new port configurations by BattlEye , we are also working on it and trying our best to remedy the situation. There are some community workarounds, we advise you to use them for now, until this gets fixed.

Thank you for understanding.

Regarding the Bad_module_info that is probably caused by the last major update of windows. Users claim that they got rid of this problem by reverting to the previous build of the OS.

So, We'll wait a update to game. I hope the game update soon

Well I have 2 file . ı searched for a some problem first ı saw some nvidia file (D3D10) and ı install directx again.I tried to launch a game but this time Arma cant find the problem(unknown module) . Now I'm sure this problem about the last update ı hope you'll find the problem soon.Good Luck :)

I get the same errors.
I'm on Windows 10 build 16299.
I have a GTX 960m and Intel HD graphics 530.
The game essentially crashes while attempting to create a DX11 device with my Nvidia card.
I rolled back my graphics drivers for both cards. With the older Intel driver, the game appropriately chooses to run on my Nvidia graphics card. When I update my Intel drivers, Arma ignores my Nvidia card and runs (at 10 FPS) off my integrated graphics.
I can't roll windows back to a previous version.
I have a friend who also has build 16299 and a GTX 1060 and no integrated graphics, and the game runs fine for him, save some occasional hangs. This leads me to believe the problem is related to dual graphics cards machines, especially Nvidia 900 series and below.
Attached are my logs and a screenshot of the relevant crash info.

Me too, as soon as I load the mission file "to_c02m02" the game crashes. Windows reports "bad_module_info" and arma says "access violation".

We published a new fix regarding ports and BattlEye issues, did it fix at least some of your problems? Please let us know.

No, it didnt fix any of the problems for my server. I still am getting the same exact issues as the guy who made this post to begin with. I run the Lythium map as well. I sure hope a fix comes soon.

I get that shit too. YOU GUYS NEED TO REVERT BACK YOUR DAMN UPDATE. WE PAID FOR A PRODUCT WE ASK THAT IT WORKS!!!!!! ONE FULL WEEK AND NO RESULT YOU SHOULD BE ASHAMED.

Server is still down and still crashing after the update 1.78 and 1.80 hotfix. FPS spikes and then the server crashes while an instance of the game is still running in the background and players just freeze in space.

The access violation bad module info error is only happening on Lythium servers that I join. This is happening on my Lythium server but not my Altis server. The servers are running the same mods and Altis hasnt crashed yet.

Same issue. Playing through the East Wind SP Campaign last night and as soon as I loaded up the "Scouting" mission, Arma Crashes - first with the bad_module_info error and then the access violation.

In T127271#1657189, @Wulf wrote:

Hello.

Thank you for the report. Indeed it is caused by the new port configurations by BattlEye , we are also working on it and trying our best to remedy the situation. There are some community workarounds, we advise you to use them for now, until this gets fixed.

Thank you for understanding.

Regarding the Bad_module_info that is probably caused by the last major update of windows. Users claim that they got rid of this problem by reverting to the previous build of the OS.

good nite,
Would you please shared the link where is the workaround as i spent all nigth i still looking for it,
best regards and thanks.

i finally found it:
https://community.bistudio.com/wiki/Arma_3_Unusual_process_exit#0xC0000005_-_ACCESS_VIOLATION

To make some order here because you all may think you are reporting the same issue when in fact it can be a different one with different cause.

NFGCaboose-1 - you said that it happens only to your Lythium server not on Altis server. Which may mean that we fixed it partially.

Pelase create a separate ticket regarding Lythium server and upload crash logs and server logs so that we can have a look at it.

google - " Playing through the East Wind SP Campaign" - Hello. Please attached the Arma report to your ticket https://feedback.bistudio.com/T127353. Also please write which mission in the East Wind campaign is causing the crash.

PS: Some users claimed that they fixed the issue by reverting to the previous version of Windows or that they started playing their games in windowed mode not in Full screen.

And btw this bad modu_info error is not an issue that Arma 3 is just suffering, other games as well suffer from this so this being a pure Arma issue is unlikely. We are working on a solution but for now please, try the above advice and let us know if it helps for now.

I got it to work by joining first a server that won't kick me out. Then joining the server i want to play in. But this needs to be fixed. Why does some server are ok and others won't recognize your battle eye.

Last night i just found that the issues its with the arma 3 server of Bravo Foxtrot Company-Exile Cherno Redux... not with my arma3 installation.

Yesterday, we published a fix for the bad_module_info error. Please, try the game and let us know if the issues regarding this error still persist.

Thank you.

In T127271#1660476, @Wulf wrote:

Yesterday, we published a fix for the bad_module_info error. Please, try the game and let us know if the issues regarding this error still persist.

Thank you.

This alone did not work, but in my compatibility settings, I forced the option which removes "fullscreen optimizations" as well as the DPI scaling, and for some reason that got it working. This solution seems to go hand in hand with the solution others found by forcing windowed mode (which did not work for me). The game seems to have trouble starting in fullscreen and so that compatibility setting mitigates the issue.

Сегодня за 4 часа игры по ошибке -- bad_module_info -игра сворачивалась 4 раза

Im having the same problem, cant load any sigle player or multiplayer with out the crash, please fix this

arma f*** up bad_module_info and Client not responding -.-

Encountered similar situation, occasionally game crashes, sometimes upon exiting game server.
Changed compatibility setting including fullscreen optimizations and DPI scaling, but happened again.

Attachment:

@qiuchengxuan @TheRealIron @Aleksis and others that haven't done so already. If you want us to fix all of the problems please create separate tickets and upload your Arma reports there. The more we have the better.

Here is how to do that.