Page MenuHomeFeedback Tracker

Memory could not be read
Assigned, WishlistPublic


While play-testing a mission I made in the 3D Editor, I'll often crash because "Memory could not be read..."

This has been going for a while (since November), but now it's practically every time since Nexus update's release. I've tried deleting my old profile and creating a new one (saw the advice on Steam forums) with no luck. {F27536}


Legacy ID
Game Crash
Additional Information

I'll also receive a "STATUS_ACCESS_VIOLATION" upon crash.

Event Timeline

Nightmare515 edited Additional Information. (Show Details)Dec 6 2015, 8:35 PM
Nightmare515 set Category to Game Crash.
Nightmare515 set Reproducibility to Always.
Nightmare515 set Severity to None.
Nightmare515 set Resolution to Open.
Nightmare515 set Legacy ID to 3502885285.May 8 2016, 1:15 PM
shukari added a subscriber: shukari.May 8 2016, 1:15 PM

I suppose, Adam will write here his standart pattern. So please add the rpt, mdmp and bidmp files....


Thank you for reporting the issue.
We need crash dump files from this folder to analyze your problem.
C:\Users\<Name>\AppData\Local\Arma 3\
Can you upload somewhere in winrar package, please?
Archive smaller than 5000 KB can be attached directly to the ticket. For bigger archives, please use some free sharing service and post link here.

How to find correct crashdump file:
Try to make the crash happen
Look into crashdump folder
Upload crashdump with latest date in name (crashdump is rpt + bidmp + mdmp file with same name). Please try to provide as many crashdumps as possible, it helps us investigating the problem in a big way.

Thank you. [^]

Adam added a comment.Dec 7 2015, 9:14 AM

Do as the man says. Thanks!

I'm able to find RPT files, but not BIDMP or MDMP files. They should be in the same folder, right?

Only if the game crashed it create dumps... if no bidmp and mdmp exists pack only the rpt in the package ;D
Edit: and yes they are in the same folder

Went back to devbranch today, this issue doesn't seem to happen anymore.