Question Can't find a way to solve this Bluetooth issue

JohnnyGui

Distinguished
Oct 27, 2012
129
0
18,680
I'm at a loss and I don't know what to do anymore...

Clean install of Windows 11 causes the following Bluetooth issues with my 8bitdo Pro+ controllers. Other BT devices are working fine. Windows 10 was working fine.

1. The controllers sometimes show a Driver error when they are paired (but not connected) with Code 10 (conflicting address range). This can be provoked by turning Bluetooth OFF and then ON again (while the controllers are OFF). This may need to be repeated since it's random.

2. The Bluetooth button in the Quick Settings gets stuck and is not interactable when clicking it to turn BT off. This is only the case when the controllers are paired with Windows. Deleting the controllers solves this issue.

What I have tried
  • Deleting and pairing the devices or deleting and reinstalling the Bluetooth driver and running the BT device Troubleshooter only fixes this temporarily
  • Swapping different Bluetooth cards didn't help
  • SFC /Scannow did not show errors
  • Different Intel BT drivers for my AX210 card didn't help
Intel advised me to contact Microsoft and 8bitdo can not reproduce the issue.

Specs:
Windows 11 Pro 21H2
i5-8600K
GTX 1070
16GB RAM
256 GB SSD

Anyone who has the same issue and/or has the slightest idea how to fix this?
 
Last edited:
Update your post to include full hardware specs and Windows OS information.

What specific driver error?

Do you see any other bluetooth related errors in Reliability History and/or Event Viewer?

Any update related problems in Update History?

How are the controller drivers being installed? Direct via the manufacturer's website or via some third party tool or installer?
 
Update your post to include full hardware specs and Windows OS information.

What specific driver error?

Do you see any other bluetooth related errors in Reliability History and/or Event Viewer?

Any update related problems in Update History?

How are the controller drivers being installed? Direct via the manufacturer's website or via some third party tool or installer?

I edited the OP . Device Manager shows a Code 10 (conflicting address range)

No BT error in event viewer or issued in Update history.

Controller drivers are installed via a third party tool from their 8bitdo website.
 
I'm at a loss and I don't know what to do anymore...

Clean install of Windows 11 causes the following Bluetooth issues with my 8bitdo Pro+ controllers. Other BT devices are working fine. Windows 10 was working fine.

1. The controllers sometimes show a Driver error when they are paired (but not connected) with Code 10 (conflicting address range). This can be provoked by turning Bluetooth OFF and then ON again (while the controllers are OFF). This may need to be repeated since it's random.

2. The Bluetooth button in the Quick Settings gets stuck and is not interactable when clicking it to turn BT off. This is only the case when the controllers are paired with Windows. Deleting the controllers solves this issue.

What I have tried
  • Deleting and pairing the devices or deleting and reinstalling the Bluetooth driver and running the BT device Troubleshooter only fixes this temporarily
  • Swapping different Bluetooth cards didn't help
  • SFC /Scannow did not show errors
  • Different Intel BT drivers for my AX210 card didn't help
Intel advised me to contact Microsoft and 8bitdo can not reproduce the issue.

Specs:
Windows 11 Pro 21H2
i5-8600K
GTX 1070
16GB RAM
256 GB SSD

Anyone who has the same issue and/or has the slightest idea how to fix this?
edit: i looked up the controller, you will want to make sure that the controller itself has had its firmware updated. https://support.8bitdo.com/firmware-updater.html
I fixed my neighbors machine using the same wireless card, it did not fix with the driver update but when I updated the xbox one elite series 2 firmware everything started working correctly.

if you can not get it to work, then a workaround the problem would to to tell windows not to let the device go to low power states ( disable sleep)


well, here is the location of the newest drivers dated 7/12/2022
https://www.intel.com/content/www/us/en/products/sku/204836/intel-wifi-6e-ax210-gig/downloads.html

just in case you have not installed them. in the past I have seen the intel driver update install drivers onto a machine but not activate the driver to the the currently selected driver and the old driver was still the running driver. you might run microsoft autoruns64.exe find the intel driver and note the date on the running driver before then after the update to make sure it gets updated. generally when this happens you have to install the new driver, then go into device manager, right mouse click on the device, update drivers but do not select the automatic update, you have to select the option that let you specify the location and pick the driver.
(often the list will be long and no way to see which version of the driver is being selected, in this case i pick a microsoft generic version since microsoft updates it or i run the pnputil.exe and delete all of the old intel oem.inf driver installs from the machine so only the new version shows up in the list. You can google "how to remove a driver from windows driverstore" to find instructions on how to do this with the pnputil.exe tool)

(i got different meaning when I looked up code 10)
code 10=STATUS_DEVICE_POWER_FAILURE
intel indicates to update the wireless driver to 22.70.X.X or newer.
https://www.intel.com/content/www/us/en/support/articles/000031150/wireless.html

device manager code 10 is a device power failure. I guess it would mean the device went sleep and can not wake up.
general fix for this would be to update bios to fix sleep function bugs, update the driver and for usb devices go to the control panel device manager find the usb hubs and right mouse click on the hub and find the power management tab and disable the selective suspend and do not let the hub or device go to sleep.

edit; also note that these device power states require bios support, often a bios update is required to get various fixes. Microsoft windows now tries to lower the power states to use less power and expose a lot of bugs in the driver, firmware and bios versions that were installed. mostly seeing this on windows 11 machines since they will have the newer hardware that is more likely to work correctly. people connect old hardware that need firmware updates and hit bugs for the most part. Various government regulations require Microsoft to make these changes but overall it is a good thing to save power on a national scale. lower the power state the more bugs exposed in firmware and bios and drivers.
 
Last edited:

TRENDING THREADS