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

Anonymous
2024-01-30T13:42:08+00:00

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.

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

276 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2024-02-25T11:30:17+00:00

    i am uncertain if they see this thread. but i would guess this problem would eventually effect more people if they dont take care of it. so we see

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2024-02-25T11:31:14+00:00

    true xD

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2024-02-25T18:51:14+00:00

    Thanks.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-02-26T17:16:02+00:00

    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.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments
  5. Anonymous
    2024-02-26T21:56:45+00:00

    Thanks for the Technical Insight here.

    Spot On!!!

    Out of all of this?

    At least I have a clean Install and Fresh Operating System.

    Now, If they can just fix, this.

    Cheers, and Thanks.

    Was this answer helpful?

    0 comments