BridgeOS Crashes Happening on 2018 MacBook Pro with TouchBar

Without some definitive answer on what exactly the issue is, we are left scrambling for workarounds and such. It's even worse when you factor a $7000 custom order 3 week lead time imac pro from china for a possible replacement. Not even considering the hours of re-setting up everything. (actually days) and hoping for one that works? No thanks. There has to be a better way. God I hate this, ,,

I just received a new Macbook Pro in the holidays and it has crashed 5 times now, with 10.14.2, inb a manner pretty close to the Bridge Crash here. In all 5 cases, there was a Timecapsule backup going on, but there were no other external devices plugged into USB/C ports except for the power convertor. I presume it has something to do with going to sleep. I may force the laptop to stay awake during backups and see if that makes a difference. I have never experienced such an unstable Macbook Pro before.

If it helps, I used the migration assistant to setup the MacBook from a 2015 model.

I have reporterd all 5 crashes in the last 10 days with a Kernel Probem Report. I am sorry about the length of the following string, but I didn't really know where to cut it off.

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 3.2 (16P2542)","timestamp":"2019-01-06 17:58:52.78 +0000","incident_id":"AC9AF040-2EC4-4B9A-A469-077F066E8771"}

{

"build" : "Bridge OS 3.2 (16P2542)",

"product" : "iBridge2,3",

"kernel" : "Darwin Kernel Version 18.2.0: Mon Nov 12 20:24:14 PST 2018; root:xnu-4903.231.4~3\/RELEASE_ARM64_T8010",

"incident" : "AC9AF040-2EC4-4B9A-A469-077F066E8771",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2019-01-06 17:58:52.59 +0000",

"panicString" : "panic(cpu 1 caller 0xfffffff0092dab14): macOS watchdog detected\nDebugger message: panic\nMemory ID: 0xff\nOS version: 16P2542\nKernel version: Darwin Kernel Version 18.2.0: Mon Nov 12 20:24:14 PST 2018; root:xnu-4903.231.4~3\/RELEASE_ARM64_T8010\nKernelCache UUID: 9B431313847263DE7B6685D864932934\nKernel UUID: 4BC02A8F-ECD4-37DE-8656-F4FCB742B8C4\niBoot version: iBoot-4513.230.5\nsecure boot?: YES\nx86 EFI Boot State: 0x16\nx86 System State: 0x0\nx86 Power State: 0x0\nx86 Shutdown Cause: 0xc0\nx86 Previous Power Transitions: 0x70707060400\nPCIeUp link state: 0x1614\nPaniclog version: 11\nKernel slide: 0x0000000002c00000\nKernel text base: 0xfffffff009c04000\nEpoch Time: sec usec\n Boot : 0x5c31b846 0x00073d44\n Sleep : 0x00000000 0x00000000\n Wake : 0x00000000 0x00000000\n Calendar: 0x5c3241ba 0x0004b1c0\n\nPanicked task 0xffffffe000542760: 3073 pages, 206 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe00085c000, backtrace: 0xffffffe016803520, tid: 369\n\t\t lr: 0xfffffff009e00a08 fp: 0xffffffe016803660\n\t\t lr: 0xfffffff009cdd610 fp: 0xffffffe016803670\n\t\t lr: 0xfffffff009d11ce4 fp: 0xffffffe0168039e0\n\t\t lr: 0xfffffff009d1205c fp: 0xffffffe016803a20\n\t\t lr: 0xfffffff009d13c94 fp: 0xffffffe016803a40\n\t\t lr: 0xfffffff0092dab14 fp: 0xffffffe016803ab0\n\t\t lr: 0xfffffff0092dcf9c fp: 0xffffffe016803b50\n\t\t lr: 0xfffffff0092da1d0 fp: 0xffffffe016803be0\n\t\t lr: 0xfffffff009293ab0 fp: 0xffffffe016803c10\n\t\t lr: 0xfffffff00a19afa4 fp: 0xffffffe016803c50\n\t\t lr: 0xfffffff00a19a834 fp: 0xffffffe016803c90\n\t\t lr: 0xfffffff009ce8614 fp: 0x0000000000000000\n\n",

"panicFlags" : "0x102",

"otherString" : "\n** Stackshot Succeeded ** Bytes Traced 103408 **\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,"pageSize":16384,"memoryPressure":false,"memoryPages":{"active":6598,"throttled":0,"fileBacked":10660,"wired":5162,"purgeable":47,"inactive":3143,"free":11309,"speculative":4015}},

[MUCH DELETED]

Model: MacBookPro15,1, BootROM 220.230.16.0.0 (iBridge: 16.16.2542.0.0,0), 6 processors, Intel Core i7, 2.2 GHz, 32 GB, SMC

Graphics: Intel UHD Graphics 630, Intel UHD Graphics 630, Built-In

Graphics: Radeon Pro 555X, Radeon Pro 555X, PCIe

Memory Module: BANK 0/ChannelA-DIMM0, 16 GB, DDR4, 2400 MHz, Micron, 16ATS2G64HZ-2G6B1 16ATS2G64HZ-2G6B1

Memory Module: BANK 2/ChannelB-DIMM0, 16 GB, DDR4, 2400 MHz, Micron, 16ATS2G64HZ-2G6B1 16ATS2G64HZ-2G6B1

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x7BF), wl0: Sep 18 2018 16:24:57 version 9.130.86.7.32.6.21 FWID 01-83a3fe91

Bluetooth: Version 6.0.9f2, 3 services, 27 devices, 1 incoming serial ports

Network Service: Wi-Fi, AirPort, en0

USB Device: USB 3.1 Bus

USB Device: iBridge Bus

USB Device: iBridge DFR brightness

USB Device: iBridge Display

USB Device: Apple Internal Keyboard / Trackpad

USB Device: Headset

USB Device: iBridge ALS

USB Device: iBridge FaceTime HD Camera (Built-in)

USB Device: iBridge

Thunderbolt Bus: MacBook Pro, Apple Inc., 34.6

Thunderbolt Bus: MacBook Pro, Apple Inc., 34.6

krotala--

If you are getting panic reports that clearly indicate BridgeOS panics, then Contact Apple Support. Only they know what to do about that specific issue.

If you are getting a different panic, or hangs, or Application crashes, or anything else, please start a new thread with a distinctive Title that will get you the personalized attention you need. We cannot possibly debug a different issue on this already overflowing thread about BridgeOS panics.

I am also having this issue with my MBP 2018 with High Sierra 10.13.6. It has crashed multiple times when trying to install some applications. It happens intermittently and for no reason. I haven't had any issues with the power nap or when going to sleep as reported in other posts. I took it to the Apple store and they couldn't find anything wrong with it. I left screenshots of the crash reports on the desktop but it looks like no one looked at them.

Here is some of the output of today's crash:

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 3.2 (16P2542)","timestamp":"2019-01-16 18:27:49.22 +0000","incident_id":"045B07ED-AAE6-4121-BD10-BB888C500595"}

{

"build" : "Bridge OS 3.2 (16P2542)",

"product" : "iBridge2,3",

"kernel" : "Darwin Kernel Version 18.2.0: Mon Nov 12 20:24:14 PST 2018; root:xnu-4903.231.4~3\/RELEASE_ARM64_T8010",

"incident" : "045B07ED-AAE6-4121-BD10-BB888C500595",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2019-01-16 18:27:49.01 +0000",

"panicString" : "panic(cpu 1 caller 0xfffffff023adab14): x86 CPU CATERR detected\nDebugger message: panic\nMemory ID: 0x6\nOS version: 16P2542\nKernel version: Darwin Kernel Version 18.2.0: Mon Nov 12 20:24:14 PST 2018; root:xnu-4903.231.4~3\/RELEASE_ARM64_T8010\nKernelCache UUID: 9B431313847263DE7B6685D864932934\nKernel UUID: 4BC02A8F-ECD4-37DE-8656-F4FCB742B8C4\niBoot version: iBoot-4513.230.5\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: 0x94721614\nPaniclog version: 11\nKernel slide: 0x000000001d400000\nKernel text base: 0xfffffff024404000\nEpoch Time: sec usec\n Boot : 0x5c2e7f31 0x00028ec3\n Sleep : 0x5c3f6e51 0x000102d2\n Wake : 0x5c3f762a 0x00022902\n Calendar: 0x5c3f7796 0x000bb309\n\nPanicked task 0xffffffe0005a6760: 3263 pages, 206 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe0007af3e0, backtrace: 0xffffffe011343520, tid: 385\n\t\t lr: 0xfffffff024600a08 fp: 0xffffffe011343660\n\t\t lr: 0xfffffff0244dd610 fp: 0xffffffe011343670\n\t\t lr: 0xfffffff024511ce4 fp: 0xffffffe0113439e0\n\t\t lr: 0xfffffff02451205c fp: 0xffffffe011343a20\n\t\t lr: 0xfffffff024513c94 fp: 0xffffffe011343a40\n\t\t lr: 0xfffffff023adab14 fp: 0xffffffe011343ab0\n\t\t lr: 0xfffffff023adcf9c fp: 0xffffffe011343b50\n\t\t lr: 0xfffffff023ada1d0 fp: 0xffffffe011343be0\n\t\t lr: 0xfffffff023a93ab0 fp: 0xffffffe011343c10\n\t\t lr: 0xfffffff02499afa4 fp: 0xffffffe011343c50\n\t\t lr: 0xfffffff02499a834 fp: 0xffffffe011343c90\n\t\t lr: 0xfffffff0244e8614 fp: 0x0000000000000000\n\n",

"panicFlags" : "0x102",

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

"macOSPanicFlags" : "0x0",

"macOSPanicString" : "CPU Machine Check Architecture Error Dump (CPU: UNKNOWN, CPUID: 0x80000009000906EA)\r\nCore: 0 \r\n IA32_MC11_STATUS=0xEE0000000040110A\r\n IA32_MC11_CTL=0x0\r\n IA32_MC11_ADDR=0xFF71D340\r\n IA32_MC11_MISC=0x3880000086\r\n",

"memoryStatus" : {"compressorSize":0,"compressions":0,"decompressions":0,"busyBufferCount":0,"pageSize":16384,"memoryPressure":false,"memoryPages":{"active":8146,"throttled":0,"fileBacked":11511,"wired":5387,"purgeable":47,"inactive":4044,"free":8549,"speculative":4219}},

MacBook Pro (15-inch, 2018), macOS High Sierra (10.13.6), 2.6Ghz i7, 32GB RAM, 1TB SSD

I just wanted to followup on my posting. As you guys suggested I did contact Apple support. And I have good news and bad news.

The good news is that my problem is no longer occurring. The bad news is that I changed two things at once, so I am not certain which solved my problem: Thing 1, suggested by Apple Support was just to CLEAR the PRAM. Thing 2, because I was dubious the PRAM settings were the cause, I also TURNED OFF POWER NAP (and TURNED OFF WAKEUP on WIFI). Once I did both of these things, I could do a terabyte backup over a day or two without crashing. So I don't know if clearing the PRAM made any difference. I really would guess this is some odd race condition with power napping.

For what it's worth, I did turn power napping/WoW back on now, and I don't crash. BUT the complicating news is that I can't easily recreate the conditions for the crashes anymore because my backups are now just incremental and short. The crashes only came when I had that long initial 1.5sh TB that stretched over days. SO I can't quickly figure out if the PRAM made any difference.

Well, I am crashing again.

As I said last, I wasn't sure if the PRAM clearing suggestion from Apple Support was the reason I was working again. I can definitely say now the PRAM clearing did not fix me.

I turned back on "POWER NAP" and "WAKEUP on WIFI", and I am back to crashing again. It is less frequent because my incremental backups are short now.

gchot20 has a machine check of some sort, while I have a timeout, so it's not obvious they are all exactly the same though. BUT, I really have no idea how to parse these Bridge OS panic reports.

My workaround is simply to turn off these power save features, and my unattended MacBook crashes seem to go away.

I am facing this issue with my new 2018 MacBook pro. It was crashed multiple times and i went Genius bar 2 times and they said everything looks normal. I have screenshot of the logs it generated after crash. Then i called Apple Support online and they collected some logs from MacBook and said their engineers will review it. They have no clue on what is going on. Apple is charging premium prices for sub standard products.

As per Apple support suggestion I did wiped HD and fresh reinstall 10.14.3. MacBook crashed within Five minutes after fresh install of OS. here is the error log. Still Apple saying there is no issue. They did ask me for screen share and collected some logs for analysis. I feeling I paid 3 grand for a brick.

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 3.3 (16P3133)","timestamp":"2019-02-24 04:44:50.55 +0000","incident_id":"EC80654E-5A5F-42C3-BE0A-4FA9FF583553"}

{

"build" : "Bridge OS 3.3 (16P3133)",

"product" : "iBridge2,3",

"kernel" : "Darwin Kernel Version 18.2.0: Wed Jan 2 20:41:23 PST 2019; root:xnu-4903.241.1~3\/RELEASE_ARM64_T8010",

"incident" : "EC80654E-5A5F-42C3-BE0A-4FA9FF583553",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2019-02-24 04:44:50.33 +0000",

"panicString" : "panic(cpu 1 caller 0xfffffff01bcdab14): macOS watchdog detected\nDebugger message: panic\nMemory ID: 0xff\nOS version: 16P3133\nKernel version: Darwin Kernel Version 18.2.0: Wed Jan 2 20:41:23 PST 2019; root:xnu-4903.241.1~3\/RELEASE_ARM64_T8010\nKernelCache UUID: 17C446FEFFDCE9EB1C0A6AA347130F4E\nKernel UUID: 61C8DB68-F4BA-33A3-BE53-622D429D9371\niBoot version: iBoot-4513.230.10\nsecure boot?: YES\nx86 EFI Boot State: 0x16\nx86 System State: 0x0\nx86 Power State: 0x0\nx86 Shutdown Cause: 0x1\nx86 Previous Power Transitions: 0x20002000200\nPCIeUp link state: 0x89271614\nPaniclog version: 11\nKernel slide: 0x0000000015600000\nKernel text base: 0xfffffff01c604000\nEpoch Time: sec usec\n Boot : 0x5c68b3be 0x000c4c16\n Sleep : 0x5c71e8d8 0x000e8ec0\n Wake : 0x5c71e8fe 0x00053778\n Calendar: 0x5c72211f 0x0000948e\n\nPanicked task 0xffffffe00082e1c0: 3488 pages, 208 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe000c08530, backtrace: 0xffffffe01638b520, tid: 376\n\t\t lr: 0xfffffff01c800ad4 fp: 0xffffffe01638b660\n\t\t lr: 0xfffffff01c6dd610 fp: 0xffffffe01638b670\n\t\t lr: 0xfffffff01c711cec fp: 0xffffffe01638b9e0\n\t\t lr: 0xfffffff01c712064 fp: 0xffffffe01638ba20\n\t\t lr: 0xfffffff01c713c9c fp: 0xffffffe01638ba40\n\t\t lr: 0xfffffff01bcdab14 fp: 0xffffffe01638bab0\n\t\t lr: 0xfffffff01bcdcf9c fp: 0xffffffe01638bb50\n\t\t lr: 0xfffffff01bcda1d0 fp: 0xffffffe01638bbe0\n\t\t lr: 0xfffffff01bc93ab0 fp: 0xffffffe01638bc10\n\t\t lr: 0xfffffff01cb9b040 fp: 0xffffffe01638bc50\n\t\t lr: 0xfffffff01cb9a8d0 fp: 0xffffffe01638bc90\n\t\t lr: 0xfffffff01c6e8614 fp: 0x0000000000000000\n\n",

"panicFlags" : "0x102",

"otherString" : "\n** Stackshot Succeeded ** Bytes Traced 107712 **\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,"pageSize":16384,"memoryPressure":false,"memoryPages":{"active":7857,"throttled":0,"fileBacked":11129,"wired":5621,"purgeable":47,"inactive":4196,"free":8508,"speculative":4103}},

I've had a dozen crashes like this in the last 2 days. Before it was less frequent. I believe one of my thunderbolt sockets is f***ed. I had this problem this time last year.... my MBP is 2016. Anyway, taking it to apple tomorrow.

For the BridgeOS version number:

About this Mac -> System report -> Hardware/Controller

I have a French version, so words may differ...

Have you tried to reset the SMC following this procedure ?

How to reset the System Management Controller (SMC) on your Mac - Apple Support

Although, who knows if this is software or hardware?

Noone knows,

@GrumFromOz thinks it's manufacture fault

Re: BridgeOS Crashes Happening on 2018 MacBook Pro with TouchBar

I contacted Apple Support and they have advised me to return the laptop as they believe it is a hardware fault.

Thanks, Grant.

I indeed reported the issue to apple support and got a case number.

Same problem here. 2018 i9/16/1TB. Wake up the MacBook Pro only to find it’s restarted on its own with the Bridge OS crash report.