Mac Mini dropping Bluetooth

[PinkyMacGodess]

I assume this could be a Monterey issue, but I'm not sure at this point.

It's a Macmini8,1, Intel 6-core, 8GB ram model.

I ride an indoor trainer, and lately (hence the Monterey belief), it will drop all Bluetooth connections. I'll be riding along, and *POOF*, no connection for anything. I lose everything connected to it. (I think this is also happening with ANT+ connected devices too, but need more research on it.

The trouble is, it doesn't do it very often, but when it does, it usually does it 2 to as many as 4 to 5 times, and in fairly quick succession. *BOOM* *BOOM* *BOOM*

I can get the connections back by power cycling the trainer, and then the Mini finds it, and is good until it happens again, or I'm done and shut it off.

Here is the message caught in the console log.

Process: bluetoothd [147]
Path: /usr/sbin/bluetoothd
Identifier: bluetoothd
Version: ???
Code Type: X86-64 (Native)
Parent Process: launchd [1]
User ID: 0

Date/Time: 2022-05-09 10:36:22.4423 -0400
OS Version: macOS 12.3.1 (21E258)
Report Version: 12
Bridge OS Version: 6.4 (19P4243)


Time Awake Since Boot: 6400 seconds

System Integrity Protection: enabled

Crashed Thread: 2 RxLoop

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: Namespace LIBSYSTEM, Code 2 Application Triggered Fault

Application Specific Information:
Bluetooth fatal error - crashing { build=release, reason=607 }


Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x7ff81874897a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x7ff818748ce8 mach_msg + 56
2 CoreFoundation 0x7ff81884bcdd __CFRunLoopServiceMachPort + 319
3 CoreFoundation 0x7ff81884a368 __CFRunLoopRun + 1276
4 CoreFoundation 0x7ff8188497ac CFRunLoopRunSpecific + 562
5 CoreFoundation 0x7ff8188d182b CFRunLoopRun + 40
6 bluetoothd 0x10bd64dd4 0x10bd4c000 + 101844
7 dyld 0x1107ab51e start + 462

The next threads are StackLoop, RxLoop, TxLoop, AudioSkywalkPipeReadLoop. Leaving an error code of 0x020000209.

I assume this is in the Bluetooth stack, and not the app I'm running to drive the trainer. Today it blipped out twice. I got it running, and it tripped out again, but stayed up.

Just curious if anyone else has this issue, and can help narrow it down to hardware/software/solar rays.

Thanks...

 

[Sheepish-Lord]

Pretty sure the Mac Mini is notorious for Bluetooth issues supposedly due to the chassis design. Maybe some Google results will help but I don't know what, if any, fix actions there are.

 

[PinkyMacGodess]

Pretty sure the Mac Mini is notorious for Bluetooth issues supposedly due to the chassis design. Maybe some Google results will help but I don't know what, if any, fix actions there are.

Hmm...

It was bad (different errors/conditions than this issue) for a while on a previous macOS version (Big Sur), and then got much much better, and now it's just flat out dropping the connection. As if it's being turned off somehow, but it's really the daemon crashing. It seems to pop up, but struggles a few times, and then is back. I did a 90 minute ride a few months back, and it tripped out about 40 minutes in, then took a few times to stabilize, and then past one hour it tripped out again, and took longer to stabilize.

If it were the chassis, the problem would be more continuous throughout my ownership, and happen way more often. It's almost like this is a Monterey problem possibly. I was just curious if anyone else had these issues start up all of a sudden, and start happening. Like I wonder if the .1 update upset the daemon somehow. I mean, tweaked it, sad bad things to it.

Funny thing is I rode for two hours on Saturday, No Error. I was kind of surprised, I figured 2 hours was tickling the dragon's tail, but... And now, today, it trips out twice. Weird... (And the wife wasn't here to use the microwave🙄)

 

[PinkyMacGodess]

Oh, one thing that nullifies post #2 is that both the Bluetooth and ANT+ services are being used with external USB sensors. So, is it possible that the USB is failing? No, the error message says it's the Bluetooth daemon that crashed. Hmm...

I give up. It happens so infrequently that it's hard to diagnose. It's just damned frustrating...

 

[PinkyMacGodess]

So it dropped again. Now in the process of reinstalling Monterey. 'Startup Disk Security'? Wow...

How can I delete the macOS install partition? I couldn't and just went to the USB media, but would have liked to wipe the drive clean and start over.

 

[RobbieTheK]

Did the reinstall work? I had the same issue on Monterey and now on Ventura. I ran Entrecheck and removed anything I no longer needed. I've reported it via the Feedback application to deaf ears. You can see my post here at Apple Discussions and the error I see is 0x02000211 so slightly different than yours.