2018 MacBook Pros crashing with "Bridge OS" error

[Premal212]

As an amateur following this thread, Im beginning to think that those of us who are casual or light users such as web surfing, e-mail, texting, etc. aren't seeing the problem because we aren't stressing the device. Those who are professional users and are attaching all kinds of equipment are getting the crashes and when they get a replacement the same thing happens because their use hasn't changed. It would be unlikely for the majority to have no problem and a few to be unlucky enough to keep getting multiple machines with the same flaw. Unfortunately that may mean all 2018 MacBook Pros are affected.

I thought this at first, but there was one person here who didn't plug any peripherals into the machine and alas, the KP.

I just hope I don't get a dud machine this week.

 

[SDColorado]

I thought this at first, but there was one person here who didn't plug any peripherals into the machine and alas, the KP.

I just hope I don't get a dud machine this week.

Yes. I don't know if you are referring to me, but that is what happened to me. I did nothing more than the initial setup and took a break to take care of my dogs. Came back, machine wouldn't wake when I hit a key. Had to restart and it restarted to a KP related to the BridgeOS. Nothing installed on the machine, not even the supplemental update. You will see some similar stories on other threads and even a few similar responses to that ZoneOfTech video. I am not the only one.

 

[Premal212]

Yes. I don't know if you are referring to me, but that is what happened to me. I did nothing more than the initial setup and took a break to take care of my dogs. Came back, machine wouldn't wake when I hit a key. Had to restart and it restarted to a KP related to the BridgeOS. Nothing installed on the machine, not even the supplemental update. You will see some similar stories on other threads and even a few similar responses to that ZoneOfTech video. I am not the only one.

Hahahaha, yes I was referring to you, I shouldn't be laughing though. Sorry !

 

[SDColorado]

Hahahaha, yes I was referring to you, I shouldn't be laughing though. Sorry !

You do have to kind of laugh at the absurdity of it don't you? Then the replacement one arrived with nicks in the aluminum along left hand side by the speaker. Apple claimed that it must have happened in shipping, but the outer brown box was pristine and unblemished, the inner white box the same. I am 99.9% sure it went into the box that way. So far unit #3 has gone 6 days without a crash, but I am honestly not sure I will ultimately keep it even if it goes to day 14 without one. Just not convinced.

Edit: The Unit #1 prior to exchange, proceeded to have random BridgeOS related KP's. Sometimes with peripherals attached, sometimes without. Sometimes with the lid open, sometimes when closed. There did not seem to be much rhyme or reason to it.

Edit 2: The other problem with unit #1 was that the laminate or coating or whatever the proper word is was really uneven and wavy along the top of the display. It almost looked like the glass was rough, but it felt smooth, but it was impossible not to see. When I took it to the local Apple store, the tech also immediately commented on it when he open it up. QC seems to be a bit of an issue lately.

 

[@mosphericBurn]

Add me to the list.
No peripherals connected at time of crash

2018 Macbook Pro 15"
i9, Radeon 560X

 

[Premal212]

You do have to kind of laugh at the absurdity of it don't you?
Then the replacement one arrived with nicks in the aluminum along left hand side by the speaker. Apple claimed that it must have happened in shipping, but the outer brown box was pristine and unblemished, the inner white box the same. I am 99.9% sure it went into the box that way. So far unit #3 has gone 6 days without a crash, but I am honestly not sure I will ultimately keep it even if it goes to day 14 without one. Just not convinced.

Before all of this, I was genuinely thinking, these guys must be really unlucky or plugging in some DODGY third party/aliexpress/shipped from china/back of a garage - peripherals. Bank Holiday in the UK today, you forget the rest of the world is still working, so we should be getting close to something tangible?

Mine has nicks in the aluminium along the keyboard. They stated the same thing, must have happened during shipping, I mean come on, you're going to blame UPS for a nick on the keyboard. Even packaging, I imagine these things happen there either, it's because you didn't pick it up on the belt as a defect, and some poor soul is going to accept this as 'okay'.

I definitely recommend extending your 14 days out mate. That's the first thing I'm doing when I receive mine, I would love to ride to 2022 without a fault, but I'm not leaving £3000 in the hands of hope and Applecare (which is awesome, but if it can be prevented in the first place i'll do that). But I'm worried about my replacement, after hearing about light bleeding.

When you start paying these prices you can be picky, you can return your device multiple times, you can ask for 30 days return period. It's not like we're buying hardware from the bottom of the tech chain #aliexpress

 

[SDColorado]

Mine has nicks in the aluminium along the keyboard. They stated the same thing, must have happened during shipping, I mean come on, you're going to blame UPS for a nick on the keyboard. Even packaging, I imagine these things happen there either, it's because you didn't pick it up on the belt as a defect, and some poor soul is going to accept this as 'okay'.

I definitely recommend extending your 14 days out mate. That's the first thing I'm doing when I receive mine, I would love to ride to 2022 without a fault, but I'm not leaving £3000 in the hands of hope and Applecare (which is awesome, but if it can be prevented in the first place i'll do that). But I'm worried about my replacement, after hearing about light bleeding.

When you start paying these prices you can be picky, you can return your device multiple times, you can ask for 30 days return period. It's not like we're buying hardware from the bottom of the tech chain #aliexpress

They offered me a bit of a refund if I was wanting go keep that one and deal with the nicks, and I did think about it. But the nicks were actually pretty sharp and trying to smooth them would have made it even bigger and more noticeable, so I declined that option. But there is just no way those occurred during shipping. Clearly a defect that should have been picked up and wasn't, as should the laminate/coating issue with the first display. It wasn't one of those micro-defects like the ones you see posted about "one of my keys sounds different" or "one button seems easier to push than the others". The screen issue was obvious and the tech made immediate note of it.

I have never had the light bleed issue, or coil whine or the proper speaker crackle, though unit #1 would at times did make a random crackle/hiss like a radio tuned into an empty channel, if you know what I mean. But not when you were using the speakers, at least not that you could notice. Just when the machine was idle and not doing anything.

I am definitely going to see if they will extend it to 30, because I am not going to be convinced inside of 14. I currently have 8 of 14 remaining on this one.

 

[csurfr]

BridgeOS changed again in this beta:

From 16P50366a

To 16P50371a

At least something is changing behind the scenes. No crashes in almost 3 weeks.

 

[Premal212]

They offered me a bit of a refund if I was wanting go keep that one and deal with the nicks, and I did think about it. But the nicks were actually pretty sharp and trying to smooth them would have made it even bigger and more noticeable, so I declined that option. But there is just no way those occurred during shipping. Clearly a defect that should have been picked up and wasn't, as should the laminate/coating issue with the first display. It wasn't one of those micro-defects like the ones you see posted about "one of my keys sounds different" or "one button seems easier to push than the others". The screen issue was obvious and the tech made immediate note of it.

I have never had the light bleed issue, or coil whine or the proper speaker crackle, though unit #1 would at times did make a random crackle/hiss like a radio tuned into an empty channel, if you know what I mean. But not when you were using the speakers, at least not that you could notice. Just when the machine was idle and not doing anything.

I am definitely going to see if they will extend it to 30, because I am not going to be convinced inside of 14. I currently have 8 of 14 remaining on this one.

Yeah, I would enforce it, someone either in this thread or the speakers thread stated they spoke to Apple Aftersales and discussed that they wanted to see if the problems disappeared after Mojave comes out, the Apple Rep stated that was a fair ask and extended their returns to 30 days. I wouldn't want to see you here in 9 days saying you've got a KP/Speaker Crackle.

I know what you mean, these are meant to be tools, not your best friend that needs to be perfect. It needs to work to a good solid standard and thats that. Right now, they aren't.

BridgeOS changed again in this beta:

From 16P50366a

To 16P50371a

At least something is changing behind the scenes. No crashes in almost 3 weeks.

Has anyone watched Oceans 13, where they rig the casino slot machines, and that fat woman takes all the cash. I'm thinking it's something like that, a sequence of events that someone must do, and a KP would happen, for SDColorado, they must have done something at the warehouse on that machine.

It's just about the right sequences and accessories. Let's see. On the note of changing SMCs, how often are they updated in normal updates, i.e. from 13.1.1 to 13.1.2. Not the bigger upgrades, but the supplementary ones.

 

[fullauto]

BridgeOS changed again in this beta:

From 16P50366a

To 16P50371a

At least something is changing behind the scenes. No crashes in almost 3 weeks.

Hey. Had a flick over your posts regarding Bridge OS - was upgrading to Mojave the only thing you did to 'fix' your crashing?

 

[csurfr]

Hey. Had a flick over your posts regarding Bridge OS - was upgrading to Mojave the only thing you did to 'fix' your crashing?

Well, I have only had two crashes since I've had the machine (launch weekend). I hadn't had any problems until I let it go to sleep with my 4k UltraFine connected. It was sporadic at best.

I hadn't upgraded to Mojave until, I think 3 betas ago. I've not had a crash since, and I have all of the things back on (Power nap, notifications, etc), and am leaving my screen connected overnight with the lid open again.

While I can't say for certain that this has fixed it, I can say that I haven't had a single problem in quite a while. Does that help?

 

[CreeptoLoser]

On the note of changing SMCs, how often are they updated in normal updates, i.e. from 13.1.1 to 13.1.2. Not the bigger upgrades, but the supplementary ones.

Whenever there’s new hardware features there will usually be an update or two. There’s almost always new firmware with the yearly macOS.

That’s less than PCs that have anywhere between 5-10 BIOS updates a year.

 

[onelm]

Well, I have only had two crashes since I've had the machine (launch weekend). I hadn't had any problems until I let it go to sleep with my 4k UltraFine connected. It was sporadic at best.

I hadn't upgraded to Mojave until, I think 3 betas ago. I've not had a crash since, and I have all of the things back on (Power nap, notifications, etc), and am leaving my screen connected overnight with the lid open again.

While I can't say for certain that this has fixed it, I can say that I haven't had a single problem in quite a while. Does that help?

I upgraded my BridgeOS using the Mojave Beta installer (see my post 20 pages back ), but kept High Sierra as my actual OS. And while the machine crashed less often, I still got overnite kernel panics, mainly with displays connected but also one with only the charger connected (lid open).

Since then, as we've all dug into our various crash logs, the "AppleSMC" driver in macOS is consistently the thread that's panicking, so it's entirely possible that upgrading to BridgeOS 3.0 but maintaining the High Sierra version of AppleSMC driver is not sufficient to stop the panics. That would make sense, if AppleSMC is one of the things that's...er...bridging macOS to BridgeOS? (take this with a grain of salt--to date I haven't seen anyone state with confidence what the actual architecture is in terms of macOS drivers and where the exact connection points are between macOS, Bridge OS, and the T2).

Anyway... upgrading to BridgeOS 3.0 _and_ actually running Mojave as the main operating system means an updated AppleSMC, and that more of the code related to these T1/T2 chips is newer witha greater potential to have had bug fixes applied. I look forward to being able to move to Mojave and see how that goes. I'd also still love to see if anyone using Win10 under boot camp is getting any overnight sleep crashes!

 

[turbineseaplane]

Bean Counter Tim's Apple sure is "fun"

 

[Premal212]

I upgraded my BridgeOS using the Mojave Beta installer (see my post 20 pages back ), but kept High Sierra as my actual OS. And while the machine crashed less often, I still got overnite kernel panics, mainly with displays connected but also one with only the charger connected (lid open).

Since then, as we've all dug into our various crash logs, the "AppleSMC" driver in macOS is consistently the thread that's panicking, so it's entirely possible that upgrading to BridgeOS 3.0 but maintaining the High Sierra version of AppleSMC driver is not sufficient to stop the panics. That would make sense, if AppleSMC is one of the things that's...er...bridging macOS to BridgeOS? (take this with a grain of salt--to date I haven't seen anyone state with confidence what the actual architecture is in terms of macOS drivers and where the exact connection points are between macOS, Bridge OS, and the T2).

Anyway... upgrading to BridgeOS 3.0 _and_ actually running Mojave as the main operating system means an updated AppleSMC, and that more of the code related to these T1/T2 chips is newer witha greater potential to have had bug fixes applied. I look forward to being able to move to Mojave and see how that goes. I'd also still love to see if anyone using Win10 under boot camp is getting any overnight sleep crashes!

God I’m so bad at remembering names, but there’s “one guy” as I always say, on this thread who had a way of bringing this on each time.

https://discussions.apple.com/thread/8465477?page=10

Scroll down to a guy called Horho77, they pasted the same thing here too. More awareness - better for us.

They found a way of replicating it each time. It would be amazing if someone with the latest beta tried this out, but I can totally understand if they don’t. I wouldn’t wish this on anyone. Literally playing with fire.

If someone can report back that there is no issue, then god bless!! We are in good hands, if not.. pls send help

 

[fireedo]

wow, happened to me last night, with only connected to the MacBook Pro is charging cable, my mbp restarted with bridge OS error message
I'm using mbp 15 2018 2.6/16/512 560x

 

[Ma2k5]

Over a month on and still no fix - it is surprising. The throttle fix came really quick. Hopefully this doesn't mean the issue is hardware level (rather than just a complex issue), that would be a disaster.

Edit: I say a month but this issue is a lot older, as it was experienced in the T2 iMac's too...

 

[apiro]

Sorry for my ignorance. I understand T2 chip is in 13" as well but most reports here are from 15". Is 13" as badly affected as 15"? Going to buy maxed out 13" soon and kinda concerned.

 

[Ma2k5]

Sorry for my ignorance. I understand T2 chip is in 13" as well but most reports here are from 15". Is 13" as badly affected as 15"? Going to buy maxed out 13" soon and kinda concerned.

Well there is a user on this post https://discussions.apple.com/thread/8465477?page=10 by user horho77
who is using a 13" and found a way to replicate, so I wouldn't say any particular model is safe.

There are users who said they have never got a KP, @maflynn springs to mind (he has the 15" model) and I would trust him. So it sounds like very specific operations cause the issue.

The steps shed some light on what the root cause can be:

--------------------------------------------------------------------------------------

--------------------------------------------------------------------------------------

Of course this is just one example of how the error comes about and there could be many other scenario's - some have mentioned they use no peripherals and got the error. Take what you will from that.

 

[RumorConsumer]

Well there is a user on this post https://discussions.apple.com/thread/8465477?page=10 by user horho77
who is using a 13" and found a way to replicate, so I wouldn't say any particular model is safe.

There are users who said they have never got a KP, @maflynn springs to mind (he has the 15" model) and I would trust him. So it sounds like very specific operations cause the issue.

The steps shed some light on what the root cause can be:

--------------------------------------------------------------------------------------
View attachment 778225
--------------------------------------------------------------------------------------

Of course this is just one example of how the error comes about and there could be many other scenario's - some have mentioned they use no peripherals and got the error. Take what you will from that.

My wife has a 2.9 fully loaded unit and uses the heck out of it and has not had one KP at all. She's had hers since launch. My 2.6 store bought unit has done it once - SMC like everybody else.

The "its a hardware thing" posts are a bit fear mongering. Its *highly* unlikely that a problem you experience on a computer cannot be resolved with a software adjustment. The line is so increasingly blurry.

Take heart friends. They are capturing units. They are smart people. The T2 has a lot more security features for bug testing procedures to clear as they work on it so this might account somewhat for the time its taking as new builds have to pass the T2's checks.

 

[maflynn]

There are users who said they have never got a KP, @maflynn springs to mind (he has the 15" model)

Correct I use my MBP daily and is been stable. I've not had one crash.

 

[dspdoc]

Over a month on and still no fix - it is surprising. The throttle fix came really quick. Hopefully this doesn't mean the issue is hardware level (rather than just a complex issue), that would be a disaster.

Edit: I say a month but this issue is a lot older, as it was experienced in the T2 iMac's too...

It is STILL occurring in the iMPs...

 

[Ma2k5]

My wife has a 2.9 fully loaded unit and uses the heck out of it and has not had one KP at all. She's had hers since launch. My 2.6 store bought unit has done it once - SMC like everybody else.

The "its a hardware thing" posts are a bit fear mongering. Its *highly* unlikely that a problem you experience on a computer cannot be resolved with a software adjustment. The line is so increasingly blurry.

Take heart friends. They are capturing units. They are smart people. The T2 has a lot more security features for bug testing procedures to clear as they work on it so this might account somewhat for the time its taking as new builds have to pass the T2's checks.

I would hope it isn't a hardware issue, the only reason I think it could be is that the T2 chip is the secure enclave for encrypted storage and secure boot, system management controller, SSD controller, and audio controller, "Hey Siri" etc - quite a lot.

Don't get me wrong, even if it was a hardware issue it isn't to say that it means everyone is likely to experience the issue, just that the issue itself may require some tweak on the hardware level. If it is software, Apple are taking a very long time to fix what I consider a very high priority issue for those who experience this.

 

[dspdoc]

I would hope it isn't a hardware issue, the only reason I think it could be is that the T2 chip is the secure enclave for encrypted storage and secure boot, system management controller, SSD controller, and audio controller, "Hey Siri" etc - quite a lot.

Don't get me wrong, even if it was a hardware issue it isn't to say that it means everyone is likely to experience the issue, just that the issue itself may require some tweak on the hardware level. If it is software, Apple are taking a very long time to fix what I consider a very high priority issue for those who experience this.

Hoping for a fix soon.

 

[tjoab]

Took a trip to the Apple store and put some of the 2018 mbp’s to sleep waiting 30 min or so while browsing any updates on this forum and tried to wake them up...of course they don’t crash

looked at the setting and those sons of b****es took the precautions from this site loooool
(https://imgur.com/a/3CnNdSg)

I left a couple of them open on this thread, maybe it’ll get to the engineers faster that way