Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Has your 2018 Macbook Pro KP'd with the Bridge OS error since 10.4.2 GM


  • Total voters
    119
  • Poll closed .
Offering as an additional data point...I've had my 2018 MBP 15'' (base model, running High Sierra, purchased from B&H during their sale) for almost a month, and have had zero issues with it.

I run it mostly in clamshell, hooked up to my HDMI monitor, audio interface, midi keyboard, etc. through a hub, but take it off occasionally. No KPs, no reboots. Crossing my fingers this continues, and definitely not messing with it by trying to upgrade to Mojave.
 
Why? It works, and works with all of my professional hardware and software. Unless there is a real reason to upgrade, I'm perfectly happy with High Sierra. I stayed on Mavericks until 2016, and then stayed on Yosemite until this last summer.
 
  • Like
Reactions: TonyK
For peace of mind knowing your T2 runs flawlessly with the latest OS and improved security.
 
For peace of mind knowing your T2 runs flawlessly with the latest OS and improved security.

Eh...I have peace of mind right now. I haven't been on the "latest OS" for the better part of a decade. Frankly OSX tends to be a bit of a mess for at least a year after each update, and I prefer to stay out of the fray. Besides the fact that a lot of very good and very expensive audio equipment isn't guaranteed to work with newer versions of the OS. I'm already annoyed every time I have to use three dongles to plug into the Firewire MOTU or RME when I work on campus.
 
Do you put them to sleep at night or shut them down ?

I cannot tell you 100% what our employees are doing but I would be surprised if anyone is shutting them down except maybe for long distance flights (but even then I don't think that anyone bothers). Personally, I worked with two i9 models (the first one got replaced by a Vega Pro 20 unit beginning of December) and I never turn my laptops off except when I need to boot a different partition.
 
My MBP 13 was replaced twice and I still have these issues..But on 10.14.2 crashes are little more strange. Before rebooting it freezes, then black screen and fans are maxed out for approximately half of a second and reboot. Don't have any idea about what triggers fans to max during crash (didn't see this before 10.14.2)

One thing I've noticed, any software I use right before the crash stops responding and cursor becomes multicolored circle.
 
My MBP 13 was replaced twice and I still have these issues..But on 10.14.2 crashes are little more strange. Before rebooting it freezes, then black screen and fans are maxed out for approximately half of a second and reboot. Don't have any idea about what triggers fans to max during crash (didn't see this before 10.14.2)

One thing I've noticed, any software I use right before the crash stops responding and cursor becomes multicolored circle.
The fan behavior is due to the part of the software that monitors the temperature failing to report it to the part that governs the fan speed. Because its crashed, the fan software assumes the worst and cranks them up to full blast to avoid damaging the chips
 
I've also had exactly the issue Rusik described on a entry 15' 2018 mbp after a month of solid use. It's still going strong, using it with an external monitor and external HDD. I'm curious to see how often will this happen. But so far it's really solid with no problems getting the device out of sleep,etc.
 
I've also had exactly the issue Rusik described on a entry 15' 2018 mbp after a month of solid use. It's still going strong, using it with an external monitor and external HDD. I'm curious to see how often will this happen. But so far it's really solid with no problems getting the device out of sleep,etc.
did yours get better? when was last crash?
 
So there's a 1 in 5 chance that if I get a 2018 MBP it'll have T2 crashes? :confused: Don't like those odds...

Wha would be really interesting to see would be any correlation between the audio issues and the KPs. Are they a package deal? A given MBPro has both issues?
 
I wiped my machine the other morning (Wednesday I think it was) and I haven't had a single crash with my monitors plugged in, when it was crashing nightly. Of course that doesn't mean it won't have a problem in a week or a month, but I'll take this as a win for now.
 
I wiped my machine the other morning (Wednesday I think it was) and I haven't had a single crash with my monitors plugged in, when it was crashing nightly. Of course that doesn't mean it won't have a problem in a week or a month, but I'll take this as a win for now.
Keep us updated!
 
Keep us updated!
I had done this before when I had the BridgeOS crash, though they were never as frequent as they had become in the last two weeks. . . I wonder if maybe the hibernation file became corrupt in all of the crashing and then it just spiraled from there? But, would that explain the crash that I had when just plugging the displays in? Maybe? The computer was (and always is) closed when I plug them in, as I put it into the 12 South BookArc.
 
I had done this before when I had the BridgeOS crash, though they were never as frequent as they had become in the last two weeks. . . I wonder if maybe the hibernation file became corrupt in all of the crashing and then it just spiraled from there? But, would that explain the crash that I had when just plugging the displays in? Maybe? The computer was (and always is) closed when I plug them in, as I put it into the 12 South BookArc.
Reaching here - Possible it writes some aspect of video memory contents on sleep and multiple displays increases it. I know how a lot of things work inside the Mac and I for sure am guessing there.
 
The first two things everyone having panics should do are disabling secure boot in system recovery, and disable sleep functions and then see if the panics go way down. Updating to 10.14.3 once available would be a 3rd thing. This has helped me keep this problem to a minimum.
 
I may have ran my luck into the ground commenting here and not knocking on wood.

I was playing Civ V, minding my own business, and the game crashed with no warning. I was pretty far along in the game, lots going on. I cannot tell if this was because of a T2 / BridgeOS issue, or if it was just the game itself failing. Any input?
 

Attachments

  • Screen Shot 2019-01-08 at 2.41.16 PM.png
    Screen Shot 2019-01-08 at 2.41.16 PM.png
    967.2 KB · Views: 323
I may have ran my luck into the ground commenting here and not knocking on wood.

I was playing Civ V, minding my own business, and the game crashed with no warning. I was pretty far along in the game, lots going on. I cannot tell if this was because of a T2 / BridgeOS issue, or if it was just the game itself failing. Any input?
that looks like a normal OS crash. Well not normal, but not bridge os.
 
Happens to me every day:
{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 3.3 (16P3133)","timestamp":"2019-02-01 03:43:09.18 +0000","incident_id":"497A45A1-8BCE-4AE1-9461-DDAD58809234"}
iMac Pro $5000 6 months old
 
  • Like
Reactions: dspdoc
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.