2018 MacBook Pros crashing with "Bridge OS" error

[drecc]

I don't see the message on my new 2018 MBP

Just to double check, did you do: Disk Utility -> Select "Macintosh HD" drive -> First Aid -> Run and then click "Show details" and then scroll through the entire output to check if there were any crypto_val warnings?

Thanks
[doublepost=1533389878][/doublepost]

Otherwise, all this is saying is the drive isn’t encrypted

That's worrying, my FileVault is definitely switched on... (I've double checked in System Prefs)

 

[patwithamac]

Just to double check, did you do: Disk Utility -> Select "Macintosh HD" drive -> First Aid -> Run and then click "Show details" and then scroll through the entire output to check if there were any crypto_val warnings?

Yes

Here is the entire output;

Verifying file system.
Volume could not be unmounted.
Using live mode.
Performing fsck_apfs -n -l -x /dev/rdisk1s1
Checking volume.
Checking the container superblock.
Checking the EFI jumpstart record.
Checking the space manager.
Checking the object map.
Checking the APFS volume superblock.
Checking the object map.
Checking the fsroot tree.
Checking the snapshot metadata tree.
Checking the extent ref tree.
Checking the snapshots.
Checking snapshot 1 of 1.
Verifying allocated space.
The volume /dev/rdisk1s1 appears to be OK.
File system check exit code is 0.
Restoring the original state found as mounted.
Operation successful.

 

[drecc]

Yes

Here is the entire output;

Doh, thanks for checking. Do you have FileVault enabled on the drive?

 

[zargap]

The drive stuff seems like a nonstarter for these restarts, of which I get one every 24 hours or so. I have filevault on and do get the error fwiw

 

[patwithamac]

Doh, thanks for checking. Do you have FileVault enabled on the drive?

No

 

[drecc]

Do you have FileVault enabled on the drive? No

Aha, maybe then the crypto_val warnings affect all 2018 MBPs that have FileVault enabled.... does anyone have a counterexample?

 

[AZhappyjack]

What about turning off FileVault and then re-enabling it? I am attempting that right now...

 

[Weaselboy]

Aha, maybe then the crypto_val warnings affect all 2018 MBPs that have FileVault enabled.... does anyone have a counterexample?

I was getting that error straight out of the box before I turned on FV.

 

[AZhappyjack]

What about turning off FileVault and then re-enabling it? I am attempting that right now...

I was getting that error straight out of the box before I turned on FV.

I just turned FileVault off and still seeing the errors when I run FirstAid...

 

[Weaselboy]

I just turned FileVault off and still seeing the errors when I run FirstAid...

I tried that also... no help.

The wipe and reinstall was the only thing that fixed it.

 

[AZhappyjack]

I tried that also... no help.

The wipe and reinstall was the only thing that fixed it.

#grrrrr

 

[eagerwu]

I have had my machine running all day with a USB thumb drive plugged in and it has gone to sleep a few times. No KPs yet...

I was getting that error straight out of the box before I turned on FV.

Do you only have the crypto errors but no restart or do you have both? Thx!

 

[Weaselboy]

Do you only have the crypto errors but no restart or do you have both? Thx!

All I ever had was the crypto errors and none of the other issues mentioned.

 

[AZhappyjack]

I tried that also... no help.

The wipe and reinstall was the only thing that fixed it.

In process right now... and annoyed that I have to spend another couple of hours on a weekend to get this thing running correctly.

 

[randolorian]

I feel that the crypto errors are probably a red herring and innocuous.

 

[AZhappyjack]

I feel that the crypto errors are probably a red herring and innocuous.

You could be right... but are you willing to bet your data on it?

 

[cynicmouth]

Watching this thread
My 1 week old CTO 15 inch 2.2g/16G/1T had the same issue....happened 4-5x over the past several days, a few hours after I put it to sleep it would greet me with restart and Bridge OS Error 2.4.1
I'm getting it returned and ordered a new one from Apple Store

 

[AZhappyjack]

command-option-r boot to Internet recovery (not command-r regular recovery). Once the recovery screen comes up use Disk Utility to erase the whole disk to APFS. Then quit Disk Util and reinstall the OS. When it restarts use the import tool (Migration Assistant) that comes up to bring in your data and apps etc from a Time Machine backup or clone.

That got rid of the crypto val errors for me.

What are you erasing? The Macintosh HD volume? The container? The Apple SSD?

 

[Weaselboy]

The Apple SSD?

This at the very top.... you will need to enable Show All Devices from Internet Recovery.

 

[PickUrPoison]

You could be right... but are you willing to bet your data on it?

I think OP meant a red herring with respect to the bridgeOS kernel panics.

There doesn’t seem to be any connection between the two.

 

[AZhappyjack]

I feel that the crypto errors are probably a red herring and innocuous.

I think OP meant a red herring with respect to the bridgeOS kernel panics.

There doesn’t seem to be any connection between the two.

I don't thinks so... he specifically mentioned "crypto errors".
[doublepost=1533407331][/doublepost]

This at the very top.... you will need to enable Show All Devices from Internet Recovery.

View attachment 774348

That wasn't my question... what are you wiping?

 

[SDColorado]

All I ever had was the crypto errors and none of the other issues mentioned.

I bit the bullet and followed your instructions. The error messages are now gone. But like you I never had any *known* issues aside from the error message

 

[Weaselboy]

That wasn't my question... what are you wiping?

I answered you by quoting "Apple SSD" from your earlier post. You musta missed it.

 

[AZhappyjack]

I answered you by quoting "Apple SSD" from your earlier post. You musta missed it.

Thanks... yeah, I missed it.

 

[PickUrPoison]

I don't thinks so... he specifically mentioned "crypto errors".

In any case there doesn’t seem to be any connection between the crypto_val errors and the bridgeOS kernel panics.