2018 MacBook Pros crashing with "Bridge OS" error

[m-e]

system.log?

in that case no signs of bridgeOS error.

In Console :
/Library/Logs > DiagnosticReports > ProxiedDevice-Bridge > Retired

See pic here.

Hope my replacement unit will be KP free now, since I can't see any logic on the KP I experienced and what everyone here is reporting. Left my MBPr toady plugged in power, no KP, unplugged (which is how I got my KP), no KP too (even after hours of sleep)

 

[doitdada]

In Console :
/Library/Logs > DiagnosticReports > ProxiedDevice-Bridge > Retired

No selection is good?

 

[patwithamac]

Watching this thread closely.
I'll be interested to see what the final fix is.

Just as another datapoint.... Since receiving my new 15" 2018 MBP w/ i9 + 32GB + 2TB... I've never had a KP, nor any crypto_val errors.

My T2 chip firmware version is - 15P6703

 

[AZhappyjack]

Watching this thread closely.
I'll be interested to see what the final fix is.

Just as another datapoint.... Since receiving my new 15" 2018 MBP w/ i9 + 32GB + 2TB... I've never had a KP, nor any crypto_val errors.

My T2 chip firmware version is - 15P6703

Just to confirm, do you have FileVault enabled? From what I've seen (and experienced), the crypto_val errors only occurs with FileVault turned on... and the only fix is to wipe/reinstall... also, it appears to be an issue with Apple's original image installed on the machines.

 

[eagerwu]

Unfortunately, yes. I had a look and was hoping that I had a different firmware version, but no

Are you on Mojave or High Sierra? Would it make a difference? Seems that no crash on Mojave yet.

 

[SDColorado]

Are you on Mojave or High Sierra? Would it make a difference? Seems that no crash on Mojave yet.

It might. I have been hesitant to go there, at least until after the Genius Bar appointment. I mentioned in an earlier post that Apple Support shut me down on support assistance with my iPhone X until I rolled back IOS to 11.

So I just don't want to listen to any BS from them about how Mojave may be the cause of my problems and how they can't support devices with beta software. So until then, I will try to avoid another "Britanie" moment

 

[zargap]

It might. I have been hesitant to go there, at least until after the Genius Bar appointment. I mentioned in an earlier post that Apple Support shut me down on support assistance with my iPhone X until I rolled back IOS to 11.

So I just don't want to listen to any BS from them about how Mojave may be the cause of my problems and how they can't support devices with beta software. So until then, I will try to avoid another "Britanie" moment

Yeah, it would be neat if Mojave fixes it but running a beta OS isn't a great solution. Frankly this is a serious and worrying issue but in practice it's more annoying than anything, I haven't lost any work or anything.

 

[macpcf]

It might. I have been hesitant to go there, at least until after the Genius Bar appointment. I mentioned in an earlier post that Apple Support shut me down on support assistance with my iPhone X until I rolled back IOS to 11.

So I just don't want to listen to any BS from them about how Mojave may be the cause of my problems and how they can't support devices with beta software. So until then, I will try to avoid another "Britanie" moment

Is there a date for official mojave release yet?

 

[SDColorado]

Yeah, it would be neat if Mojave fixes it but running a beta OS isn't a great solution. Frankly this is a serious and worrying issue but in practice it's more annoying than anything, I haven't lost any work or anything.

Well, the solution the tech gave me over the phone was also half-arsed. While it appears to work in preventing crashes, I am not going to leave it that way. Shouldn't have to leave it that way.

His suggestion was to go into Energy Saver and set the "Turn Display Off After" setting to Never. Which of course comes with a warning that says "Never letting your display go to sleep may shorten its life" to which he assured me it would not. Yeaaaah.

But it also causes the laptop to remain warm and effectively stops it from deep sleeping to. That is definitely a half-arsed fix to a real problem.

 

[fokmik]

nothing here,after one week

 

[m-e]

Yeah, it would be neat if Mojave fixes it but running a beta OS isn't a great solution. Frankly this is a serious and worrying issue but in practice it's more annoying than anything, I haven't lost any work or anything.

No, Mojave doesn't solve this issue (at least not on Public Beta 4, since I had 2 KP on it)
I am on Public Beta 5 now and waiting to see. But since in my case I can't reproduce it, we are never really sure it's ok...
[doublepost=1533742028][/doublepost]

No selection is good?

Means at least it wasn't a KP... so may be good!

 

[eagerwu]

Beta

No, Mojave doesn't solve this issue (at least not on Public Beta 4, since I had 2 KP on it)
I am on Public Beta 5 now and waiting to see. But since in my case I can't reproduce it, we are never really sure it's ok...
[doublepost=1533742028][/doublepost]
Means at least it wasn't a KP... so may be good!

Beta 6 has been released. Care for a quick test on the latest version?

 

[jjs357]

Anyone doing this:

https://support.apple.com/en-us/HT208891

to use your main APFS disk to host High Sierra and Mojave at the same time?

Are the new 2018 Macbook Pros supported for this option?

 

[Marketh]

I really want to know what the root cause of this is, as at the moment there seems to be no rhyme or reason as to who is being affected and who isn't.

You would think a fix will come in a supplemental update, but we might never find out the exact reason why

 

[zandorf]

I really want to know what the root cause of this is, as at the moment there seems to be no rhyme or reason as to who is being affected and who isn't.

You would think a fix will come in a supplemental update, but we might never find out the exact reason why

Hmm, I was just about to buy a new MacBook Pro but I think I will wait to see this issue resolved.

 

[Marketh]

Hmm, I was just about to buy a new MacBook Pro but I think I will wait to see this issue resolved.

I think in the grand scheme of things, this issue isn't majorly widespread. However waiting is never a bad idea!

 

[vtgeek]

Just happened to me after 4 hours use and did it yesterday morning after using it less than 20 minutes. 13, i7,16GB, 1TB. LG 4K Display via USB C, bluetooth wireless apple keyboard and magic trackpad 2.

Just going to some web sites.

The machine completely freezes and then the fan on the unit spins up about 5-8 seconds later and it reboots.

Get the bridge OS error report and submit it.

Seems par for the course.

 

[SDColorado]

Hmm, I was just about to buy a new MacBook Pro but I think I will wait to see this issue resolved.

I am at that point as well. I have had mine a week. Not sure whether to have them swap it and hope for better luck, send it back and wait until a fix has been announced, or go a different route. I am as comfortable and happy with Windows 10 and I am with OS, so not fussed there

 

[patwithamac]

Just to confirm, do you have FileVault enabled? From what I've seen (and experienced), the crypto_val errors only occurs with FileVault turned on... and the only fix is to wipe/reinstall... also, it appears to be an issue with Apple's original image installed on the machines.

I do not have FileVault enabled.
I also did a wipe/reinstall of High Sierra on day-1.
My use case requires case-sensitive file system. So, I reformatted the SSD as APFS case-sensitive (no encryption).

 

[iam2diezel]

I had not experienced any KPs since this past Friday afternoon when the computer was left to sleep, lid closed, not connected to anything, including power, until last night.

Left the machine connected to my TB3 dock last night. Screen saver came on but I never did put the machine to sleep. Woke up this morning to grab the computer before heading out the door and found that it wasn't responsive. Closed the lid, threw it in my bag and headed in to work. When I got there, I opened the lid and it was still unresponsive. It was also pretty hot. No matter what I did, it wouldn't come on, so I needed to do a force shutdown. Started it back up a few minutes later, at which point I received the Bridge OS error.

15" i9 with 32 GB RAM and 1 TB SSD
10.3.6 with Supplemental Update
T2 Firmware: 15P6703

 

[navaira]

Just to confirm, do you have FileVault enabled? From what I've seen (and experienced), the crypto_val errors only occurs with FileVault turned on... and the only fix is to wipe/reinstall... also, it appears to be an issue with Apple's original image installed on the machines.

I got another MBP – it's production date is July 30! – and out of the box Disk Utility had crypto_val errors. Formatted the drive, reinstalled system (without recovery loop this time, phew), no crypto_val. I haven't experienced the bridgeOS error YET, because I'm still busy keeping the computer on doing backups of backups of backups, but it fell asleep today (forgot to check power settings after migration), and nothing happened.

I have to say the crypto_val thing might be the worst mess I experienced from Apple so far. Not because of what it does, but because my machine was manufactured literally nine days ago and as evidenced they are still all being flashed with the corrupt image.

 

[m-e]

Just happened to me after 4 hours use and did it yesterday morning after using it less than 20 minutes. 13, i7,16GB, 1TB. LG 4K Display via USB C, bluetooth wireless apple keyboard and magic trackpad 2.

Just going to some web sites.

The machine completely freezes and then the fan on the unit spins up about 5-8 seconds later and it reboots.

Get the bridge OS error report and submit it.

Seems par for the course.

At least seems like the use of external screen and hubs multipliés the chances of a KP.
Will be using mine (dell 24" plus Belkin TB3) in 2 weeks and will see how it goes.

Beta

Beta 6 has been released. Care for a quick test on the latest version?

Dev Beta 6 is Public Beta 5

I got another MBP – it's production date is July 30! – and out of the box Disk Utility had crypto_val errors. Formatted the drive, reinstalled system (without recovery loop this time, phew), no crypto_val. I haven't experienced the bridgeOS error YET, because I'm still busy keeping the computer on doing backups of backups of backups, but it fell asleep today (forgot to check power settings after migration), and nothing happened.

I have to say the crypto_val thing might be the worst mess I experienced from Apple so far. Not because of what it does, but because my machine was manufactured literally nine days ago and as evidenced they are still all being flashed with the corrupt image.

Were did you find the date of production?

 

[sk8r1230]

Kinda sad macrumors hasn’t done a story on this while the speaker crackle issue has over a 100 less posts but gets front page news.

 

[zargap]

I messed up my own testing of this theory by accidentally connecting my dock, but if anyone else would like to try it it would be neat, I'm trying to see how long I can go without crashes if I only ever have the power brick plugged in after booting. I went a whole 48 hours crash-free before accidentally connecting my dock (I bought a new longer cable for it that's also white lol).
It's clear that this crash can happen with nothing connected, but I'm not sure if it's happened if nothing has been plugged in previously.
Also I don't think I've said I'm on a base model 15", High Sierra w/ Supplemental Update.

 

[AZhappyjack]

Kinda sad macrumors hasn’t done a story on this while the speaker crackle issue has over a 100 less posts but gets front page news.

https://www.macrumors.com/2018/08/08/2018-macbook-pro-crackling-speakers-reports/