The instruction at referenced memory at could not be written. *still unsolved *

CW3 (Ret) Wilson

CW3 (Ret) Wilson

153A Rotary Wing Aviator
So before i left for work i was getting this error message.
"  The instruction at 0x00732520 referenced memory at 0x00732520 could not be written. "

It was making my game crash and returning me to desktop. Some times it would happen, sometimes it would be fine, It would happen if I was running vanilla or 506th.

Any help would be appreciated.
bE2DI.png

^not the real image

PC specs (I have upgraded the ram to 16gb, and am still running windows 8.1)
http://www.dinopc.com/shop/pc/-b-NEW-b-Magma-wrath-Gtx-770-94p2196.htm
 
SPC Carrera said:
In your arma 3 directory folder there is a folder thats named Dll, try deleting the files in there.
Click to expand...

Yes, I used to get that error all the time before I did this. I have also had better luck on Win10 than I did on Win8.1
 
Deleting the dll folder is a brutal solution. To accomplish the same thing, add the line '-malloc=system' to your startup parameters OR, if you are using the Arma 3 launcher, in Parameters > Advanced > Advanced check 'Malloc' and type 'system'
 
SGT Otto said:
Deleting the dll folder is a brutal solution. To accomplish the same thing, add the line '-malloc=system' to your startup parameters OR, if you are using the Arma 3 launcher, in Parameters > Advanced > Advanced check 'Malloc' and type 'system'
Click to expand...

Ah yes, I did both lol  ;)
 
also if you are going to delete files in your directory> Dll, do NOT delete the readme everything but the readme
 
PV2 Bingham said:
How much ram do you have
Click to expand...

I doubt it's a RAM issue in regards to amount - I have 32gb and do not run anything but ArmA, TS, and Steam when playing and I was getting this issue until I did the Win10 upgrade and deleted the DLLs and the '-malloc=system' part.

It might be, just thought I'd add that since my system was barely hitting 25% memory usage when I was getting this.
 
I was having the same issue. I tried the same solutions as you but no joy. What fixed the problem for me was doing a clean reinstall of the NVidia driver. I had been auto updating it but it apparently doesn't correctly delete the old driver. Haven't had the error once since then.

 
You must log in or register to reply here.
Back
Top