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: Most helpful
  1. Anonymous
    2024-03-23T13:53:54+00:00

    Found in a Reddit forum. Disabling the GameInput Service stops this.

    It does, and I cannot find where this interferes with my controller, keyboard or mouse, which are the only Game Input devices I have.

    This is so simple and it actually works.

    Windows Key> type services.msc hit enter.

    Scroll to GameInput Service, double click and stop the service, then change the startup type from manual or current setting to disabled and apply.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-03-04T19:47:37+00:00

    Greetings from France !

    Im glad to find the post and not to be isolate in that problem who is linked with windows.

    Same error with explorer.exe happen for about 1 month ago, "instruction at 0x00007FFF84123ACA referenced memory at 0x0000000000000024, could not be written blabla...

    I guess i have this error only after a session of gaming but not on every games apparently because no issue with Helldivers 2 was released recently.

    I tried all the things mentionned before and 2 complete reinstallation of windows without any sucess...

    Setup :

    ╔►CPU: AMD Ryzen 7 7800X3D
    ╔► MOTHERBOARD: ASUS ROG Strix X670E-A Gaming Wifi
    ╔► CPU WATERCOOLING ALL IN ONE: NZXT Kraken Elite RGB 280mm
    ╔► GPU: RTX 4070 Ti ASUS STRIX OC
    ╔► PSU: CORSAIR RM Series RM750 - 750W - 80 PLUS Gold - White
    ╔► RAM: G.Skill Trident Z5 Neo RGB Series 32 Go (2x 16 Go) DDR5 6000 MHz CL30
    ╔► SSD: NVMe 4.0 Samsung 990 pro 2 To
    ╔► CASE: CORSAIR 4000D airflow white
    ╔► OPERATING SYSTEM: Windows 11 Home

    Thank you all and i hope the microsoft team will solve the problem !

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-03-01T18:13:30+00:00

    I have the same problem it started about a month or so ago. I noticed that if a play certain games after an hour or so the error would appear. However, when I play Fortnite sometimes it would happen at shutdowns and sometimes it wouldn't. If I play overwatch for 2+ hours I get no errors - in fact with overwatch I never have the error. In one game, Atelier Ryza 3 - I would get the error after 50 minutes of use but not after ten minutes of play. However, if I am just browsing the internet and watching YouTube after 1+ hour no error. So I have noticed it really only happens to me after playing certain games after an hour or so. Also it happens if I play multiple games in in one session - for example if I play Atelier Ryza 3 for 10-20 mins then some borderlands 3 and then Fortnite the same error with appear on shutdown.

    I have a newly built PC and I am really baffled at what is going on. I have noticed earlier in this thread people where suggesting it could be something to do with DDR 5 and I can confirm that my system is using DDR 5 memory. In fact the memory I am using is CORSAIR VENGEANCE RGB DDR5 RAM 32GB (2x16GB) 6400MHz CL36 Intel XMP iCUE Compatible Computer Memory.

    I have done all the checks and scans like memory diagnostics/chk dis r etc - and all is fine

    I haven't done a full reinstall of windows since I thought the error could just comeback.

    my PC specs are

    Intel® CoreTM i7-13700 Desktop Processor 16 cores (8 P-cores + 8 E-cores) 30MB Cache, up to 5.2 GHz

    MSI MAG B760M MORTAR WIFI Motherboard, Micro-ATX

    CORSAIR VENGEANCE RGB DDR5 RAM 32GB (2x16GB) 6400MHz CL36 Intel XMP iCUE Compatible Computer Memory.

    Gigabyte GeForce RTX 4070 WINDFORCE OC

    I hope this helps as this error is so annoying

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2024-02-25T05:06:30+00:00

    yup, as crazy as it sounds i too was relieved when i found this thread. still kinda bothers me but not nearly as bad as costing money to replace all the things would bother me.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  5. 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