"iMac Pro" kernel crash

Same story for me but I had my motherboard replace twice and then got a new machine; still crashes; kernel panic; everyone thinks it is the embedded T2 chip; but Apple Support will not own this; just this support group; and numerous websites that cater to Apple owners. I just greatly disheartened that Apple has not come out and said: "We have a problem and we are working diligently to fix and will replace your machine or provide a new OS that will fix this. Just hang in there. We got this. We are on this." My customer support at Apple went to highest level and she was wonderful. Wonderful. But keep telling me that know one is admitting or telling her this was recognized problem. Wow. Sales and product reputation over being honest when a well known problem is present. I am guessing the new OS well fix???? What does everyone else think? Also I cannot keep my computer from going to sleep and when it does it crashes.

I think Apple has this blocked at a lower level to save people’s careers who pushed the design. I’m certain the issue is fully understood but would require a substantial redesign of costly components, which would take a massive effort, huge costs and would still be a “best guess”. So without senior management owning the issue, the lower management will do its best to bury the negative press. Replacing systems and motherboards is a complete waste of time. If you cannot live with what you have today, get a refund and move on. If you want to keep trying, you must reconfigure and fully reload your system until you find a combination that works well enough. Be prepared to replace both peripherals and associated software. This is what I did and eliminated panics and reboots, but have a system which can’t sleep and hits the remaining external storage every 90 seconds doing something I cannot find. Good luck!

I purchased a new iMac Pro 8 core in April 2018. I've had continual major issues with it since day one. Kernel panics, lost data, corrupted ArchiCad 21 and 22 project files. It's losing settings for email and also has issues that are unrelated to ArchiCad. I had it in service with Apple Support and they did not diagnose nor fix the problems correctly. Calculations that should be a breeze for this computer bog it down (in Adobe Illustrator and other software too).

I'm putting it back in my Apple Support service center this week. I've had Apple computers since 1983 and am an advanced user. So far this is the worst experience I've ever had with an Apple product. According to Apple certified techs, who don't work for Apple but work for independent repair shops, iMac Pros are having major issues and Apple does not yet have the diagnostic tools to repair them, plus the techs are not receiving training in how to repair them.

I hate to say it... but I cannot recommend purchasing an iMac Pro. High Sierra may also be part of the problem, but there is no excuse for releasing a product that is this expensive without having repair protocols in place.

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.

macOS Mojave fixes absolutely nothing regarding this issue. See bellow:

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 3.0 (16P375)","timestamp":"2018-09-25 23:33:33.39 +0000","incident_id":"E51E345D-4EFF-4F11-B23A-006CBF469125"}

{

"binaryImages" : [

[

"fb8d452c-2a8d-17ca-c5e3-a3a22ee2ea50",

18446743936270598144,

"U"

],

[

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

0,

"A"

],

[

"f1e4e7eb-d326-3fe5-b9d5-78a7ef251f3e",

6442450944,

"S"

]

],

"build" : "Bridge OS 3.0 (16P375)",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-09-25 23:33:33.24 +0000",

"incident" : "E51E345D-4EFF-4F11-B23A-006CBF469125",

"kernel" : "Darwin Kernel Version 18.0.0: Thu Sep 6 18:24:30 PDT 2018; root:xnu-4903.201.2~72\/RELEASE_ARM64_T8010",

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

"macOSPanicFlags" : "0x4",

.

.

.

.

.

.

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.

Sorry to disappoint you but macOS Mojave fixes absolutely nothing regarding this issue. See bellow a log of the crash that happened yesterday one day after installing Mojave.

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 3.0 (16P375)","timestamp":"2018-09-25 23:33:33.39 +0000","incident_id":"E51E345D-4EFF-4F11-B23A-006CBF469125"}

{

"binaryImages" : [

[

"fb8d452c-2a8d-17ca-c5e3-a3a22ee2ea50",

18446743936270598144,

"U"

],

[

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

0,

"A"

],

[

"f1e4e7eb-d326-3fe5-b9d5-78a7ef251f3e",

6442450944,

"S"

]

],

"build" : "Bridge OS 3.0 (16P375)",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-09-25 23:33:33.24 +0000",

"incident" : "E51E345D-4EFF-4F11-B23A-006CBF469125",

"kernel" : "Darwin Kernel Version 18.0.0: Thu Sep 6 18:24:30 PDT 2018; root:xnu-4903.201.2~72\/RELEASE_ARM64_T8010",

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

"macOSPanicFlags" : "0x4",

.

.

.

.

.

.

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)

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?

I ran Titanium Maintenance on my Mac: perhaps it helped somewhat in reducing the issue. Try it at your own risk: in the worst case it will do nothing, but I suppose it won't damage any data on your Mac either (perform a backup first, just in case).

https://www.titanium-software.fr/en/maintenance.html

Today another frozen/black screen after a long while without the issue.

I was extracting with The Unarchiver 4.0 a huge (44,9 Gb) splitted .rar archive on an external SSD via Thunder3->adapter->Thunder2.

Suddenly I got frozen mouse and keyboard and, after 1 minute or so, the display turned black.

I had to shutdown the iMac Pro pressing the power button.

Like two months ago, the issue arose when working with large files and external disks.