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.

"iMac Pro" kernel crash

I have a new iMac Pro 8core 32gb ram 1tb SSD and Pro Vega 64

(attached are a usb hub, usb audio speakers, usb trackball, thunderbolt 3 raid with a thunderbolt 2 raid chained to it via thunderbolt 3 to thunderbolt 2 adapter)


I am looking for input


Within the first 8hours I had two kernel Panics but now seem ok...my iMac shut off and rebooted by itself...both logs have {"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_versio n":"Bridge OS 2.0 .....


To note my Logitech software wasn't recognizing my trackball but it worked ...after crashes I unplugged and replugged the trackball and the software was able to see it.


Should I be concerned?

iMac Pro (2017), macOS High Sierra (10.13.2), null

Posted on Jan 9, 2018 7:25 PM

Reply
277 replies

Jan 31, 2018 1:28 PM in response to mustgroove

On my entry level iMacPro i started to get nearly daily kernel panics starting on Jan 22nd. (also Bridge O2 2.01) First two weeks (from Jan 9th to Jan 22nd) i had no problems. All crashes happened while i was away from the iMac. Started to slowly disconnect all devices (Now only a Scanner conneted to a USB3 Port remains). Will turn off PowerNap and disconnect the scanner next).


Am also having strange network hiccups, where it looks like the network connection is lost, but comes back after a couple of minutes.


Since i had no crashes when due to the migration to the new mac a lot more devices were attached to the iMac i suspect, that some system software update introduced the problems.

Jan 31, 2018 4:14 PM in response to Nikki Gordon-Bloomfield

So this is crazy. No I haven't been getting crashes lately, but... I suspect the CPU has been radically scaled back. I've been importing, editing and exporting videos with iMovie. I've used Activity Monitor with the graphic CPU history displays per core and watched iMovie render at full capacity. Repeating that now, I only seem to be able to get to about 12 percent. I can find nothing else that is waiting - plenty of network, disk bandwidth, memory... so I'm at a loss. It's almost like Apple sent out a "throttle back" command to the iMac Pro!

Feb 1, 2018 3:51 PM in response to mustgroove

we also turned of the new boot security via recovery mode/security. also no display sleep mode. no screensaver.

we use storage over 10GbE ethernet server. sonnet thunderbolt 3 to DisplayPort adapter to power two external 4K Computer displays.. one apple tb 3 to 2 adapter with Blackmagic ultra studio 4k to video monitor. focusrite usb audio interface. but it kept crashing after without any external devices, just after leaving it alone for some minutes. now without power nap, its gone.

Feb 2, 2018 8:19 AM in response to MFASM

So this is crazy. No I haven't been getting crashes lately, but... I suspect the CPU has been radically scaled back. I've been importing, editing and exporting videos with iMovie. I've used Activity Monitor with the graphic CPU history displays per core and watched iMovie render at full capacity. Repeating that now, I only seem to be able to get to about 12 percent. I can find nothing else that is waiting - plenty of network, disk bandwidth, memory... so I'm at a loss. It's almost like Apple sent out a "throttle back" command to the iMac Pro!

UPDATE: And after a week, after turning off Power Nap and replacing the crashed external drive, I had my first hard reboot at 2:07AM when nothing was happening. No logs that i can find, just a hard reboot. This is starting to get really bad.

Feb 2, 2018 8:26 AM in response to sysengr-2

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

Feb 2, 2018 11:52 AM in response to mustgroove

Thats really not okay for a machine like that. We will watch that and post it if we will see more crashes. Yes it was a Problem when Idle, just when nobody touched the mouse or keyboard for some time. So we could not render out a feature length movie from final cut pro x without having someone sitting next to it just clicking around for nothing. Its a "pro" machine.. so u just can work on it.. hehe 😀 ...as I said before, for now what I wrote above helped. we will see.. I hope its just the t2 chip and the new bridge os and apple will fix it soon. unfortunately this is not what a 9k machine should work like. do you read this apple?

Feb 20, 2018 8:24 AM in response to MFASM

Me too, 8 core/64GB/2TB SSD/VEGA 64.


Kernel Panic in low power mode even in Safe Mode. I've gone through all the steps with Apple several times so Apple sent me two replacements (to be fair I requested the first one separately as UPS delivered it frozen), same issue, eventually the Mac restarts with a kernel panic while in low power mode.


At this point unlikely that it's a hardware issue related to your or my specific unit but either an OS/Kernel glitch or an architectural issue related to the new iMacs.


So my choices are either wait and hope for Apple to release a software fix or return it, doing another exchange seems futile.


Looking at the Kernel Panic dumps looks like someone MAY have been working on it, the Kernel Version got bumped from 17.3.0 in January to 17.4.0 yesterday and it "feels" like I'm seeing fewer panics. Where it used to panic once or twice a day it now appears to panic once or twice per week.


Currently I'm leaning to wait for Apple to fix this.


Also, shout out to the AppleCare and Apple Store Genius people who have been great in trying to get this resolved and from experience no other company has treated their customers as well as Apple has treated me with this issue.

Feb 22, 2018 7:19 AM in response to MFASM

So here's something new. I have an old game, RollerCoaster Tycoon 3 Pro, from the App Store, that runs fine on iMac 2011 but fails on iMac Pro, about 70% of the time, in the first 60 seconds after launch. The other 30% it runs without failing. I started tracing the crash report back, and I ran into an error some people are having with their iMac Pro SSDs - when you run a disk check on the SSD you get this error:

warning: crypto_val: object (oid 0x4): invalid state.major_version (0)

warning: crypto_val: object (oid 0x4): invalid state.key_os_version (0x0)

warning: crypto_val: object (oid 0x4): invalid state.key_revision (0)

Apple can only tell people to reformat, reload and in most cases this solved the problem. Pretty drastic and really bad... I haven't done that yet, but am hoping to find out why iMac Pro users are getting this error and what it is. I mention this because it ties back into disk I/O issues I mentioned earlier... and of course because its another Apple failure with the iMac Pro!

Feb 24, 2018 10:51 AM in response to MFASM

I have the exact same issue. I called AppleCare and the told me to bring the iMacPro back for a replacement machine. I did that and it did not solve the problem. The new machine had the exact same kernel panic crashes. Then they told me to erase the machine and reinstall from clean copy of OS. They told me NOT to use my time machine backup of my old machine and to reload each item and all software manually from scratch. I had no idea how long this would take. My first mac was 1985 512K so I have been collecting stuff for a very long time. No worries, I did not put any of the system 9 stuff on my new macs for many years now.


I invested 3 or 4 hours in loading things on the new clean system and then went home for the night. Came in on Saturday to see how the new system is doing and found it had crashed overnight. Good news is that I no longer need to keep avoiding migration from my old system and get all my stuff back in one easy restore. Bad news is that I still don't know what the issue is. AppleCare tech does not want to look at my crash logs. That seems crazy as I would think Apple would be all over this. I am going to try turning off the power nap and some of the other ideas listed in this fourm. If that does not work, I will be returning the iMac Pro for refund. I did not NEED to upgrade to this unit, I did it to avoid potential issues with my aging 2011 iMac 27". Turned out to be a big mistake.


Does anyone have any updates on what did work to solve this problem?

Feb 26, 2018 5:03 AM in response to Jeeper plow guy

First, what’s connected on Thunderbolt? I stopped daisy-chaining any devices at the strong recommendation of Apple, this is very important. This made a difference.


Second, change Energy Saver settings. Most important turn off Power Nap. This also made a difference in reducing the problem.


Third, don’t unlock with Apple Watch. Really! I can’t go into details on this other than to say there is a problem that is being addressed by Apple Engineering.


Fourth, (which you already did) First Aid your internal SSD (active mode is OK) to see if it throws 3 different errors that include:

warning: crypto_val: object

Apple says wipe and reload from scratch. I have not done this, but am concerned about what this means.


There you have it. I have gone from 3 PANIC’s a day to none in over a week. We’ll see...

Mar 7, 2018 8:25 AM in response to danieljag1

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.

"iMac Pro" kernel crash

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