BridgeOS Crashes Happening on 2018 MacBook Pro with TouchBar

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 @GrumFromOz, @maksimrv,

I was leaning towards hardware myself. Maybe it's a quality issue. I was running the same applications on Mojave 10.4, 2015 MacBook Pro and didn't experience this problem so I don't think it's Mojave. I'm back to could be either.

Let's hope the fact that it's in new machines results in more attention being paid. As I mentioned earlier... now on BridgeOS 3.1 and not fixed.

Fingers crossed (technical term I've used before).

Hi @jttaggart,

Do you still have the 2015 MacBook Pro? Would you consider selling it secondhand? I desperately need to upgrade my 2009 and 2012 MBP's and Apple don't seem to have made a reliable one since 2015 (given keyboard and T1/T2 chip issues).

I'm considering moving to Windows or Linux, but I've been Apple only since 2009 and really don't want to have to go through the hassle.

Cheers,

jttaggart wrote:

Let's hope the fact that it's in new machines results in more attention being paid

Sadly, I wouldn't hold your breath.

Going back to August, or possibly before, Apple had a dedicated team trying to find the issue, with no apparent success so far.

Also, there are active threads a year old for iMac Pro's with very similar BridgeOS issues. There must be people who's warranty is ending about now.

Bottom line: One year down Apple continue to sell machines with known issues AND has released four new machines with BridgeOS issues!

What happened to "It Just Works" hey? Poor old Steve must be turning in his grave at an extraordinary RPM.

Sorry, It seems to be appeared on Mojave. Well, I slightly remember It was not appeared on MBP2018 Touch bar/macOS High Sierra.

http://osxdaily.com/2018/11/07/supplemental-update-for-new-macbook-air-2018-rele ased/

Hi jttaggart,

I'm sorry to hear that. I got same issue when I used High Sierra on MBP2018 Touch bar model. I found the issue(message) when I finally logged in MBP after resuming or power on after using MBP with peripherals (ANKER's network interface) and power cable. Also, I don't remember exactly whether MBP was connected to outlet or not. But, I got the crash message when I was using MBP. It was tough week for me and our AppleCare was not proactively help me out. But, I got help from US directly. I was very glad that.

However, Even though I've kept the condition by sleeping after I cannot use any peripherals using with all USB port, It worked when I visited at Apple Store. I'm doubt T2(SMC(lid, power, misc)) and BridgeOS.

By the way, Did you use any peripherals(any USB interface devices) before sleeping? And, Did you connect MBP to outlet to use your MBP before you get the issue? Please kindly let me know.

I've returned my MBP already. I've been waiting to be fixed the issue by Apple's smart creatives. My current MBP is very heavy... getting tired every day.

Hi LoveSteveJobs365,

I disconnected all peripherals and still crashed with same error. It was middle of the night with nothing running besides email and basic Mac programs. Even if it was peripherals, how can one practically work with no peripherals? No backups?

I'm considering returning mine as well. And this is the 2nd time in 24 hours that crashed while replying to this forum!

Hi LoveSteveJobs,

Yes I did install the supplemental update first thing upon receiving the MBA. I installed it through the 'About This Mac -> Software Update' interface. Yes 2018 MBA was connected to a power outlet when I experienced the Bridge OS crash.

I posted this on other threads, but I can tell you this problem has not been fixed at least on the latest brand new imac pro custom order, and with the latest mojave or even the betas. I have frequent crash to power off ("bridge OS" cited in the crash report) during startup only (or reboot) with all T2 chip functions turned off that I can do myself incl the secure boot setting off. I do not use sleep or filevault etc, so it only happens during startup so far. I have done a fair amount of, so far ineffective, troubleshooting and have a case with Apple, but Apple is still hare triggered for only to advise to do a clean install. Obviously not the solution. Unfortunately I don't feel much hope here until they replace the T2 chip hardware entirely. It has been a year since these problems started appearing on the forums and the situation isn't any better. I have limited the functionality of my computer so as to reduce, but not eliminate the problem. So in effect I have a $7000 crippled product waiting for a fix which may never come. That is the sobering bottom line.

part of one of the reports:

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 3.2 (16P52540a)","timestamp":"2018-11-24 17:17:32.92 +0000","incident_id":"324AD759-2B36-40F0-9F64-D852A528AF5A"}

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

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-11-24 17:17:32.79 +0000",

"incident" : "324AD759-2B36-40F0-9F64-D852A528AF5A",

"kernel" : "Darwin Kernel Version 18.2.0: Mon Nov 12 20:25:54 PST 2018; root:xnu-4903.231.4~4\/RELEASE_ARM64_T8010",

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

"macOSPanicFlags" : "0x4",

"macOSPanicString" : "panic(cpu 2 caller 0xffffff801e0da1ed): Kernel trap at ...

This is very interesting. Last week I got my 3rd MacBook Pro 2018, Mojave 10.14.1. The 2 I had previously were crashing with Bridge OS 3.1 error. I was going to get an iMac without the T2 chip as I had to get work done but couldn't get one until 5th December so my only option was to try another MacBook. Since getting the 3rd machine last week I haven't had a single crash. I was wondering if it was hardware or software related and if they had updated Bridge OS. What is very interesting is that you got Bridge OS 3.2 error. Maybe that fixed the problem or maybe not. In your case, not.

And yes, they appear to have been aware of this problem for a year. What I find, (ironic or absurd), is that they suggest you turn off everything related to T2 chip which kind of defeats the purpose and also indicates that they are pretty sure that's the problem. Apple are definitely not the company they used to be.

A very sobering and **** annoying bottom line to say the least. My sympathies.

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

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

Mine just had its first crash since completely wiping the hard drive and reinstalling everything. Bridge OS Error again during sleep. Woke up to the "your Mac has restarted due to a problem" message. I had only the power cable and a Thunderbolt 3/2 adapter (with no TB devices powered on in case the frequent waking of the monitor was the culprit).
BTW, you can find these panic logs in /Library/Logs/DiagnosticReports/ProxiedDevice-Bridge within Console.

I just read a few interesting posts in another thread (iMac Pro).

Some claim that their kernel panics are related to Apple TB3->TB2 adapter. This is similar to my experience. The difference is that my MBP 2018 should have not been in an active transfer. While my kernel panic was definitely BridgeOS and bug type 210, it's not clear whether their TB adapter kernel panics are the same as mine and most MBP 2018 users'.

Anyway, for cross reference, let me link my post of the thread here. You will find those posts a few above the following link: Re: "iMac Pro" kernel crash