Author Topic: The instruction at referenced memory at could not be written. *still unsolved *  (Read 6571 times)

CW3 (Ret) Wilson

  • 153A Rotary Wing Aviator
  • Retired
  • Posts: 223
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.

^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
« Last Edit: September 08, 2015, 02:16:22 PM by CW2 Wilson »
J. WILSON
CW3, USA
Retired


Carrera

  • Posts: 102
Re: The instruction at referenced memory at could not be written.
« Reply #1 on: August 16, 2015, 08:32:00 AM »
In your arma 3 directory folder there is a folder thats named Dll, try deleting the files in there.

McGuire

  • Posts: 170
Re: The instruction at referenced memory at could not be written.
« Reply #2 on: August 16, 2015, 09:32:35 AM »
In your arma 3 directory folder there is a folder thats named Dll, try deleting the files in there.

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

SFC (Ret) Otto

  • 11B4O Infantryman
  • Retired
  • Posts: 196
Re: The instruction at referenced memory at could not be written.
« Reply #3 on: August 16, 2015, 09:40:17 AM »
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'
W. OTTO
SFC, USA
Retired


McGuire

  • Posts: 170
Re: The instruction at referenced memory at could not be written.
« Reply #4 on: August 16, 2015, 10:03:40 AM »
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'

Ah yes, I did both lol  ;)

CW3 (Ret) Wilson

  • 153A Rotary Wing Aviator
  • Retired
  • Posts: 223
Re: The instruction at referenced memory at could not be written.
« Reply #5 on: August 16, 2015, 10:46:57 AM »
Thanks for all your help will try it when I get home in about 20 days
J. WILSON
CW3, USA
Retired


Bingham

  • Posts: 367
Re: The instruction at referenced memory at could not be written.
« Reply #6 on: August 16, 2015, 01:16:01 PM »
also if you are going to delete files in your directory> Dll, do NOT delete the readme everything but the readme

CW3 (Ret) Wilson

  • 153A Rotary Wing Aviator
  • Retired
  • Posts: 223
Re: The instruction at referenced memory at could not be written.
« Reply #7 on: August 16, 2015, 01:33:57 PM »
also if you are going to delete files in your directory> Dll, do NOT delete the readme everything but the readme

 Thanks for the heads up
J. WILSON
CW3, USA
Retired


CW3 (Ret) Wilson

  • 153A Rotary Wing Aviator
  • Retired
  • Posts: 223
Re: The instruction at referenced memory at could not be written.
« Reply #8 on: September 08, 2015, 11:19:35 AM »
Done both with no affect any other ideas?
J. WILSON
CW3, USA
Retired


Bingham

  • Posts: 367
How much ram do you have

McGuire

  • Posts: 170
How much ram do you have

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.

CW3 (Ret) Wilson

  • 153A Rotary Wing Aviator
  • Retired
  • Posts: 223
I have 16gb of RAM and have deleted the DLLs and done the '-malloc=system' part with still no affect
J. WILSON
CW3, USA
Retired


Schram

  • Posts: 202
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.


Tabor

  • Posts: 67
i only got this issue when using real light

SPC (Ret) Ciancio

  • 11B Infantryman
  • Retired
  • Posts: 395
i only got this issue when using real light

Same
B. CIANCIO
SPC, USA
Retired