Jump to content
SystemiK

CTD introduced after manually updating Battleye

Recommended Posts

After updating to 1.7.2.3 / 94876 yesterday I had a solid 7 hours of trouble free gameplay (not a single issue, which surprised me considering the problems many people did have).

Upon logging in this morning the first server I joined (same as the one I was playing on last evening for several hours) kicked me with a BE kick message "Battleye not updating" I would get this message (and kick) around 15 minutes after joining game. I kept re-joining the server. Soon, it was happening right after getting in each time, and a bit later I was getting kicked at the lobby before I could even join the game. Joining other servers had the same result. There were actually two BE errors I was getting kicked for, "BE not updating" or "BE not responding", seemed a bit random which reason would kick me.

Since it seemed Battleye related, my next step was to manually update Battleye. I manually updated to BE version v1.11 / v1.60 since version v1.61.94945+ seemed to indicate a more recent beta than my current 94876. Now started getting CTD during loading screens. Later tried v1.61.94945+ and again still CTD's on all servers during join.

From that BE update onward it's been CTD every single time I begin loading into a server. I get the screen with the arma tanks/hangars and progress bar beneath and immediately when the bar completes progress it's instant CTD. Tried replacing the BE files with the BE v1.61.94945+ files and no change, still CTD. Occasionally I see a quick (42KB of 42KB) message pop right before the CTD.

Since then I have re-installed the game twice.

1st time: Manually add DayZ and Beta patch as usual. I did all the usual steps for steam, i.e launch A2 then A2OA etc. (same CTD)

2nd time: Deleted all Arma folders in Steam and Documents as well as deleting all registry entries to Arma. This time used 6 updater to install DayZ and Beta (just in case I borked the previous reinstall somehow). Same CTD. Nothing gained from reinstall.

I'm not sure how this CTD is persisting across new installs. I made no changes to my computer in the interim, all was well last night when I logged out for the night, and then logging in this morning all hell broke loose.

Any suggestions would be appreciated, I really dont know what else I can try at this point. I've been playing dayz for 10 weeks now, today is the first CTD I've had but now they are every single time i join a server...

The only solid clue I can offer is that manually updating Battleye immediately introduced this CTD. I have not loaded into game without CTD since, and 2 complete reinstalls of arma have had no result.

tl;dr nothing to see here.

Share this post


Link to post
Share on other sites

Same problem. Also tried reinstalling the game, reinstalling battleeye. I've tried everything that I could think of. Nothing has worked so far.

Share this post


Link to post
Share on other sites

did a system restore, got back into a server that worked, can't join many other servers though, constantly stuck on "waiting for host"-error now.

Share this post


Link to post
Share on other sites

Got it working. The "Reinstall" option of Battleye in steam doesn't actually reinstall it.

  • Go to your windows start menu -> All Programs.
  • Look for Bohemia Interactive.
  • Go into Battleye subfolder and chose to uninstall from there.
  • After that is finished. Make sure every BattleEye file is removed from its directory.
  • Now, go into steam and chose to reinstall BattleEye again. This time you will be prompted with a popup like the first time. Just click next until it's done.

It should now work again!

Share this post


Link to post
Share on other sites

Also don´t forget to check BE files under C:/User/Name/AppData/Local/ArmA2OA

Share this post


Link to post
Share on other sites

I understood that I have 94876, and update for 94900+, lol. Now it's fine, I've fixed it.

Share this post


Link to post
Share on other sites

Well I've managed to get my client to load into a server without crashing now, but I'm still getting Battleye kicks for BE Not Responding / BE Not Updating.

Fuck it. I'll just give it a go on the next release.

Share this post


Link to post
Share on other sites

Well I've managed to get my client to load into a server without crashing now, but I'm still getting Battleye kicks for BE Not Responding / BE Not Updating.

Fuck it. I'll just give it a go on the next release.

Try different servers. Mine managed to update on a server I usually don't play on.

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×