The instruction at 0x000******* referenced memory at 0x0000****** written SOLUTION for WINDOWS 11 23h2

Yup the controller works perfectly apart from the XBox button as I mentioned.

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

Click ok to terminate the program.

Edition Windows 11 Pro

Version 23H2

Installed on ‎6/‎30/‎2024

OS build 22631.3880

Experience Windows Feature Experience Pack 1000.22700.1020.0

IT'S VERY ANNOYING!

Another update from me. As per the experience of others, my brand new installation of Windows 11 yesterday worked flawlessly till the moment I plugged the XBox controller in. Literally, the very next time I re-started, the error message was there. Thankfully, the published work around on the net does work (to disable the gaming input service). And it definitely does not seem to make the slightest difference to the performance or the functionality of the controllers I have at all, apart from getting rid of the error messages. I sit a bit easier if a workaround simply involves doing something I can achieve through the Windows 11 user interface. If it meant getting more deeply under the bonnet, I would be more worried about the consequences (I am finding when it comes to Windows 11, it is best not to too too much DIY under the bonnet (hood for you in the US :) and instead just go with the flow lest the next forced update breaks what you did and makes things far worse. Not like the old days when we had total control over what updates we accepted from Microsoft.

I have thus decided to stick with this workaround and if Microsoft comes around and breaks the workaround (or breaks something else entirely), I will deal with that when the time comes. Life is too short to be afraid of Microsoft updates that break things!!

Incidentally, I am not counting on a fix anytime soon - the drivers that were loaded when I installed the controller last night were dated June this year. Given this issue has been around for more than 5 months, if Microsoft were going to fix it, they would have already. I suspect the answer is that firmware updates are required for Xbox controllers in order to properly fix this which puts the ball in the hardware vendor's court. And since many of these controllers are quite old (but perfectly good as in my F710), I am not counting on firmware updates either. Logitech probably had to be dragged kicking and screaming just to put out a Windows 10 driver for this product!

I wouldn't be the slightest bit surprised if Microsoft in a future update make this game controller service one of those services that is impossible to disable!!

Did all that also.

However I have not had the error return after the last MSFT Udate, last.

I do feel the pain of living like that for months was annoying, but I just lived with it.

Hope something works out for everyone here.

I've sat months waiting.

Cheers.

Hi have spent months looking for a solution, and it seems its gamepad related, I have the same memory write error if I have my GameSir G7 se gamepad plugged in when I restart windows (I have tried multiple other solutions none where the solution)

I found that its cause when I use the 500hz experimental polling rate on the controller