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: Most helpful
Most helpful Newest Oldest
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  2. Anonymous
    2024-07-17T20:00:11+00:00

    the instruction at 0x00007ff678000df2 referenced memory at 0x0000000000000010. the memory could not be read. click on ok to terminate the program

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-07-09T05:28:16+00:00

    I wanted to input on this, I have had the same problem. However, I seem to have got rid of the problem by downloading a complete fresh install of Windows 11 by USB.

    The instructions to do this are here...

    https://www.microsoft.com/en-us/software-download/windows11
    ...     you want to go through the second option "Create Windows 11 Installation Media".

    Go here...

    https://support.microsoft.com/en-us/windows/create-installation-media-for-windows-99a58364-8c02-206f-aa6f-40c3b507420d

    ... for other Windows Media Installation.

    I hope this helps as it did me.

    I have been trying to fix the issue since February when I got my gaming machine.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-07-07T11:30:44+00:00

    This is a new problem for me after I clean install of windows, but I have the same memory error every time I shut down windows… this is obviously been going on for at least six months and they haven’t fixed it… that or we all have bad memory sticks.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-07-06T17:29:06+00:00

    I will have to look into that but I don't think hibernation was disabled as I use it regularly. It is happily in hibernation right now as I type (I am using a different computer to type this). As a further update though, although I found the error messages completely went away by stopping the gameinputsvc I did "lose" the controller after a few days - in as much as it needed to have the driver re-installed as it was sitting there in Device Manager with the yellow warning against it.

    I wasn't sure if disabling that service had anything to do with it so I wrote some simple bat scripts to have it running all the time that Windows is running and to only stop the service when the machine was being re-started, put into sleep / hibernation or shut down completely. Although that also works perfectly I still "lost" the game controller again after another few days - even with the service running.

    I then checked the power profiles and the associated USB devices in Device Manager and did notice that it had the check box checked that allows Windows to put it to sleep. And if that controller ever gets witched off when Windows is running, you will have to re-install the drivers all over again.

    So I suspect the Logitech F710 controller is always going to be problematic under Windows 11 without a firmware update, even if this message does or does not appear (or even have anything to do with it).

    Was this answer helpful?

    0 comments