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-13T11:56:49+00:00

    I cannot believe this is happening again.

    ALL THUS after a Clean Install, New Digital license I paid for, and just last night.

    The same bloody box came on me screen again.

    I need this intel, provided to the people that do the updates for windows 11 23h2.

    This rubbish started after an MSFT update, yes I hold stock too.

    I certainly hope, this is addressed.

    I do not see doing all of this again, will solve the problem.

    I know, thats just a guess.

    Be advised, this is happening again, at shutdown.

    What do I know.

    All the help you can offer would be good.

    After ALL OF THAT WORK, why is this happening,(sigh)

    Katharina

    Was this answer helpful?

    6 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-02-15T17:49:45+00:00

    I have the same error well it’s very close to it. explorer.exe “The instruction at 0x00007FFBEE743ACA referenced memory at 0x00000000000000024 the memory could not be written” It usually happens at shutdown. I’m also on Windows 11 23h2. What’s your computer specs? I’m hoping it isn’t this new DDR5 RAM that is the problem.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-02-15T23:51:56+00:00

    Thanks for replying!!!

    Heres what I am working with:

    DDR 4800 32gb x 2 = 64gb Ram Just bought it MAC Store put it inNot sure of DDR Value

    Could be DDR5 I dont know

    13th Gen i7 16 cores On a PRIME Z790-A Wifi Motherboard.

    All put in for me by the Tech Store downstairs.

    Good work, This SCREAMS HIGH PERFORMANCE!!!

    Hope this helps.

    This thing with this stuff is less than 2 months old.

    Thanks.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2024-02-16T13:01:12+00:00

    I'm having almost the same exact issue, have tried all the things that OP has. and yes. I have ddr5 memory. corsair dominator titanium 48GB 7000, 13900K (for now) asus maximus hero z790, asus strix 4090 oc, and 2 nvme drives, t700 gen 5 (in a 4.0 slot) 2TB and a 990 pro 1tb. my error is slightly different. but IMO it's the same issue. When i first installed windows I want to say it didn't error right away. It was only after either several windows updates or possibly even something after that. but, the only things i can figure are A: faulty RAM which i doubt especially since i've ran memtest86 on them and the results were clean, B: faulty CPU: which I highly doubt or C: something that's randomly been updated or installed that isn't playing nice. or not exiting properly at shutdown/reboot. I'm starting to have a sneaky suspicion that it could possibly be GPU Tweak tbh. just a hunch.

    The instruction at 0x00007FFC846A3ACA referenced memory

    at 0x0000000000000024. The memory could not be written.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2024-02-16T17:55:00+00:00

    Maybe it’s a bug in explorer they seem to have been working on it a lot so that could explain it.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments