iMac Pro restarting because of a problem?

Question

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

Reply

Answer 1

Top-ranking reply

dfpsmith

Level 1

4 points

Jan 23, 2019 10:51 AM in response to nickatnyte_

I was getting kernel panics, mostly while using Premiere/After Effects, also my wifi would sometimes freak out.

Took to apple care, they replaced the logic board, didn't help. After chatting with Apple support technicians and giving them all kinds of logs from the computer, they said it was related to the software on the computer not being able to contact a server and freaking out, making it kernel panic and restart.

I have little snitch installed on my computer to monitor internet traffic, I uninstalled it and changed over to the open source software Lulu instead and it completely fixed my problem. The computer has not had a single kernel panic in over a week, it used to have a panic 2-3 times per day while doing video editing.

Other things that helped reduce panics before I got to this solution:

Disconnected a USB-C iMac Pro Hub

Turned off Filevault

Turned off power saving features

Hope that helps someone else.

Reply

Answer 2

Jan 24, 2018 7:14 AM in response to nickatnyte_

I just had a call with Apple support - they said that this issue was patched in 10.13.3, which I installed yesterday. I haven't had this issue again since then, but seeing as it's been less than 24 hours that's not entirely conclusive at this point. Will post back with any further info.

Reply

Answer 3

May 17, 2018 8:30 AM in response to sugaraspa

I unticked "Put hard disks to sleep when possible" seven days ago today, and have not had a single restart since then. My other Energy Saver settings are "Prevent computer from sleeping" active, the other four inactive.

High Sierra 10.13.4.

If nothing else this should give Apple something to go on. With the "Put hard disks to sleep" option ticked, I had a crash as soon as I left my mac alone for too long, since I unticked it I haven't had a single crash.

My gut feeling is that this is a software-correctable bug, but possibly one which is triggered by hardware being at the edge of specs. Maybe my hardware is slightly closer to average and only triggered the bug on hard disk sleep, while others' hardware is a little closer to the spec edge and trigger the bug on other events as well...

If I have a new crash I will post here immediately again.

Reply

Answer 4

May 27, 2018 6:47 AM in response to INvisibleART

Production issue as in OS and/or hardware in combination. Personally I treat them as the same and it’s up to apple to fix it. I’ve gone through the process with Apple support twice, uninstalling, reinstalling Mac OS with and without time machine backups, enabled and disabled all kinds of power options, resetting smc, disabled system integrity protection, had my iMac replaced twice and the issue is still ther and occurs with no software other than Mac OS installed. If that’s not a production issue don’t know what is.

Reply

Answer 5

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.

Reply

Answer 6

Jul 26, 2018 7:19 PM in response to nickatnyte_

FYI to everyone following this thread: there are now multiple reports of very similar crashes from users of the new 2018 MacBook Pro, which also incorporates the same T2 chip in the iMac Pro; the crash reports reference Bridge OS as the cause, same as on the iMac Pro.

Thread on MacRumors: https://forums.macrumors.com/threads/2018-macbook-pros-crashing-with-bridge-os-e rror.2128976/

Numerous Apple/tech sites also reported on this issue today, so hopefully that will give it some traction with Apple, and light a fire under someone to get this resolved. They responded to the 2018 MacBook Pro throttling issue within a couple weeks, can't believe this issue has gone on for months now.

Reply

Answer 7

MFASM

Level 1

75 points

Jan 14, 2018 4:56 PM in response to nickatnyte_

My problem seems to be that I had two RAID hard drives daisy chained through thunderbolt...so now they are plugged in separately into the iMac Pro ...one drive is a thunderbolt 2 drive with a thunderbolt 2 to 3 adaptor.....seems to have ended the panics for me so far.

Reply

Answer 8

DustyRo

Level 1

4 points

Jul 7, 2018 5:50 AM in response to nickatnyte_

So, I got a call from Apple Support about this issue on Friday. We talked for an hour, time in which I explained when it happens and when it doesn't happen. He was watching with me what I was doing, what settings I had enabled or disabled and he witnessed the crash with me. In my case if I have the power saving settings turned on + the apple watch login + asking for the password after sleep or lock it crashes either in sleep or when I export 4K video in Final Cut Pro. Once I disable all those settings the machine runs fine. It never restarts while sleeping and I am able to export my 4K videos. This gives me hope, because it could be only a software issue.

Reply

Answer 9

Jun 13, 2018 8:53 AM in response to nickatnyte_

I disabled unlock with apple watch and my kernel panics stopped immediately. I was getting them every 30 minutes.

Reply

Answer 10

Mar 24, 2018 12:06 PM in response to Jorgen Gustafson

Hey there, sorry to hear about the trouble, it's frustrating most of all because Apple won't say or commit to anything. They've told me it's a hardware problem and replaced the Mac and the problem re-occurs, so at this unless they admit to a serious production problem it's more likely to be software.

I'd try the following;

1) Run diagnostics (How to use Apple Diagnostics on your Mac - Apple Support), and if it passes it should give you a level of comfort that it's not your unit, and

2) I can't find it here but someone had said to turn off the Secure Boot feature (About Secure Boot - Apple Support), not counting my chickens yet, but no restarts after 5 days so far. Before that I'd gone almost three weeks between restarts so can't confirm this is a fix yet.

Good Luck,

Martin/Happy

Reply

Answer 11

May 27, 2018 6:04 AM in response to nickatnyte_

I'm also investigating this problem from Belgium. In my case, compressor seems to be responsible for nearly all restarts and freezes. After a lot of testing I narrowed it down to a job I'm doing where I have to compress old DV-Pal movs (+30min movies) to H264 movs. In the activity monitor CompressorTranscoderX goes up first and then falls back to 4 procent. Then pretty much everything I do will cause the computer to freeze up or restart.

Next step I compressed a bunch of +45 min prores movs to H264 movs and everything remained stable.

I then tried to compress the dv-pal movs to prores and everything remained stable... In the Activity Monitor CompressorTranscoderX even went up to 780 procent. Very nice. The job was done at a tremendous speed!

So... DV-pal quicktime to H264 (any container) is the elephant in my room here.

What conclusion get we draw?

1) DV-Pal to H264 is a VERY complicated task and asks a lot of computing power which makes the system crash? So there is something wrong with the system (hard- or software)

or

2) There is something up with the Pro Video Formats

3) There is something up with compressor...

Feel free to add your own reasoning, guys 'n galls.

Monday, I will mail these conclusions to a pro apps specialist at Apple Care and see if he can upgrade this to engineering.

Reply

Answer 12

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.

Reply

Answer 13

mc22cc

Level 1

12 points

Jun 13, 2018 7:45 AM in response to MiguelF03

Apple should ask you to use a special program called Capture Data (they will email you the link to download the program), then you will download these huge log files from your computer (mine were enormous - 4 files > 1 gig zipped) and then Apple's engineers will look at the files and let you know if you have the same problem I am having which a bad Radeon Pro 64 graphic card that is embedded on your logic/motherboard. If so you will need a new logic board like I am waiting to receive. There are comments out there that the wait is for a new "fixed" motherboard to be produce since the ones in stock are similar to the one I already have. Until other folks get the same answer that I did we will not know if this is truly the problem. I run very clean machine also except I do use two monitors.

Reply

Answer 14

Oct 11, 2018 7:30 AM in response to newmediagroup

As I had previously unplugged all of my ports (see my prior post above) including external thunderbolt hard drives for 3 weeks while away on a business trip, then replugged them, can't fathom why, but just on a whim considering that I had not replugged the external drives (two thunderbolt dongles) in the same ports they came out of (a 50/50 chance) I switched these two port connections and my iMac Pro lasted overnight now for the first time in about a week!

I'm not convinced yet, as there are other variables I need to consider, but I'll start testing and logging incrementally as I add back other items and peripherals. I doubt what I'm speaking of (the switched ports) could be my Random Restart problem, but who knows! Hey, it's worth a shot!

John

Reply

Answer 15

Oct 12, 2018 9:10 AM in response to newmediagroup

....followup from a few days ago.

Well, I can't explain it, but it's been several nights now with all kinds of apps running (24/7 as always) including automatic SuperDuper nightly backups, and after having switched the two thunderbolt hard drive dongles I have NOT had any random restarts. Go figure. Could be just an anomaly, but, now that I'm stable again I'm not touching those two USB/Thunderbolt plugs!

John

Reply