iMac Pro restarting because of a problem?

Glad to hear from INvisibleART that things are looking up in Mojave (which I have not installed yet).

On a slightly different topic, I had a Mac Pro which was running fine in Sierra. Tried upgrading it from Sierra to High Sierra and it blew up. Had to downgrade it back to basically just a "dumb" terminal running the old Sierra. Because of this, I would have purchased a new Mac Pro but it really would not be radically "new." So, instead I opened temporarily for a new iMac Pro instead.

***

John

Ocean City, NJ

Hi ! 👋

I'm having the same issue, not on an iMac Pro, but on my MacBook Pro ... I had this crashes on High Sierra and now I have it on Mojave, less often but still here. It's quite a shame on products over 2k €. When it's happening, I'm not asking a lot from my device, just safari and mail open almost every times. It happened 1 hour ago with the same apps opened, when I swiped on the dashboard to check a date.

I did a complete reboot of my Mac when Mojave came out because I couldn't install it (crashes and failed during the install process) (formatting the disk and make a new clean install).

I really hope Apple will do something because it's really a problem and I think it's not a good publicity for Apple's expensive products.

Valentin.

I have been looking for a solution for this issue, and this worked for me, YMMV. After testing so many different things on my iMac Pro, i started using the new screen recording feature built into Mojave. I did this so that i could remember what i did last, to keep track. Once i tested it, i would have the settings to make it stop shutting down while editing. While using Premiere Pro CC 2018 and After Effects 2CC 2018 (editing 4k footage) it would randomly shut down. So i decided to put the video together to help someone else out. Hope that it helps someone out!

iMac Pro random reboot fix 2018 - YouTube

A small update. My iMac Pro has not rebooted after I tried this fix. It usually rebooted when I was exporting big projects from Premiere (media encoder), Davinci Resolve or transcoding clips in Kyno. Now instead of restarting the computer, the export/transcoding hangs (somewhere usually 30-40% per cent into the export) and then the computer is super slow, refreshing actions on the screen every 3 ish seconds. When I try to force quit the export (media encorer, resolve or kyno) the computer freezes and a hard reboot is needed. Then after the reboot, I get the inspiring message that "You shut down your computer because a error". This is so much fun...

draken182 - I'm more of the opinion your problem is strictly a memory related issue in it's pure form. Your using very memory intensive software and suffering shutdowns while doing so. I, for one, do not have any of the high end software you are using, and my Panics are occurring at startup. Sure am happy to hear you got yours taken care of though as it sounds like you needed a fix much more than I do!!!

Slight Wrinkle in Random Reboot scenario:

Still running (old) High Sierra v10.13.6 (17G65) on a (late 2017) iMac Pro, 3.2 HGz Intel Xeon W, 1Tb SSD (APFS). Have not yet upgraded to Mohave.

Just back from a 3 week business trip so I'm snowed under and don't have time to post all the details, BUT, the long and short of it is that while away from my iMac Pro for the 3 weeks I had unplugged all of the ports. I don't know why but I stupidly forgot to unplug the power. So, therefore, I had shut down the machine normally, unplugged all the ports, with the exception of the power, to isolate the machine against lightning, power surges, etc.

Upon my return I replugged all of the ports, which include numerous external thunderbolt hard drives, all kinds of USB peripherals, and my LAN connection.

Believe it or not I've not experienced the RR (random reboot) now for many months have no idea whatsoever why not. Now however, I am experiencing what appears to be a slight variation on the RR situation. I don't think my iMac Pro is actually "rebooting" however if left running (which I do 24/7) overnight, the next morning I'm faced with the "Login Screen!" If I select my user icon and enter my password (BTW my login settings are set NOT to reboot upon a power failure, and always to log me in automatically) my desktop appears, oddly with what seem to be all of the apps that had been running from the night before (in other words already running), but instead of in their individual 5 or 6 "spaces" they are all on the first space. Point being they appear to be already running, and I don't believe the machine actually rebooted per se.

It's more like some kind of auto-sleep condition, but I checked my power settings and don't see anything out of the ordinary.

Will post more on this later, but just wondering if anyone else has experienced this "Random Logout?"

All the best,

John

Having the same issue. iMac Pro (2017), High Sierra 10.13.6, 3 GHz Xeon W 10-core, 64 GB memory (4x16).

{"caused_by":"bridgeos","macos_system_state":"running","bug_type":"210","os_vers ion":"Bridge OS 2.3.2 (15P6059)","timestamp":"2018-10-26 15:11:08.05 +0000","incident_id":"D7BA6A5F-390F-4A7C-8095-6D8E87E11E21"}

{

"binaryImages" : [

[

"ea400d2a-e41f-6e4e-0b32-a5e6010e1110",

18446743936270598144,

"U"

],

[

"00000000-0000-0000-0000-000000000000",

0,

"A"

],

[

"5abdfdb4-5f50-3aef-abc4-2c2671a4a572",

6442450944,

"S"

]

],

"build" : "Bridge OS 2.3.2 (15P6059)",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-10-26 15:11:06.77 +0000",

"incident" : "D7BA6A5F-390F-4A7C-8095-6D8E87E11E21",

"kernel" : "Darwin Kernel Version 17.7.0: Fri Jun 15 23:12:25 PDT 2018; root:xnu-4570.71.1~3\/RELEASE_ARM64_T8010",

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

"macOSPanicFlags" : "0x6",

"macOSPanicString" : "panic(cpu 0 caller 0xffffff8003299785): bridgeOS panic detected\nBacktrace (CPU 0), Frame : Return Address\n0xffffff873ef93c20 : 0xffffff8002c6c1c6 \n0xffffff873ef93c70 : 0xffffff8002d95274 \n0xffffff873ef93cb0 : 0xffffff8002d87544 \n0xffffff873ef93d20 : 0xffffff8002c1e1e0 \n0xffffff873ef93d40 : 0xffffff8002c6bc3c \n0xffffff873ef93e70 : 0xffffff8002c6c6aa \n0xffffff873ef93ed0 : 0xffffff8003299785 \n0xffffff873ef93f30 : 0xffffff8003297ef2 \n0xffffff873ef93f70 : 0xffffff800329752c \n0xffffff873ef93fa0 : 0xffffff8002c1d557 \n\nBSD process name corresponding to current thread: kernel_task\nBoot args: -v\n\nMac OS version:\n17G65\n\nKernel version:\nDarwin Kernel Version 17.7.0: Thu Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~1\/RELEASE_X86_64\nKernel UUID: 1AE5ACFD-3B6F-3D74-AD52-31F1430DBC6F\nKernel slide: 0x0000000002a00000\nKernel text base: 0xffffff8002c00000\n__HIB text base: 0xffffff8002b00000\nSystem model name: iMacPro1,1 (Mac-7BA5B2D9E42DDD94)\n\nSystem uptime in nanoseconds: 25935191203330\nlast loaded kext at 5172454767274: >!AXsanScheme\t3 (addr 0xffffff7f86995000, size 32768)\nlast unloaded kext at 5241102344579: >!AXsanScheme\t3 (addr 0xffffff7f86995000, size 32768)\nloaded kexts:

I am having reboots all day every day :-(

5664A35EB86DC49DF634\nKernel UUID: 4A1BD27F-3E02-3C61-8254-E173B853B18F\niBoot version: iBoot-4513.200.293\nsecure boot?: YES\nx86 EFI Boot State: 0xe\nx86 System State: 0x0\nx86 Power State: 0x0\nx86 Shutdown Cause: 0x5\nx86 Previous Power Transitions: 0x20002000200\nPCIeUp link state: 0x14\nPaniclog version: 11\nKernel slide: 0x0000000021800000\nKernel text base: 0xfffffff028804000\nEpoch Time: sec usec\n Boot : 0x5bd227aa 0x000477c9\n Sleep : 0x5bd8aa2f 0x000bc3e1\n Wake : 0x5bd8b26f 0x00027b8c\n Calendar: 0x5bd8bb3d 0x000ae98e\n\nPanicked task 0xffffffe000562760: 3448 pages, 208 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe000822eb0, backtrace: 0xffffffe015f1b530, tid: 372\n\t\t lr: 0xfffffff028a012ec fp: 0xffffffe015f1b670\n\t\t lr: 0xfffffff0288dd610 fp: 0xffffffe015f1b680\n\t\t lr: 0xfffffff028911ce8 fp: 0xffffffe015f1b9f0\n\t\t lr: 0xfffffff028912060 fp: 0xffffffe015f1ba30\n\t\t lr: 0xfffffff028913c98 fp: 0xffffffe015f1ba50\n\t\t lr: 0xfffffff027ee29f4 fp: 0xffffffe015f1bac0\n\t\t lr: 0xfffffff027ee4e7c fp: 0xffffffe015f1bb60\n\t\t lr: 0xfffffff027ee21c0 fp: 0xffffffe015f1bbe0\n\t\t lr: 0xfffffff027e9bab0 fp: 0xffffffe015f1bc10\n\t\t lr: 0xfffffff028d9c0fc fp: 0xffffffe015f1bc50\n\t\t lr: 0xfffffff028d9b964 fp: 0xffffffe015f1bc90\n\t\t lr: 0xfffffff0288e8614 fp: 0x0000000000000000\n\n",

"panicFlags" : "0x102",

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

"macOSPanicFlags" : "0x0",

"macOSPanicString" : "BAD MAGIC! (flag set in iBoot panic header), no macOS panic log available",

"memoryStatus" : {"compressorSize":0,"compressions":0,"decompressions":0,"busyBufferCount":0,"pa geSize":16384,"memoryPressure":false,"memoryPages":{"active":7568,"throttled":0, "fileBacked":11667,"wired":5545,"purgeable":45,"inactive":3496,"free":9471,"spec ulative":4158}},

I can’t speak for the newer models with USB-C ports. But if you are like me with a vintage early 2011 MacBook Pro 15” then absolutely NO second monitor is recommended. Until recently the 2011/2012 15” MacBook Pro was subject to a free replacement program to have the Mainboard with the on-board video chip replaced for free. The on-board video was the problem. It turns out they were prone to self destruct when you used a second monitor with a Thunderbolt 1 connection. Mine did the self destruct routine, but unfortunately the free replacement offer had expired and you could only get a Mainboard for my model from 3rd party suppliers. Very expensive refurbishment! If I were you settle for the current screen.

November build imac pro 10 core, same issue here with bridge os panics on startup. Posted on other threads here too. So far it is hard to get a real consensus as to what is going on other than the wonky T2 and Bridge OS sen sensitivity to just about anything plugged in to your mac and no easy swap out and test. Frustrating indeed.

Hmmm.... now I have started having the same problem of my iMac Pro restarting once or more every day GRRR!!! I had thought it was since I upgraded to the latest version of Mojave (10.14.2) but maybe the restarts are more likely attributed to the additional T3 to T2 dongle I have added to the system now, as as to be able to use an older iMac as a secondary display. Based on this thread I am thinking that is more likely the issue.... it's so frustrating tho'..!!!

Thursday, February 21, 2019

Well, it's be quite a while now since I've noticed much activity on this thread, so I'm hoping that things have been resolved.

Was the "official" cause of the problems ever stated by Apple?

All the best,

John

Sadly the problem isn‘t solved since more than a year as it seems. Really bad experience for the current top of the line computer. I already bought a new imac pro and i am confronted with the same error. Currently i think its the xrite color profile wich causes this error.

I have an iMac Pro which I purchased last April and the last week I have noticed my machine crashing and rebooting. It happened about 7 times in one day and I did a PRAM and SMS reset which made it last of a day before it started again. I can't do anything to make it happen it just comes at random while working or even from when the computer has just been switched on.

I am really worried as only have a week or two left on my year warranty and had a really bad experience with Apple before getting this machine. I went through 5 MacBook Pro that would get stuck in Caps lock mode, wasted weeks instilling and installing software/ testing etc and was told by one guy in Birmingham store to deal with it or return it. So ended up returning it and as I need a Mac was forced to go for the iMac Pro as need the power.

I also have had several panic reboots, I am currently working with a AppleCare engineer to find out what is going on