Connecting Xbox Controller via BT after Xbox USBDevice update causes GSOD

I ran Windows Update earlier and there was an update for Xbox USBDevice (Xbox - USBDevice - 1.14.20.740). I installed that, then rebooted and now every time I try to connect my controller via Bluetooth, it will cause an immediate GSOD. I can plug in the Elite Series 2 controller via USB and it doesn't cause a crash.

Dump file: Google Drive link

i have the exact same issue, i dont like played wired so this is really inconvenient

Same here. This is the only forum reporting on the issue I could find on google.
I've tried to pause driver updates and rollback to a previous system restore point but without much success, it will crashes.

Ronico94 said:

Same here. This is the only forum reporting on the issue I could find on google.
I've tried to pause driver updates and rollback to a previous system restore point but without much success, it will crashes.

Click to expand...

I ended up having to disable the device in Device Manager, because even unplugging it after it was plugged in would cause the GSOD because it would attempt to reconnect via Bluetooth. Seems like Windows Update may have pushed out a bad driver update.

I just saw this update on my windows update page and im skeptical about it...thank god i checked before i updated it...maybe give it a couple of days before i update

blackroseMD1 said:

I ran Windows Update earlier and there was an update for Xbox USBDevice (Xbox - USBDevice - 1.14.20.740). I installed that, then rebooted and now every time I try to connect my controller via Bluetooth, it will cause an immediate GSOD. I can plug in the Elite Series 2 controller via USB and it doesn't cause a crash.

Dump file: Google Drive link

Click to expand...

Please post share links without restrictions (sign in):

How to use Google Drive - Computer - Google Drive Help

Same issue as well. There was a controller update available through the Xbox Accessories app but it didn't help the crashing. I ended up reinstalling my old Windows Xbox Adapter and connecting the Xbox Series controller to that which is working/not causing crashes. Hope this gets resolved so I can go back to bluetooth and avoid the less reliable adapter.

I got the exact same update today and it does the same thing, I fire up my Xbox series controller and get the immediate Green screen of death. This happened while I connected a new external USB drive to my PC. Not sure if the two are connected but it happened at the same time. I'm on Win 11 pro build 26120.3863.

Same. How can we rollback? I found the driver in Device Manager, but rollback isn't working.

I found a solution to this problem.
First you need to disable Windows Update until Microsoft releases a fix for this. Next hit Windows +R and type misconfig and hit Enter. Then click on the boot tab then check Safe Boot and below that check network then click Apply and restart.
Then once boot into windows, open cmd but run as administrator
In the command prompt type below

pnputil /enum-drivers > drivers.txt

Then a file will appear on the desktop as drivers.txt

Now open this file with notepad and search for 1.14.20.740. If notepad fails to open this file use MS Word or any other document editor app.

Once it finds it look for something like oem74.inf but the 74 might be a different number for you. Copy that oem inf text then go back to command and type below but replace the oem inf text with the one you copied from the drivers file

pnputil /delete-driver oem74.inf /uninstall /force

Then hit enter.

This will remove the issue that’s causing the GSOD when connecting the controller to Bluetooth

Go back to win+r and type msonfig the hit the boot tab then uncheck Safe Boot then click Apply then restart

Remember to pause windows update until a new fix is made

Now connect your controller to Bluetooth. This should fix your issue.

zbook said:

Please post share links without restrictions (sign in):

How to use Google Drive - Computer - Google Drive Help

Click to expand...

My bad. Could have sworn I did it that way.

Drive link

@MacGeekAz's solution worked for me. No GSOD after using that method and connecting my controller via BT.

@MacGeekAz's solution worked for me as well but I didn't boot into safe boot. I just uninstalled the driver using an administrator Terminal and then restarted the PC (to reload the drivers) and that worked.

Simple steps for those that reach this through google:
0. Pause windows updates and driver updates (look this up on google)
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.

Reason why I did the safe boot with network turned off is to prevent Microsoft forcing the reinstallation of the driver after deleting it.

Glad I found this thread...the GSoD issue was driving me insane. I realized there had been an Insider build update yesterday and figured that was the culprit, but wouldn't have known the fix unless it was posted here. I didn't boot Windows into Safe mode...simply uninstalled the faulty Xbox controller driver from the terminal as admin and rebooted. Voila, no more GSoD when connecting my Xbox controller via BT.

Just to clarify for anyone referencing post #13—those steps are actually based on the solution I originally shared earlier in this thread.

I’m glad it’s helping folks (that was the goal), but if you found it useful, please consider giving credit where it’s due. I spent quite a bit of time troubleshooting the issue, testing the steps, and writing them out so others wouldn’t have to.

I have no problem with others summarizing or tweaking solutions, but resharing it almost verbatim with only a slight change—and without directly linking or crediting the original post—can be misleading. Let’s keep this community collaborative and respectful.