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

Did you disable your hibernation file? For example to create or work with disk image files which benefit from smaller backup size if the hibernation file is deleted and disabled.

It's trying to dump the memory contents into the hibernation file at shutdown but is unable because you disabled it. It's nothing to worry about.

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!!

Do you know what that last update was? It seems they either might spread updates across different regions at different rates so that an update someone in the US might have gotten some weeks ago I only get a few days ago. Either that or people are pausing their updates to the maximum time allowed (5 weeks?) and are now shy to deploy any updates till they absolutely have to. After this I am going to wait as long as possible before installing any updates.

My new Windows 11 build uses my pre-existing Clubsport 2.5 wheelbase with the XBox wheel. That combination is perfectly happy even now as was the F710 gamepad I use for flight simming and FPS games until the message began appearing 100% of the time a few days ago. I even might have considered getting an XBox gamepad (the actual Microsoft one) in lieu but I don't trust that will fix the issue. However I did read somewhere today that someone who was getting the error message all the time got rid of it with a firmware update to their XBox controller. There hasn't been a driver update for a few years for the F710 let alone a firmware update. I'm beginning to get the impression this will be widespread without firmware updates for pretty much anything that is seen as an Xbox device. Interestingly, as part of the latest Fanatec driver update, both my wheelbase and Xbox rim did get firmware updates...

I'm trying a brand new install as I write and I am going to install the gamepad related games but no actual gamepad right away. First I am going to make a drive image of the install as it is without any XBox hardware (apart from the wheel rim which is perfectly happy). That way at least I can freely experiment with things without undoing all the work to this point.

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.