Bluetooth BTHUSB error ID (3,5,18 or 34) crash dongle and/or USB ports

Question

Bluetooth BTHUSB error ID (3,5,18 or 34) crash dongle and/or USB ports

A.P 1

Hi!
After working for several hours, we will get an BTHUSB ID5 (or other error) from the Bluetooth driver. Sometimes the Bluetooth can recover, other times it freezes and only a REBOOT of the PC will get the usb working again. Neither Devcon reset/disable, nor physically removing the dongle and inserting it back in allows the usb ports to work. furthermore, any USB device inserted after the error will not work until a reboot is performed.
I'm attaching windows logs, event viewer logs as well as a simple CS file where we scan for BLE advertisements, read services and characteristics, then disconnect. Run this example for a few hours with several peripherals and you will crash as well.
Were using inter NUCs, windows 10. latest BIOS and BLE drivers. This happens with different BLE dongles, with different chipsets, so I don't think the dongle is the cause.
We use Windows.Devices.Bluetooth under UWP and are having many issues related to the BLE drivers.

Here is a link to logs, event viewer errors and a simple C# program which if you run vs more than 1 peripheral, will produce the issue within a few hours.
https://drive.google.com/drive/folders/1SOlwDnTWeap6HyG7g6ZbPqGKazF3Z0O0?usp=sharing

Please advise.
Thanks!

Nico Zhu (Shanghai Wicresoft Co,.Ltd.) 12,871 Reputation points

2020-09-17T08:45:52.17+00:00

Could share uwp sample, and could tell more detail about under UWP and are having many issues related to the BLE drivers?
A.P 1 Reputation point

2020-09-27T10:01:13.467+00:00

Hi NicoZhu, thank you for responding and sorry for my delay!

We're developing a product where one or more 'centrals' communicate with a few dozen 'peripherals' over bluetooth BLE protocol. Most connections very little info is passed (~200 bytes), but rarely more info is passed between them (~5000 bytes). Between communications the peripherals 'Sleep' (i.e they are in very low power consumption and are not advertising). The centrals run constantly. We use PCs and Nucs running our software and using BLE dongles from different manufacturers with different chipsets to provide us with BLE capability.
On all devices we run, different errors are generated from the BLE drivers at different times. BTHUSB errors (IDs 3,5,18 and 34 so far) cause the Bluettoth communication to stop until a system reboot is performed. Other errors include invalid RSSI value reads (-127 or high positive values like +80), but this issue is less important.
A.P 1 Reputation point

2020-09-27T10:03:31.773+00:00

We use the Windows.Devices.Bluetooth namespace whice defines a Windows Runtime API that allows UWP desktop apps to interact with Bluetooth devices.
All PCs & NUCs run a fully updated Win10 with updated drivers and Bios.
We wrote our app using .Net core 3.0 and run it on windows only.
In the G drive link you can find error logs, event viewer reports and other items requested by Microsoft team for a BTHUSB ID5 event which forces a complete system reboot to resolve.
You'll also find a simplified C# .cs file which we've built for you to try and recreate the problems. We open two or more Bluetooth peripherals and have them advertise without stopping.
We then connect, read characteristics, write others (only a few, and the characteristics are all 4 bytes or less) and disconnect from the peripheral.
Do this for a few hours and you'll get one of the BTHUSB event which will crash your USB port system or at least disable all Bluetooth communication until you reboot the PC.
A.P 1 Reputation point

2020-09-27T10:24:20.737+00:00

In our example we added comments like //read characteristics here or //read services here since we do not know against which devices you'll be initiating the connection and what services or characteristics they will be exposing. Simply read one or two characteristics, write to one or two and disconnect. Do this non- stop and you will crash. You can use the battery service to access the battery percentage, which is a very common value exposed on BLE devices, for example.
Setting up the environment should include downloading the .net core runtime and not much more.

Any pointers will be greatly appreciated!
Thanks!
Nico Zhu (Shanghai Wicresoft Co,.Ltd.) 12,871 Reputation points

2020-09-28T03:23:27.373+00:00

Thanks for your info, I will check above that and test it.
Nico Zhu (Shanghai Wicresoft Co,.Ltd.) 12,871 Reputation points

2020-09-29T09:13:11.663+00:00

It's looks driver issue, could you try to update the derive and test again?
A.P 1 Reputation point

2020-09-29T10:03:09.28+00:00

Windows is updated to the latest release, as are the Bluetooth drivers offered by Intel.
The update driver wizard suggests I have the best drivers for my device already installed.

Any specific driver I should look for?
Chris Hicks 1 Reputation point

2021-07-12T14:15:45.257+00:00

It's a windows driver bthusb.sys located in \Windows\System32\drivers folder I get EVENT ID 34: The local adapter does not support an important Low Energy controller state to support peripheral mode. The minimum required supported state mask is 0x2491f7fffff, got 0x1fffffff. Low Energy peripheral role functionality will not be available.

Prior to this error, I have an Informational log of EVENT ID 18: Windows cannot store Bluetooth authentication codes (link keys) on the local adapter. Bluetooth keyboards might not work in the system BIOS during startup.

I haven't resolved anything yet, but it seems to be related to returning from sleep state.

2 answers

Your answer

Nico Zhu (Shanghai Wicresoft Co,.Ltd.) 12,871 Reputation points

2020-09-17T08:45:52.17+00:00

Could share uwp sample, and could tell more detail about under UWP and are having many issues related to the BLE drivers?
A.P 1 Reputation point

2020-09-27T10:01:13.467+00:00

Hi NicoZhu, thank you for responding and sorry for my delay!

We're developing a product where one or more 'centrals' communicate with a few dozen 'peripherals' over bluetooth BLE protocol. Most connections very little info is passed (~200 bytes), but rarely more info is passed between them (~5000 bytes). Between communications the peripherals 'Sleep' (i.e they are in very low power consumption and are not advertising). The centrals run constantly. We use PCs and Nucs running our software and using BLE dongles from different manufacturers with different chipsets to provide us with BLE capability.
On all devices we run, different errors are generated from the BLE drivers at different times. BTHUSB errors (IDs 3,5,18 and 34 so far) cause the Bluettoth communication to stop until a system reboot is performed. Other errors include invalid RSSI value reads (-127 or high positive values like +80), but this issue is less important.
A.P 1 Reputation point

2020-09-27T10:03:31.773+00:00

We use the Windows.Devices.Bluetooth namespace whice defines a Windows Runtime API that allows UWP desktop apps to interact with Bluetooth devices.
All PCs & NUCs run a fully updated Win10 with updated drivers and Bios.
We wrote our app using .Net core 3.0 and run it on windows only.
In the G drive link you can find error logs, event viewer reports and other items requested by Microsoft team for a BTHUSB ID5 event which forces a complete system reboot to resolve.
You'll also find a simplified C# .cs file which we've built for you to try and recreate the problems. We open two or more Bluetooth peripherals and have them advertise without stopping.
We then connect, read characteristics, write others (only a few, and the characteristics are all 4 bytes or less) and disconnect from the peripheral.
Do this for a few hours and you'll get one of the BTHUSB event which will crash your USB port system or at least disable all Bluetooth communication until you reboot the PC.
A.P 1 Reputation point

2020-09-27T10:24:20.737+00:00

In our example we added comments like //read characteristics here or //read services here since we do not know against which devices you'll be initiating the connection and what services or characteristics they will be exposing. Simply read one or two characteristics, write to one or two and disconnect. Do this non- stop and you will crash. You can use the battery service to access the battery percentage, which is a very common value exposed on BLE devices, for example.
Setting up the environment should include downloading the .net core runtime and not much more.

Any pointers will be greatly appreciated!
Thanks!
Nico Zhu (Shanghai Wicresoft Co,.Ltd.) 12,871 Reputation points

2020-09-28T03:23:27.373+00:00

Thanks for your info, I will check above that and test it.
Nico Zhu (Shanghai Wicresoft Co,.Ltd.) 12,871 Reputation points

2020-09-29T09:13:11.663+00:00

It's looks driver issue, could you try to update the derive and test again?
A.P 1 Reputation point

2020-09-29T10:03:09.28+00:00

Windows is updated to the latest release, as are the Bluetooth drivers offered by Intel.
The update driver wizard suggests I have the best drivers for my device already installed.

Any specific driver I should look for?
Chris Hicks 1 Reputation point

2021-07-12T14:15:45.257+00:00

It's a windows driver bthusb.sys located in \Windows\System32\drivers folder I get EVENT ID 34: The local adapter does not support an important Low Energy controller state to support peripheral mode. The minimum required supported state mask is 0x2491f7fffff, got 0x1fffffff. Low Energy peripheral role functionality will not be available.

Prior to this error, I have an Informational log of EVENT ID 18: Windows cannot store Bluetooth authentication codes (link keys) on the local adapter. Bluetooth keyboards might not work in the system BIOS during startup.

I haven't resolved anything yet, but it seems to be related to returning from sleep state.

Answer 1

琳戚 0

您好请问这个问题最后解决了吗？因为我现在也遇到了代码18的问题，更新驱动更新BIOS清除缓存也无法解决这个问题，导致我的蓝牙连接一直用不了

0 comments

Answer 2

Hello,

Welcome to Microsoft Q&A.

Your issue that might be related to ble devicer and I'm afraid is not suitable to discuss in the Forum. It is not allowed for us to tell you about our the email or address and we also won't ask you for private information. For your scenario, I suggest that you might need to open a support ticket for this. Please contact our paid phone support at MS Support. You will get 1:1 support on that. Select Developer Tools -> Windows UWP Development -> Windows 10 Universal App Dev -> Devices and Sensors Development-> Bluetooth API in the support page and you could contact the team. Please kindly note that your support ticket will be free if it is Microsoft's issue.

Thank you!

Share via

Bluetooth BTHUSB error ID (3,5,18 or 34) crash dongle and/or USB ports

2 answers

Your answer