"iMac Pro" kernel crash

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.

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.

Not sure where everyone is standing. I returned my iMac Pro in April but still have bug reports outstanding with Apple for the numerous hardware kernel panic issues.

Apple has closed the issue of iMac Pro kernel panic during SMC reset as "resolved in internal tests" and should be fixed in upcoming10.13.6. Not sure where that leaves sleep panics, though.

I also have issues w/ sleeping, similiar to what's been described. I've turned the features off (in Mac OS), due to the problem -- however, I have no issues w/ Windows sleeping/hibernating.

I can also confirm that the spontaneous "Bridge OS 2.x" crashing still exists (for me) in 10.13.5. I actually have had more crashes since the upgrade, however since it's ~random, I can't attribute them to the update. My ticket is still being worked by Apple engineers -- and I hope to hear more details/direction this weekend.

Once again, I expressed that I believe that it is somehow related/correlated to the new T2 co-processor (due to the ARM64 kernel reference, in the error message body), however they have not confirmed/denied anything at this time.

Nevertheless, I hope that we hear something soon... I've had these (volatile) issues for 6 months. 😕

I'm still awaiting information from the engineers on my latest ticket (06/06/2018). It's been weeks, w/ no input -- though I've been keeping a pulse with the case worker. Nevertheless, I will say: I've reinstalled twice (via Repair Partition method) -- at the advisement of Apple Engineering -- and reinstalled a third time (via Internet Recovery method). Reinstalling the OS has not solved the problem. Removing 'legacy' external drives has not solved the problem. Uninstalling virus protection software has not solved the problem. I wouldn't advise anyone to reinstall their OS, without additional cause or a knowledge-base article (for this specific issue). As of this weekend, I've updated to the latest version of Mac OS (10.13.5), and I have experienced this issue three times since the update.

I highly suggest everyone call Apple support. I have been in touch and they are gathering data around the crash to understand what's happening. Given my computer ran for 6 months with no issues, and this only cropped up lately, Im inclined to believe this is software related. But I guess we'll see what the outcome is.

I've been in talks with them also. I got a second call, this time asking for a FCP project that crashes the iMac Pro. Also, while it has been crash free in sleep mode for the past 1 week and a half, yesterday it restarted again. So no, turning off all the power saving options and the apple watch login doesn't fix the problem completely. So the problem goes deeper than just settings.

So, our dear friend Kevin Parrish (over at digitaltrends.com) has posted an article outlining this issue. With the new MacBook Pros (2018) also experiencing/exposing this issue, Apple may soon admit the problem as systemic, treat it as such, and offer an appropriate resolution.

https://www.digitaltrends.com/computing/apple-t2-chip-may-be-causing-imac-pro-ma cbook-problems/

They’re not keeping silent. They’re actively trying to work out what’s causing the crashes. In my case, tech support collected a bunch of information and narrowed down the culprits to three possible applications that were causing crashes. In my case, it was a backup application that was backing up a Thunderbolt drive. I was in the process of switching backup applications and had the luxury of being able to uninstall the problem app. I’ve since not seen any crashes. If the application in question was something I needed for work, It would be a different story for me. But I’m glad they’re working through the issues.

Other than this issue cropping up for me (only recently) I’ve had no other issues, and found that the iMac Pro is probably one of the best Macs I’ve ever owned. The screen is amazing, and it’s a solid performer.

UPDATE.

1. Yesterday, the issue (frozen mouse&keyboard, then black screen) occurred when attempting to unzip and install a huge Piano Library via the Continuata Connect app to a Thunderbolt 2 ssd connected via the Apple adapter Thunderbolt 3 > Thunderbolt 2.
2. Similarly, the issue occurred when attempting to manually unzip at once all the downloaded 31 Sample files (±30Gb) using the Apple Compression Utility.
3. Today a further test was made unzipping the very same bunch of files, but using the latest version of Stuffit Expander, instead, and saving the extracted files in the Documents folder on the iMac 1Tb flash drive. It seems that Stuffit does not perform a parallel extraction. Anyway, no freeze and/or black screen occurred. The iMac Pro, so far, is rock-solid again.
4. My best guess (but I'm not an geek at all!) is that there is an issue either with the Continuata software (the latest available version of Connect dates back to 2015: avoid it, just in case) and, possibly, a bottleneck when transferring huge amounts of data via T3-to-T2 external device. But, as I said, I'm not a technician.

To me, now the ball is down to Apple engineers.

I got the new iMac Pro in March specifically for FCP. Unfortunately, FCP crashes the new iMac Pro reliably whenever I try to export video (pretty basic) and at other times as well. After isolating the problem to the point where the FCP lab could duplicate it without any of my media, the "captured" my unit and I bought another one just like it (maxed out). Same problem and my iMac Pro has been crashing every day since then.

Also, FCP totally fails to take advantage of those 18 cores I have in there. It still does practically everything single-threaded, even though video is the perfect application for multi-processing. My $2K MacBook Pro is only about 25% slower than my $14K iMac Pro and it never crashes.

I am hopeful that the new Mojave release will fix both of these problems, but I am out of town and won't be able to test that there until next Wednesday. Stand by for my next report.

Since I uninstalled Continuata Connect, an old small software (2015) requested by some producers to download their sound libraries, the frozen-desktop/black-screen issue disappeared. Unfortunately I recently had to reinstall Connect for a single purchase, but the issue did not happen anymore. Couldn’t it be something related to third party software or to a specific app preferences?

Just encountered this issue... Screen went black while I was working in FCPX, and the system froze. This occurred while transcoding 4k video to proxy within FCPX, using a LaCie 32TB external drive with Thunderbolt 2 connection and Apple Thunderbolt 3 adapter. No daisy-chaining. I've disabled PowerNap.

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 2.3.2 (15P6059)","timestamp":"2018-10-22 18:10:53.25 +0000","incident_id":"9E8E9731-CD20-42EC-8607-438E3521F792"}

{

"build" : "Bridge OS 2.3.2 (15P6059)",

"product" : "iBridge2,1",

"kernel" : "Darwin Kernel Version 17.7.0: Fri Jun 15 23:12:25 PDT 2018; root:xnu-4570.71.1~3\/RELEASE_ARM64_T8010",

"incident" : "9E8E9731-CD20-42EC-8607-438E3521F792",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-10-22 18:10:53.21 +0000",

"panicString" : "panic(cpu 0 caller 0xfffffff0132ab984): macOS watchdog detected\nDebugger message: panic