Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
2018 MacBook Pros crashing with "Bridge OS" error
- Thread starter kryptticAZ
- Start date
- Sort by reaction score
Getting pretty sick of this. It didn't even save a crash log so had to take a screenshot.
I had 3 at my MBP 13'' 2018 model that I recently purchased for 3100$.....
I really hoped that Mojave would fix it but it hasn't. I just had my second in Mojave now...
I am really frustrated and I don't even know if i can replace my mac or not. I haven't been able to reproduce the issue with consistency. I have only noticed that it relates to either sound or graphics, it has only happened when I had music (itunes) playing or watching a video (either utube, vlc, or iina).
It is not related to having anything plugged on it really. I only had the usb-c power cable at one or two of the 4-5 total kernel panics.
Also I noticed that the Mojave "Previous Shutdown Cause" changed from -11 that were at High Sierra to 5 or 6. I really really don't know how to even approach this **** :/
I really hoped that Mojave would fix it but it hasn't. I just had my second in Mojave now...
I am really frustrated and I don't even know if i can replace my mac or not. I haven't been able to reproduce the issue with consistency. I have only noticed that it relates to either sound or graphics, it has only happened when I had music (itunes) playing or watching a video (either utube, vlc, or iina).
It is not related to having anything plugged on it really. I only had the usb-c power cable at one or two of the 4-5 total kernel panics.
Also I noticed that the Mojave "Previous Shutdown Cause" changed from -11 that were at High Sierra to 5 or 6. I really really don't know how to even approach this **** :/
Last edited:
I still believe all units are affected in the same way. The difference is that some users get more KPs, others get less KPs, and some others didn't get any KP yet, but my belief is that this is because they use the MBP in different ways, or have different settings, or even KPs depend on pseudo-random scenarios that depend on how "lucky" you are (due to weird syncing between heterogeneous chips that could cause problems similar to race conditions, for example, and that are not always easy to reproduce).
Not impossible! You'd think if it was gonna happen it would be happening 90+ days from launch which is about where we are at right now. Again, I have a 2.9 unit with ZERO KPs that is being run daily with audio and video and graphics. Adobe, Final Cut, the works.
Eventually, this thread will die, no fix from Apple, no mention from Apple that a problem existed, problem solved....
for Apple.....
I noticed no more youtube posts on this issue, it's dying quickly...
cricket noises.
There is no fix coming, because in Apple's world, this doesn't exist.
They can deflect this for longer than you can wait on a fix.....
for Apple.....
I noticed no more youtube posts on this issue, it's dying quickly...
cricket noises.
There is no fix coming, because in Apple's world, this doesn't exist.
They can deflect this for longer than you can wait on a fix.....
How much money will you give me if they fix it in the next month?
I don't understand why people don't just return their MBPs if they're unhappy with it. It's over $3000 for a laptop you can't even work properly on. And this crash is just one of the many problems of the 2018 MBP.
because we can't, some out of the return window and others don't live in places with apple stores and are at the mercy of third party service providers.
If I could I would return this piece of junk in a heart beat.
If it was a hardware defect, you might be correct. But it seems to be software/firmware, and the MBP is a product that sells quite a number of units, so I think it's quite possible that it will be fixed in the next months. The sad thing is that Apple invests more in the products they sell most. If there were the same number of engineers working on MacOS as on iOS, this would be fixed already. Also, some iMac Pro users say their T2-related KPs have not been fixed yet, but I wouldn't be surprised if the MBP 2018 KPs get fixed before the iMac Pro (just for the reason above: more units sold, more people shouting).
I'm getting ready to leave Apple in the future, but for the moment I cannot do it yet. And I really need a new MacBook right now, as I extended the life of my late 2010 MBA beyond what most people would consider reasonable... waiting until Apple released a new MacBook worthy of being the successor to the late 2010 MBA. I hoped for the MBA successor to have been presented in September, but it wasn't. I cannot wait more (I need to run a VM with Autodesk Revit and Robot on it, and that's not possible to achieve with my 4GB MBA anymore). Also, the MBP lets you configure it with 32GB RAM, and this will extend its life, so I went for it.
BTW, I just got an email telling my 15''/i9/560X/32GB/1TB/Silver is ready for pick up (it was delayed to next Wednesday, but it already arrived, so they finally were only 1 day late --it was initially for last Friday). I have mixed feelings... very happy but also scared to get KPs... I'll go to the shop 3 hours from now... will it have Mojave or HS? (ordered in Sept 14)... hmmm....
What I am doing in order to "consistently" reproduce it, is to download a season series (many hours of video) and leave it playing the whole season overnight.
If you wake up and your laptop is off, it means that it crashed during the night. I have found that it does for me 2/3 of the times i do this, at least. This is why I believe its media related, graphics card or sound card, firmware or hardware...
If you wake up and your laptop is off, it means that it crashed during the night. I have found that it does for me 2/3 of the times i do this, at least. This is why I believe its media related, graphics card or sound card, firmware or hardware...
No It won't. I bought mine last friday and it had High Sierra on it, even though I expected Mojave. My adivce: Don't do a clean install with the current situation. The T2 Chip won't let you install something from USB.
If the issue you are able to reproduce is actually media related, then I believe it's not the same issue as the BridgeOS KPs (even if you get a BridgeOS KP, I believe it was triggered after some other fault). The "genuine BridgeOS KP" (TM) that people are reporting is related to T2 tasks: sleep, wake from sleep, and disk I/O -because of encryption.
However, your media playback depends heavily on encrypted disk I/O, so even you think it's media related, it could actually be T2-related.
[doublepost=1538390961][/doublepost]
So, if it has HS, would you suggest to stay in HS, or to update from HS to Mojave without doing a clean install?
Yes I get BridgeOS KPs. These are the same ones as many of them have pasted here. What you are saying this be the case, about the encrypted disk i/o. I didn't think about it this way.
However, the Kernel Panics I am getting report Bridge OS errors, I actually googled the first line of the KP and found this post, it should be the same. It's just that I have found a more "consistent" way to trigger it, since it is not that often.
That’s the route I took. If they get it fixed down the road I may have another look, but I had too many issues with the 3 units that I had, from KP’s to keys failing to register consistently when pressed. I fear that there are some things with this model that will never be truly fixed until 2019 or beyond. But time will tell.
Haven't had any bridgeOS panics for weeks, after tweaking the pm settings on my 2018 i9 MBP, but there's definitely something wrong with the T2; can't upgrade to Mojave, and others seem to have the same issue: https://discussions.apple.com/thread/8551507 Would love to test bridgeOS behavior on Mojave, but no can do. Apple has become a total sh*tshow.
Well normally when I do a clean install it takes 1-2h maximums. Due to the fact that I was unaware of the security of the T2, it took me about 4-5h not even having installed it.
The way which worked for me was to enter the recovery mode during boot process CMD+OPTION+R. Then Wipe it and then Install the new OS, without USB and stuff. At the first time he loaded like forever, after 3h I cancelled all and did it the next day and somehow it worked.
What would do if you could travel back in time? Would you still install from scratch? Would you update instead? Or would you keep HS for a while? (because today I'm actually in the same situation as you last week, so I'd like to know what would you do if you had this chance...)
I’d still call AppleCare and raise hell to at least get a replacement unit. Based on the facts it seems only right. They may want to service it first so let them and if it doesn’t work out then nuclear.
After 4 weeks of blood, sweat and tears they approved my replacement today.. but I have to wait 2 weeks to get it (custom). Painful. What’s more disappointing was the tech, first day on the floor, had no care about the last 4 weeks, stepped through diagnostics (all fine), then said we need to reinstall Mojave - advised I’ve done all of this twice. Oh ok well we can replace maybe the logic board? (highly doubt this is the issue - diagnostics were fine) - or order a new one. Done. Hopefully there’s no round 2, it’s not looking promising but I’ll try to remain optimistic, it’s just so much money ($5k!).