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 restarting because of a problem?

iMac Pro intially booted as a Mac Pro backup, then reverted and reinstalled fresh High Sierra because of some compatibility issues, now getting forced restarts with this error code, thank you for any help!


{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 2.0 (15P2064)","timestamp":"2018-01-12 06:47:28.38 +0000","incident_id":"3D1765A6-5583-44EF-9F16-BABB863EF278"}

{


"build" : "Bridge OS 2.0 (15P2064)",


"product" : "iBridge2,1",


"kernel" : "Darwin Kernel Version 17.3.0: Thu Nov 30 19:54:28 PST 2017; root:xnu-4570.37.11~2\/RELEASE_ARM64_T8010",


"incident" : "3D1765A6-5583-44EF-9F16-BABB863EF278",


"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",


"date" : "2018-01-12 06:47:28.05 +0000",


"panicString" : "panic(cpu 0 caller 0xfffffff0070fb3ec): macOS panic detected\nDebugger message: panic\nMemory ID: 0x6\nOS version: 15P2064\nKernel version: Darwin Kernel Version 17.3.0: Thu Nov 30 19:54:28 PST 2017; root:xnu-4570.37.11~2\/RELEASE_ARM64_T8010\nKernelCache UUID: D342183B0DC346B22ADABA5BB3219178\niBoot version: iBoot-4076.37.9\nsecure boot?: YES\nx86 EFI Boot State: 0xe\nx86 System State: 0x0\nx86 Power State: 0x0\nPaniclog version: 9\nKernel slide: 0x0000000000800000\nKernel text base: 0xfffffff007804000\nEpoch Time: sec usec\n
Boot : 0x5a57ac79 0x00085f05\n
Sleep
: 0x00000000 0x00000000\n
Wake : 0x00000000 0x00000000\n
Calendar: 0x5a5859ed 0x000e98dd\n\nPanicked task 0xffffffe0002eb610: 3545 pages, 156 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe000314000, backtrace: 0xffffffe017f43550, tid: 334\n\t\t
lr: 0xfffffff0079f32e0
fp: 0xffffffe017f43690\n\t\t
lr: 0xfffffff0078dd588
fp: 0xffffffe017f436a0\n\t\t
lr: 0xfffffff00790dce4
fp: 0xffffffe017f43a10\n\t\t
lr: 0xfffffff00790dff4
fp: 0xffffffe017f43a50\n\t\t
lr: 0xfffffff00790f874
fp: 0xffffffe017f43a70\n\t\t
lr: 0xfffffff0070fb3ec
fp: 0xffffffe017f43ae0\n\t\t
lr: 0xfffffff0070fd674
fp: 0xffffffe017f43b80\n\t\t
lr: 0xfffffff0070fabac
fp: 0xffffffe017f43c00\n\t\t
lr: 0xfffffff0070bab08
fp: 0xffffffe017f43c30\n\t\t
lr: 0xfffffff007d56064
fp: 0xffffffe017f43c60\n\t\t
lr: 0xfffffff007d559b0
fp: 0xffffffe017f43c90\n\t\t
lr: 0xfffffff0078e84e0
fp: 0x0000000000000000\n\n",


"panicFlags" : "0x102",


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


"macOSPanicFlags" : "0x4",


"macOSPanicString" : "panic(cpu 0 caller 0xffffff8008f4bd7f): \"TLB invalidation IPI timeout, unresponsive CPU bitmap: 0x40, NMIPI acks: 0x0, now: 0x0, deadline: 9665438133613\"@\/BuildRoot\/Library\/Caches\/com.apple.xbs\/Sources\/xnu\/xnu- 4570.37.11\/osfmk\/x86_64\/pmap.c:2797\nBacktrace (CPU 0), Frame : Return Address\n0xffffffce4ac3af70 : 0xffffff8008e4f5f6 \n0xffffffce4ac3afc0 : 0xffffff8008f7c6f4 \n0xffffffce4ac3b000 : 0xffffff8008f6e109 \n0xffffffce4ac3b080 : 0xffffff8008e01120 \n0xffffffce4ac3b0a0 : 0xffffff8008e4f02c \n0xffffffce4ac3b1d0 : 0xffffff8008e4edac \n0xffffffce4ac3b230 : 0xffffff8008f79db8 \n0xffffffce4ac3b280 : 0xffffff8008e4f15a \n0xffffffce4ac3b2d0 : 0xffffff8008f7c6f4 \n0xffffffce4ac3b310 : 0xffffff8008f6e109 \n0xffffffce4ac3b390 : 0xffffff8008e01120 \n0xffffffce4ac3b3b0 : 0xffffff8008e4f02c \n0xffffffce4ac3b4e0 : 0xffffff8008e4edac \n0xffffffce4ac3b540 : 0xffffff8008f4bd7f \n0xffffffce4ac3b5e0 : 0xffffff8008f52ac4 \n0xffffffce4ac3b6c0 : 0xffffff8008f53a94 \n0xffffffce4ac3b720 : 0xffffff8008edbb1f \n0xffffffce4ac3b850 : 0xffffff8008edb402 \n0xffffffce4ac3b890 : 0xffffff8008f03e5b \n0xffffffce4ac3b8d0 : 0xffffff800906d4d9 \n0xffffffce4ac3b8e0 : 0xffffff7f8e27a49c \n0xffffffce4ac3b970 : 0xffffff8009076622 \n0xffffffce4ac3bab0 : 0xffffff800907a2d6 \n0xffffffce4ac3bb50 : 0xffffff8009079c97 \n0xffffffce4ac3bc90 : 0xffffff800907e2c4 \n0xffffffce4ac3bd00 : 0xffffff7f8e278e7e \n0xffffffce4ac3bd90 : 0xffffff80090ada64 \n0xffffffce4ac3be40 : 0xffffff8009341d8a \n0xffffffce4ac3bee0 : 0xffffff8009341efe \n0xffffffce4ac3bf40 : 0xffffff80093fa0b8 \n0xffffffce4ac3bfa0 : 0xffffff8008e01906 \n Kernel Extensions in backtrace:\n com.apple.filesystems.afpfs(11.1)[18924E77-CD8C-34F7-9C9F-D11EACF8A795]@0xffffff 7f8e272000->0xffffff7f8e2c1fff\n dependency: com.apple.filesystems.hfs.encodings.kext(1)[F1862033-F96A-398C-8231-DC48CC99056 7]@0xffffff7f8a5ad000\n dependency: com.apple.security.SecureRemotePassword(1.0)[347C3F6A-3E70-3DA1-B3B8-CD3746576C E7]@0xffffff7f8e261000\n\nBSD process name corresponding to current thread: diskimages-helpe\n\nMac OS version:\n17C2205\n\nKernel version:\nDarwin Kernel Version 17.3.0: Thu Nov 30 16:32:47 PST 2017; root:xnu-4570.37.11~1\/RELEASE_X86_64\nKernel UUID: AB211A98-9AA0-3640-9478-D16ABD4093BB\nKernel slide: 0x0000000008a00000\nKernel text base: 0xffffff8008c00000\n__HIB
text base: 0xffffff8008b00000\nSystem model name: iMacPro1,1 (Mac-7BA5B2D9E42DDD94)\n\nSystem uptime in nanoseconds: 9666940877554\nlast loaded kext at 1987187667816: @filesystems.smbfs\t3.2 (addr 0xffffff7f8e2c2000, size 434176)\nloaded kexts:\ncom.uaudio.driver.UAFWAudio\t4.3.1 47542\ncom.uaudio.driver.UAD2System\t9.4.0\n@filesystems.smbfs\t3.2\n@filesyste ms.afpfs\t11.1\n@nke.asp-tcp\t8.0.2\n@filesystems.msdosfs\t1.10\n>!ATopCaseHIDEv entDriver\t127.1\n>!AUpstreamUserClient\t3.6.4\n@kext.AMDFramebuffer\t1.6.4\n@ke xt.AMDRadeonX5000\t1.6.4\n>!AGraphicsDevicePolicy\t3.16.21\n@AGDCPluginDisplayMe trics\t3.16.2\n>!AHV\t1\n|IOUserEthernet\t1.0.1\n|IO!BSerialManager\t6.0.3f4\n>p mtelemetry\t1\n>AGPM\t110.23.24\n>!APlatformEnabler\t2.7.0d0\n>X86PlatformShim\t 1.0.0\n@Dont_Steal_Mac_OS_X\t7.0.0\n>AudioAUUC\t1.70\n@kext.AMD10000!C\t1.6.4\n> AGDCBacklightControl\t3.16.2\n>ACPI_SMC_PlatformPlugin\t1.0.0\n>!ABacklight\t170 .10.2\n>!AThunderboltIP\t3.1.1\n>!ABridgeAudio!C\t3.97\n>!AGFXHDA\t100.1.4\n>!A! ISlowAdaptiveClocking\t4.0.0\n>!AFIVRDriver\t4.1.0\n>!A!IPCHPMC\t2.0.1\n>!AOSXWa tchdog\t1\n>BridgeAudioCommunication\t3.97\n>!AMCCSControl\t1.5.3\n@filesystems. autofs\t3.0\n>!AHIDALSService\t1\n>!U!SCoexistentDriver\t439.37.1\n>!UCardReader \t439.37.1\n>usb.!UHostBillboardDevice\t1.0\n|SCSITaskUserClient\t404.30.2\n@!AE thernetAquantiaAqtionFirmwareDev\t1.0.34\n@!AEthernetAquantiaAqtionFirmware\t1.0 .34\n>BCMWLANFirmware4364.Datastore\t1\n>!ABCMWLANCoreV3.Datastore\t1\n@filesyst ems.apfs\t748.37.18\n>!AFileSystemDriver\t3.0.1\n@filesystems.hfs.kext\t407.30.1 \n@BootCache\t40\n@!AFSCompression.!AFSCompressionTypeDataless\t1.0.0d1\n@!AFSCo mpression.!AFSCompressionTypeZlib\t1.0.0\n>!AAHCIPort\t329\n>!ABCMWLANBusInterfa cePCIe\t1\n>!AACPIButtons\t6.1\n>!ASMBIOS\t2.1\n>!AACPIEC\t6.1\n>!AAPIC\t1.7\n@n ke.applicationfirewall\t183\n$TMSafetyNet\t8\n$quarantine\t3\n@IOBufferCopyEngin eTest\t1\n$SecureRemotePassword\t1.0\n>usb.cdc.acm\t5.0.0\n>!AHIDKeyboard\t203\n >!AMultitouchDriver\t1204.13\n>!AInputDeviceSupport\t1201.8\n>!AHS!BDriver\t127. 1\n>IO!BHIDDriver\t6.0.3f4\n|IOAccelerator!F2\t376.6\n@kext.AMDRadeonX5000AccelL ibs\t1.4.4\n>!AGraphicsControl\t3.16.21\n>!ASSE\t1.0\n|IOSurface\t209.2.2\n@kext .AMDRadeonX5100HWLibs\t1.0\n>!AHDA!C\t280.12\n|IOHDA!F\t280.12\n@!AGPUWrangler\t 3.16.2\n>IOPlatformPluginLegacy\t1.0.0\n@kext.AMDSupport\t1.6.4\n@!AGraphicsDevi ceControl\t3.16.21\n>!ABacklightExpert\t1.1.0\n|IONDRVSupport\t517.22\n|IOFireWi re!F\t4.6.8\n>!UAudio\t311.9\n|IOAudio!F\t206.5\n@vecLib.kext\t1.2.0\n>!ASMBusPC I\t1.0.14d1\n|IO!BHost!CUARTTransport\t6.0.3f4\n|IO!BHost!CTransport\t6.0.3f4\n> !A!ILpssUARTv1\t3.0.60\n>!A!ILpssUARTCommon\t3.0.60\n>!AOnboardSerial\t1.0\n|IOS kywalk!F\t1\n|IOSlowAdaptiveClocking!F\t1.0.0\n>X86PlatformPlugin\t1.0.0\n>IOPla tformPlugin!F\t6.0.0d8\n@kext.AMDRadeonX5000HWServices\t1.6.4\n>!ASMBus!C\t1.0.1 8d1\n|IOGraphics!F\t517.22\n>!AThunderboltEDMSink\t4.1.2\n@kext.triggers\t1.0\n> usb.IOUSBHostHIDDevice\t1.2\n>usb.cdc.ecm\t5.0.0\n>usb.cdc.ncm\t5.0.0\n|IOUSBMas s!SClass\t4.0.4\n>usb.cdc\t5.0.0\n>usb.networking\t5.0.0\n>usb.!UHostCompositeDe vice\t1.2\n|IOAHCISerialATAPI\t267\n@filesystems.hfs.encodings.kext\t1\n>!AThund erboltDPOutAdapter\t5.0.2\n>!AThunderboltPCIUpAdapter\t2.1.3\n>!AHPM\t3.1.3\n>!A !ILpssI2C!C\t3.0.60\n>!A!ILpssDmac\t3.0.60\n>!A!ILpssI2C\t3.0.60\n>!AThunderbolt PCIDownAdapter\t2.1.3\n>!AThunderboltDPInAdapter\t5.0.2\n>!AThunderboltDPAdapter !F\t5.0.2\n|IOAHCIBlock!S\t301.20.1\n|IOAHCI!F\t288\n>!AXsanScheme\t3\n>!AThunde rboltNHI\t4.5.6\n|IOThunderbolt!F\t6.6.4\n>!UVHCI\t1.2\n>usb.!UVHCICommon\t1.0\n >!AEffaceableNOR\t1.0\n|IOBufferCopy!C\t1.0.0\n|IONVMe!F\t2.1.0\n>!ABCMWLANCore\ t1.0.0\n>IOImageLoader\t1.0.0\n|IOSerial!F\t11\n|IO80211!FV2\t1200.12.2\n>coreca pture\t1.0.4\n>!AEthernetAquantiaAqtion\t1.3.43\n>mDNSOffloadUserClient\t1.0.1b8 \n>!UMergeNub\t900.4.1\n>!UHostMergeProperties\t1.2\n>usb.!UXHCIPCI\t1.2\n>usb.! UXHCI\t1.2\n>usb.!UHostPacketFilter\t1.0\n|IOUSB!F\t900.4.1\n>!AEFINVRAM\t2.1\n| IOHID!F\t2.0.0\n>!AEFIRuntime\t2.1\n>!ASMCRTC\t1.0\n|IOSMBus!F\t1.1\n$sandbox\t3 00.0\n@kext.!AMatch\t1.0.0d1\n|IOBufferCopyEngine!F\t1\n>!AKeyStore\t2\n>!UTDM\t 439.37.1\n>!AMobileFileIntegrity\t1.0.5\n|IOUSBMass!SDriver\t140.30.1\n|IOSCSIBl ockCommandsDevice\t404.30.2\n|IOSCSIArchitectureModel!F\t404.30.2\n>!ACredential Manager\t1.0\n>KernelRelayHost\t1\n>!ASEPManager\t1.0.1\n>IOSlaveProcessor\t1\n> !AFDEKeyStore\t28.30\n>!AEffaceable!S\t1.0\n|IOTimeSync!F\t650.7\n|IONetworking! F\t3.4\n>DiskImages\t480.30.2\n|IO!S!F\t2.1\n|IO!B!F\t6.0.3f4\n|IOUSBHost!F\t1.2 \n>usb.!UCommon\t1.0\n>!ABusPower!C\t1.0\n|IOReport!F\t31\n>!AACPIPlatform\t6.1\ n>!ASMC\t3.1.9\n|IOPCI!F\t2.9\n|IOACPI!F\t1.4\n@kec.Libm\t1\n@kec.pthread\t1\n@k ec.corecrypto\t1.0\n",


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


"macOSRawStackshotData" : "AAEEACAAAAAAA\/



"binaryImages" : [["d342183b-0dc3-46b2-2ada-ba5bb3219178",18446743936270598144,"U"],["00000000-0 000-0000-0000-000000000000",0,"A"],["d34499bb-a808-3dbb-8766-9aa38ce89f35",64424 50944,"S"]],


"notes" : ["Source: \/dev\/rdisk1","28 unindexed user-stack frames from 17 pids: 26,27,28,29,30,31,36,37,38,39,41,42,44,46,47,51,58"]

}

Model: iMacPro1,1, BootROM , 10 processors, Intel Xeon W, 3 GHz, 128 GB, SMC

Graphics: Radeon Pro Vega 64, Radeon Pro Vega 64, PCIe, 16 GB

Memory Module: NODE 1/CPU1_DIMM_A0, 32 GB, DDR4, 2666 MHz, Micron, 36ASF4G72PZ-2G6D2 36ASF4G72PZ-2G6D2 36ASF4G72PZ-2G6D2 36ASF4G72PZ-2G6D2

Memory Module: NODE 1/CPU1_DIMM_B0, 32 GB, DDR4, 2666 MHz, Micron, 36ASF4G72PZ-2G6D2 36ASF4G72PZ-2G6D2 36ASF4G72PZ-2G6D2 36ASF4G72PZ-2G6D2

Memory Module: NODE 1/CPU1_DIMM_C0, 32 GB, DDR4, 2666 MHz, Micron, 36ASF4G72PZ-2G6D2 36ASF4G72PZ-2G6D2 36ASF4G72PZ-2G6D2 36ASF4G72PZ-2G6D2

Memory Module: NODE 1/CPU1_DIMM_D0, 32 GB, DDR4, 2666 MHz, Micron, 36ASF4G72PZ-2G6D2 36ASF4G72PZ-2G6D2 36ASF4G72PZ-2G6D2 36ASF4G72PZ-2G6D2

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x7BF), wl0: Nov
9 2017 09:46:34 version 9.100.30.0.32.1.18 FWID 01-57236d12

Bluetooth: Version 6.0.3f4, 3 services, 27 devices, 1 incoming serial ports

Network Service: Ethernet, Ethernet, en0

Network Service: Wi-Fi, AirPort, en1

PCI Card: pci1b4b,9220, AHCI Controller, Thunderbolt@184,0,0

PCI Card: Universal Audio Apollo Twin - SOLO, Other Multimedia, Thunderbolt@68,0,0

Serial ATA Device: LaCie
2big v2 THB USB3 Raid 0, 6 TB

Serial ATA Device: MARVELL VIRTUAL

USB Device: USB 3.0 Bus

USB Device: Card Reader

USB Device: Logitech Webcam C930e

USB Device: Thunderbolt 3 (USB-C) to Thunderbolt 2 Adapter

USB Device: Gaming Mouse G502

USB Device: AppleUSBVHCIBCE

USB Device: Headset

USB Device: iBridge ALS

USB Device: iBridge FaceTime HD Camera (Built-in)

USB Device: iBridge

Thunderbolt Bus: iMac Pro, Apple Inc., 25.4

Thunderbolt Device: Apollo Twin, Universal Audio, Inc., 3, 7.1

Thunderbolt Bus: iMac Pro, Apple Inc., 25.4

Thunderbolt Device: 2big TBT2 USB3, LaCie, 1, 22.1

iMac Pro (2017), iOS 11.2.2, Restart / Crashing

Posted on Jan 12, 2018 4:02 PM

Reply
252 replies

Jun 15, 2018 8:43 AM in response to newmediagroup

Sorry, somehow I clicked on the wrong button and my prior post got "reposted" by mistake.


Was just wondering what's new? Any word from the Apple engineers?


Today, I noticed some strange behavior, which I had experienced prior to one of the updates before, whereby if I save a file to my desktop, it does not appear on the desktop (as it normally should and does) nor does it appear in the Finder, however, if I REBOOT, then these files show up properly in both locations. Trying to see if I can recreate this behavior in the hopes it "may" have "something" to do with the ReStart issue in this discussion.


All the best,

John

Ocean City, NJ

Jun 15, 2018 4:52 PM in response to newmediagroup

It's been a while since I've shared my progress, it's now at a point that it's probably worth sharing.


A LONG story short: I got to the top tier technical support, and uploaded a few images from Capture Data. Feedback from the technical team is that they recognize there is a problem, and that they have said a fix is forthcoming.

When I asked when I could expect a patch to fix it, all they could tell me was "not the next update, and maybe not the next patch either".


So, it seems as though there is light at the end of the tunnel, but we don't know how long the tunnel is.


Hopefully this feedback helps others here..

Jun 16, 2018 2:10 AM in response to sugaraspa

Thanks for the update sugaraspa,

It's still all very vague, a bit too vague for my taste as a professional user. I would very much like to know more about the problem. (not asking you, for the record. Asking Apple)

Then again, the problem that I have - my computer crashing and locking up every time I compress a certain set of videofiles (who cause no problems on inferior and older macs by the way) - might not be the same as your problem. There might be more than one problem with this machine. Anyway, I'm still waiting for my feedback from Apple and they'd better give me a technical answer and some kind of timeframe. The price of the machine alone dictates they owe me that much.

Jun 16, 2018 3:55 AM in response to nickatnyte_

Just had another random restart, and i have the basic 8 core iMac Pro with Pro Vega 56, it happened during night after 4-5 days that iMac is on and running.

Its my second random restart after two weeks that i own the iMac Pro.

In my Energy Saver settings I disabled power nap , if its enabled then my iMac can go to sleep and never wake up until hard reset so I'm disabling that option.

Now I will disable the Prevent computer from sleep automatically when the display is off option and see how that will affect the situation.

Anyway as agreed with apple support that contacted me as well ill sen the log directly to them to email that they provided me.

its very problematic situation because we stuck with computer that we can't rely on and no one knows what is the issue and how and if it can be fixed.

Jun 18, 2018 10:13 PM in response to newmediagroup

I'm not an expert (but I'm not a novice either); I'd imagine that if it's a hardware problem, then the software would apply to all machines with the faulty hardware in perpetuity (unless Apple recalls those models, which I'd highly doubt).


Remember, when the OS queries Apple HQ for software updates, they send their serial number, which tells the update servers the exact hardware configuration (among other things, including when it was actually shipped off the production line; which means even if it's a faulty batch of hardware, a software fix would apply and work).

Jun 19, 2018 8:50 AM in response to sugaraspa

Yes, I am aware of the slight build variations that end up on various machines for the same MacOS updates. Smart, Kudos to Apple for being this dogmatic and detailed in this regard. So, I agree with your conclusion that if there in fact is a hardware issue that at least Apple can handle it based upon serial numbers, etc.


I guess I'm still just wondering, could this all be solved by a specific FIRMWARE update to the affected machines?

Jun 23, 2018 5:20 PM in response to newmediagroup

We have had a lot of unfortunate experience with this issue on multiple iMac Pros right up to yesterday 22 June. This remains a serious problem and these do not appear to be isolated incidents. Compare my notes below with previous reports in this thread these panic/restarts and I believe we can almost certainly conclude this is an APPLE problem vs a problem caused by user files, third party software or third party peripherals.


We have just yesterday identified a possible mitigating workaround (see my last paragraph). It doesn't STOP the panics, however it appears to consistently reduce the frequency with which they occur.


iMac Pro USERS: PLEASE HELP us isolate the problem!

• If you've experienced this problem and it's been fixed by Apple or yourself please speak up and tell us what caused or fixed the problem and how you got Apple to take action.

• If you still have this problem please tell me your screen saver and display-sleep settings.

• If you still have this problem please speak up, tell the rest of us and PRESS APPLE TO DO SOMETHING!

<><><><>


Summary of our iMac Pro experience:

• Identical problem "day one, out-of-the-box" with three new base-config iMac Pros 20 May-22 June, 2018.

• The panic/restart problem has been verified to occur at least 2-3 times on each of the three new iMac Pros with ZERO 3rd-party apps and NO external peripherals attached.

• The problem persists even AFTER we fully erased the internal SSD and reinstalled a fresh copy of the latest version of MacOS (10.13.5) from the Apple internet "Recovery" server. After the first sign of panic problems we did not attempt to restore from a backup or migrate from another Mac. These were 100% virgin configurations.

• In our normal configuration with our usual Apple and third-party apps and peripherals install the panics increase from 1-3 times per day to as often as 3-9 times per hour, i.e. these iMac Pros are unstable and totally unusable for production (or much of anything, really).

• Although we have in every case had these panics occur within the first two hours of setup and use AppleCare's initial response was to put us through 1-2 hours of troubleshooting then ask us to either take the units to an Apple Store (90 minute drive) and wait 10-20 days for repair or ship the unit to Apple and wait up to 21 days for repair or replacement.

• Advance replacement required PAYING another $5000 (or a bank card hold--same thing really) to have a new unit shipped, then waiting a week or two for Apple to receive the defective unit and get a refund. We're short of iMacs anyway, so we PURCHASED a second iMac Pro. It immediately failed with the identical problem.

• At that point (three weeks after the initial purchase and after 14 hours of troubleshooting including 4+ hours talking to AppleCare) I pitched a fit and asked the nice, dedicated-but-powerless AppleCare Senior Advisor to connect me to Apple Corporate / Consumer Affairs. This very quickly changed the picture: the CA person listened patiently to my story, asked a few questions (including verifying that the manufacture date was the first week of Dec, 2017) then offered to replace the original iMac Pro purchased three weeks earlier with one that was "fresh inventory". He expedited shipment to an Apple Store and it was received there in about three business days. (Actually picking it up was a horrible experience, but I'll give the Store people a pass on that as their key people did their best to be helpful once I got there).

• The replacement iMac Pro A.) was NOT "fresh stock"; like the first two it was made on about 1 December, 2017 probably the first week of iMac Pro production, and it B.) FAILED WITHIN TWO HOURS. Same panic & restart.


I certainly appreciate the efforts of the AppleCare advisors and the intervention of the Consumer Affairs agent who expedited this last replacement, HOWEVER:


• The identical problem has been reported by a significant number of users for more than six months. It's bad enough Apple has not yet resolved the issue, but it adds insult to injury when we're given NO meaningful information about the root cause... and when new examples of this old problem are treated as though the store Geniuses and AppleCare advisors are hearing about the issue for the first time.


• I'm amazed at the patience most of the customers on this thread are exhibiting. Most of you sound like pro users. How can you afford this? We've lost dozens of hours of billable time struggling with this issue the past four weeks, I've now paid my IT support staff several thousand dollars to troubleshoot brand new $5000 iMacs and run around dealing with replacements, setting temporary workstations and at least 40 time-consuming 5-800GB backups and restores. Any way I look at this it has not been a good customer experience.


CONFIGURATION

Our standard iMac Pro peripheral configuration:

2, 3 or 4 external displays:

A.) One LG 5K Ultrafine 27" + one or two LG 4k Ultrafine 22"

B.) Two LG 5K Ultrafine 27"

C.) Four LG 4k Ultrafine 22"

External Storage:

• 2-4 Samsung T5 USB-C SSDs, 500GB or 1TB

• 0-2 Promise Pegasus R3 Thunderbolt 3 RAID drives

• Time Machine backups to Drobo 5n2 or Apple TimeCapsule

• Apple High Sierra file sharing via 1 or 10Gb ethernet

Network:

• Meraki 1 or 10Gb switching

• Meraki 4x4 SU/MU-MIMO multi-gigabit 802.11ac up to 160MHz channels. (It's not clear to us if the iMac Pro supports half those specs as Apple stopped publishing full WiFi specs even for the Pro).


Please note once more that the panics occur even with NO external displays or storage and with standard 1Gb ethernet, so there is no pointing to our hi-spec configuration as the culprit, however the frequency of the panics appears to increase significantly when we add our peripherals.


MY CONCLUSION

• Apple does not appear to have a timely solution for this problem. We need working iMacs and we don't have these panic / restart problems with BTO i7 non-pro iMacs, therefore we may need to give up and return these iMac Pros.


• We've just now tested a single, recently-built 14-core Vega 64 BTO iMac Pro. It does not appear to have the same panic problem as the three 8-core base models, but this is not conclusive as we only tested it in our configuration for a day. (It also appears to be SLOWER that both the 8-core Pro and the non-pro i7 iMac on Photoshop and InDesign, so there's no way to justify the extra $3-4k cost for the users for whom we bought the base iMac Pros for nothing more than to get iMac Pros that actually work.)


• Yesterday (22 June, 2018) we identified a possible mitigating workaround involving the standard Apple screen saver. The problematic iMac Pros were set to start the screen after 5 minutes. (This may be the factory default setting--I've not verified that.) We noticed that the panic restarts frequently occur when the user walks away from the iMac Pro, so we watched what happens and found a strong correlation between the screen saver coming on in 5 minutes and the frequent panic /restarts. Two base-model iMac Pros (including the one just replaced by Apple) that were restarting 3-9 times per hour did not have a panic/restart at all in the first 24 hours after the screen saver was set to start in 60 minutes. When I reset one to 5 minutes and left it idle it had a panic in about 5 minutes. The other restarted a few minutes later while still set to start screen saver in 60 minutes, so this workaround doesn't necessarily STOP the panics. However, it may consistently reduce the frequency with which they occur. Note that we normally also set all our Macs to "Prevent computer from sleeping automatically when the display is off" and "Turn off display after 60 minutes". We've not yet experimented with changing those settings.

Jun 24, 2018 2:51 AM in response to dlo

That's extremely painful and I recognise a lot here. Especially how this issue is being dealt with by Apple.

In my case, my machine is not restarting (happened only once) because I didn't do anything with it, but because I AM doing something with it. It's now clear to me as well that Apple has no correct protocol for dealing with professional users. The kind people at Apple Care always give you the same scripted BS ("this is the first time we heard of this, it shouldn't be allowed to happen to such a beautiful machine", etc, etc) but they really seem te be quite powerless. In my case they even refuse to get back to me for an update on my status, probably because Apple is not giving them any feedback EITHER. I've been dealing with this for almost a month now, without any results or news.

My next step is to contact the supervisor of Apple Care in the Benelux (I'm from Belgium), but reading all of the above, I'm not convinced he will be able to change anything for me.

I mean, right now it seems that the only solution they can think of is shipping another iMac Pro and hoping this unit will work as advertised.

I still think they are STARTING to realise something is seriously wrong with the iMac Pro. They just don't know exactly what, so they don't communicate about it. Scared of this thing getting into the open?

Well, maybe we should get this thing into the open. We payed enough for these machines. If we are not treated as professionals, well, maybe we should let the pro-world know about this.

Right now, until this is resolved somehow, I ADVISE ANY COLLEAGUE OR PRO-USER I KNOW OR ENCOUNTER TO NOT PURCHASE AN IMAC PRO! Right now, this thing is like the gun in a Russian roulette.

So, if anybody at Apple is paying any attention, start treating me like a professional and not like an iPhone user!

Jun 24, 2018 2:00 PM in response to INvisibleART

Okay I have had my motherboard replace twice and third visit from "Apple Premium Service Partner" to try to get my iMacPro to boot up and after 3 home visits for 3 hours plus I still do not have a working iMac Pro. My computer is dead. The tech worked with online support and he could not get the computer to start up - "it needs firmware update to get it to fire up" and with multiple attempts he could not get it to work. So here I am with very expensive iMac Pro that does not work after two attempts to replace the motherboard and 3 rd attempt to try to get the motherboard to work. So disappointed in Apple.

Jun 26, 2018 8:21 AM in response to mc22cc

I'm also sorry to say that Apple has totally FAILED in helping me with this problem. So far I had ZERO respons from the engineering team regarding the tests. And after putting a lot of pressure on the Apple Care team they finally told me that engineering wanted me to discuss it with Pro Applications. And then Pro Applications told Apple Care this was useless because they would not be able to help me anyway.

All I have left is an option for a refund, basically.

What strikes me the most is the shadiness, the way they're refusing to tell me what they have discovered (or not discovered). That makes it clear to me there IS something wrong with this machine and they DON'T WANT ANYBODY TO KNOW ABOUT IT.

Jun 26, 2018 12:05 PM in response to INvisibleART

The whole thing is bizarre. So many people with variations of the same problem. Some partially sorted with clean installs, others for whom this doesn’t solve anything. Noone who has been contacted by Apple (on this forum) seems to have had a solution or fix, and yet the iMac Pro is still on sale in stores ... no recalls etc. Is this only affecting a relatively small number of people?

iMac Pro restarting because of a problem?

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