2018 MacBook Pros crashing with "Bridge OS" error

[yakz]

Just to add one more... 2018 15" i7 2.6 32GB 560 purchased in February of this year. Although it has crashed a few times like this before, yesterday around 4 PM it started to rapidly increase in frequency of crashes until it was stuck in a reboot loop (crashing during boot-up) and finally today it will not turn on at all. Before it was completely dead, there were lots of panic logs (in /Library/Logs/DiagnosticReports/ProxiedDevice-Bridge). Starting in on the warranty / AppleCare process today to see what they do with it.

 

[xgman]

sad to hear some 2019 models still do this.. just ordered one for son's college. ugg

 

[tmmacops]

sad to hear some 2019 models still do this.. just ordered one for son's college. ugg

Yup. My 2019 13" MBP w/ TB was fine for the first couple of months. Ran the supplemental update a week ago, and thought all was well. Used it for 5 days, and opened up this AM only to see it restarted on it's own. Frustrating...

 

[spyros_mac]

my second kernel panic occurred on my 2019 15 inch MacBook Pro today. just after waking from sleep the computer froze and I had to power off- power on.
only a mouse was connected via a USB-C adapter on it.

{"caused_by":"macos","macos_version":"Mac OS X 10.14.5 (18F203)","os_version":"Bridge OS 3.5 (16P5200)","macos_system_state":"running","incident_id":"23550A36-F9A4-4F8E-B0BB-3276111AE8BC","timestamp":"2019-08-09 13:54:21.97 +0000","bug_type":"210"}
{
"build" : "Bridge OS 3.5 (16P5200)",
"product" : "iBridge2,3",
"kernel" : "Darwin Kernel Version 18.6.0: Thu Apr 25 21:46:37 PDT 2019; root:xnu-4903.261.4~1\/RELEASE_ARM64_T8010",
"incident" : "23550A36-F9A4-4F8E-B0BB-3276111AE8BC",
"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",
"date" : "2019-08-09 13:54:21.77 +0000",
"panicString" : "panic(cpu 1 caller 0xfffffff009e5cc60): macOS watchdog detected\nDebugger message: panic\nMemory ID: 0xff\nOS version: 16P5200\nmacOS version: 18F203\nKernel version: Darwin Kernel Version 18.6.0: Thu Apr 25 21:46:37 PDT 2019; root:xnu-4903.261.4~1\/RELEASE_ARM64_T8010\nKernelCache UUID: DC9A6AF1699676A67006EC794A8BEC87\nKernel UUID: D387D0DA-9EFE-345B-A278-38D53FD2C1CC\niBoot version: iBoot-4513.260.80\nsecure boot?: YES\nx86 EFI Boot State: 0x16\nx86 System State: 0x0\nx86 Power State: 0x0\nx86 Shutdown Cause: 0x5\nx86 Previous Power Transitions: 0x20002000200\nPCIeUp link state: 0x94721614\nPaniclog version: 12\nKernel slide: 0x0000000003770000\nKernel text base: 0xfffffff00a774000\nEpoch Time: sec usec\n Boot : 0x5d428974 0x000db477\n Sleep : 0x5d4d7934 0x0008f845\n Wake : 0x5d4d7ab1 0x000a68a9\n Calendar: 0x5d4d7aef 0x000c1510\n\nPanicked task 0xffffffe0002f6760: 3390 pages, 207 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe0006e33e0, backtrace: 0xffffffe015d8b490, tid: 415\n\t\t lr: 0xfffffff00a8821c4 fp: 0xffffffe015d8b520\n\t\t lr: 0xfffffff00a96f788 fp: 0xffffffe015d8b660\n\t\t lr: 0xfffffff00a84d610 fp: 0xffffffe015d8b670\n\t\t lr: 0xfffffff00a881768 fp: 0xffffffe015d8b9e0\n\t\t lr: 0xfffffff00a881ae0 fp: 0xffffffe015d8ba20\n\t\t lr: 0xfffffff00a8837f4 fp: 0xffffffe015d8ba40\n\t\t lr: 0xfffffff009e5cc60 fp: 0xffffffe015d8bab0\n\t\t lr: 0xfffffff009e5f094 fp: 0xffffffe015d8bb50\n\t\t lr: 0xfffffff009e5c1c8 fp: 0xffffffe015d8bbe0\n\t\t lr: 0xfffffff009e15a98 fp: 0xffffffe015d8bc10\n\t\t lr: 0xfffffff00ad083f4 fp: 0xffffffe015d8bc50\n\t\t lr: 0xfffffff00ad07c68 fp: 0xffffffe015d8bc90\n\t\t lr: 0xfffffff00a858614 fp: 0x0000000000000000\n\n",
"panicFlags" : "0x102",
"otherString" : "\n** Stackshot Succeeded ** Bytes Traced 114176 **\n",
"macOSPanicFlags" : "0x0",
"macOSPanicString" : "BAD MAGIC! (flag set in iBoot panic header), no macOS panic log available",

Model: MacBookPro15,1, BootROM 220.260.171.0.0 (iBridge: 16.16.5200.0.0,0), 8 processors, Intel Core i9, 2,3 GHz, 16 GB, SMC

 

[me55]

So I was getting tired of these kernel panics since 10.14.6 related to video-chatting, and contacted Apple support again. It even crashed with a clean macOS, so they accepted it for repair. Other people experienced the same issue.

Apple returned my Mac very quickly (3 days from dropping it off to receiving it back) and they replaced the "Logic Board" (Diagnosis: Kernel Freezes) and "Touch ID Board" (Diagnosis: Cable causing Issue) in it, the diagnostics at the Depot were able to reproduce the issue I assume. Updated to 10.14.6 18G87 right away, no reboots so far and everything works.

The replacement logic board came with macOS 10.14.4, but the current Boot ROM (220.270.99.0.0) and iBridge/T2 (16.16.6568.0.0,0) firmware version on it. The old logic board had the same firmware versions on it.

Interestingly enough, the preinstalled macOS on the replacement logic board had a partially disabled System Integrity Protection and a whole bunch of boot arguments set on it, but it booted looking totally normal like a new Mac with the initial setup screen. A fresh Mac does not have any boot args set by default.

boot args:

rootless=0 kext-dev-mode=1 agc=2 smc=0x2 watchdog=0 nvme=0x9 legacy_hda_tools_support=1 sandcastle=0 amfi_hsp_disable=1

 

[macjunk(ie)]

...

boot args:

rootless=0 kext-dev-mode=1 agc=2 smc=0x2 watchdog=0 nvme=0x9 legacy_hda_tools_support=1 sandcastle=0 amfi_hsp_disable=1

How can we see the boot args?

 

[me55]

EtreCheck shows them, or you can type "nvram -xp" in the Terminal and search for the boot args section.

 

[me55]

Update: The new logic board just crashed for the first time with the same error while doing video chatting. This is getting annoying to say the least. The Apple forums have a lot of people with this issue now too (notice the counters on the buttons "I have the same question", 15 and 57 people):

• Mojave 10.14.6 crashes while using video camera
  
• kernel panic since upgrading to 10.14.6

EDIT (08/17/19): The engineers are aware of this exact issue, they have numerous reports and are currently working on a fix. It is most likely a software bug which will be fixed with an update, but the senior advisor does not have detailed information about that. He also said he does not know if the fix is going to be released as a Mojave Supplemental Update or if it gets included into Catalina.

 

[yurc]

Three months passed, so far no serious problem (2018 models, i7-8850H, 512 SSD, 560X, 16GB RAM)

I have read so many bridgeOS problem regarding T2 chips equipped Macs, so I’m quite paranoid with my own machine too. But from day one I’m do some adjustment on my machine like:

• Disabled file vault
• Disable secure boot
• Disable SIP
• Disable auto boot
• Disable gatekeeper check
• Not partitioning my primary SSD (no other volume besides Macintosh HD)

Hiccups I’ve encountered with T2 mostly are with 3rd party USB drivers and peripherals. I’ve done some test on multiple non T2 chips (2017 15 inch MBP, 2012 Mac Pro, even hackintosh) and they working fine. Not so good on 2018 MBP, so I’m suspect T2 was the culprit here.

Besides any T2 inconvenient, benefit with T2 chips for my usage is just for helps speed up H265 encoding under videotoolbox which inexistent with my any current setup.

 

[swissbob]

No I haven’t got the Trackingnumber. I am based in switzerland. Shipping takes 1-2 days in every direction.
Today it was exactly 14 days. 3-4 days shipping, 2 Weekends (Nobody works here on saturday and sunday).
6 days to fix it.

I have to Quote myself.
Good news: No Bridge OS error anymore.
Bad news: No Wi-Fi anymore....

 

[yakz]

Just to add one more... 2018 15" i7 2.6 32GB 560 purchased in February of this year. Although it has crashed a few times like this before, yesterday around 4 PM it started to rapidly increase in frequency of crashes until it was stuck in a reboot loop (crashing during boot-up) and finally today it will not turn on at all. Before it was completely dead, there were lots of panic logs (in /Library/Logs/DiagnosticReports/ProxiedDevice-Bridge). Starting in on the warranty / AppleCare process today to see what they do with it.

Warranty repair replaced:

Logic Board (No Power/Light)
Touch ID Board (Cable Causing Issue)
I/O Board (Cable Causing Issue)

 

[mdnz]

EDIT (08/17/19): The engineers are aware of this exact issue, they have numerous reports and are currently working on a fix. It is most likely a software bug which will be fixed with an update, but the senior advisor does not have detailed information about that. He also said he does not know if the fix is going to be released as a Mojave Supplemental Update or if it gets included into Catalina.

Not to rain on your parade but they've been saying this for over a year now...

 

[me55]

The issue I'm talking about started with 10.14.6 and involves crashes when using the webcam. When not using the integrated webcam, the machine is 100% stable. It is a T2 related crash because the webcam runs through the T2 chip. A lot of people on the Apple discussion forums have this issue, but I haven't read about it on this forum interestingly enough.

Most people in this thread seem to have T2 related crashes that happen during sleep, while browsing, doing anything.

 

[TigerWolf]

Another casualty of this issue. Also testing if plugging into power helps avoid this issue.

Is this fixed in the 10.15 beta?

 

[befab59ce]

My fresh-out-of-the-box $4800 MBP has "restarted due to a problem" during sleep twice in three days. Apparently, I'm not alone:

https://discussions.apple.com/thread/8465477
https://discussions.apple.com/thread/8464031

In my reading, I found that users of the Mac Pros are having the same issues:

https://discussions.apple.com/thread/8232619

The symptoms are crashing during sleep or high I/O activities (with a Bridge OS error), and a report of "Warning: crypto_val: object" when running Disk Utility (which may be unrelated). Note that these are the only two machines that use the new T2 chips.

Note that I reinstalled only the bare minimum software I use from scratch and avoided using Migration Assistant just so I could be sure nothing bad was transferred from my old computer.

Any of you other new MBP users experiencing the same?

I just made an account to reply to your post. I have had this happen every single time I've used FaceTime or Skype. It's very bad. A 3,000 machine should not be crashing. it should be reliable.

I have all the available software updates for the OS, and FaceTime, etc. I also have the system logs.

To top it off, the keyboard is starting to show the signs of distress that were presented in the media many times.

This is so bad apple.

 

[evilaci2]

Happend an official statement from Apple for this bug type 210 and macOSPanicString : "BAD MAGIC!....
Not only the customers earned an information about this crazy situation.

 

[b.basov]

Had this type of crashes several times during the day, but when I turn off Find my mac, it seems to be fine

 

[me55]

Apple just now released a supplemental update for 10.14.6 which is supposed to fix sleeping Mac's that crash and other things. Installing it right now.

EDIT: macOS 10.14.6 18G95, T2 firmware was updated to 16P6571, Boot ROM stayed at 220.270.99.0.0.

 

[appleuser181]

Apple just now released a supplemental update for 10.14.6 which is supposed to fix sleeping Mac's that crash and other things. Installing it right now.

EDIT: macOS 10.14.6 18G95, T2 firmware was updated to 16P6571, Boot ROM stayed at 220.270.99.0.0.

fingers crossed lol

 

[GoldfishRT]

2018 15" 2.2 - No crashes. Starting YouTube videos makes that slight pop to the speakers though. Otherwise fine.

 

[ThomasBPG]

Added the cumulative update this morning. It lasted less than four minutes with webcam turned on with Cisco WebEx and crash....

 

[AdminSamuel]

Praying for an update lol

Everyone needs to call Apple and go through all the steps to get your crash log to the technicians.
That being said my case mentioned T2 in the title so they I assume they know about it.

I work with 100s of these MacBooks and have one that is consistently crashing.
Another crashed but the user had not experienced it again (though he is aware what triggers it)

(I haven't tried it on my own machine.)

These are both brand new MBP 15"s spec'd out running the latest Mojave

So far I've worked out (from our two machines that kernel panic'd)

The crash only happens on battery power. Yes, it does seem related to the webcam because the laptop can be used all day until a call is joined - that being said they do not use any other software that utilizies the GPU.

I can trigger it 100% by:
1 - Putting the computer to sleep or closing the lid (if it's set to go to login screen immediately).
2 - Plugging in the charger to the top left usb c port.. I then unplug the charger and wake the mac up.
3 - Open Google hangouts and join or create a chat
4 - wait. sometimes it happens straight away sometimes not. I've noticed the laptop is quite hot after it happens.
5- The computer freezes completely. screen goes black and the fans whirl on for 1 second.


Clean OS reinstall does not fix. Went through every trouble shooting step with Apple and finally have sent my crash logs to a technician. the message is something like dec0dedec0de etc - I've seen it on two of our machines and reported by others.

Hardware related. I'm not sure it's directly related to the webcam as I've read reports of crashing using Premiere Pro or playing games.

From what I understand I would guess that it has to do with gpu switching with the webcam on. I noticed when I plugged the charger in the camera would zoom in, not sure if that supports my theory.

Waiting for apple's technician to get in touch. Other option is take it to an apple certified store and who knows what they will do.

 

[ria1980]

As for me - I had Kernel Panic during FB video call on my MPB mid 2018 - it was hard reset and KP warning every time on 2nd minute of calling after I update to 10.14.6. Yesterday I did supplemental update, suggested by Apple. Reset SMC and PRAM - and Kernel Panic's reset gone for me. Just had a long video conversation with my wife by FB video chat - everything is ok now. 10 minutes call made - nothing wrong happened.

 

[AdminSamuel]

As for me - I had Kernel Panic during FB video call on my MPB mid 2018 - it was hard reset and KP warning every time on 2nd minute of calling after I update to 10.14.6. Yesterday I did supplemental update, suggested by Apple. Reset SMC and PRAM - and Kernel Panic's reset gone for me. Just had a long video conversation with my wife by FB video chat - everything is ok now. 10 minutes call made - no any tproblem now.

Seemed to me that an SMC or possibly the Safe Boot fixed the issue until I put the machine back to sleep with the steps I posted just earlier and it started reappearing.

Did you happen to Safe Boot?

Apparently they released an update today? It's not showing up on my machine. I'm in Australia.

 

[ria1980]

Seemed to me that an SMC or possibly the Safe Boot fixed the issue until I put the machine back to sleep with the steps I posted just earlier and it started reappearing.

Did you happen to Safe Boot?

Apparently they released an update today? It's not showing up on my machine. I'm in Australia.

I did not test all that sleep/wake up staff, in fact. It was just permanent problem (plug or unplug power did not make any difference), I made an update, made SMC and NPRAM reset/all works now. I just did not have so much time for experiments) Will try next time to make my MBP sleep and make a call after wake it up, will notice about a result!

About an update - it just appeared in my "Software Update" folder in System Preferences, I even did not check it - it just suggested me to install it - and I did it.