BridgeOS Crashes Happening on 2018 MacBook Pro with TouchBar

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

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.

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

New Mac? Contact Apple support directly.

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}},

There is 131 pages discussion on https://forums.macrumors.com/threads/2018-macbook-pros-crashing-with-bridge-os-error.2128976/page-130 Apple is not interested to address the issue.

A user suggested to do the SMC reset twice in a row.

Im free of kernel panics for more than 48hours!

I can only encourage you to try it out, but be aware of the new procedure for Macs with T2 chip!

Den System Management Controller (SMC) auf dem Mac zurücksetzen - Apple Support

(Hope you will be redirected to your country page 😁 )

I will keep you updated!

Hi @philthyPhil618,

I'm sorry to hear you're having similar problems. Thank you for contributing to the thread, your problem could well be pertinent to what we've all seen with with the MacBook Pro's. It may be unrelated given your machine was not asleep, but who knows?

It seems on macOS machines, a variety of functions run on the T1/T2 chip itself using it's own BridgeOS operating system. Given this, only machines that have a T1 or T2 chip can have kernel panics caused by BridgeOS. So, your new November 2018 MacBook Air with T2 chip may well be seeing the same issue. The new Mac Mini may also start seeing the same problems!

I had hoped Apple had silently found and fixed a hardware or manufacturing fault, however, if November MacBook Air's are having BridgeOS crashes, then that's not the case 😢. I read elsewhere a theory that Apple is doing more QA testing to weed out "bad" machines. However, if that is the case, then clearly the testing isn't perfect!

By the way, a bunch of other threads are actively tracking people with BridgeOS crashes;

• 2018 MacBook Pros crashing with "Bridge OS" error | MacRumors Forums
• "iMac Pro" kernel crash
• iMac Pro restarting because of a problem?

Yet again, I'm glad I returned my two MBP's. I'm sorry you're having to struggle through the same issues.

Cheers,

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.

This problem is occurring regularly for me. I have only had the laptop two days and it has crashed at least 6 times.

Mostly it just happens on wake from sleep with no peripherals attached.

"caused_by":"bridgeos","macos_system_state":"running","bug_type":"210","os_versi on":"Bridge OS 2.4.1 (15P6613)","timestamp":"2018-07-22 08:19:35.87 +0000","incident_id":"6EF39A3D-35F6-47FB-85DA-6AA87B321A12"}

{

"build" : "Bridge OS 2.4.1 (15P6613)",

"product" : "iBridge2,3",

"kernel" : "Darwin Kernel Version 17.7.0: Fri Jun 15 18:33:47 PDT 2018; root:xnu-4570.71.1~1\/RELEASE_ARM64_T8010",

"incident" : "6EF39A3D-35F6-47FB-85DA-6AA87B321A12",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-07-22 08:19:35.70 +0000",

"panicString" : "panic(cpu 1 caller 0xfffffff00e34a81c): ANS2 Recoverable Panic - assert failed: [11993], src\/drivers\/apple\/aspcore\/nandeng\/ans2\/pre_nand_eng.c:506:AXI_ERR F2H 0 SL[0] ERR 0x80000000 HIX 1 LBA 0x985dfaab secOffset 0x5 dp[41a70001, 6f0005, 985dfaab, a71] mmu[7752a38, 1348000, 8080c, 0, 41000700, 108d\n assert failed: [11993], src\/drivers\/apple\/aspcore\/nandeng\/ans2\/pre_nand_eng.c:506:AXI_ERR F2H 0 SL[0] ERR 0x80000000 HIX 1 LBA 0x985dfaab secOffset 0x5 dp[41a70001, 6f0005, 985dfaab, a71] mmu[7752a38, 1348000, 8080c, 0, 41000700, 108d00, 40f]\nRTKit:

Apple is not here. Apple Support Communities is a User-to-User support forum. If other users can not help you think of a fix, No further help is likely to be forthcoming using this medium. There are no standard mechanisms for escalating problems to Apple support from here, and Apple support does NOT monitor these forums looking for trends and outstanding issues.

DO NOT "wait for Apple to provide a fix". Unless and until a large number of users present their issues through standard problem-reporting channels, Apple does not know there is a problem, and is NOT working on a fix. Being selfish is the best policy, getting yours fixed helps everyone.

If advice supplied here does not provide resolution, You must take additional steps to resolve your issues. Contact Apple support directly through one of these methods:

• contact telephone support (free for 90 days with a new Mac, of for three years with AppleCare purchase)

• make an appointment at the genius bar at an Apple-owned store for hardware evaluation and advice (free anytime, but after five years parts may no longer be available).

• initiate an Online chat

• Visit an Apple Authorized Service Provider (there may be an "evaluation fee", but if they perform any service for a fee, ask for a rebate of the evaluation fee).

After I started collecting and analyzing of the crash logs I found that crashes happened on:
"name" : "idle #0" and

"name":"AppleSMC"

But after I modified the configurations - the issue disappeared:

Go to Settings->Energy Saver.

1. UNCHECK automatical switching between the GPUs (if exists of course)
2. CHECK prevent computer from sleeping automatically...
3. UNCHECK put hard disk to sleep

4. UNCHECK Power Nap (regarding)
5. Turn display off after: - NEVER

I will update this topic if everything is fine.

Hi everybody,

I have the same problem. My specs (custom order - arrived yesterday):

MBP 13 / 2.7GHz i7 / 16GB / 1TB

How to reproduce "error & reboot":

- Get USB type-C flash drive - mine was bought from Apple store https://www.apple.com/uk/shop/product/HLN92ZM/A/sandisk-64gb-ultra-dual-drive-us b-type-c?fnode=fdfa86997e21866c3157f86a3616d1d16ed7bc54dfcdb2a293df2462412e8b487 3efa966fa5e5bd9eb4889e739053cbbb1a552d4a62d3af2360fedba2d43af71ff0e736e16e94a894 5436af666e5a946922ca18a5b5db40327ff674fd76a6a20

- Get big enough file and put in on the flash drive - I use VMWare virtual machine file which is about 24GB

- Plug the flash drive into either of the two left side thunderbolt ports

- Copy the file to the Desktop

What will happen (or what does happen on mine mbp):

- Unplug the flash drive and the MacBook will reboot

- On power up there will be the "bridge os" auto report

This only happens with the thunderbolt ports on the left-hand side!!!

I can copy the file OK both ways if the flash drive is plugged into one of the two thunderbolt ports on right-hand side of the MacBook.

I have started seeing the issue while using my back-up flash drive (standard USB 3.0 Type-A) with Apple Type-C to USB adapter. The behaviour is the same for me, whether I use an old drive with the adapter or new type-C flash drive.

If this is a software/firmware issue, then its quite weird. I suspect some deeper issue, because of the different behaviour on the left and right side of the laptop. I will be returning mine and will go back to some older hardware until this is clearly resolved.

It is a big shame, I really love the form factor & power of the 13 inch MacBook Pro.

Good luck everyone...

Jan