Forum Discussion
DWM (Desktop Window Manager) Gameinput.dll Xbox controller crash after controller sleep wakeup
Hey,
There is the following issue with Xbox controllers connected with Windows 11 via Xbox Wireless adapter (maybe also via BT not sure), that if the controller enters sleep mode after x minutes, and youre in a game or using Microsoft Edge (for example Xbox cloud streaming) and wake up the controller, there is high chance, DWM will crash with faulty module gameinput.dll, the game running also crashing, and you cant connect the Xbox controller anymore, (it will turn off the moment you connect and press a button), until you restart Windows.
You can see here a lot of other people having the same issue:
Beschreibung
Name der fehlerhaften Anwendung: dwm.exe, Version: 10.0.22621.1635, Zeitstempel: 0x6201aae6
Name des fehlerhaften Moduls: gameinput.dll, Version: 0.2204.22621.1848, Zeitstempel: 0x1f22cecc
Ausnahmecode: 0xc0000005
Fehleroffset: 0x000000000000eee5
ID des fehlerhaften Prozesses: 0x0x790
Startzeit der fehlerhaften Anwendung: 0x0x1D9DD89C1F7BD7E
Pfad der fehlerhaften Anwendung: C:\Windows\system32\dwm.exe
Pfad des fehlerhaften Moduls: c:\windows\system32\gameinput.dll
Berichtskennung: 7354f7b8-5a92-4d1d-bb7b-a25c7436494f
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:
There is also another issue with gameinput, that it reconfigures itself everysingle time when you reboot the pc:
Would be nice if someone could deliver these two issues to the internal team working on Xbox / Gameinput and DWM. Thank you very much
I am the original owner of the post u have tagged, makedir
I stummbled across this issue when I upgraded my computer from a z390e to a x670e AMD platform with a 7900x. I even posted on reddit and found quite few users with the exact same problem. I have yet to fix the problem, It got to the point I returned all my AMD hardware and now own a z790e system with a 13700k and the problem is still there, there is defo a issue with gameinput.dll the way it is behaving when the controller turns off or looses its connection. After testing this on a few systems the problem is still there, I just hope microsoft address this and fix it, most likely a controller update is needed
