2018 MacBook Pros crashing with "Bridge OS" error

[Ma2k5]

It is one of the most powerful laptops with a Gtx 1050 or 1060 in such a slim form


Bridge OS crashes? Nope
Crackling speakers? Nope
Glitching touchbar? Nope
Stuck keys? Nope



It's the exact same as the MBP

1) It’s dGPU might be strong but it’s CPU isn’t, it is far weaker.
2) You are comparing it to the wrong machine, I thought this was alternatives to the MBP... Compare it to Windows laptops. There is a reason this is rarely ever the recommended laptop for anyone.

 

[Plutonius]

Thanks. Do you think if it's a good idea to return this 2018 mbp and buy a 2017 mbp? I need a laptop and cannot wait until 2019.

Nope, stick with your 2018 mbp. The 2017 mbp had massive keyboard issues.

If you need one now, the 2018 mbp should be ok. I just think that people who don't need a new one now should consider holding off until 2019 because of the T2 issues.

 

[studying001]

Nope, stick with your 2018 mbp. The 2017 mbp had massive keyboard issues.

If you need one now, the 2018 mbp should be ok. I just think that people who don't need a new one now should consider holding off until 2019 because of the T2 issues.

Yes only the crash thing troubles me. It means I can never use this laptop to do video interview.

 

[brainray]

Yes only the crash thing troubles me. It means I can never use this laptop to do video interview.

You might try an external camera. Today I asked my colleague with a brand new 15" MBP to do the PhotoBooth test, but not with the internal cam but with an attached Apple Thunderbolt display: he was able to run it about 70 minutes without any problem. BTW: the MacBook lid was closed while testing.

 

[studying001]

You might try an external camera. Today I asked my colleague with a brand new 15" MBP to do the PhotoBooth test, but not with the internal cam but with an attached Apple Thunderbolt display: he was able to run it about 70 minutes without any problem. BTW: the MacBook lid was closed while testing.

Thank you! That's a very good suggestion! But when I use OneNote to record lecture (just voice without using webcam), it also crashes. Probably the voice record has problem too.

 

[SDColorado]

It also has a 15W CPU, so a lot weaker. It has various other issues as well (Reddit/forum them). I wouldn't recommend the Book 2 as a product personally.

So do the latest gen MBP’s, but people still buy them. I personally wouldn’t recommend them either. But according to folks here, you can’t believe the complaints you read on forums, because forums are just a place where people go to complain

Razer Blade 15
XPS 9570
HP Spectre x360 15
X1 Extreme
Aero 15X

I got talked down from the Razer Blade 15”. Both the Best Buy and Microcenter near me said they are among the most returned laptops they sell. Also that customer service was very poor

 

[Ma2k5]

So do the latest gen MBP’s, but people still buy them. I personally wouldn’t recommend them either. But according to folks here, you can’t believe the complaints you read on forums, because forums are just a place where people go to complain

I mean this was in the context of an alternative to the MBP 15, I wouldn’t pick the overpriced SB2 (imo). The others Windows alternatives are cheaper, have less issues and are more portable, as well as being more powerful . Of course no laptop is issue free, but like the MBP 15, if you charge top dollar as they do with the SB2 and then gimp it with a 15W CPU, they got to do better.
[doublepost=1542754462][/doublepost]@SDColorado

Look at this for value: https://www.dell.com/en-uk/shop/lap...pd/xps-15-9570-laptop/cnx97010/configurations

i7/32GB RAM/4K/1 TB SSD for £1954. They even got a discount for 4 years premium support plus (on site warranty plus accidental damage cover) for only £152. All in, £2106 with 4 years onsite warranty plus accidental cover.

Now compare that to the ridiculous pricing of the SB 2 15” (which has an inferior CPU).

 

[PalidinoDH]

Probably already known about the air, but I bought an air Friday and just experienced my first BridgeOS crash today

 

[michael31986]

I think it has to be something we are doing. It doesn't happen every time. I'm wondering what is causing it.

 

[asiga]

Really appreciate your efforts to test it. Today I used the mbp at apple store to do test.The crash happens the same.
Actually, I don't use photo booth often, but it does affect almost all the recording. It crashes 3 times during my video interview. That's the thing I worry about most.
Do you know if it's hardware issue or software issue?

Is it reproducible in all 2018 MBPs? If affirmative, then either all the units have faulty hardware, or it is a software issue. OTOH, if it happens only to some units, then I'm afraid we are just at the same unknown situation we already were.

 

[mr.bee]

I too have the KP's on my MacBook Pro 15" bought in oktober.
Just by plugging in an external monitor I could reproduce the KP at the Genius Bar. I wasn't even logged into the system. A replacement is on it's way.

I hope this 'late' in the production line, the replacement unit is not bugged with this issue.

I received my replacement last Friday. haven't had a single crash! It's connected to an external monitor, which made it crash multiple times per day, but with this replacement unit I haven't experienced any KP.

Since yesterday I'm again on 10.14.2 Beta (18C48a) maybe this latest build also has something to do with it.

 

[studying001]

Is it reproducible in all 2018 MBPs? If affirmative, then either all the units have faulty hardware, or it is a software issue. OTOH, if it happens only to some units, then I'm afraid we are just at the same unknown situation we already were.

At least all the four mbps I tested have the same issue..

 

[michael31986]

Haven't had a crash except for once in four months and nothing was connected. No external anything. I see most get it from external monitors or connections. Very strange.

 

[KhunJay]

What is Bridge OS error? Can someone explain it in a simple way?

I use Touch ID (T2 chip) on my 2018 machine and it is stellar.

 

[Ma2k5]

What is Bridge OS error? Can someone explain it in a simple way?

I use Touch ID (T2 chip) on my 2018 machine and it is stellar.

It’s the macOS equivalent of a blue screen of death caused by T2 chip.

 

[norcal618]

Probably already known about the air, but I bought an air Friday and just experienced my first BridgeOS crash today

Have you had anymore crashes since the first? I also experienced a Bridge OS crash three days ago, after having the new MBA for almost two weeks, and using it heavily everyday. I haven't had another since though.

At first I was going to wait and see if it would happen again, before returning the laptop, but I changed my mind on that. I want to get this thing returned while I'm still within my return policy, instead of waiting for problems to happen after it is too late. I initiated the return process, now just have to ship it back. I'm torn on whether to buy another MBA, or to buy an XPS 13 for almost $400 less, with better specs. Only thing the XPS 13 is missing is Mac OS.

 

[Ma2k5]

Have you had anymore crashes since the first? I also experienced a Bridge OS crash three days ago, after having the new MBA for almost two weeks, and using it heavily everyday. I haven't had another since though.

At first I was going to wait and see if it would happen again, before returning the laptop, but I changed my mind on that. I want to get this thing returned while I'm still within my return policy, instead of waiting for problems to happen after it is too late. I initiated the return process, now just have to ship it back. I'm torn on whether to buy another MBA, or to buy an XPS 13 for almost $400 less, with better specs. Only thing the XPS 13 is missing is Mac OS.

There is no way Apple don’t know about this issue, so the question is, why are they not fixing the issue before selling it? It’s really bizarre just how long this issue has gone on for.

I am starting to doubt it’s a software issue due to how long it has gone on, and we might need some T3 hardware chip repair programme in the future.

 

[betadecay]

Some member stated that most KP's reported by BridgeOS as the T2 chip manages different things.
However, in most cases users report that the machine reboots instead of awakening and a KP pops up starting with:

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 3.1 (16P1065)","timestamp":"2018-11-06 05:43:11.83 +0000","incident_id":"D66C632B-1EBC-471B-8696-6AC8377472DA"}

But what is about the rest of the report? In example some reports show:

1. "macOSPanicString" : "panic(cpu 0 caller 0xffffff7f976f3307): \"DSB0(MacBookPro15,2): thunderbolt power on failed 0xffffffff\n\"@\/BuildRoot\/Library\/Caches\/com.apple.xbs\/Sources\/IOPCIFamily\/IOPCIFamily-330.200.11\/IOPCIBridge.cpp:1314\nBacktrace (CPU 0),
   
   
2. "macOSPanicString" : "panic(cpu 0 caller 0xffffff800fcc306f): UUID: 47D2BC26-0426-428C-A375-59C980C76CFE\nStackshot Reason: Sleep transition timed out after 180 seconds while entering darkwake on way to sleep. Suspected bundle: com.apple.driver.usb.AppleUSBXHCI. Thread 0x639c8.\
   
   
3. "macOSPanicString" : "panic(cpu 0 caller 0xffffff8006678792): \"Restart timed out in phase 'Quiescing PM'. Total 30000 ms:\nvfs_unmountall: 1214 ms\nif_down_all: 127 ms\nPowerOff\/Restart message to priority client: 362 ms @ 0x<ptr>, com.apple.driver.IOBluetoothHIDDriver(6.0.9f2)[C65C951F-5EA3-3567-888E-9426F9C6C9CE]@0x<ptr>->0x<ptr>\nPowerOff\/Restart message to priority client: 220 ms @ 0x<ptr>, com.apple.driver.IOBluetoothHIDDriver(6.0.9f2)[C65C951F-5EA3-3567-888E-9426F9C6C9CE]@0x<ptr>->0x<ptr>\nPowerOff\/Restart handler completed: 188 ms @ 0x<ptr>, com.apple.iokit.IOUSBHostFamily(1.2)[922E7520-229B-3C68-B232-A8727A20D44D]@0x<ptr>->0x<ptr>\nPowerOff\/Restart handler completed: 200 ms @ 0x<ptr>, com.apple.iokit.IOUSBHostFamily(1.2)[922E7520-229B-3C68-B232-A8727A20D44D]@0x<ptr>->0x<ptr>\nPowerOff\/Restart handler completed: 207 ms @ 0x<ptr>, com.apple.iokit.IOUSBHostFamily(1.2)[922E7520-229B-3C68-B232-A8727A20D44D]@0x<ptr>->0x<ptr>\nPowerOff\/Restart handler completed: 209 ms @ 0x<ptr>, com.apple.iokit.IOUSBHostFamily(1.2)[922E7520-229B-3C68-B232-A8727A20D44D]@0x<ptr>->0x<ptr>\nPowerOff\/Restart handler completed: 218 ms @ 0x<ptr>, com.apple.iokit.IOUSBHostFamily(1.2)[922E7520-229B-3C68-B232-A8727A20D44D]@0x<ptr>->0x<ptr>\nPowerOff\/Restart handler completed: 291 ms @ 0x<ptr>, com.apple.iokit.IOUSBHostFamily(1.2)[922E7520-229B-3C68-B232-A8727A20D44D]@0x<ptr>->0x<ptr>\nPowerOff\/Restart handler completed: 506 ms @ 0x<ptr>, com.apple.iokit.IOUSBHostFamily(1.2)[922E7520-229B-3C68-B232-A8727A20D44D]@0x<ptr>->0x<ptr>\nPowerOff\/Restart handler completed: 233 ms @ 0x<ptr>, com.apple.iokit.IOUSBHostFamily(1.2)[922E7520-229B-3C68-B232-A8727A20D44D]@0x<ptr>->0x<ptr>\n\"@\/BuildRoot\/Library\/Caches\/com.apple.xbs\/Sources\/xnu\/xnu-4903.221.2\/iokit\/Kernel\/IOPMrootDomain.cpp:4804\n

But all start with
{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 3.1 (16P1065)",...

In my case the most frequent KP is 1.)

What's about you guys?
Use the search option in "Console" to search for >macOSPanicString<.

Cheers

 

[brainray]

Is it reproducible in all 2018 MBPs? If affirmative, then either all the units have faulty hardware, or it is a software issue. OTOH, if it happens only to some units, then I'm afraid we are just at the same unknown situation we already were.

studying001 reported that he has seen it on all 4 Macs he tried. I had it on 2 MacBooks 13" here, the second one only had the PhotoBooth T2 crash.

Today I asked 2 colleagues with 15" 2018 MBPs to do the PhotoBooth test: one of them ran 1 hour without any crash, the other 2 hours. They both didn't crash. They also both didn't have any other suspicious crashes, even not with running 2 (!) Apple Thunderbolt Displays daisy-chained on one Thunderbolt 3 adapter since weeks.

This says to me: there are T2 Macs out there (probably the most) that work T2-crash-free.

All other T2 Macs are in some way faulty. Apple has not been able to fix this within the last 9 months, starting with iMac Pro. Apple won't be able to fix them, neither they are willing to identify the faulty units and they still resell them in the refurbished channel.

Conclusion as user (as others here have said before): send the Mac back - for a refund or a replacement one.

I will go for a refund and then buy a non-refurbished Mac.

 

[studying001]

studying001 reported that he has seen it on all 4 Macs he tried. I had it on 2 MacBooks 13" here, the second one only had the PhotoBooth T2 crash.

Today I asked 2 colleagues with 15" 2018 MBPs to do the PhotoBooth test: one of them ran 1 hour without any crash, the other 2 hours. They both didn't crash. They also both didn't have any other suspicious crashes, even not with running 2 (!) Apple Thunderbolt Displays daisy-chained on one Thunderbolt 3 adapter since weeks.

This says to me: there are T2 Macs out there (probably the most) that work T2-crash-free.

All other T2 Macs are in some way faulty. Apple has not been able to fix this within the last 9 months, starting with iMac Pro. Apple won't be able to fix them, neither they are willing to identify the faulty units and they still resell them in the refurbished channel.

Conclusion as user (as others here have said before): send the Mac back - for a refund or a replacement one.

I will go for a refund and then buy a non-refurbished Mac.

I actually went to apple store today to return considering I bought this Mac just last week. However, they don't allow me to return because I bought it from my school, instead of directly from the apple store. They asked me to go back to school to return, but my school only accept laptop without opening box. What should I do?

 

[Plutonius]

There is no way Apple don’t know about this issue, so the question is, why are they not fixing the issue before selling it? It’s really bizarre just how long this issue has gone on for.

I am starting to doubt it’s a software issue due to how long it has gone on, and we might need some T3 hardware chip repair programme in the future.

Yep, hopefully they replace the T2 with a T3 in the 2019 models.

 

[BeatCrazy]

There is no way Apple don’t know about this issue, so the question is, why are they not fixing the issue before selling it? It’s really bizarre just how long this issue has gone on for.

I am starting to doubt it’s a software issue due to how long it has gone on, and we might need some T3 hardware chip repair programme in the future.

I think it's software. I have some issues with the T2 in my iMac Pro. After a reboot, it works perfectly (for a while), which leads me to believe it needs a software tweak.

 

[SDColorado]

I think it's software. I have some issues with the T2 in my iMac Pro. After a reboot, it works perfectly (for a while), which leads me to believe it needs a software tweak.

Out of curiosity, what software issue do you think it would be? I mean Apple hasn’t figured it out through High Sierra into Mojave and has also had several firmware updates. It seems a bit bizarre that if it is software that they haven’t been able to figure it out yet with a system as closed as theirs, but anything is possible.

 

[BeatCrazy]

Out of curiosity, what software issue do you think it would be? I mean Apple hasn’t figured it out through High Sierra into Mojave and has also had several firmware updates. It seems a bit bizarre that if it is software that they haven’t been able to figure it out yet with a system as closed as theirs, but anything is possible.

Hard to say. My main issue is playing YouTube videos within Safari. The video will not play correctly, or is garbled/sped up. So it could be some issue with how the T2 interacts with video decoding where certain things (Google’s video codec) causes some kind of overrun error.

 

[chrfr]

Some member stated that most KP's reported by BridgeOS as the T2 chip manages different things.
However, in most cases users report that the machine reboots instead of awakening and a KP pops up starting with:

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 3.1 (16P1065)","timestamp":"2018-11-06 05:43:11.83 +0000","incident_id":"D66C632B-1EBC-471B-8696-6AC8377472DA"}

But what is about the rest of the report? In example some reports show:

1. "macOSPanicString" : "panic(cpu 0 caller 0xffffff7f976f3307): \"DSB0(MacBookPro15,2): thunderbolt power on failed 0xffffffff\n\"@\/BuildRoot\/Library\/Caches\/com.apple.xbs\/Sources\/IOPCIFamily\/IOPCIFamily-330.200.11\/IOPCIBridge.cpp:1314\nBacktrace (CPU 0),
   
   
2. "macOSPanicString" : "panic(cpu 0 caller 0xffffff800fcc306f): UUID: 47D2BC26-0426-428C-A375-59C980C76CFE\nStackshot Reason: Sleep transition timed out after 180 seconds while entering darkwake on way to sleep. Suspected bundle: com.apple.driver.usb.AppleUSBXHCI. Thread 0x639c8.\
   
   
3. "macOSPanicString" : "panic(cpu 0 caller 0xffffff8006678792): \"Restart timed out in phase 'Quiescing PM'. Total 30000 ms:\nvfs_unmountall: 1214 ms\nif_down_all: 127 ms\nPowerOff\/Restart message to priority client: 362 ms @ 0x<ptr>, com.apple.driver.IOBluetoothHIDDriver(6.0.9f2)[C65C951F-5EA3-3567-888E-9426F9C6C9CE]@0x<ptr>->0x<ptr>\nPowerOff\/Restart message to priority client: 220 ms @ 0x<ptr>, com.apple.driver.IOBluetoothHIDDriver(6.0.9f2)[C65C951F-5EA3-3567-888E-9426F9C6C9CE]@0x<ptr>->0x<ptr>\nPowerOff\/Restart handler completed: 188 ms @ 0x<ptr>, com.apple.iokit.IOUSBHostFamily(1.2)[922E7520-229B-3C68-B232-A8727A20D44D]@0x<ptr>->0x<ptr>\nPowerOff\/Restart handler completed: 200 ms @ 0x<ptr>, com.apple.iokit.IOUSBHostFamily(1.2)[922E7520-229B-3C68-B232-A8727A20D44D]@0x<ptr>->0x<ptr>\nPowerOff\/Restart handler completed: 207 ms @ 0x<ptr>, com.apple.iokit.IOUSBHostFamily(1.2)[922E7520-229B-3C68-B232-A8727A20D44D]@0x<ptr>->0x<ptr>\nPowerOff\/Restart handler completed: 209 ms @ 0x<ptr>, com.apple.iokit.IOUSBHostFamily(1.2)[922E7520-229B-3C68-B232-A8727A20D44D]@0x<ptr>->0x<ptr>\nPowerOff\/Restart handler completed: 218 ms @ 0x<ptr>, com.apple.iokit.IOUSBHostFamily(1.2)[922E7520-229B-3C68-B232-A8727A20D44D]@0x<ptr>->0x<ptr>\nPowerOff\/Restart handler completed: 291 ms @ 0x<ptr>, com.apple.iokit.IOUSBHostFamily(1.2)[922E7520-229B-3C68-B232-A8727A20D44D]@0x<ptr>->0x<ptr>\nPowerOff\/Restart handler completed: 506 ms @ 0x<ptr>, com.apple.iokit.IOUSBHostFamily(1.2)[922E7520-229B-3C68-B232-A8727A20D44D]@0x<ptr>->0x<ptr>\nPowerOff\/Restart handler completed: 233 ms @ 0x<ptr>, com.apple.iokit.IOUSBHostFamily(1.2)[922E7520-229B-3C68-B232-A8727A20D44D]@0x<ptr>->0x<ptr>\n\"@\/BuildRoot\/Library\/Caches\/com.apple.xbs\/Sources\/xnu\/xnu-4903.221.2\/iokit\/Kernel\/IOPMrootDomain.cpp:4804\n

But all start with
{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 3.1 (16P1065)",...

In my case the most frequent KP is 1.)

What's about you guys?
Use the search option in "Console" to search for >macOSPanicString<.

Cheers

This is the macOS panicking, not the T2. I strongly suggest most of the crashes users are blaming on the T2 are macOS panics which are now handled by the T2. Do you have Thunderbolt or USB devices attached to the computer? The backtraces indicate power issues with Thunderbolt in item 1, and USB in items 2 and 3.