BridgeOS Crashes Happening on 2018 MacBook Pro with TouchBar

A few days ago updated my MBP to Mojave and today crash happened again.
But I realized one thing: every time I had the crashes after configuring the touchbar in different ways (in Safari, Chrome, IDEA)

Hi,

I bought my MB Pro 15-inch last week in Belgium: I have multiple crashes a day with the same error report as described in this thread. I straight away installed Mojave (10.14.1), the MB doesn't wake up out of sleep mode and crashes after the lid has been closed. Nothing but the charger connects to it. Didn't use Migration Assistent, only installed Office 365, Adobe Pro and Slack so far. I also have the impression this MacBook is not very fast. I'm actually quite disappointed: I work with Apple computers since 1994 and I never had issues like this. In general I find the charger tacky (where is the magnetic connection and the charging LED's???), the Touchbar not amazing and the keybord not bad (I'm an advertising copywriter) but also not great. I find the edges under the trackpad (where you open the laptop) quite sharp, they used to be much smoother on my old MacBookPro 2015 (which is sold already).

Anyway, I haven't reported this to Apple yet nor to the shop where I bought the Mac from. If it's a software issue it might be worthed to wait for a fix, if it's hardware related: how will I be sure it doesn't happen on a different machine?

BTW, I bought an Acer for one of my boys as well: the look and feel is no longer that much different from a MacBook... I'm quite sure all of this would not have happened under Steve Jobs. It feels like they definitively took the magic out of Apple. I wished I could say something different, but I can't. And I've always been a huge and very happy Mac fan.

Hi 卓,

After clean installed, Have you used any peripherals such network interface, external drive, USB dongle? Have you used MBP without charging?

Please kindly tell me.

P.S.

I've not been able to use MBP2018 Touch bar model several days because of All USB port was dead. Only once, I could use MBP2018 touch bar after connecting to outlet due to lower battery and also changed the position of the open status lid a little bit when I move to other desk that has an outlet. But, It's never solved even though it's same scenario. Moreover, Even though I could not use all USB port and try to keeping the condition by closing the lid. But, All USB port worked after I twice opened the lid. But, There is the duration of sleep between the twice. It's 30 mins approximately. No special application was running at that time. But, I could see BridgeOS crash report after login.

Just wanted to note that since the Mavericks update a week ago (the one right after the new Macbook Airs were announced) I have had NO kernel panics of any kind (overnight, while using, etc). So to be clear, Mojave 10.14.1 (18B75).

I'm curious if any others on this build are still facing issues.

Hi, I know this thread is in respect to the MacBook Pro, but I just want to report that I'm having a similar issue on the new 2018 MacBook Air, with the latest Mojave 10.14.1 update. I've had the computer since November 7th, and have used it heavily everyday since. I just experienced this crash last night. The only difference is that the computer wasn't in sleep mode. Also didn't have any peripherals connected. I was in the middle of using it when it crashed. It rebooted into the lock screen. When logging back in I got the kernel panic message with log file. The cause being Bridge OS 3.1. It didn't happen until almost 2 weeks after getting the computer, and has not happened since.

**** machine crashed as I was typing in this reply!

I have a MacBook Pro 2018, Mojave 10.14.1. Crashes randomly with BridgeOS 3.1. Happens even when I'm sleeping. I did a clean install but problem still persists. Also, replaced machine but same problems. I tried resetting SMC twice which didn't work. Thought it was a bit of a long shot but why not as I have spent weeks on this already.

As far as I can tell Apple have been aware of this since January 2018. This is just ridiculous. Apple's product and reputation are getting worse each year. Particularly with software releases. Although, who knows if this is software or hardware? Either way, I'm actively looking for an alternative.

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

Yep, sure do. Didn’t think they were related though.

FWIW, I’m Setting up this MacBook Pro the hard (long) way, downloading all my software from scratch. I’m not using Migration Assistant.

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.

Same exact thing (Bridge OS 2.4.1 crash) here on my new 2018 i9 MBP. I've been reading similar threads from iMac Pro users.

It has happened twice in three days where the computer was asleep and I came back to find it restarted on its own "due to a problem."

Any suggestions?

Not yet, especially if I might have to turn in this machine for a different one. I did look those errors up and convinced myself it was nothing to worry about, but really don’t know for sure. I’m going to wait and see for now...

Put the laptop to sleep last night. Woke it up this morning and sure enough, it had restarted and I was staring at the login screen. No Crash Reporter this time however. Also, I've been running it in clamshell mode, but I know I had this happen at least once, if not more, when I was using it normally while setting it up.

Argh; so, I had thought getting rid of the xbox360 controller extension had solved this crash problem for me. It only seems to have reduce the frequency. I saw the crash come back after the laptop had been sleeping overnight and I opened the lid in the morning. 😟

We'll all be interested to hear if that fixes the issue for you. But if that is the fix, then I'll be ****** because it's taken me 3 days to get this machine back to the state of my old machine. I wonder if a full disk erase and fresh OS install can be followed by a Migration Assistant?