BridgeOS Crashes Happening on 2018 MacBook Pro with TouchBar

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

My experience has been that if I have things connected I get the crash. If have nothing connected I don't. I don't have a TB3/TB2 adapter. I have a USB 3 hub, an LG 5K monitor with its embedded usb c hub and an Anker adapter plugged in to that with wired ethernet port and a couple more USB ports. I have two drives connected to the hub, a headset, a microphone and a Logitech unifying receiver.

FWIW, my interaction with support has been excellent so far. I reached out to them and later they reached back. I know better now how to collect diagnostic info for them.

Hello,

It just happened to me (Mbp 2018 15" i72.6). "Clean installation", and only plugged to a LG monitor for charging (usb-c). Not going to look for crash report, not interested.

Funny enough I was questionning if I should keep the computer or return it (it is getting too hot to the touch when working with like 25% of the processor. + other details here and there). So I guess that will be a return ?... I already knew about the T2 reboot risk (heard about the mac pro T2 issues), but I guess I am getting sick of it...

I hope you wont experience too much crashes.

I've got a new 2018 13" MBP -- have had around 8 kernel panics. Sometimes plugged in, sometimes not, sometimes while the device is being used, sometimes while it is not.

The fan whirs loudly for a second and the device shuts off suddenly.

For 7 of the 8 times there was no diagnostic log or message. For the most recent I finally got a crash log...

I have the same issue.

didn't connect to anything, it was in sleeping mode. when took it out, it already showed the information of some issued caused the crush ( i remember it says Bridge 2.4.2 causing the crush)

called apple see what's next. if it's crushing again i might have to send it back and get a refund since it's still in 14 days.

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

I had a call from Apple support on Friday asking for details and logs. Spoke a good 15-20 minutes trying to find out more and asking me to upload logs if and when I experience the crash again. Person I spoke to said that the issue will need a software update at some point, but it sounds like they are still trying to get to the bottom of it. For me, it's not a reproducible thing - and typically, I've not had a crash in the past 4 days...

An Apple representative called me a day or two ago asking for more details and diagnostic information around this issue -- they couldn't say too much, but basically said they are looking into the issue and actively searching for a solution.

It sounds like Apple is aware that this is a real problem. They said to keep my ear to the ground and look at software patches / etc -- and that if it turns out to be a hardware issue I won't have to worry about winding up with a dud of a machine.

Also getting the Bridge OS 3.0 error. 1-3 times a day.

15” 2018 MBP, i7, 32GB, 1TB. Fresh install, no TM restore or data migration. I have encountered the crash with no inputs in USB ports as well as connected to a Caldigit TS3 Plus driving two Dell 27” monitors.

When it panics and crashes the fans make a brief but loud woosh noise for a second. I had no idea what it was at first, fortunately I found the thread at MacRumors. Inspecting the crash reports the error states Bridge OS 3.0.

I have had the errors with Adobe programs open mid-work, a full screen live steam video (3-4 times) in Safari, randomly whilst setting up the machine/tweaking touch bar etc.

Considering it’s a $5,500 machine - why is there no fix? People have had this problem for months?

I installed Mojave PB hoping it would solve the issues, no luck.

Hello!

As it was mentioned above - unchecked option "Put hard disks to sleep when possible."
As I wrote around 10 days ago or even more - after doing the same - I don't have any crashes anymore, not on the battery, nor with the charger.

Also, I'm using sometimes my external Samsung SSD for TM backup.

So, this option "Put hard disks to sleep when possible." might be one of the possible reasons.
Also, I have checked "Prevent computer from sleeping"

Worth to try.

I have the same problem. Any news from Apple on this?

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 2.4.1 (15P6805)","timestamp":"2018-09-02 23:35:54.14 +0000","incident_id":"FBE2821D-A221-470D-8C5F-63784D4EA213"}

{

"binaryImages" : [

[

"e0e6f8b6-c72f-e2cd-30ef-30dd2c2f37fe",

18446743936270598144,

"U"

],

[

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

0,

"A"

],

[

"7f5e330b-f8bd-3c53-b45c-7726c2bb0d74",

6442450944,

"S"

]

],

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

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-09-02 23:35:53.65 +0000",

"incident" : "FBE2821D-A221-470D-8C5F-63784D4EA213",

"kernel" : "Darwin Kernel Version 17.7.0: Fri Jul 6 19:25:51 PDT 2018; root:xnu-4570.71.3~1\/RELEASE_ARM64_T8010",

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

"macOSPanicFlags" : "0x4",

Dear, Apple Same here when I working and crash for 2-3 times, please fix as soon my crash log:

{"caused_by":"bridgeos","macos_system_state":"running","bug_type":"210","os_vers ion":"Bridge OS 2.4.1 (15P6805)","timestamp":"2018-09-06 07:40:07.61 +0000","incident_id":"95D99768-1DF4-4F5D-BE45-59040179DD6C"}

{

"binaryImages" : [

[

"e0e6f8b6-c72f-e2cd-30ef-30dd2c2f37fe",

18446743936270598144,

"U"

],

[

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

0,

"A"

],

[

"7f5e330b-f8bd-3c53-b45c-7726c2bb0d74",

6442450944,

"S"

]

],

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

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-09-06 07:40:06.93 +0000",

"incident" : "95D99768-1DF4-4F5D-BE45-59040179DD6C",

"kernel" : "Darwin Kernel Version 17.7.0: Fri Jul 6 19:25:51 PDT 2018; root:xnu-4570.71.3~1\/RELEASE_ARM64_T8010",

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

"macOSPanicFlags" : "0x6",

I would agree that from what you read here and from personal experiences that there appears to be no simple correlation to something that causes the problem. At least a few dozen people have been working hard to find an obvious cause and willing to spend some hours trying things. There have been rebuilds, machine replacements and all sorts of configurations tried. Particularly since this has been an issue for even longer on iMac Pros that have been out for a while. I would also agree that this is the first hardware upgrade I have had in a while that is immediately noticeable in its positive performance impact. The extra cores and double the memory make an immediate difference when you use VMs for development purposes. It would be hard to go back to MBP 2016 for me. That said, I have had a few more stability issues than you would expect leading to some reboots. But, those could as easily be caused by non-Apple software running on this new platform. (problems partitioning and formatting, a network copy issue, etc.) Each time the reboot cleared things up. Those things were extremely rare on my MBP 2016.

I use 2FA using with Yubico. I cannot use my Mac for three days at least even though I tried to login many times with making the break for the next time login. which means I tried to do it in the morning, noon, afternoon, evening and night. But Once I plugged my power cable into my Mac at Starbucks in the night, It worked. I was very lucky to move my table at Starbucks to charge the battery. And, It happened next morning again and so I left my Mac with the condition to show the issue at AppleStore. But It worked when I am about to show the issue to the staff. I don't know... I took a video that I can not use All USB Type-C port. Frequency : It happened almost everyday even though I could login once in a while and making it sleep then resume it and then happen. I can not figure out how/when to reproduce the issue. So, I removed the 2FA functionality from configuration file. But It happened again that I can not use LAN and others. But I could charge the battery. I hope your proactiveness will find a route cause of this and to fix.

I upload related information about T2 issue. https://www.digitaltrends.com/computing/apple-t2-chip-may-be-causing-imac-pro-ma cbook-problems/ the update that many not be worked for the issue occurred when you resume. https://support.apple.com/kb/DL1973?locale=en_US I've not tried this yet. F.Y.I.

Hi Grum,

I bought my machine a month ago and since then I've only had the problem once (happen 16 September with high sierra).

I contacted apple support who advised me to do an SMC reset : I did it.

Now i'm on Mojave and for now all it's fine.

I hope it'll be good, I let you know.

What about all of you?

Regards,

Olivier