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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2024-04-02T03:38:37+00:00

    Same exact error as OP on shutdown.

    I just built two new PC's that are identical except for the video cards which is irrelevant here. The input devices are however different.

    Only PC#2 was throwing this error.

    Both have Razer USB gamepads, both have wired USB mouse.

    PC#1 Has a wired USB Keyboard.

    PC#2 Has a wireless keyboard with USB Dongle and a wireless MSI GC30 (Xbox Style) controller with USB Dongle.

    My Mobos have the following USB connectors on the back panel.

    4 - USB 3.2 Gen 1 5Gbps Type-A ports (From Hub GL3523) (Blue) <------------- Removed everything from these

    4 - USB 3.2 Gen 2 10Gbps Type-A ports (From Z790 chipset) (Red) <---- Plugged it all into these

    1 - USB 3.2 Gen 2 10Gbps Type-C port (From Z790 chipset)

    1 - USB 3.2 Gen 2x2 20Gbps Type-C port (From Z790 chipset)

    They also have connectors for front panel USB.

    2 - USB 3.2 Gen 1 5Gbps Type-A ports (Blue)

    1 - USB 3.2 Gen 2 10Gbps Type-C port

    2 - USB 2.0 Ports (Black)

    All the drivers are from MSI.

    After reading this thread, I moved everything that was plugged into a blue slot to a red slot on PC#2 and the error went away.

    Main hardware.

    MSI MAG Z790 Tomahawk WiFi (WiFi is disabled, both are hardwired)

    Intel Core i9-14900K Raptor Lake Refreshed 6.0 GHz FCLGA1700 (Gen 14)

    32GB (2x16) GSKILL Trident Z5 RGB Series (Intel XMP 3.0) DDR5 RAM @ 7200MHZ

    Samsung 980 PRO SSD 1TB PCIe 4.0 NVMe Gen 4 Gaming M.2

    Windows 11 Pro

    Version 23H2

    Installed on ‎3/‎16/‎2024

    OS build 22631.3296

    Windows Feature Experience Pack 1000.22687.1000.0

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-04-01T22:28:57+00:00

    Im at the office right now, my Gaming unit is at home.

    I will try this when i get to my flat.

    Thanks I will give this a go.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-04-01T20:16:09+00:00

    Since I did this on March 23rd I have not seen the error even once.

    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?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2024-04-01T11:14:22+00:00

    Yes! I thought the same thing for a bit.

    But, Let me put this forward, It disappeared for me just a couple of days, then,

    like a ugly beast, it reared its head again, threw me this error back.

    Thanks.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-03-31T18:04:51+00:00

    After scanning through all the posts I saw a common denominator. A lot of people have a gaming controller. Mine is a Logitech F310. I would get this error almost every single time I sign out or shutdown from 1 of my 3 Windows 11 accounts. After unplugging the gaming controller, I no longer receive this error. So, some kind of driver issue with gaming controllers?

    Will update if this changes.

    Was this answer helpful?

    0 comments