"iMac Pro" kernel crash

I am extremely furious at this point. I can no longer export any video from FCP X. I know I have issues exporting 4K video but now I cannot export even 1080p video. So this machine became absolutely useless. Sorry, but I have to rely on a machine to edit and get video content out there. This is not it. Im gonna try to get a refund and get build a windows machine. I give up.

After several days of no issues, a few minutes ago I got a "computer restarted because of a problem" message out of the blue. I simply turned on the Mac and got the message followed by the usual "send to Apple" dialog:

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 2.3.2 (15P6059)","timestamp":"2018-08-12 15:54:42.72 +0000","incident_id":"F324FAC8-004C-47C5-99D6-C81B7DB4B873"}

{

"binaryImages" : [

[

"ea400d2a-e41f-6e4e-0b32-a5e6010e1110",

18446743936270598144,

"U"

],

[

"00000000-0000-0000-0000-000000000000",

0,

"A"

],

[

"5abdfdb4-5f50-3aef-abc4-2c2671a4a572",

6442450944,

"S"

]

],

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

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-08-12 15:54:42.48 +0000",

"incident" : "F324FAC8-004C-47C5-99D6-C81B7DB4B873",

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

"macOSOtherString" : "\n** In Memory Panic Stackshot Succeeded ** Bytes Traced 521168 **\n",

"macOSPanicFlags" : "0x4",

(...)

etc etc.

Very bad.

Happen'd three times to my MBP13".

Two times during watching a HD-Movie from the iTunes-Store in iTunes. Both times running on battery.

The picture froze, then goes to black and the computer dosen't responded to anything more, except forcing a reboot. Both times in the last 2 days. No external devices or adapters attached.

The third time during typing this comment: the screen went almost completely black, except half an inch at the top, and nothing reacts. So I have to force a restart - no Crash-Report this time.

Usually I work for hours running the Pioneer Rekordbox DJ-App with an external Samsung T5 SSD, Apple MagicKey & MagicPad, multiple (min. 3) DJ-Controllers, with multiple soundcards, some on an USB-C multihub and even an Acer USB-C-Powered Monitor. No issues then :-O

Also Adobe Lightroom with an external LaCie D2 with Thunderbolt3; also no issues.

I have also a 2017 MBP15" who has problems with the internal speakers. :-(

I bought the 2017 MBP after my 2011 MBP's-GPU died from the known graphics-problem - also happend to a friends 2012 MBP :-((

This *****. All the time new problems. For the first time after taking delivery of this months ago, my Logitech mouse was the subject of a new problem. Suddenly with no warning, it stopped functioning and the red LED just started to pulse every second, sitting down on the mouse pad and not being touched. When you moved the mouse, it would move the cursor an inch or so and stop. Rebooted and of course everything is back to normal. What next? Flashing screens?

Same here always when resuming from sleep, it just goes black and crashes. Well I'll just to go the apple store and complain, they'll replace it with a new one. Apple can eat the cost that happens with this even though it feels like a software bug...

I was complaining that FCP X crashes the iMac Pro when exporting 4K video. I was very familiar with FCP but I wanted to see if switching to another video editing software would get the same result. So I switched to Adobe Premiere Pro. Sure, I had to learn how to use it, but I was shocked to see that it doesn't crash the iMac Pro at all. I am now an Adobe customer. One of the downsides is that it takes more time to export a video. I have a feeling that Premiere Pro doesn't use Metal. This leads me to think it has something to do with Metal, in my case. I know FCP was optimized to take advantage of Metal and the new hardware in the iMac Pro. So there is hope for people who do video editing.

"Luckily" I'm not hit that frequent with it, but it's crap quality Apple is delivering. If the throw in new hipster features they should get their **** tested and quality assured. It's the world's valuable company not being able to deliver high quality? That's just a joke...

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 2.3.2 (15P6059)","timestamp":"2018-09-17 18:46:21.50 +0000","incident_id":"82037917-46FE-4770-A2AD-115B2865D2C5"}

{

"binaryImages" : [

[

"ea400d2a-e41f-6e4e-0b32-a5e6010e1110",

18446743936270598144,

"U"

],

[

"00000000-0000-0000-0000-000000000000",

0,

"A"

],

[

"5abdfdb4-5f50-3aef-abc4-2c2671a4a572",

6442450944,

"S"

]

],

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

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-09-17 18:46:21.38 +0000",

"incident" : "82037917-46FE-4770-A2AD-115B2865D2C5",

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

"macOSOtherString" : "\n** In Memory Panic Stackshot Succeeded ** Bytes Traced 201312 **\n",

"macOSPanicFlags" : "0x404",

"macOSPanicString" : "panic(cpu 30 caller 0xffffff8012eba24d): \"a freed zone element has been modified in zone kalloc.160: expected 0xe4988e30b2c8b0c4 but found 0x94, bits changed 0xe4988e30b2c8b050, at offset 0 of 160 in element 0xffffff814879aa00, cookies 0x3f001126c1046af6 0x53521f9ad6164dd\"@\/BuildRoot\/Library\/Caches\/com.apple.xbs\/Sources\/xnu\/ xnu-4570.71.2\/osfmk\/kern\/zalloc.c:1122\nBacktrace (CPU 30), Frame : Return Address\n0xffffffce52053970 : 0xffffff8012e6c1c6 \n0xffffffce520539c0 : 0xffffff8012f95274 \n0xffffffce52053a00 : 0xffffff8012f87544 \n0xffffffce52053a70 : 0xffffff8012e1e1e0 \n0xffffffce52053a90 : 0xffffff8012e6bc3c \n0xffffffce52053bc0 : 0xffffff8012e6b9fc \n0xffffffce52053c20 : 0xffffff8012eba24d \n0xffffffce52053c80 : 0xffffff8012eb9b20 \n0xffffffce52053cd0 : 0xffffff8012eb8523 \n0xffffffce52053e00 : 0xffffff8012e77c14 \n0xffffffce52053e70 : 0xffffff80132c7a86 \n0xffffffce52053eb0 : 0xffffff80132d3ccc \n0xffffffce52053ef0 : 0xffffff80132d3c13 \n0xffffffce52053f40 : 0xffffff80132d8c5b \n0xffffffce52053fa0 : 0xffffff8012e1d557 \n\nBSD process name corresponding to current thread: kernel_task\n\nMac OS version:\n17G65\n\nKernel version:\nDarwin Kernel Version 17.7.0: Thu Jun 21 22:53:14 PDT 2018;

I can't believe that we are one day away from another major macOS release and this hasn't been fixed. A few more months and we can call it a year since it was first reported. This is just outrageous. It pains me to say this and I really can't believe I'm typing this, but this will be my last desktop computer I buy from Apple. I still love the iPhone and iPad but I'll chose to build my own machine for heavy duty tasks.

You, sadly, are right. I could have had two maxed out iMacs for the cost of this, and the time i have wasted on this is clearly more than the time saved from having more cores.

But their utter failure in accepting responsibility for this and solving the problems is the final nail in the coffin.

Anyone have the base Vega 56 graphics card having this issue? I currently have the iMac Pro with the Vega 64 but for a short time I had a iMac Pro with the Vega 56 and didn’t have any of these crashing issue. Curious.

I have upgrade system to Mojave， but this problem still exists!

Now there will be a random black screen shutdown.

Not working at all!!! This model has been released for a year, and I have endured this problem for half a year!!!

-------------------

iMac Pro(2017)

3.2Ghz Intel Xenon W

32GB 2666 MHz DDR4

Radeon Pro Vaga 56 8176MB

macOS Mojave 10.14(18A391)

Yeah definitely fewer crashes here, pretty much 0 since I updated to Mojave, but admittedly I'm not pushing the machine that hard so hard to tell if fix or improvement or dumb luck.

Really disappointed in my purchase however, could have spent almost half and got a loaded iMac 5K and pretty much have as much utility at this point.

My iMac Pro 10 core has started having Kernel Panics in recent weeks. A few a week. Often when idle. Only peripheral that is involved is Thunderbolt 3 to 2 adaptor for my RME 802 audio interface. Up until recently this set up had very few if any Kernel Panics. I haven't changed anything in my set up either. Diagnostics and Disk utility reveal nothing different. Bit of a mystery.

Thanks. Yeah I'm aware of an issue with the adaptor. But for some reason I've had very few if any Kernel Panics since May of last year when I got the iMac Pro. Nothing has changed in my set up. Only factor I can think of right now is that a third-party plug-in in Logic Pro X is crashing the iMac Pro. That or the size of my Logic Pro X projects, which are quite large at the moment.