BridgeOS Crashes Happening on 2018 MacBook Pro with TouchBar

I just had my first reset with the machine awake and working on something. The error report was for BridgeOS. My resets had calmed down to less than one per week when sleeping.

I had a horrible lapse in judgement after loading the second supplemental update and also noticing that the Bootcamp drivers are now available. So, I attempted to create a Bootcamp partition and install Windows on it. Somewhere during the partitioning, close to the end I think, the machine spontaneously restarted. Now my partition map is "broken" and I am unable to get rid of the Windows partition that it was creating and is now marked as free space but somehow inaccessible to either use or delete. My Mac partition returns errors during first aid that won't clear. <<inode_val: object (oid 0x3) invalid nchildren (-1) fsroot tree is invalid. The volume could not be verified completely.>> I've worked on that for a day and a half trying to get the volume back to normal. I won't even bother calling support and am preparing to rebuild the machine once I am sure I am backed up redundantly.

Out of interest if you go to > Apple menu, About This Mac, System Report - Under 'Thunderbolt' (left side) - what firmware version are you running?

I have a Caldigit TS3+ dock and stumbled across this article this morning (from April 2018). http://www.caldigit.com/KB/index.asp?KBID=228&viewlocale=1

I fail to understand how a new machine, purchased 3 weeks ago AND now running the latest Mojave beta was shipped with such an old Thunderbolt 3 firmware version. My machine is running Thunderbolt controller firmware 30.2 - I'm awaiting a call from Apple support now on how to upgrade the firmware to 33.2.

My rebuild went smoothly. I reloaded everything from the App Store and by re-downloading fresh binaries from their publishers without restoring anything except some VMs and a couple of data folders or by re-sync with iCloud and Dropbox. All settings are now default, including FileVault (on). I am in day 2 with no restart, but it is early to tell.

Interestingly, the first thing I tried (again) was installing a Bootcamp partition with Windows and it went flawlessly. I can boot to the new Bootcamp partition or use it through Parallels. So, that is great. I am going to avoid using the Bootcamp version of Windows until all of this settles out a little, though. I only need to be on hardware for one specific type of work task. Otherwise, I will used VHD based VMs whenever possible.

The only issue I have seen since the reload, which continues to make me nervous, was I could not erase a USB flash drive (new out of box with NTFS format) until the 4th try without some sort of Disk Utility error. My main non-reset symptom continues to be odd behavior with external drives.

Yes. I have the supplemental updates loaded and latest re-downloaded version of High Sierra.

I just happened to rebuild mine from scratch about 36 hours ago. My first act was to load the supplemental updates. My second act was to use Bootcamp Assistant to create a Windows partition just in case it were to fail and force me to rebuild the machine again. But all went smoothly.

I have the same problem. Any news from Apple on this?

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 2.4.1 (15P6805)","timestamp":"2018-09-02 23:35:54.14 +0000","incident_id":"FBE2821D-A221-470D-8C5F-63784D4EA213"}

{

"binaryImages" : [

[

"e0e6f8b6-c72f-e2cd-30ef-30dd2c2f37fe",

18446743936270598144,

"U"

],

[

"00000000-0000-0000-0000-000000000000",

0,

"A"

],

[

"7f5e330b-f8bd-3c53-b45c-7726c2bb0d74",

6442450944,

"S"

]

],

"build" : "Bridge OS 2.4.1 (15P6805)",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-09-02 23:35:53.65 +0000",

"incident" : "FBE2821D-A221-470D-8C5F-63784D4EA213",

"kernel" : "Darwin Kernel Version 17.7.0: Fri Jul 6 19:25:51 PDT 2018; root:xnu-4570.71.3~1\/RELEASE_ARM64_T8010",

"macOSOtherString" : "\n** In Memory Panic Stackshot Succeeded ** Bytes Traced 633216 **\n",

"macOSPanicFlags" : "0x4",

Mine doesn't need to be connected to anything. It happens most often when the wifi tries to attach to my 5G main network and the 5G extender. Sometimes, for whatever reason it will have problem and wifi will turn on and off repeatedly and eventually crashes.

Dear, Apple Same here when I working and crash for 2-3 times, please fix as soon my crash log:

{"caused_by":"bridgeos","macos_system_state":"running","bug_type":"210","os_vers ion":"Bridge OS 2.4.1 (15P6805)","timestamp":"2018-09-06 07:40:07.61 +0000","incident_id":"95D99768-1DF4-4F5D-BE45-59040179DD6C"}

{

"binaryImages" : [

[

"e0e6f8b6-c72f-e2cd-30ef-30dd2c2f37fe",

18446743936270598144,

"U"

],

[

"00000000-0000-0000-0000-000000000000",

0,

"A"

],

[

"7f5e330b-f8bd-3c53-b45c-7726c2bb0d74",

6442450944,

"S"

]

],

"build" : "Bridge OS 2.4.1 (15P6805)",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-09-06 07:40:06.93 +0000",

"incident" : "95D99768-1DF4-4F5D-BE45-59040179DD6C",

"kernel" : "Darwin Kernel Version 17.7.0: Fri Jul 6 19:25:51 PDT 2018; root:xnu-4570.71.3~1\/RELEASE_ARM64_T8010",

"macOSOtherString" : "\n** In Memory Panic Stackshot Succeeded ** Bytes Traced 1207872 **\n",

"macOSPanicFlags" : "0x6",

I wish I could say for sure that it was the rebuild that helped. I had nightly restarts in the beginning but was fairly stable immediately before this rebuild. I went at least a week without restart. The reason for the rebuild was a Boot Camp partitioning that failed in the middle and left me unable to straighten out the partitions. That said, I have my fingers crossed now that it stays stable for a while. BTW, I attempted the Boot Camp partition immediately after the rebuild and it went flawlessly. So, for the moment everything is as it should be.

In my opinion, there is still no recipe for getting rid of those crashes when you have them. In my experience, re-installing clean (did it many times) has not been the solution (had one the following morning a while back after doing that). The 2nd update seems to have reduced occurrences, but not totally. Having plugged or not different USB devices or adapters did not make any difference in my case. Changing the unit was not the total solution neither (finally had a one wake-up crash a couple of weeks after that).

I personnally can live with those rare crashes, while being optimistic that this is probably software-related and fixable. Overall, very happy with my MacBook Pro 2018.

I would agree that from what you read here and from personal experiences that there appears to be no simple correlation to something that causes the problem. At least a few dozen people have been working hard to find an obvious cause and willing to spend some hours trying things. There have been rebuilds, machine replacements and all sorts of configurations tried. Particularly since this has been an issue for even longer on iMac Pros that have been out for a while. I would also agree that this is the first hardware upgrade I have had in a while that is immediately noticeable in its positive performance impact. The extra cores and double the memory make an immediate difference when you use VMs for development purposes. It would be hard to go back to MBP 2016 for me. That said, I have had a few more stability issues than you would expect leading to some reboots. But, those could as easily be caused by non-Apple software running on this new platform. (problems partitioning and formatting, a network copy issue, etc.) Each time the reboot cleared things up. Those things were extremely rare on my MBP 2016.

Happens today again.

BUT! Caused by "macos"{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 2.4.1 (15P6805)","timestamp":"2018-09-18 18:35:53.08 +0000","incident_id":"A8AFEAD0-EAB4-4450-860F-0A4CC97EF052"}

And

"macOSPanicString" : "panic(cpu 6 caller 0xffffff7f97a4787b):

instead of

"macOSPanicString" : "panic(cpu 0 caller 0xffffff8004699995):

Apple! Take a look at this.

Apple is not here. This is a User-to-User forum. Apple does not troll these forums looking for problems.

If you want Apple to notice, be selfish and present your computer at an Apple-owned store or Apple-Authorized Service Provider and ask them for relief. Or call AppleCare (free for 90 days). When the chorus of complaints gets loud enough, Apple will act.

Hi Grant,

Oh, I know, it was kind of sarcastic humor. Of course, that I have reported already a few bugs. And I'm sure that apple aware of the problem.

But the interesting case is that today the crash happened not because "bridge os", but because of "mac os".
Probably, there are people who had the same and could share their thought.

I ended up returning the MBP 2018 40 days after the standard return window -- they didn't put up a fight, they know this is a real issue affecting a bunch of people. Keep contacting support, and consider a return until they fix their shiz!

It crashed 3 times while I was sitting in the Apple store. RIP.

Apple called me after I posted in this exact thread, actually. Blew me away.

...and I hope they'll call again, because my replacement MBP just did this today for the first time. :/

The Stackshot trace is over a megabyte. Ouch.