Forum Discussion
BSOD when connecting Xbox controller via bluetooth
My windows 11 updated yesterday to the latest insider build and I noticed the following:
BSOD now changed to GSOD (yes yes, now its green screen of death)
And most annoying thing - Xinput driver for bluetooth communication is now busted and causing a system crash.
Updating the Xbox controller didn't help. Deleting and reinstalling the driver didn't help either.
What did help is to move to Beta version of windows build (what shows under recommended) and that fixed my issue.
33 Replies
- MikeLovellBrass Contributor
1. Open terminal as administrator
2. List drivers with this command: pnputil /enum-drivers > drivers.txt
3. Type pwd and navigate to that path to find the text file. You can just copy paste the response into the file explorer.
4. Open the driver.txt file and search for 1.14.20.740 (this is problematic driver version). Take note of the driver file name. For me it was oem72.inf, for other user it was oem74.inf, for you it may be different.
5. Uninstall the driver by running the command: pnputil /delete-driver driverName.inf /uninstall /force, replacing the "driverName.inf" with what you got from the previous step
6. Restart computer and reconnect your Xbox controller. It should now work.- Ajr37Copper Contributor
Followed this but again the Green Screen (and what a horrible green) as soon as I connect an XBox Controller. Controller is an Elite v2 if that helps others.
- BintazminCopper Contributor
This worked for me. Thanks.
- RaikenCopper Contributor
Btw; as it worked for me, I also added it to the Feedback Hub:
https://aka.ms/AAvnjbu
Feel free to upvote and confirm.
- JosephKimIron Contributor
What did you expect? Insider builds of Windows are work-in-progress builds that will be unstable at times--particularly in the Dev and Canary channels. Often these instabilities involve drivers.
- mexicanskynetCopper Contributor
This particular driver issue happened in the release preview channel, usually updates from this insider program are bug tested since they become most of the time the actual update to be released to public. Obviously some bugs just slip trough the cracks, being this particular issue one instance.
The current solution for all adopters of this update requires pausing windows update followed by removing the driver directly using commands in safe mode, or by using a tool like DriverStore Explorer. Hopefully Microsoft addresses this issue soon. Some users are also reporting that the driver no longer appears in windows update, but better turn it off for the time being just to be sure it won't download it as a background task.
Current faulty driver: Xbox – USBDevice – 1.14.20.740