happening to me as well, Dell Precision 5560.  I've had to reboot 3 times and its only 8am. 

I am having the same problem with my Dell XPS 15 9510 that is just a little more than a year old. I can not use any bluetooth devices with the laptop, (mouse, headset, speaker, etc.) and in the windows device manager when selecting properties it says: "This device has failed and is undergoing a reset. (Code 54)" as device status. Hopefully Dell support can help find a solution, or fix it in a driver update.

I am having the same issue with my Dell Precision M5550. I am constantly getting "This device has failed and is undergoing a reset. (Code 54)"  error on Intel Wireless Bluetooth adapter. Sometimes a reboot solves the issue for several minutes but after several minutes of use the device stops working. I hope this is a software issue and can be solved with a new driver update.

I've had some success with the last round of Dell updates.  So far it seems to have alleviated the issue.

Hopefully that doesn't jinx it!

not for me- Bluetooth just shut off. There's a code 54 error.

Dell XPS 15 9500  Windows 11,  everything updated to the best of my knowledge

I am having this issue also, everything appears to be up to date but devices aren't working and error code 54 showing on Bluetooth device - Dell XPS 9510. Restarting not solving anything for me, not found a solution yet.

I also solved my issue easily by rolling back the Intel Wireless Bluetooth Driver to version 22.40.0.2

My Bluetooth has been rock solid ever since (on my dell precission 5560 laptop).

Hi,

I had also the same issue on my XPS 15 9500 laptop. It occured after carrying out the latest Windows Update.

The same solution worked for me as for some others here in the discussion: Roll Back the Bluetooth driver to the last one - in my case to 22.130.0.2. One restart after the RollBack and everything seems to work fine again... hopefully it stays like this.

I hope also that @DELL-Cares notices the issue and fixes the problem with the newest driver update / Windows compatibility, so that it won't occur again with the next automatic Win-update.

Thanks for posting.  I just updated the driver and hope that resolves the issue.

Thanks , the solution worked for me.