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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-03-29T23:52:48+00:00

    I’ve changed my memory ram and my SSD, and I still have the error when I turn off my pc, I also reinstalled windows and still have the error, I’m about to buy a new motherboard

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-03-29T23:46:58+00:00

    Im getting the same error code

    The instruction at 0x00007FFE484C3ACA referenced memory at 0x0000000000000024.

    he memory could not be written.

    Click on OK to terminate the program.

    Were you able to fix it???

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-03-27T11:34:59+00:00

    True!

    The Jury is out on this one.

    Updates were installed last, and this one yesterday.

    As you said, the error box, has appeared less frequently.

    Will post results.

    Thanks.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-03-26T21:32:09+00:00

    Haha!

    I do apologize for not having posted the following day. The good thing is that it gave me more time to test.

    The bad news is that it seems arbitrary. But installing the latest updates has reduced the frequency at which I receive the error, funnily enough.

    Its comically lamentable at this point, that MS can't get its releases under control!

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-03-25T11:19:22+00:00

    That was me mate, just a few days ago.

    Now, back to waiting for a fix, down the line.

    I thought it was actually fixed for a bit there.

    Was this answer helpful?

    0 comments