"iMac Pro" kernel crash

BTW:

In 13.3.4 Beta 7 the error message changes:

NEW:

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 2.3 (15P53168a)","timestamp":"2018-03-27 18:04:58.36 +0000","incident_id":"B465E322-6B52-4DB2-8CCF-65F1525B8891"}

OLD:

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 2.0.1 (15P2542)","timestamp":"2018-03-27 03:21:21.67 +0000","incident_id":"ABC686DC-3B30-4429-A4BB-2D1081C8931A"}

So my problem has been temporary solved these are the step I took

1) I erased my hard drive and reloaded mac os

2) i disabled sleep and power nap

3) I removed a sonnet chassis on the the thunderbolt drive that contained a PCIe card ( this seemed to be the solution)

It seems when this card was on the thunderbolt connection to the computer at the same time my la cie hard drive was on thunderbolt crashes occurred frequently. they were never daisy chained and had their own port. Disconnecting either seemed to solve random crashes.The card inside was a universal audio card.

the crashes that happened overnight stopped when I disabled power nap.

4) As others thought the crash is related to daisy chaining I disagree as on another thunderbolt port i have several hard drives daisy chained. It seems certain devices are not playing well together on the thunderbolt data pipe wether or not they are on the same port or not.

I will update if I have any more crashes. The problem is now I can't use my Universal audio PCIe card 😟

This problem needs fixing asap. I've spent a ton of money on this machine and its my income maker. Im getting this issue daily. It started 2 days ago. I have the iMac Pro for 2 weeks. 2 weeks without any issues. If i think about it, it started after the last macOS updated I did a few days ago.

Sorry to say but this issue has been around since before the most recent OS update and occurs with both devices attached and nothing attached to your Mac. If you go through the process with Apple support you may get a new Mac but so far nothing has solved the problem for me, including two replacement Macs.

I'm currently waiting for Apple to issue a software fix or a hardware replacement but to my knowledge no root cause has been identified.

I agree with Happy Puppy this problem occurs with nothing connected to iMac Pro and even after the SSD was reformatted (APFS), system restored and updated to OS 10.13.4 and nothing else installed or migrated to the iMac Pro and no email services activated. My computer was thoroughly checked by authorised Apple Service Centre a few days ago and passed all the tests thrown at it. However the problem persists with kernel panics occurring when the unit is in sleep mode. This problem is out-of-box problem with many (if not all) iMac Pros affected. There is some evidence that attempts were made to address the issue in OS 10.13.4. (Eg. Bridge OS 2.0.1 (15P2542) was upgraded to Bridge OS 2.3 (15P3169) in OS 10.13.4.)

In OS 10.13.3: {"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_versio n":"Bridge OS 2.0.1 (15P2542)","timestamp":"2018-03-28 00:33:46.63 +0000" …

In OS 10.13.4: {"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_versio n":"Bridge OS 2.3 (15P3169)","timestamp":"2018-04-05 12:51:01.05 +0000" …

Agreed on all except my 10-core hasn’t panic’d in over a month after turning off every option in power management . Probably burning a lot of electricity but better than reboots until it gets fixed. And YAY for the garbled graphics fix in that last release!

My iMacPro still cashed when disabling sleep and security options. I believe that these options are there to enhance the utility of the device and they work well on my late 2015 MacBook Pro running OS10.13.4. Apple released iMac Pro too early without proper testing and is too slow to respond to the calamity.

After over a month of sheer frustration and several sessions with Apple Support senior advisors I returned the computer for the full refund. In meantime I'll revert using my MacBook Pro as the main computer. I really do not want to go to the dark side at this stage and would like to own fully functional iMac Pro (or highly anticipated new MacPro). I'll reconsider when and if the issues are sorted out.

The error we get when it crashes is related to the T2 chip. So, its either a software issue related to the chip, or, in the worse case scenario, the T2 chip is to blame which will turn this into a pr disaster if Apple has to recall all imac pros for a motherboard replacement. I have a feeling its a hardware issue. Since this is the only computer that i own and i rely on it to make a living, i wonder what apple will do when they will take in my imac pro to fix the issue. Will they offer a loaner imac or mbp? I hope they do.

One more brand new iMac Pro with this problem. Also have the crypto_val problem, slow login screen problem, single drive shared by 4 volumes weirdness. So far no missing files though. Called AppleCare and they basically just said to keep watching the forums. Seems very clear it's a T2 chip integration problem. We're the beta testers as this particular hybrid setup has not been attempted before. Really hoping this is not a recall situation...

Just return your iMac Pro for full refund. The issue has not been dealt with since the release of this machine late last year. Wait for the next iteration of the hardware as the problem is most likely a hardware issue with Apple T2 chip which is part of the motherboard and clearly not fully debugged as yet. Reconsider buying when and if they fix the problem. Returning buggy iMac Pros sends a clear message to Apple we are not going to pay premium price for so called "pro" machine unless it is fully functional. We understand that unexpected problems may emerge with newly released hardware (and software) but we also expect the problems to be dealt with promptly and we are informed about the progress. I concur with other contributors that Apple Support responses (wrongly) suggest that no other users are experiencing this problem and that we should follow the forums. It is not for us to come up with solutions – Apple needs to do its bit!

If you look through the forum, you will see this same issue over and over again. Something apparently went a rye at the factory when they were installing the operating system. If you do an erase and then reinstall MacOS. It seems to clear most of the problems. But funny enough not all. Some software seems to still give it a hiccup. Make sure you do a complete back up to time machine on an external drive before you under take doing this or you will lose everything. If you search reinstall Mac OS on this website, Apple provides a nice tutorial on how to do it. Good Luck

Crypto Val error is easily cleared by erasing your SSD and reinstalling the proprietary Apple Software and updating to the latest OS version. Painfull but at least one issue resolved. However this will not eliminate the kernel panics caused by Bug_Type 210 error. The crashes will continue even if you have nothing connected to your iMac Pro and nothing installed with the exception of the Apple proprietary software. The frequency of the crashes (when in low energy mode) may vary depending on your setup but they will continue to occur.

I'm going to pin the blame on some interaction with Chrome that Apple doesn't do in Safari. I almost never use Chrome, except when Safari is too stupid to figure out a web page. Well first time in about two months, I used Chrome yesterday and today, and for the first time in those two months, my iMac Pro restarted with the Bug_Type 210. This isn't just coincidence...

I am having the same issue,

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 2.3 (15P3169)","timestamp":"2018-05-22 22:29:18.05 +0000","incident_id":"FA5B2B0E-B89A-4502-B467-90B0FD72A2DD"}

I've now experienced it a total of 5 times. I am running a base model imac pro with 2 LG ultrafine 27in displays. No other thunderbolt devices.

I have now disabled powernap, if this happens again I'm calling apple, the computer is less than a few weeks old.

Sounds good. Hopefully that will fix the issue. One thing that I have noticed, that others are now also mentioning is that Chrome seems to cause the kernel warning and reboot if the application is left open and the Mac goes to sleep. Other than that, once I did the reinstall, I have had no other issues.