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: Oldest
  1. Anonymous
    2024-02-26T23:00:06+00:00

    It's your XBOX gamepad. Unplug it if wired (or turn it off if wireless), do a reboot (you'll still get the error this time), leave it unplugged or off and then try to get the error. Reboot, restart, sign off, whatever. It won't happen again until you plug the controller back in.

    Until it gets fixed officially, I've created a batch files on my desktop that restart Windows Explorer before shutting down or restarting. Here's the code for each. Just open notepad and paste either of the texts into it, and save. Then change the file extension from .txt to .bat

    REM Restart Explorer and Reboot

    taskkill /F /IM explorer.exe & start explorer

    shutdown /r /t 0

    or

    REM Restart Explorer and Shut Down

    taskkill /F /IM explorer.exe & start explorer

    shutdown /s /t 0

    Run the batch file instead of the normal shutdown or reboot and you won't see the error even with the gamepad plugged in.

    Was this answer helpful?

    10 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-02-27T00:44:03+00:00

    I do not leave my controller plugged in at all. I get this error regardless.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-02-27T02:00:32+00:00

    Do you have fast startup enabled? Unless you do a reboot, you are just loading the same condition back into memory with fast startup, ala hibernation.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-02-27T02:07:03+00:00

    no, i have fast startup disabled in windows and in bios.

    edit: I did like your approach to restarting explorer prior to a shutdown/reboot though, so I've added those to desktop. thanks for that.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2024-03-01T11:18:55+00:00

    Hi everbody,

    I have a similar issue with my brand new PC:

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

    Click ok to terminate the programme.

    The message is related to the explorer.exe and appears randomly at shutdown of Windows.

    Here are the specs of my PC;

    Microsoft Windows 11 Professional (x64) Build 22631.3235 (23H2)
    AMD Ryzen 7 7700
    MSI B650 GAMING PLUS WIFI (MS-7E26) (Bios Date: 08/10/2023; BIOS-Version:1.30)
    2 RAM Modules: 16 GB PC5-48000 DDR5 SDRAM Team Group UD5-6000

    I also tried several of the solutions that were already mentioded in the posts above like

    Windows Memory Test

    lots of variations of /DISM /Online /Cleanup-Image/... which al led to no results or errors.

    According to the tests my System is fine.

    At the moment I am using a wireless Xbox Controller which was mentioned above as possible source of this problem so I will take it of and see what happens.

    Anyway this wouldn't be an acceptable solution and I hope that Microsoft will fix these issues soon.

    I might also try a fresh Windows 11 installation (although this might not change anything) and see what happens.

    Greetings to anyone and keep in mind...

    You are not alone :-)

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments No comments