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

May 30, 2018 12:57 AM in response to INvisibleART

You may be right. I did notice the mouse pointer freezing about 20 seconds before the machine re-started. There could be more to this than I think! I'll take more notice next time as to whether I am using Parallels at the time or not. I will sleep the machine tonight and see how it behaves in the morning.

May 31, 2018 7:13 AM in response to newmediagroup

Yep, this is not a third party software issue, lots of people including myself have experienced the problem with nothing installed out of the box iMac Pros.

On more than one occasion and on more than one Mac (as I've gone through the process a number of times), it was not connected to my iCloud account and there was no restore done from Time Machine, just Mac OS and a new user account. Left it running overnight and by the time I went to use it in the morning it had restarted.

So no, it's not your software, or your peripherals.

May 31, 2018 7:25 AM in response to newmediagroup

My only thought is that some peripherals or software may exacerbate the problem but it happens even without those.

I've gone through the troubleshooting process with Apple twice and on both occasions they said it's a hardware problem and shipped me a new iMac, problem with their process however is they then close the ticket and "fuggitaboutid", when I tried to follow up to say the new iMac hadn't solved the problem they told me to open a new ticket and after the second replacement I couldn't be bothered.

If INvisibleART got it escalated beyond second level, good for him and us!!!

May 31, 2018 7:26 AM in response to newmediagroup

I do, John, I do. But they have not contacted me yet. The deal I made with the Apple Care senior was that if I hadn't been contacted by somebody from engineering before this friday (noon, standard European time) he would call me with word of how things are doing. So, I guess it will be Friday then. I'll keep you all posted.

Besides, there is a new OS update coming soon. Maybe some fixes are already incorporated in that update. Is anybody here running the latest beta by any chance?

Jun 1, 2018 10:26 AM in response to nickatnyte_

One more voice/machine to add to this thread. I'm on build 17E202 (10.13.4) - and while some version numbers differ from the OP, the report contents are the same. Restarted during the night - 3 day of ownership - with no active apps. Only thing that would/should happen would be power nap waking up to check to see if a Time Machine backup was needed, or to check online for updates.

Difference from OP's crash report is that mine refers to Bridge OS 2.3 (15P3169) and Darwin Kernel 17.6.0. Panic Flag is 0x4; Panic String is "SleepVWake hang detected".

I have nothing special connected to the machine yet (still transferring/loading content) - a scanner and USB 3 drive for Time Machine.

Really unhappy that Apple is taking so long to address this and other iMac Pro issues. (The number of error messages in the Console log is insane - grows worse with each MacOS release, rather than Apple fixing their own software components.)

I put off purchasing this iMac Pro because of this and other threads, but took a chance that maybe the group on this thread was having a unique experience. Hopefully, 10.13.5 will be released before my 14 day return window is over and will fix things, or at least be encouraging. My Early 2008 Mac Pro didn't stop suffering from crashes/panics until a full year after delivery when an OS release finally fixed everything. Not sure I want to go through that experience again.

Apple should be ashamed. Software quality on all of their platforms has really suffered the last few years.

DustyRo

Level 1

4 points

Jun 2, 2018 12:06 AM in response to NorthofYellowstone

Guys, it's not the fault of the peripherals. Its the T2 chip and the software for it. It's been months and no sign of getting this fixed so my assumption is that it's a design flaw. Of course, they won't admit it, unless a class action suit is filed. I'm very torn because I love this machine and I have saved money for years to afford a professional machine and now all that hard work seems it has gone to waste. Apple really ***** this time.

mc22cc

Level 1

12 points

Jun 2, 2018 12:09 AM in response to MFASM

I have the same issue like all of you; Apple engineering saying it is a faulty video card in my iMac Pro. Has anyone else gotten this answer and did the new motherboard (video card embedded into motherboard) fix the problem?

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 2, 2018 11:38 AM in response to newmediagroup

Haha John, the pic says it all. Well, that intervention places you one step above or beyond my current position. I wouldn't mind being called by them as well (and they will, next week, I'm still confident about that). After all, I've been editing episode drama on Final Cut Pro for over 10 years now, that's roughly 130 hours of fiction. It would break my heart to see Apple descent into mediocrity.

But I don't like to generalise, and I loooove facts. So, let's put some light on the facts. What do they (the engineers) know and what do they believe? They are the ones who have the data. And how real are their concerns (I hope VERY real). If they can show me the attitude I expect from them, then I'll help them solve this in any way I can! So in case they are reading this: I HAVE A TEST THAT CAN FREEZE AN out-of-the-box (+compressor) IMAC PRO, 100 PROCENT, EVERY TIME.

Thanks for the update and by all means keep them coming. At least this is going SOMEWHERE.

Jun 2, 2018 12:03 PM in response to newmediagroup

I got a (pleasant) surprise, Apple actually reached out to me yesterday based on this or the other thread and I'm actually working with somewhat from a higher level support area on the issue again. He also won't be back in the office until Tuesday but I have some action items and feels like we're actually moving forward again. I'm feeling a little more positive on this.

Cheers,

Happy/Martin

Jun 2, 2018 12:21 PM in response to HappyPappy

Glad to hear HappyPappy that things are moving along for you. As for me, I've become so disenchanted over the last several months since my Mac Pro exploded when I tried upgrading it from Sierra to High Sierra, and now dealing with all this (the Freeze/Crash/ReStarts) that I'm just getting fed up. Okay, fair enough, I probably got one of the first Mac Pros off the assembly line and it didn't have the advantage of the newer ones currently shipping. Okay, so be it. So now what do I do? I need a working Mac Pro. The only reason I have an iMac Pro is because the Mac Pros currently shipping are now virtual relics, and from what I understand the "new" Mac Pros won't be available until 2019, and that's only a rumor. If Apple doesn't step up I'm not sure what I'll do.

I'm still waiting to hear "their" side on this coming Tuesday. We'll go from there.

****

Thank you,

John

[Edited by Host]

mc22cc

Level 1

12 points

Jun 3, 2018 9:42 AM in response to nickatnyte_

I have been having the same problem everyone else is writing about in Apple Support communities and all over the internet. I have sent 4 files x2 separate times to Apple engineering (4 gigs each time) and they have finally determine it is the embedded Raideon Pro Vega 64 video card which part of the motherboard (not plug in video card). I have new motherboard on order that is going to be replaced. I have also read about folks getting their iMac Pro replaced and the same problem happening with clean "Macs" with no additional software or peripherals (I am assuming Apple did not know with these folks that the GPU was the issue). My take is that Apple has found the problem and they probably had to get AMD to fix the GPU in their video card, so now the new motherboard and hopefully new AMD Raideon Pro Vega 64 card are fixed. I will let you know. If you are not sending large files to Apple to review (what I did) you may be wasting a lot time with all these theories out there. My reason for posting is, if everyone does what I did (send crash files to Apple), we may all get to the bottom of this quicker. I not certain this is the fix until I get the new motherboard with new embedded video card and the problem (kernel crashes) goes away. My kernel crashes happen now nonstop. that is another question, why did the frequency increase so much if it was always a hardware issue.

Jun 3, 2018 10:20 AM in response to mc22cc

Another stupid question. When you get your new motherboard, I assume the SSD(s) can simply be swapped out from the old to the new motherboard not necessitate doing any kind of a "restore" or any other complications or adjustments? I never had to do this, so just planning ahead. Hope this all gets resolved soon. I'm sure the engineers at Apple are doing their best.

John

Ocean City, NJ

Jun 3, 2018 2:39 PM in response to mc22cc

mc22cc wrote:

... I have sent 4 files x2 separate times to Apple engineering (4 gigs each time) ...

Which is why I have to rely on you and others here to work out a solution with Apple... uploading a 4 GB file would take over 15 hours at the pitiful CenturyLink speeds available to me... I do have the Vega 64 ...

Jun 3, 2018 2:43 PM in response to newmediagroup

newmediagroup wrote:

Another stupid question. When you get your new motherboard, I assume the SSD(s) can simply be swapped out from the old to the new motherboard not necessitate doing any kind of a "restore" or any other complications or adjustments?

My understanding, John, is that the content of the SSD's cannot be read by another motherboard/machine because of the encryption performed by the T2 chip - keys unique to the chip on each motherboard (?) ... which is a separate encryption from FileVault. Apple has warnings in various places to be sure that we backup via Time Machine and/or other means saying that the content of the SSDs cannot be recovered. Not the same as the old days with Mac Pro's - swap drives into bays of a new machine.

iMac Pro restarting because of a problem?