You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

mac mini 5,2

Have a Mac Mini 5,2 Mid 2011. Has been upgraded to 8 GB RAM and 500 GD SSD with High Sierra 10.13.6 with ALL Security Updates. EFI Boot Rom 135.0.0.0.0 installed with Security Update 2020-001 and all works well. Have Magic Mouse 2 and Magic Keyboard 2 with 27 Inch monitor connected via HDMI.


Have an ongoing issue with Bluetoothd crashing only at every Startup and only at startup. Below is excerpt of Crash.


Any ideas what is causing this or / and how to fix it?


Process: bluetoothd [92]

Path: /usr/sbin/bluetoothd

Identifier: bluetoothd

Version: 6007.4.18

Code Type: X86-64 (Native)

Parent Process: launchd [1]

Responsible: bluetoothd [92]

User ID: 0


Date/Time: 2020-03-28 09:57:21.555 -0400

OS Version: Mac OS X 10.13.6 (17G12034)

Report Version: 12

Anonymous UUID: ED86473E-9F86-6813-A5D6-F0279943591B



Time Awake Since Boot: 67 seconds


System Integrity Protection: enabled


Crashed Thread: 0 Dispatch queue: com.apple.main-thread


Exception Type: EXC_CRASH (SIGABRT)

Exception Codes: 0x0000000000000000, 0x0000000000000000

Exception Note: EXC_CORPSE_NOTIFY


Application Specific Information:

*** Terminating app due to uncaught exception 'NSRangeException', reason: '*** -[_NSInlineData subdataWithRange:]: range {2, 6} exceeds data length 4'

abort() called

terminating with uncaught exception of type NSException

Mac mini, macOS 10.13

Posted on Mar 28, 2020 10:21 AM

Reply
Question marked as Top-ranking reply

Posted on Mar 28, 2020 11:25 AM

Hmm... I have a 2010, a 2011 and two 2012's that are upgraded to SSD's, so I know that it should not damage or effect the wireless chip.


The only thing I can think of, is that one of the snap-on antenna cables is loose or pinched and grounding somewhere. Or that the ribbon cable is not fully or correctly seated.


Similar questions

24 replies
Question marked as Top-ranking reply

Mar 28, 2020 11:25 AM in response to PRP_53

Hmm... I have a 2010, a 2011 and two 2012's that are upgraded to SSD's, so I know that it should not damage or effect the wireless chip.


The only thing I can think of, is that one of the snap-on antenna cables is loose or pinched and grounding somewhere. Or that the ribbon cable is not fully or correctly seated.


Mar 29, 2020 4:59 AM in response to den.thed

Thank you. Will explore this once COVID - 19 locked down has passed here in Canada.


1 - Do you think the Magic Keyboard 2 and Magic Mouse 2 could be playing a part in this? Older Hardware Mid 2011 with newer accessories 2020 not 100% compatible?

2 - if, as you mentioned, a pinched cord etc would not the Bluetooth KB or mouse drop connections from time to time while in use? Have run the machine for hours without dropped KB or mouse connections.

Mar 29, 2020 6:43 AM in response to PRP_53

If you look at the system requirements for the Magic Mouse 2 and either extended or compact Magic Keyboard 2 devices, they required either El Capitan, or Sierra, and your running a fully updated High Sierra certainly exceeds those specs.


Any other paired (or attempting to pair) Bluetooth devices at the time of these crashes? Any third-party Bluetooth devices that needed software installed to support them?

Mar 30, 2020 7:33 AM in response to VikingOSX

Thank you Both for your help.

Have taken steps - 1 - Rest SMC - no joy, 2 - Rest PRAM 3x - no joy, 3 - Run AHT Extended - no joy, 4 - Boot from USB installer 10.13.6 - wiped SSD and reinstalled with all updates.

During the setup, had to use lighting to USB for both Magic Keyboard 2 and Magic Mouse 2 for macOS 10.13.6 to pair devices. They would not pair otherwise - still no joy. Still getting the bluetooth crash only at start-up.

Looking deeper, have iMac late 2012 running 10.15.4 and checked System Info Bluetooth Software version 7.0.4f6 whereas Mid 2011 Mac mini with HS latest running Bluetooth version 6.0.7F18

Kind of guessing therein is the issue. Yes new keyboard and mouse function 100% of the time but the crash at startup.

I will have to live with.


Apr 2, 2020 7:32 AM in response to den.thed

Followup - have paired circa 2012 ( 2-battery Magic Keyboard & 2-battery Magic Mouse ) to this unit. Still getting the bluetooth crash at startup. So this disproves my original idea that newer keyboard and mouse are source of the issue.

Thinking the pinched wire etc as den.thed mentioned maybe the true source of issue. Will investigate once COVID-19 and local lock down is over.


Thank again to you both for all your help.

Apr 15, 2020 10:08 AM in response to den.thed

Have been working on this and testing various setups. Turn off Bluetooth on computer and turn off each mouse and keyboard, attached usb keyboard and mouse. Then did a restart several times with usb mouse and keyboard attached. Checked Console after each restart without bluetooth turn on and usb mouse and keyboard connected. Still getting the bluetooth crash after each and every reboot.

So, something is very wrong in High Sierra?? The only other thing that might come into play was when I received this Mac mini from my son, he was running El Capitan and so EFI Boot ROM was the original 5.2xx. When I erased and clean installed HS 10.13.6 there was an EFI ROM update to 135.0.0.0.0. Any chance this is the issue?

Apr 24, 2020 1:02 PM in response to Andrii Zaiats

Actually, the problem started right after I erased the SSD and did a Clean install from Bootable Install HD of High Sierra 10.13.6. Before doing the Erase, my son had El Captain on it. The EFI Boot Rom was version MM51.0080.B00. Once I installed HS 10.13.6 the updates ( Not including the Security 2020-02 ) wanted to update the EFI Boot ROM to 135.0.0.0.0. It was at that exact moment my issue ( Bluetooth crashing ONLY at cold startup but working 100% once totally booted. Never any bluetooth drops etc. I am suspecting either there is a pinched wire as previously suggested or the age of this hardware is borderline time to retire. Have tried to wipe and clean install Sierra 10.12.6 but have issues getting it to install. Even tried removing 1 stick of 4 GB Ram and booting in HS, reseating both stick RAM and still issues.

Kind of given up and will just live with it annoying error message.


As for downgrading the EFI Boot ROM, I do not think it can be done except by Apple if at all.

Apr 29, 2020 5:04 AM in response to den.thed

Have continued working on it matter. Have done Verbose mod and tried to video capture. The best I can see is "Airport_Brcm 4331: : get SSIData():Get Failure: Apple 80211_IOC_SSID : 6 " followed by " Brcm kext failure "

Otherwise, system continues to work fine.

Though of 1 - reinstall HS over existing HS via Cmd + R and hope it sorts itself out? or 2 - downgrade to El Capitan, see how it works and then upgrade back to HS and fingers crossed the problem does not reappear.


Thoughts welcome

Apr 29, 2020 5:32 AM in response to PRP_53

Maybe you could create another partition and install El Capitan alongside existing High Sierra.


If it fails even in El Capitan, then this is a more hardware problem so any software manipulation would not help. I use more word because there are a plenty of reports around about this new Boot ROM version for Macmini5,2 that make them work improperly in a one or another way. And it could not be downgraded without an external hardware tool. Last year Apple released Security Updates approx. every two months, so maybe several weeks later new firmware upgrade will cure our Macs.

mac mini 5,2

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.