• 0
Mail Escort

Memory could not be read/written crash

Question

Would someone from the Exile team be so kind to take time and try helping me?

In short, since patch 1.66 I cannot string together 1h of gameplay without crashing to desktop. It's the old, and by now infamous, "Memory could not be read" or "Memory could not be written" error, 0xffffffff. The reason I came here, to Exile forums, asking - more like begging -  for help, is because I have no CTDs when running Arma 3 without any mods.

But as soon as I turn on mods required on The Walking VoiNoob server, CTDs occur anywhere from 5min - 45min after joining the server. It's a handful of mods: Exile 1.0.2, CUP Weapons, CUP Vehicles, CUP Units, Ryan Zombies, RZInfection for Exile, CBA. Same deal on CCGs servers (note that I play on Tanoa, since I only just recently purchased Apex).

Should anyone be willing to try assisting me, I've posted a rather detailed report on bistudio troubleshooting forum, with a lot of info regarding my game issues (dump files, various settings etc.), before coming here to ask for help.

Any help would be greatly appreciated!

 

Thank you kindly in advance,

Mail

 

EDIT: In case it is a problem that I've linked to my thread on bistudio's forum, let me know, and I will re-post everything here from scratch.

Edited by Mail Escort

Share this post


Link to post
Share on other sites

10 answers to this question

  • 0

@Mail Escort

I had a similar issue a few months back. I believe I toyed with my registry and deleted my Arma profile, but unfortunately I can't remember what actually fixed it. I would try deleting your profile(s) first.

I quickly read through your post over at bistudio, and didn't see anything regarding profiles or registry edits, so I'm posting the link I used from the Steam Community regarding the topic I read through when I was troubleshooting HERE.

... a short Youtube vid I watched speaking more to profile removal HERE.

Apologies for the crude response, I wish I remembered what I did to fix the issue. Hopefully this is something you haven't yet tried and you can get it resolved. Good luck!

  • Like 1

Share this post


Link to post
Share on other sites
  • 0

Hm, as a matter of fact your response is anything but crude. It's interesting you mentioned the deletion of the Arma profile, as I completely overlooked it now in 1.66. Back in 1.64, the deletion of Profiles and various fiddling with files (game cache verification, mod verification, re-installation of game/mods) never yielded any results. Will try this again, thanks!

As for editing the registry, I'll definitely fiddle with that, on my own if I have to - will just back up entries prior to any editing/deletion.

Share this post


Link to post
Share on other sites
Advertisement
  • 0

Excellent. Hopefully it does the trick!

I still do get memory errors when loading into an Arma 3 server but I've found that when I Alt+Tab while the mission is loading, the memory error doesn't occur. I think I read somewhere Arma 3 tries to load something with the editor that the OS doesn't like. This is separate from in-game memory crashes, but good to know nonetheless!

Share this post


Link to post
Share on other sites
  • 0

Do this:

Start in SP

Load the Tanoa map

Move around via the editor for about 1 minute, exit out

Start a MP session from the game browser within ARMA

 

This is a 'fix' that I have seen and can verify as 'working' too.

:)

 

Share this post


Link to post
Share on other sites
  • 0

Yeah, memory errors while logging onto a server are a different affair and easier to work around by alt-tabbing.

Memory could not be read/written CTDs during game-play on the other hand, man you could literally film a conspiracy-theory documentary series on this topic - akin to cuckoo UFO nonsense on ie. History Channel - and, in episode 1, speculate that Putin's causing the Arma 3 CTDs, by orchestrating a BIStudio & ExileMod cyber-sabotage, in order to distract the masses from the real threat... watch Episode 1 on April 1st, History Channel!

On the bright side, it seems that players who are fiddling with the 1.67 dev branch are optimistic about the upcoming patch and the ironing out of the Memory 'read/write' crashes. But by the time 1.67 stable comes out in... 2019 or early 2020, chances are that  'documentary' will be filmed xD.

Share this post


Link to post
Share on other sites
  • 0
9 hours ago, Z80CPU said:

Do this:

Start in SP

Load the Tanoa map

Move around via the editor for about 1 minute, exit out

Start a MP session from the game browser within ARMA

 

This is a 'fix' that I have seen and can verify as 'working' too.

:)

 

I saw your post just now. Never tried this, will do. Thanks.

Share this post


Link to post
Share on other sites
  • 0

Breakthrough? Playing for over 2 hours now, no crash. I've posted more on the BIStudio forum. I'll report back if this turns out to be stable, or if I crash again. Should anyone have any questions, post here or in my thread on BIStudio forum.

Share this post


Link to post
Share on other sites
Advertisement

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.