Page MenuHomeFeedback Tracker

Arma 3 game crash, "bad_module_info"
Closed, ResolvedPublic

Description

My Arma 3 crashes after joining a server a min or two in. A popup window says "bad_module_info has stopped working"

. After closing the popup the game closes, and i get this
. Here is my saved Arma report

Details

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

Ran the game a couple of times, keeps getting the same results.

Event Timeline

Erase ur arma 3 battleye folder then reverify it should find 10 file missing let it reinstall and then launch arma 3 ...worked for been in 2w different server spread the word

I am getting the same error. It started today. I wasn't happening yesterday evening when I had been playing the same server. I tried another server I have played often, and it also crashes the same way.

The crash occurs after about 1 minute after getting the player list when first joining the server. If I quickly hit [OK] to start the game, it looks to be proceeding with the usual startup processes, but then crashes out after about a minute.

I've been changing the /Arma 3/..... .exe file property settings as I was reading that it might be the "Compatibility"/"Disable fullscreen optimizations" issue. That didn't stop the error.

I then found this Thread and began to do what subscriber jprod7808 suggested in his comment (ie,"Erase ur arma 3 battleye folder then reverify it should find 10 file missing let it reinstall and then launch arma 3 ...worked for been in 2w different server spread the word"), but found if I deleted the ".../SteamApps/common/Arma 3/Battleye" directory the ArmaLauncher wouldn't allow me to "Join" a server. And I wasn't clear on what jprod7808 meant by "reverify". I decided against fiddling around with a Battleye re-install (the ArmaLaucher didn't seem to do it automatically), so just reverted the deleted "/Battleye" directory back to what it was, and can now Join servers from ArmaLauncher again. (but it crashes with the "bad_module_error" after about a minute)

I suspect this is an issue with other users, and so I will wait to see if the cause and the solution get posted in this thread at some point soon.

note: bug entry T128113 has similar complaint

note: the two server names I've been trying to connect to are: "[WaW] World At War's IFA3 Liberation Server" (Type CTI) and "teamrevolt.org - King of the Hill - AU #2 LV - armakoth.com" (type KOTH) - I mention this because, if this is a BattleEye issue (suggested by jprod7808), looking at the Battleye download page I see it no longer supports "Iron Front: Liberation 1944, ArmA: Armed Assault / Combat Operations, Soldat, S.T.A.L.K.E.R.: Clear Sky, S.T.A.L.K.E.R.: Shadow of Chernobyl, Warsow, Urban Terror", and I also noticed my ".../SteamApps/common/Arma 3/Battleye" directory holds two recent files from 6/4/2018: BEClient.dll and BEClient_x64.dll, so wondering if maybe the servers have gotten some updated files (or missing recent files) that are causing the issue maybe.

Observation:

looking at my ArmaLauncher Servers/Favorites list I've set up, there are some servers with lots of users. So I tried:

"Strayagaming.com.au|Invade & Annex"

... and got in with no crash.

This makes me wonder if its a server related issue.

Wulf added a subscriber: Wulf.Apr 10 2018, 10:44 AM

Hello.

Thank you for the report. We are looking at the issue right now so hopefully all of these recent crashes are all related.

Soldat_Ryan added a subscriber: Soldat_Ryan.EditedApr 10 2018, 12:36 PM

I did the same problem and I'm preventing the problem by starting the game then close the launcher and join server from "multiplayer" tab.
Solution is working too for players playing on my servers.

After submitting my 7:08pm comment, I read something on possible solutions to 0xC000005 - STATUS_ACCESS_VIOLATION errors, and one suggestion was to log-in succesfully to a different server, then again try logging into the server that crashes. It doesn't explain why this works.

But, having already logged into a different server as explained in previous comment, I tried logging into the "Iron Front: Liberation " server, and I got in and played for an hour or so with no problems.

So, for me, the issue seems to have resolved for that particular server.

Wulf added a comment.Apr 10 2018, 6:31 PM

The fix should be live. Could you please test if the issue persists? Thank you.

logged back into the server today. Not getting the bad_module_info error. And other players are logging in ok from the looks of it.

Wulf closed this task as Resolved.Apr 11 2018, 9:54 AM
Wulf claimed this task.
This comment was removed by LouMontana.