Once again, Bridge OS is not the problem. In the many calls I've had with Apple Engineering on a number of Macs, it hasn't been — not once.
It's the symptom. Bridge OS is telling you there is a problem. You need to pay attention or this will not go away.
Apple can run a trace of exactly what's going on and (a) find the conflict and help you remove it — (b) or tell you that there's none and that Engineering is working on it — (c) or escalate to Engineering and they will get back to you. I've had (a) and (c) but never (b)
To make any of this happen, you need to initiate a phone support call on Apple's support site. It's free and they usually call back within 10 minutes of the request. Let us know what they say.
In your case, something called AFK_KIC_MAILBOX is showing up in the crash report. Don't be surprised if Apple points to it as the culprit. It may be connected to something old on your system — if so, removing it will not affect anything that should be running.
In the case of my iMac Pro, it was three old .kxt files that haven't been valid since OS 10.7 including Soundflower (the current version is fine). This happens a lot with ancient code trying to load when it shouldn't. With my clients, it's been crap such as 2005 HP print drivers, Finale 2009 help files, the Bresink temp sensor and other 3rd party crapware. It's always something and removing it has always fixed the problem.
Fixing the problem always stops the crashing but doesn't always cure the shut down and slow boot issue that often accompany this problem. For that, you need to Reset Launch Services using the Terminal Commands I've posted before. This will also reset the boot routines of each of your installed apps. Not a bad idea to to that once a year or so—you'll notice that some slow loading apps now start up much faster.
Wll, I understand your point, but this Mac mini is not eligible for the service. At first I'd try to fix it by myself.
Which Mac Mini model are you using?
When did these panic crashes start to happen?
Also, why did a Mac OS install/upgrade put your MM into such a mess? Was it an upgrade or fresh install?
If you indeed wiped the boot disk and did a complete fresh OS install without any Migration Assistant transfers nor individual software installs afterwards, then I can't think of anything else than a hardware fault of some kind.
Did you check if the MM fan is running, i.e. with Mac Fans Control?
2018 mini with i5 3.0, 256 gb ssd, 8 gb ram
It's a long story. It worked as a build machine in our company for 2 months and then just died, we couldn't switch it on anymore. We brought at service (I don't know where it was) and in a month according to the documents the motherboard was replaced and everything was wiped. We already bought a new mini then, so this one was a reserved machine, but not used for half a year.
Later I got it and wanted to use as a build machine too. It worked for a day or more, but then I decided to install Catalina from App Store over Mojave to it, but once the upgrade was downloaded and mini rebooted to install, it failed to boot. And it couldn't boot anymore (infinite boot loop again), so I ran Hardware Diagnostics and restored Mojave. But it didn't work well even for an hour because of random crashes and eventually fall back to boot loop. I left it for a while.
Recently I read the new about Bridge OS update, revived mini, but all the problems remain. I noticed, that it works well when it's cool and no displays connected (I use it via Screen Sharing).
Fan is running according to iStat menus.
Also, ensure that you used a very recent MacOS Mojave, such as 14.6.06, for the installation, since older versions might not be compatible with newer Bridge OS firmware.
10.14.6 (18G6042) installed, this is the latest release with all security update onboard.
mrmacintosh.com
forums.macrumors.com
