BridgeOS Crashes Happening on 2018 MacBook Pro with TouchBar

Well I also got a 2018 13inch macbook pro with Touch Bar 16Gb memory and 2.7 GHZ i7 processor. My computer doesn't crash but it sometimes just froze randomly and I need to wait about 1 minute until it is awake

My new MacBook Pro 2018 13” i7 is having this exact issue. Kernel Panic when waking from sleep, all updates installed, atttempted to reinstall OS, no change. Very frustrating for a brand new computer.

Hello Russ, I can imagine how you feel. Please let all us confirm in below.
1. Do you use Mojave same as Andrew? Or Do you use High Sierra 10.16.3 with Supplemental update 2?
2. Do you see the report of issue when you login right after opening the shell from closed clamshell style?

Please kindly let all us know. Thank you.

Heya -- sorry for my delay in responding.

The only peripheral I have is an iPhone, and even then just to charge it. I didn't notice any issues connecting to it.

Also just wanted to reiterate that the crashes when the clamshell is closed continue to happen. It is not 100% of the time, but I would say a few times a week.

Hello slifty,

Thank you so much for your information. It was really helpful for me. Almost there, maybe.
However same issue as me exists still when use external devices to supply the power according to him maksimrv. Let me see two more weeks whether the issue occur in new model that has T2 security chip.

To All,
Please Kindly provide me whether you can use peripherals without any issue especially BridgeOS issue. I really need two functionality. The one of them is to supply electric power to the device and the other ons is possible to transfer data(communicate). In my case and most of scenario, I saw BridgeOS crash report after logging in after I opened a lid. But I maybe seen when I use a device after login. When I got this issue, I could not use all USB Type C port. But After I moved to other desk with my Mac by changing the angle of the lid a little bit and the connect to power cable, It worked with my devices that did not work several days. It was very tough week.

Well, Apple can fix this issue on High Sierra 10.13.6 and Mojave.

Thank you.

Hi @maksimrv,

I'm wondering when your MBP was manufactured? I have a hunch that Apple fixed a manufacturing fault that causes this issue. If your MBP was made recently, then my hunch would be wrong. I returned two with the same fault about 4 months ago and I'm hoping new machines are good and I can re-purchase.

By the way, Apple support engineers recommended I return the machines, and they guessed it would be a hardware fault that would get ironed out at some stage. I really hope I don't have to wait for a whole new MBP refresh!

Cheers,

Hi @GrumFromOz,

Thank you so much for your valuable information.

I was expecting the information. It's surely same issue. It makes me sure that It's really difficult problem to be fixed. Well, I usually take my old MBP somewhere to working on my project. But, I cannot say there is an outlet there. Which means, I should wait for buying MBP2018 touch bar until I will get the good news from you or this thread.

It was really helpful information for all. Thank you so much!

I had MBP 2018 Touch bar model, was according to above tool;

Production week : -34- (August)

Production year : -2018-

Factory: C0 (Quanta Computer (Subsidiary = Tech Com) China)

Anyway, My old MBP Mid-2012 "13(Not Retina Display) has more than 8GB memory and SSD. So, I can still survive except the resolution. But, I really need T2 security chip and high resolution.

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,

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

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

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.

Thanks, Grant.

I indeed reported the issue to apple support and got a case number.