Surface Pro 6, Marvell Bluetooth Driver .121. Same issue - bluetooth began operating erratically after my machine ran updates on the 6th. Bluetooth just stops. I only run a mouse and some bluetooth speakers and never had an issue before the last few days. I opened a case with Microsoft three days ago, they told me to roll back the driver (already did), run the .msi update (already did). I also played with seetting bluetooth audio bridging service to auto, turned off power saving for bluetooth, etc. SO.....Before they could tell me to, I went ahead and did a clean install.
In order to determine if it was firmware or driver, after the clean install I did not update the Surface Pro 6 with any updates at all by keeping it off the internet. The Marvell driver that ships with the current version of the USB Media Creation Tool for a clean install is 15.68.9112.23 and is dated 12/2/2016. Same mouse and speaker ran for two hours straight, no hiccups or issues. SO... Firmware may not be the issue.
I disabled the Vendor Driver Auto Install capability thinking Marvell might have slipped in a sketchy driver through this annoying avenue, crossed my fingers, and enabled the internet and let the Updates go. The Marvell .121 driver installed, machine updated completely with mouse and speakers running fine, and rebooted.
After reboot, mouse and speakers worked fine for 31 minutes, then took a a dump. Same issues. In my mind, anyway, the .121 Marvell Avastar bluetooth driver (which is in the .msi they direct you to as well as in Windows update) is the problem.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
