BridgeOS Crashes Happening on 2018 MacBook Pro with TouchBar

Having received my new 15" MBP yesterday, incorporating the new T2 chip, I have experienced two BridgeOS crashes in the past 18 hours.


The most recent happened with a USB-C Samsung drive, an external keyboard and mouse as well as a Belkin USB-C ethernet adapter all connected directly into the USB-C ports on the device.


I did a straight-up Migration Assistant from my 2017 15" MBP with a Touch Bar and had to set up TouchID again on the new one!


The Crash Reporter error was in a completely different format from a normal Crash Report and is not documented on the Mac in the usual /Library places.


Due to fat fingers, I was unable to capture the latest log, but I will post again once I have some more detail.


Has anyone experienced the same thing?

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

Posted on Jul 16, 2018 10:30 PM

Reply
Question marked as Top-ranking reply

Posted on Jul 25, 2018 6:00 PM

FYI, I was seeing the same issue: when I open the lid on the laptop, it would already have crashed/restarted and I'd see the Bridge OS crash report. It was easy to reproduce: close the lid, wait a bit, open it.


I wasn't able to reproduce the problem in Safe Mode. (Reboot, hold shift down while it is powering up.) That suggested to me that for me, at least, it is likely a software issue.


I looked for older kernel extensions I had installed that got copied into the new laptop by the migration tool. One stood out: I had an xbox360 controller extension installed, from when I was futzing around with that on my prior laptop. I removed the extension (removed it from /Library/Extensions -- I forget the names, but there were two .kext files associated with it -- something like xboxcontroller or similar), and rebooted.


Since I did that, I haven't seen a crash.

270 replies

Jul 26, 2018 8:18 AM in response to JMcKee

As it happens, I had to wipe clean and restore the first day. So, no difference. I am still having the issue. I started with Migration Assistant coming from my MBP 2016 over Thunderbolt and there was some sort of disaster. After the end of the process, the screen was not readable with only gibberish like the fonts had blown up somehow. So, I deleted the volume and did a ground up restore. I did reattempt Migration Assistant and it worked great (and fast) the second time.


Summary being, at the end of a long day 1, I had migrated twice and formatted and restored once. Anyway after all that I am still having nightly spontaneous restarts. Really wish I did not sell off my MBP 2016 so fast. This is killing me for work.


Being the paranoid type, at the end of this journey I will feel like I have to rebuild again given how many hard crashes have occurred and concerned about the status of the disk contents.

Jul 29, 2018 1:18 PM in response to krypttic

Totally agree. I got the maxed out version at over $7k w/Apple care and tax. Pretty much a month’s income for most. I am a heavy user of virtual machines. As an EE and developer myself, I get how hard these things can be to isolate and how disparate things can interact. Just trying to get Apple support any info I can. That said, Apple is one of the highest valued companies on the planet with 10s of thousands of people begging to work there. It was disappointing to hear this issue may have started with iMac pro so the runway for the solution is longer than just a couple of weeks. I am hopeful they’ll apply whatever resources are necessary. I had been resisting all the Thunderbolt docs. I ordered a Caldigit dock today to clean up all my device connections. Just to make troubleshooting a wee bit more interesting.

Aug 4, 2018 4:10 AM in response to kzone272

Yes, those errors seem to go hand-in-hand with the crashing I believe. However, even though I still have those errors, I can't get my MacBook to crash now. I've tried using it connected to peripherals and by itself with PowerNap reenabled, letting it both fall asleep by itself and putting it to sleep. Nothing...working like a charm now. Sure wish I knew what I did so I could tell you all.

Aug 4, 2018 12:48 PM in response to kzone272

Same error again. This time it wasn't plugged into the charger. It went to sleep with the lid open. When I came back after about a half hour it had crashed. I could get the thing to wake up or show any signs of life until I held the power button down for a while.


The battery had 77% when I rebooted so I know the battery didn't die. And I had no peripherals connected at all.


I also don't have Power Nap enabled, and never did. Time to contact Apple Support...

Aug 6, 2018 3:25 PM in response to alexdav4

I was trying to get into the Startup Security Utility from recovery mode.


I am told I need to supply an administrator password. I do enter the correct password but the password is rejected.


I do have a fairly short password and perhaps there is some unknown (to me at least) password complexity checking going on that fails. I am sure I am entering the right password. This password works for me for ordinary login but not for the Security Settings app available from recovery mode.


There is only one administrator user set up.


Any ideas?

Aug 6, 2018 4:12 PM in response to James Solderitsch

James,


I got the same offer. Keep in mind you could just return your machine and repurchase (or not). You aren't obligated to do Apple's troubleshooting for them. I was a bit irked that I was being made to jump through these hoops just to get a new machine ordered. It seems that they should at least throw in free AppleCare or give you a partial refund for agreeing to go through all this.

Aug 6, 2018 4:19 PM in response to krypttic

My machine was a custom build (extra RAM and higher capacity SSD). I could not walk in to an Apple store and get this machine off the shelf. I have not migrated my stuff yet to the new machine so there is not yet lots to re-do. And I don't want to acquire a machine that maybe has the same firmware in the T2 chip and hope for the best. A newer custom build MIGHT have newer firmware. But no one is saying this for a fact.


I think the problem is solvable but it may take time.


I know T2 issues for the new iMac Pros have not been totally eradicated after quite some time so that's another negative.

Aug 6, 2018 5:41 PM in response to James Solderitsch

James Solderitsch wrote:


My machine was a custom build (extra RAM and higher capacity SSD). I could not walk in to an Apple store and get this machine off the shelf. I have not migrated my stuff yet to the new machine so there is not yet lots to re-do. And I don't want to acquire a machine that maybe has the same firmware in the T2 chip and hope for the best. A newer custom build MIGHT have newer firmware. But no one is saying this for a fact.


I think the problem is solvable but it may take time.


I know T2 issues for the new iMac Pros have not been totally eradicated after quite some time so that's another negative.


I realize this. I was just pointing out that the process you're going through still requires you to wait a week or so to exchange your machine, and Apple is making you provide them all your diagnostic info for the privilege of an exchange you could do yourself under the normal return policy.


I'm also curious why you think the replacement machine could have different firmware. There is no indication that Apple has even acknowledged this problem, much less updated firmware behind the scenes just two weeks later.

Aug 12, 2018 8:24 PM in response to samkapoor

Please reply to this thread after your appointment. Good luck and I hope a new machine fixes the problem for you.


I just had another panic just after 2 hours of sleep. Will be speaking to an AppleCare rep tomorrow about my case.


I am also upgrading from a mid 2012 Retina Pro (boosted to 1 TB SSD with 16GBs of RAM). I guess I will need to hold on this machine for awhile longer while this problem gets sorted out.


Really was looking forward to the increased speed, more RAM and higher capacity SSD.

Aug 13, 2018 4:13 PM in response to Andrew Preece

FWIW, I haven't had the BridgeOS panic now in 8 days. I had it every night for the first week and told support I could reproduce it at will. Now, nothing. I guess that is a good thing. But, it hints at how challenging this may be for Apple to find and resolve. I just decided to go back to working as normal. All my devices are connected. I work during the day and backup/sleep at night. There have been no restarts now in over a week. Go figure. I have rebooted a couple of times for other things (Logitech receiver stopped being recognized a couple of times and a monitor flaked out). Presumably a reboot wouldn't effect the issue though because a reboot IS the issue, sort of.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

BridgeOS Crashes Happening on 2018 MacBook Pro with TouchBar

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.