The instruction at 0x000******* referenced memory at 0x0000****** written SOLUTION for WINDOWS 11 23h2

Question

The Instruction at 0x00007FFBCEAC3ACA reference memory at 0x0000000000000024. The memory could not be written.

Click ok to terminate the programme.

I use windows 11 23h2 this happened after the latest update, and happens at shutdown.

sfc /scannow, ran it three times. I do not know what to place on the command line to run

DISM. DISM /Online /Cleanup-Image /RestoreHealth does NOT WORK. I am frustrated, and nerves are getting bad.

I am NEW to windows 11 and just installed it on my High End Gaming Computer. I am frustrated, after gaming, seeing this

when I shut down.

I NEED HELP NOW please.

I cannot run DISM, till I get the correct command line sequence.

Thanks.

Answer 1

LETS RAISE IT TO THE DEVS EVERYONE!!!!!

This is a HUGE Problem, caused LOADS of issues.

I did CLEAN install and it still EXISTS!!!

LETS RAISE THIS UP to the Developers!!!

Lets get this Started.

Answer 2

This happened after a windows update I have no idea when that last was.

Is there any way other than system restore?

I just did the feedback hub submitted this issue.

The last is do a clean install and i do not want to do that being the last update

caused the problem. This did not happen till the last update.

Please submit this to the developers at MSFT.

Im at me wits end.

Answer 3

I guess I am just another user experiencing the same problem, and yes it started happening after one of the recent Windows updates. Running Windows 11 23H2, and it is explorer.exe doing it on shutdown. It doesn't happen every time which is interesting.

This post should have enough upvotes now to raise it to the devs, what if this bug does something dodgy to the memory.

Answer 4

Hi OP

I can confirm that I have the same issue.

Like many of the previous replies, the error message also began appearing for me after I installed a recent windows update.

I think that I was able to identify the problematic update being related to .net 3.5 or its newer version. This update dates back to February the 16th iirc.

The application concerned is also explorer.exe

Some research on the web shows that this was a known issue since windows 8/windows server 2012 from what I was able to gather.

It is discouraging to read that fresh installs are not a viable solution, as I've exhausted every other method available to me.

Uninstalling the update that I suspect to be at fault does not solve the issue because it gets re-downloaded and reinstalled after you reboot following the uninstallation. Its a bit of a catch 22 situation here.

I think upvoting this thread is the only thing we can do to draw attention to a bug that's been present in Windows OSs since the early 2010s.

Answer 5

Sorry for the late response.

Can you check which app getting the error?

It should be written in the Title bar of the error window just like in the image below.

Thank you.