"iMac Pro" kernel crash

Hi all,

i was having this problem too. I had replaced my ram 5 years a go and getting this error for a year. Also my macbook was crashing and restarting every 4 hours. Some times it was not booting up and i had to install OSX ( My mac is late 2011 and i started to think that apple was slowing down my computer and crashing to buy a new one.). Last time of crash, i did a macbook hardware test and got 4mem/9/4000000000 0x830ec598 error. When i ran this test before the osx crashing i did not get any error. So i replaced my ram with the old ones. Voila! Problem solved.

I hear you. Yes having exactly same issues - System - iMacPro (2017) MacOS Mojave V 10.14.2, 3Ghz Intel Xeon W Memory 128GB 2666 MHz DDR4, 10 Cores, Radeon Pro Vega 56 8176 MB - purchased mid 2018, with extended Apple care warranty - set me back $15,000 AU.

I seem to get the Kernel panic, finder crash and auto reboot when I run a large project using EW Play and Hollywood Strings Diamond ed on Logic Pro. I am also using VEPRO on the same machine for the loading of project. This helps immensely with Audio inside Logic project (my orchestral template is 2,500 midi tracks, basically the full Hollywood Orchestra Diamond Ed. loaded) I have done a fresh reinstall of OS today after crash yesterday.

Have read all forums here and turned off Power nap and disconnected daisy chain EXHDD. I have 2 EXSSD's connected via dedicated Th.3 leads where libraries are stored. I have HWStrings diamond on one and the other HW Orchestra families on the other. Currently testing the largest String multi patches in Play standalone and they seem to be loading fine and load way quicker btw. About to run VEPRO and load the string patches and connect to Logic project again to see if it crashes. Will update.

This points to hardware problems rather than software cause of the kernel panics.

Hi.

Are you experiencing high temperatures in your studio, by chance? I have had lots of KP when the summer temp was around 38°C, and I suspected an environmental (thermal) issue.

Interesting - I'm still having panics but I'm not daisychaining any drives at all, there's a daisychain connected to 1 of the ports on my iMac Pro but 95% of the time only the 1st device on the chain is actually turned on, and I've definitely had panics when just that device has been on.

Any chance you can let us know your case number with Apple? The guy assigned to my case seems adamant that the next step for me will be a full reformat & reinstall, which I'd prefer not to do if Apple have already recognised a cause

Good question! Thunderbolt 3 to Thunderbolt 2 adaptor initially to transfer files off one of my G-Tech Studio RAIDs, but as the errors continued, I removed all the adaptors. Even with just the NIC connected and nothing else (and copying files off the SSD to the SSD on my server) the same kind of crashes happened.

Nikki.

A lot of my panics were also in the middle of the night when the machine was idle - I would come back to the machine in the morning and see the "Your Mac has restarted because of a problem" error message, and there would be a fresh crash log with the same old "Bridge OS" line in it.

It ***** that users can go for extended periods with no issues, and then get a panic out of the blue, like you have. I've tried pretty much everything that's been discussed in these threads as a possible fix for the problem, gone for a few days without crash (thinking to myself "Oh hey I guess that fixed it"), and then had one overnight while the machine was idle like this, or sometimes 2 or 3 per day during use.

Something is definitely up

Hey, sorry to tell you but I think it's a systemic problem with the current iteration of the iMacs and MacOS. I've gone through all your steps three times over (on three separate iMacs) with the same configuration as yours and the problem is still here. Irritating as every time I call they go through that process because it's on their scripts, I just stopped calling AppleCare and am hoping and waiting for some kind of (hopefully software) fix.

P.S. I have NO hardware attached to my iMac other than an ethernet cable, not even a USB hub, and the problem still occurs, so no, unplugging your thunderbolt and USB devices will not fix the problem and frankly defeats the purpose of having an iMac with those ports.

I have a new iMac Pro 8 core, 32 GB ram, 1 TB SSD and Pro Vega 56. The machine has been crashing regularly when in sleep mode due to the iBridge Type_Bug 210. I tried just about everything suggested on this forum to no avail. Had two more crashes in the last 12 hours. I had three sessions with Apple Support. They believe it is likely to be a hardware problem and suggested the machine is returned. They think the problem does not exist on all Mac Pros. I'll be returning my iMac Pro on Monday.

Has anyone actually resolved this issue and has no more kernel panics due to Bug 210?

I returned my 8-core/64GB/2TB/64Vega this morning for a refund. My machine kernel panicked on any SMC reset, with certain (otherwise good) drives attached via USB, when opening `.webloc` files with Firefox, and of course the random kernel panics related to 'Sleep Wake Failure' overnight.

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.

Sorry for this intrusion, but I want to get to this threads followers and contributors... I wanted to say the original iMac Pro hasn't failed in months after removing all the checks in the sleep settings and separating the attached drives.

But something interesting is happening.
I always leave activity monitor running with "Command-3" window showing (the individual processor core / hyperthread bar charts) to gauge the CPU use.
Suddenly, I'm getting these random core spikes showing up.
I didn't screen grab the really busy ones I saw, which I should have done, but here's an example of just a couple spikes.
Not thinking it's the 10.13.4 update, that was back in March.
Any ideas or similar situations?