I would've had returned that MBP by now for sure.I have tried this. It does not work. Thank you though for trying to help. I really appreciate anyone trying to help troubleshoot this.
I would've had returned that MBP by now for sure.I have tried this. It does not work. Thank you though for trying to help. I really appreciate anyone trying to help troubleshoot this.
I'm running the 13" 2018 MBP with the LG 5K monitor and I am not having KPs at all, so it is not likely the LG monitor on its own causing this for others.
Ok, so let's marked this as SOLVED. In order to re-enable startup security settings you have to boot into recovery using opt-cmd-R as opposed to just cmd-r in order for the proper download to take place from Apple's server. I figured this out by trying the many different key commands to boot into recovery. Thanks to everyone for all the ideas!So in the midst of trying to do a clean install of macOS on my new MBP I discovered yet ANOTHER oversight on Apple's part that has to do with startup security settings. I have documented it here in a video. All I can do at this point is SMH.
Ok, so let's marked this as SOLVED. In order to re-enable startup security settings you have to boot into recovery using opt-cmd-R as opposed to just cmd-r in order for the proper download to take place from Apple's server. I figured this out by trying the many different key commands to boot into recovery. Thanks to everyone for all the ideas!
https://support.apple.com/en-us/HT204904
Thank you for the kind words. I just want to do whatever I can to help Apple become a better company for us all. What I find most troubling is the fact that 9 out 10 times when you get a 'senior' advisor on the phone from Apple that you know way more than they do. They are simply reading a script with no real world experience and having no clue how to even begin solving your issue. Having had a love/hate relationship with Apple over the past 24 years has made me realize that in all actuality it is far more love than hate. I would be devastated if the company that I and people like yourself have invested so much of themselves into tanked.Kudos to you for your efforts and diligence in solving the problem. Apple should hire you.
Man I am so sorry about this. You are not alone in your frustrations. That is how I discovered my first KP. I just went to make something to eat in the kitchen and came back to the same message. I really hope the engineers are digging deeply into this. I was told that they would be and/or are.Just had my second kernel panic. Put it to sleep last night, woke up in the morning and was welcomed with the Apple logo.
"Your computer has shut down because of a problem."
This ****ing blows.
Mine just had its first crash since completely wiping the hard drive and reinstalling everything. Bridge OS Error again during sleep. Woke up the "your Mac has restarted due to a problem" message. I had only the power cable and a Thunderbolt 3/2 adapter (with no TB devices powered on in case the frequent waking of the monitor was the culprit).
BTW, you can find these panic logs in /Library/Logs/DiagnosticReports/ProxiedDevice-Bridge within Console.
[doublepost=1532809176][/doublepost]I think the worst part of this is not being able to TRUST an expensive computer that I depend on to make a living. I'm really worried that if this hasn't been fixed yet after having T2 iMac Pros out for so long, we just have to live with the crashes or return the machines.
LOL. "Direct reports" from whom? Many of us have in fact contacted Apple directly."MacRumors reached out to Apple, which told us that this is not a widespread issue, nor one that it has received any direct reports about."
Knock on wood, I'm not having this problem with my iMac Pro or MBP, but I always love it when forums (including Apple's own) are overflowing with posts from users having a particular issue (and have been in touch with Apple), and Apple's response to the media is, "hmmm... this is the first we're hearing of it."
Has your replacement machine crashed? I don't see any point in exchanging mine for a new one. I get the feeling they all do this.Man I am so sorry about this. You are not alone in your frustrations. That is how I discovered my first KP. I just went to make something to eat in the kitchen and came back to the same message. I really hope the engineers are digging deeply into this. I was told that they would be and/or are.
It has not crashed yet, but I’ve only had it one day and barely used it so far.LOL. "Direct reports" from whom? Many of us have in fact contacted Apple directly.
[doublepost=1532823556][/doublepost]
Has your replacement machine crashed? I don't see any point in exchanging mine for a new one. I get the feeling they all do this.
Mine just had its first crash since completely wiping the hard drive and reinstalling everything. Bridge OS Error again during sleep. Woke up the "your Mac has restarted due to a problem" message. I had only the power cable and a Thunderbolt 3/2 adapter (with no TB devices powered on in case the frequent waking of the monitor was the culprit).
BTW, you can find these panic logs in /Library/Logs/DiagnosticReports/ProxiedDevice-Bridge within Console.
[doublepost=1532809176][/doublepost]I think the worst part of this is not being able to TRUST an expensive computer that I depend on to make a living. I'm really worried that if this hasn't been fixed yet after having T2 iMac Pros out for so long, we just have to live with the crashes or return the machines.
I guess you need to let it sleep for a while and see if it wakes up reporting the crash, eh? Did you run Disk Utility on your new machine to check for the crypto_var errors?It has not crashed yet, but I’ve only had it one day and barely used it so far.
Those sound like different crashes than the Bridge OS ones we're discussing here. Check the Console app in the path I specified above to see if you have any of these crashes in your logs.Hoe does the log look like, specifically?
I have 3 files: deviceMetadata.proxy, tasking.ca1.proxy, tasking.da3.proxy
Does that mean I am concerned by these?
I just had 2 crashes in 10 days: MacBook Pro just froze and nothing was responsive. I did a hard reboot. Where can I find info about these crashes?
Nope, although I did have this happen sometimes on my 2016 MBP. The issue being discussed here is the machine rebooting all by itself (usually during sleep) and displaying "your Mac has restarted due to a problem."Is the errors you guys are experiencing kind of like this one?
https://forums.macrumors.com/thread...2016-mb-pro-sleep-wake-failure.2028092/page-4
Do you have a "ProxidedDevice-Bridge" folder you're looking in?These are the logs in the path you mentioned. Not sure if it is related or not to your crashes or if they refer to the 2 crashes I had since I bought my Mac 10 days ago.
Nope, that's something different. The one we're talking about here will have this line at the top of the window on the far right: {"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 2.4.1 (15P6703)"I do, I guess. You confirm I am impacted by the same bug as you?