"iMac Pro" kernel crash

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!

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.

I hear you!

I've just heard that my replacement machine is on the way, although I have no expectation that this will solve the problem.

Apple is going to take my current machine and examine it in Cupertino. In the meantime? I'm back to editing large video projects on a MacBook Pro 😟

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?

Im having this problem as well with my iMac pro(base config). I can say without a doubt this is the least reliable mac Ive ever used. I have had more kernel panics with this mac since february than Ive had since Ive used a mac(since 2008). Im starting to lose my patience with this one. a 5 thousand dollar computer shouldn't crash like this.

I have the same kernel panics due to iBridge type bug 210 with my new iMac Pro. I tried everything that has been suggested on this forum but the crashes continue. Apple Support has been notified.

How is your machine? Do you still experience kernel panics?

I have the same problem (10 core, 1 TB storage) since March the 19th. Since this date, more or less 4-5 restarts / crashes (especially during idle times, sleep wake failiure) per day. No single crash / kernel panic while working even with heavy load! No external equipment!

Today I've installed 10.3.4 Beta 7 without any success :-( Same behavior!

I've tried all described solutions - fresh install, disable security, power nap etc.

Any German member here who could share experience how Apple / a distributor handled this problem in Germany. My iMac Pro is roughly 6 weeks old. Anyone tried to replace the machine.

Hi everyone wondering what to do as I also have random kernel panics mostly at night?

I have a 10 core 64gb 2TB iMac Pro.

Is it worth calling Apple support at this time. Will the same crashes happen if they get me a replacement machine?

Some on here have recommended not daisy chaining on thunderbolt? I bought this machine with the plan of daisy chaining several drives.

Thanks

Hey, with respect to you an Mike, more than one person have reported the problem with absolutely nothing attached on any port (I have Ethernet plugged in). In my case there’s nothing to unplug.

TB may exacerbate the problem but I guarantee it’s neither the problem nor the solution.

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"}

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.

Gee, thanks Apple. That last 2018-001 "Security" update screwed up the fix you put in earlier for the second monitor graphics screwups... so we're actually going backwards here, not forwards... does this look like how a CPU display is supposed to look?

Never got around to getting rid of the crypto val stuff, but I figured I'd do that tonight. re-formatted, reloaded from time machine, disk utility now runs clean, system still can't sleep. 30 seconds and the fan turns on, the screens come up and system beeps at me.

This is really getting old.

I have same problem, It seriously affected my work. 😰

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 2.3.1 (15P5064)","timestamp":"2018-06-10 19:29:54.48 +0000","incident_id":"A6E6A47A-C0D1-4548-9846-B839CF4B"}

{

"build" : "Bridge OS 2.3.1 (15P5064)",

"product" : "iBridge2,1",

"kernel" : "Darwin Kernel Version 17.6.0: Sat May 5 19:46:24 PDT 2018; root:xnu-4570.60.21~23\/RELEASE_ARM64_T8010",

"incident" : "A6E6A94A-C0D1-45r8-98r6-B8394CF0B",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-06-10 19:29:54.41 +0000",

"panicString" : "panic(cpu 0 caller 0xfffffff014aae984): x86 CPU CATERR detected\nDebugger message: panic\nMemory ID: 0xff\nOS version: 15P5064\nKernel version: Darwin Kernel Version 17.6.0: Sat May 5 19:46:24 PDT 2018; root:xnu-4570.60.21~23\/RELEASE_ARM64_T8010\nKernelCache UUID: 82688F4A0C28C17581768EF79472E265\niBoot version: iBoot-4076.60.11\nsecure boot?: YES\nx86 EFI Boot State: 0xd\nx86 System State: 0x0\nx86 Power State: 0x0\nPaniclog version: 9\nKernel slide: 0x000000000e200000\nKernel text base: 0xfffffff015204000\nEpoch Time: sec usec\n Boot : 0x5b1d599e 0x000b79e9\n Sleep : 0x00000000 0x00000000\n Wake : 0x00000000 0x00000000\n Calendar: 0x5b1d7c15 0x0007eca4\n\nPanicked task 0xffffffe0007c85c8: 2461 pages, 166 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe000b72370, backtrace: 0xffffffe01738b530, tid: 337\n\t\t lr: 0xfffffff0153f96bc fp: 0xffffffe01738b670\n\t\t lr: 0xfffffff0152e15f4 fp: 0xffffffe01738b680\n\t\t lr: 0xfffffff015313a44 fp: 0xffffffe01738b9f0\n\t\t lr: 0xfffffff015313dd4 fp: 0xffffffe01738ba50\n\t\t lr: 0xfffffff015315914 fp: 0xffffffe01738ba70\n\t\t lr: 0xfffffff014aae984 fp: 0xffffffe01738bae0\n\t\t lr: 0xfffffff014ab0bc8 fp: 0xffffffe01738bb80\n\t\t lr: 0xfffffff014aae13c fp: 0xffffffe01738bc00\n\t\t lr: 0xfffffff014a6daa4 fp: 0xffffffe01738bc30\n\t\t lr: 0xfffffff0157710b8 fp: 0xffffffe01738bc60\n\t\t lr: 0xfffffff015770a10 fp: 0xffffffe01738bc90\n\t\t lr: 0xfffffff0152ec500 fp: 0x0000000000000000\n\n",

"panicFlags" : "0x102",

"otherString" : "\n** Stackshot Succeeded ** Bytes Traced 76416 **\n",

"macOSPanicFlags" : "0x0",

"macOSPanicString" : "BAD MAGIC! (flag set in iBoot panic header), no macOS panic log available",

"memoryStatus" : {"compressorSize":0,"compressions":0,"decompressions":0,"busyBufferCount":0,"pa geSize":16384,"memoryPressure":false,"memoryPages":{"active":4806,"throttled":0, "fileBacked":7096,"wired":4084,"purgeable":20,"inactive":1389,"free":16903,"spec ulative":2696}},

This is still continuing for me as well. I am not super thrilled at the prospect of a full OS reinstall. I have a ton of challenge/response apps to deal with an this just *****. I did a few of the configuration changes mentioned in this thread,(disable powernap, unlock with watch) but I am noticing an uptick in kernel panics lately. I think Im going to have to return this one...