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 No comments

276 answers

Sort by: Newest
  1. Anonymous
    2024-06-25T10:32:54+00:00

    Hi have spent months looking for a solution, and it seems its gamepad related, I have the same memory write error if I have my GameSir G7 se gamepad plugged in when I restart windows (I have tried multiple other solutions none where the solution)

    I found that its cause when I use the 500hz experimental polling rate on the controller

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-06-25T06:14:05+00:00

    Just an update from me. I was "lucky" (if you could use the term) in that this error was occurring 100% of the time whenever I would shut down or re-start the computer. Not even 99% of the time - 100% of the time. After systematically removing all updates that I was allowed to remove, there was no change (though there are a still a lot of updates remaining that I cannot remove).

    I then began systematically removing hardware. The error persisted until I removed the USB wireless dongle for my Logitech F710 wireless game controller which Windows identifies as an XBox 360 wireless controller. I then re-tested and verified this scenario, re-starting about 30 times each with and without the dongle and the result was consistent.

    So although n my case I appear to have found the culprit (so the same as others earlier in the thread - Xbox related), it does not provide an actual solution apart from not using the hardware of course.

    Strange thing is that I was using this precise mainboard, memory, F710 controller, optical drive, power supply up until yesterday under a previous Windows 11 install without any problem. This new build replaced the CPU and graphics card, however both flawlessly survived their torture testing for 12 hours before I began installing anything (I never believed this was a pure hardware fault anyway). It is almost as if one of the updates relating to the new CPU or GPU are having some unintended side effect - there are a number of AMD related updates there.

    The hardware that did not present this issue was an Nvidia RTX3070 with a Ryzen 2700X CPU. The hardware with the XBox 360 problem is an Nvidia 4080 Super and Ryzen 5700X. Not that this may have anything to do with it - that is what was changed with the new install.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-06-25T00:58:03+00:00

    I was replying to Peter but ok.

    My issue was to do with OneDrive - uninstalled and reinstalled and the error has gone (for now).

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-06-25T00:49:15+00:00

    I'm just chiming in to say that I have the problem on a brand new Windows 11 installation that I did yesterday 24th June 2024. It began happening after it did all the windows updates. How annoying this is even after just one day of use - I can't imagine living with this for months on end!! And yes, it ONLY happens when shutting down.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-06-23T01:29:39+00:00

    No I do not know which update.

    But the Latest One that just dropped.

    I have yet, to see any more of the error.

    Hope this update that just dropped took care of it.

    Was this answer helpful?

    0 comments No comments