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.

nickatnyte_ Author

Level 1

42 points

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

252 replies

Jun 3, 2018 3:50 PM in response to NorthofYellowstone

Oh man. Well, thank God I have plenty of full backup clones, but still, you know how it goes sometimes even with the best of intentions. Sure do hope I don't need to do a full restore.

I hope we hear some encouraging news from Apple on Tuesday.

All the best,

John

mc22cc

Level 1

12 points

Jun 3, 2018 6:20 PM in response to newmediagroup

Yea Apple told me I would lose all my data and needed a good back. Currently I use Time Machine only. I hope that has everything. Yea I made my post above to see if anyone else had arrive at this spot with Apple; specifically engineering is finding out it is the Radeon Pro Vega 64 embedded video card that is the problem. Anxious to hear if anyone has has gotten the same answer. I have read on macrumors that Apple did not plan on having the "new iMac Pros" until 2019. I guess it is inventory issue, so many machine may have faulty boards. I am just guessing though. I am waiting to see if this fix my issues. Others have posted a fix was coming with OS 10.13.5. So it will great when we find out is hardware or OS. I suspect since I am getting a new motherboard it is hardware.

Jun 3, 2018 6:47 PM in response to INvisibleART

INvisibleART, just curious, do you get the same "Bridge OS" kernel panic? That's what I see, so far only while I'm away from the computer (but it's not asleep, I have it set not to sleep, but I do have it blank the screen). I did talk to AppleCare about it, they said to let them know if it happened again. I've gotten into the habit of shutting the iMac down when I step away in the evening so it hasn't happened in several weeks. I'm wondering if I should leave it running just so I have something to report.

I'm hoping this ends up being like when they switched some iPhones to the Intel radio chip -- the bluetooth just didn't work, lots of people (myself included) reported the problem. Apple replaced my phone, the new one was the same as the old one. People were starting to wonder if it was a fundamental hardware flaw. Finally an update fixed it. Whole unit replacements and even mainboard replacements are expensive, eventually somebody in Apple is going to notice and if it's fixable they'll fix it.

Jun 3, 2018 7:28 PM in response to mc22cc

A new rev of the current motherboard or replacement motherboards in general? There's no way Apple would start shipping a computer and not plan to have replacement parts for a year. The numbers guy is running the company now.

Jun 4, 2018 11:34 AM in response to Markarian421

So, like a few of you, I also got a call from engineering in the US. The nice lady referred to what was being discussed here on this forum and asked me to help her gather the necessary information. I duplicated the freeze triggering event and I uploaded a report. They will analyse it and call me back same time tomorrow. Chances are she will ask me to do it again on a clean test partition I got installed. Or maybe the report from today will already have exposed something significant. Let's wait and see.

I have to say that I'm impressed by Apple's approach so far, guys. They really want to figure this out. I hope we'll help them get this machine to the status it's inspected to be in: perfect ;-)

Jun 4, 2018 3:54 PM in response to INvisibleART

Thanks for your perseverance INvisibleART! The update to Parallels on my iMac made no difference... perhaps they thought they were partly the cause of the problem. However, we will wait upon Apple with anticipation. Kind regards.

Jun 4, 2018 4:48 PM in response to petethepossum

I got a phone call (uninitiated by me) from Apple tech support today. I gave them permission to screen share and provided some huge crash-log files for them to analyze, so Kudos for reaching out to me.

John

Ocean City, NJ

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:23 AM in response to Viktor Fougstedt1

Viktor,

Thank you for the info. But I'm a bit confused. Glad it seems to be working for you!

You say you are getting the message "A software update is required to use this Startup disk."

Is this simply an informational pop-up message, or does this require additional steps beyond simply running the 10.13.5 update?

I only ask because I've had so many weird issues, and don't want to chance falling into another endless odyssey of hours or days recovering, after simply running an update.

Please advise. A million thanks. On 10.13.4 right now. Want to update, based upon your reply to 10.13.5.

All the best,
John

Ocean City, NJ

High Sierra v10.13.4 (17E199) on a new (late 2017) iMac Pro, 3.2 HGz Intel Xeon W, 1Tb SSD (APFS)

lienffur

Level 1

4 points

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 5, 2018 8:05 AM in response to Viktor Fougstedt1

That's also a big nuisance for me: my external drive recycling or waking up over and over again when the computer has gone to sleep. That's way I just leave the iMac pro on, just because of that. Would be great if they could fix that too.

I also had the Crypto_Val’ errors, but after I wiped the SSD and put back a Timemachine BU, those errors were gone.

My feeling is there's not one thing wrong with the iMacs being shipped, but several. The OS, the way it is installed on the SSD's, probably the Vega64 card... I updated to 10.13.5 but didn't get the additional upgrade message for my harddisk...

Jun 5, 2018 8:51 AM in response to Viktor Fougstedt1

Viktor Fougstedt1 wrote:

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.

I updated to 10.13.5 as soon as it was available last week. (No 'restarting because of a problem' since then.)

But, I did not get prompted like you for any additional update related to the startup disk.

(I'm on a 10 core / 64 GB / 2 TB SSD / Vega 64 from the refurbished store.)

DustyRo

Level 1

4 points

Jun 5, 2018 10:06 AM in response to NorthofYellowstone

I installed it also the same day it was released. The first thing i did was to put my iMac Pro in sleep mode and wait. Two hours later, it restarted itself. So no, it doesn't fix anything. I didn't get prompted with the startup disk message.

Jun 6, 2018 7:18 AM in response to NorthofYellowstone

Wednesday, June 6, 2018

So far, so good. Upgraded from 10.13.4 to 10.13.5 on my iMac Pro, without any prompts.

Did I miss something? I thought INvisibleART was supposed to hear from Apple engineering yesterday, Tuesday?

What is their position on the Crash/ReStarts? Does anyone know?

All the best,

John

iMac Pro restarting because of a problem?