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

Apr 12, 2018 6:26 AM in response to zedv

Hardware test never show any problems. I'm confused that Apple have problem to fix this issue. Very strange. Don't they really understand their new iMacPro mother board design? :-D I believe it's not harware anyway, it's something in macOS that don't play clean with this new mother board. I put my money on firmware & hope for a specific update for iMac Pro soon, probably a strange firmware update with many restarts meanwhile updating. :-)

I'm i a better mood today & give Apple 2 weeks for this, if not I return the macine and say goodbuy to iMacPro for this time.

Apr 13, 2018 10:08 AM in response to Jorgen Gustafson

Just wanted to add to the list really - same issue. Brand new base model iMac Pro, less than a week old. Took maybe three days to install all my Adobe CC software, video editing apps, Logic Pro etc etc (including creating templates for various bits of work). Long & short - lots of installs, reboots, full overnight shutdowns before I had it up and running and started to use 'sleep'. Seeing the same panic crashes as everyone else, even with nothing running before putting the thing to sleep.


I do have a LaCie D2 plugged in, using a thunderbolt 3 adapter (Apple branded). What I've also seen is that the LaCie is repeatedly spinning up during sleep (whereas with my old iMac 2012, it would stay asleep with the Mac). It knows the iMac is sleeping, so does its own power down cycle, and the blue light goes off. In less than 5 seconds, it gets woken by what can only be some activity on the thunderbolt port, and it spins back up again ... then goes straight back into its power off cycle. Once off, 5 seconds pass, then it's back on again ... and so on, and so on.


So I'm not only bothered about an almost £5,000 new computer that constantly crashes in sleep, but also my main external drive which is being spun up and down in an endless cycle during sleep too.


I'm having to power down every time now; this pains me, as this thing is a workstation-class bit of hardware that should be good to leave on (rendering animation for example) for long periods without worry of any issues. I want to be excited by having got one of there expensive new Pro models, but I'm disappointed within the first week.


Not good form, Apple ...

May 3, 2018 8:33 AM in response to sugaraspa

My iMac Pro (second one) don't randomly shut down/restart sinece I started to choose "no sleep" in energy settings (it's on 24/7). I'm in production now and I will use this one 11 month (still can get a new one first year) - IF Apple havn't fixed this issue untill then. I will get a new one...and do the same with that one, use it for 11 month. Maybe I can get a new iMacPro every year for a decade...just because they are to lazy to fix the problem. :-D

May 13, 2018 11:18 PM in response to nickatnyte_

I had the same problem, with the same error codes. Disabling "put hard disks to sleep", as suggested by our local mac admin, and in another reply here, has stopped it from happening.


Our theory is that it has to do with the SSD encryption not playing well with hard disk sleep. One idea is that the operating system wakes up quicker than the security hardware, and accesses the disk before it has been "unlocked". The system sees random garbage and crashes.


So waiting for an Apple fix, it would seem that some users can stop it from happening by disabling "put hard disks to sleep". Since it's an SSD, putting it "to sleep" is gibberish anyways.

Jun 2, 2018 10:18 AM in response to mc22cc

I haven't been contacted by the engineers yet, busy time I assume, Apple Care guy said he'd contact me again by Tuesday. Anyway, I installed the OS update. I'm on 10.13.5 now. Ran the test. And saw the iMac pro freeze up again after seven minutes or so. No fix.

This is what I'm going to do: there is a high probability engineering will advice me to replace the iMac Pro. Let's call it a hunch. I made a deal at the store that any new iMac Pro, would be tested on site. So, if it freezes up: take it back, gimme another one. Every. Single. Time. Until they give me one that does the job or they give me my money back.

They agreed.

So... let's see how far this adventure will take me. Software fix? New iMac? Second New iMac? Third? Or money in my hands (final stage). That would mean the iMac Pro is indeed a mutilated creation. Let's hope it's not.

Jun 5, 2018 6:36 AM in response to Viktor Fougstedt1

Just wanted to update a bit. Today I installed the 10.13.5 update, and got an extra update message "A software update is required to use this Startup disk".


I have now re-ticked the "put hard disks to sleep"-option, which previously was a guaranteed way to get a "0xc0dec" Bridge-OS panic on the next sleep on my machine. It has now been running with that option ticked for more than 7 hours, which is a world record for this machine. It also makes sense that the bug was startup-disk-related.


There _might_ be hope!


Have you others gotten the extra startup-disk-related software update?

Jun 5, 2018 7:30 AM in response to Viktor Fougstedt1

For what it’s worth, there seem to be a lot of threads discussing different instances of what might be the same thing.


My experience was purchasing a base model iMac Pro a couple of months ago. I had multiple Kernel Panic crashes in the first week, mainly overnight or just after auto-sleeping. Even straight out of the box with no added software. No Parallels, no Chrome, no Compressor etc etc. Would return to the room my iMac Pro is in, to find it awaiting login after a restart, with the ‘shut down because of a problem’ message, and logs mentioning Bridge etc.


At the same time, I did a boot into Diagnostic mode, and checked the SSD, resulting in several ‘Crypto_Val’ errors. These messages didn’t occur if I checked the SSD from within OSX/Disk Utility - only ever in boot diagnostics.


One LaCie external Thunderbolt drive would continue to spin up and down, endlessly, even during sleep - as if something was continually waking it.


The last thing is that my machine won’t ‘remember’ the display brightness settings after a full reboot. I set it at 50%, but it always reverts to 90% after a reboot (but retains 50% coming out of sleep).


I made a full back-up using time machine, then fully wiped the SSD and restored High Sierra from Internet Recovery (NB Not from the recovery partition of the SSD, or the Time Machine backup; I didn’t select the SSD encryption options either). I then reinstalled all files and apps from Time Machine.


After the restore, I turned off File Vault, and Power Nap, as many users suggested. OS at the time was HS 10.13.4 (upgraded from 10.13.3 which was the install version), plus the subsequent security patch.


Since that time - maybe 4-5 weeks now - I’ve had no Crypto_Val errors showing in boot diagnostics, no Kernel Panics or sleep crashes. The LaCie now sleeps when the iMac Pro is sleeping.


Just updated to 10.13.5 on release (didn’t see any message about using the Startup Disk etc as per Viktor’s post), and since then have re-enabled Power Nap with no additional issues.


For me, everything seems to be working as expected, with the one exception of the display brightness setting - it still reverts to 90% after every full reboot.

Jun 5, 2018 7:39 AM in response to newmediagroup

John,


The 10.13.5 update ran as usual. On first startup after the normal update I got a popup with the message "A software update is required to use this Startup disk." The only two options was to update (I never wrote down the exact text on the button, but I seem to remember it actually saying "Update disk" - not certain though) or to select another startup disk.


When I chose "update", I was informed that reboots would follow, and that the screen would be completely black for up to several minutes. A second update started, and since the final startup after that my machine has been running without Bridge-OS panics.


My feeling was that the 10.13.5 OS checked my disk on startup and determined that a special update was required for it.


This is my experience of the update so far. Of course, my machine might crash as soon as I have hit "Reply" on this message. Can't promise you anything... :-)

Jun 6, 2018 7:59 AM in response to mc22cc

They are still working the problem over here. I demonstrated the crash/restart two days in a row and I finally uploaded the videofiles that made the computer crash/restart. What they are doing now, or will be doing in the very near future, is duplicate this event on a similar setup (using my videofiles) so that they can further analyse the problem.

So, we are still in the middle of the investigation.

Mc22cc: Now that they have told you something's up with the videocard, what do they advice you to do? It was obviously shipped to you this way. Do they see this as a thing that can happen to a machine, or do they think it's a potential problem every iMac pro with a Vega64-card can have? What did they advice you to do?

Chances are the engineers are going to arrive to the same conclusion in my case. My only hope is they will be able to duplicate the problem on their own machine. If that's the case, it will be the beginning of their own search for the cause of this problem. Bad hardware (AMD) or bad software (the OS)...

Jun 6, 2018 10:05 AM in response to INvisibleART

They did not say INvisibleArt, but I am so glad to hear your about your troubleshooting. That is the million dollar question is it hardware or OS. I think you test by engineers with your files will give us the answer. My answer was "the engineers see it is video card" and I read somewhere that new video cards (not stocked; old video cards) were the answer. Anxiously waiting your results. Please let us know what you find out. My logic board with video card is not in stock right now and I am waiting for tech service to get the board to replace mine. Not looking forward to that solution since it will mean I have to transfer all my files from Time Machine. I hope that is easy process.

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.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

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.