Windows 10: Error: BTHUSB event id 5

Hello everyone,

Hope you all are doing well in this unprecedented timesCorona pandemic 2020.


Here is the problem:

I have searched whole of the internet for an issue regarding the auto-restart of my PC whenever it shuts downmy PC automatically turns ON after I shut it down, it does not throw any error or any other blue screen issues during shut down. One of the solutions in the internet said to check system logs in the event viewer against the time of shutdown.


Fortunately, I found an error: BTHUSB with event id 5 stating:The Bluetooth driver expected an HCI event with a certain size but did not receive it.

Can this error be the reason why my PC restarts automatically?

And if not still how to resolve this and how to overcome the problem of auto restarting.

Any help is appreciated.


I'm currently on Windows 10.

Detailed description from the event viewer is as follows:



Log Name: System

Source: BTHUSB
Date: 4/26/2020 12:47:32 AM
Event ID: 5
Task Category: None
Level: Error
Keywords: Classic
User: N/A

Description:
The Bluetooth driver expected an HCI event with a certain size but did not receive it.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="BTHUSB" />
<EventID Qualifiers="49157">5</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-04-25T19:17:32.771177800Z" />
<EventRecordID>45438</EventRecordID>
<Channel>System</Channel>
<Computer>DESKTOP-88GURV7</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Binary>000014000100000000000000050005C00E0000000000000000000000000000000000000000000000080000000C0000000E0C010B1000020205000000</Binary>
</EventData>

</Event>


Thanks in advance.

:)

 

Warning Event ID 25 BTHUSB

I have a Bluetooth ear piece I've attempted to update the firmware for multiple times. Every time I've tried to, the device fails to update. There are no instruction on how to up the earpiece other than "download the updater software, run it and hit the update button". When I check the Event Viewer for the error, I get "The local adapter does not support a critical Low Energy feature, the Low Energy functionality will therefore be disabled" and the source is BTHUSB with event ID 25. I've tried to locate a solution online and nothing with that specific source and event id combination shows up. The earpiece is a Sennheiser Presence.

 

BTHUSB Event 22 in the Event Viewer

Good morning,
the help page of the June Monthly Rollup update for Windows 8.1 (KB4503276) says to check the BTHUSB Event 22 in the Event Viewer. I have not managed to find this event. I have found 3 items regarding Bluetooth, which are: Bluetooth-BthLEEnum, Bluetooth-HidBthLE
and bluetooth-MTPEnum, but there is no sign of BTHUSB.

Could someone please tell me where it is?

Thanks.

 

Event ID 5 Kernel-General error in Event Viewer


Thanks.

That's also what I suspected.

OK, I don't (yet) run Win10, and I don't have a test box or VM.
So I don't know if what you're seeing is "normal" or not (as you know, the Windows Event logs can make one crazy with 1000000s of unimportant "errors" and entries).

I do know this:

• We aren't seeing similar reports at the MBAM forum (but few basic home users would probably look for errors, if they think the program is working properly and it doesn't mean that what you report is not real).
• It is "best practice" and was recommended even by M$ to temporarily uninstall one's security programs prior to an on-top Win10 upgrade. Something may have "broken" in MBAM during the on-top OS upgrade.

So, I have 2 suggestions for how to proceed:

1. Option 1: Perform a proper "clean reinstall" of MBAM following this tutorial carefully, and being sure to reboot both after running the removal tool and again after the reinstall: MBAM Clean Removal Process 2x
   1. NOTE: You need to have your Premium ID/Key available before you start, but the entire process will only take about 5-10 minutes, or less.
   2. You could then monitor the situation for a few days to see if this resolves the error.
2. Option 2: Head over to the MBAM forum and start a new post there, where we can collect some basic diagnostic logs for the QA team.
   1. I would suggest doing this BEFORE attempting the clean reinstall, so that we can capture whatever is happening with the *current* installation.
   2. You could then attempt the clean reinstall after that.

It's up to you.
If the program seems to be working OK, the error might be unimportant.
But it's hard to say without a bit more data.

Thanks,

MM (@daledoc1 at MBAM forum)