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

Romarrrio

macrumors newbie
Original poster
Dec 24, 2019
11
4
Hello mates,

I just got a new MacBook Pro and after going through settings (country, language etc) it showed me this:

macos-mojave-restart-problem-ignore-report-alert.jpg


After a couple of days after the sleep mode my MBP showed me the same message.

I am a bit concerned as it's a new device, with my previous MBP I haven't seen anything like this.
 
Check this thread. The panic string in the log file may provide more info.

 
Check this thread. The panic string in the log file may provide more info.


Saw this today (once again)

Can't find a proper answer in a thread, unfortunately

Screenshot 2019-12-30 at 11.30.57.png
 
There is no answer in that thread, the T2 is causing crashes and Apple has yet to fully fix the issue.

It is very frustrating. I have this issue - Sleep Wake failure in EFI every morning and I send the info to Apple every time but still no help.

Am I the only one with 16" MBP with this issue?
 
  • Like
Reactions: g75d3
It is very frustrating. I have this issue - Sleep Wake failure in EFI every morning and I send the info to Apple every time but still no help.

Am I the only one with 16" MBP with this issue?

It’s definitely not widespread. You should return your computer while still in the window to do so and buy a replacement.
 
It’s definitely not widespread. You should return your computer while still in the window to do so and buy a replacement.

Unfortunately I am not in the window to return my computer, all I have is a service and support coverage.
 
Remember that the returns period is extended over Christmas, I think for new 16" MBP purchases its open until the 15th January or thereabouts.

If you have an open fault call with Apple, what are they recommending? If you've done everything suggested, it will get to the point where you'll have to take it in to a store and given its so new they'll probably just swap it out anyway.
 
  • Like
Reactions: MareLuce
Remember that the returns period is extended over Christmas, I think for new 16" MBP purchases its open until the 15th January or thereabouts.

If you have an open fault call with Apple, what are they recommending? If you've done everything suggested, it will get to the point where you'll have to take it in to a store and given its so new they'll probably just swap it out anyway.

That is of course depending where you bought it from. Not everyone buys it from apple.
 
  • Like
Reactions: ascender
I have the exact same issue with the a 2019 16" MBP with the 2.4GHz i9 and 5500M 8GB. I have 4 days left to return the computer. Trying to decide if I should keep it and wait for a software fix or return it so I don't get stuck with a lemon.
 
I have the exact same issue with the a 2019 16" MBP with the 2.4GHz i9 and 5500M 8GB. I have 4 days left to return the computer. Trying to decide if I should keep it and wait for a software fix or return it so I don't get stuck with a lemon.

This happened again just a few minutes ago while my MBP was charging:

panic(cpu 2 caller 0xffffff7f8edcca97): GPU Panic: mux-regs 4 3 7f 1f 0 0 severity 3 WS-ready 1 switch-state 0 IG FBs 1 EG FBs 0:0 power-state 3 3D idle HDA idle system-state 1 power-level 15:10 power-retry 0:0 connect-change 0 : AGC GPU REGISTER RESTORE FAILED with 1 reset, g3d BAR0 invalid

Opened a MBP and it did a strange fan noise then rebooted.

Trying to contact Apple customer support..
[automerge]1578152300[/automerge]
That is of course depending where you bought it from. Not everyone buys it from apple.

Yeah, I bought it not from Apple but from another company..
 
Last edited:
Remember that the returns period is extended over Christmas, I think for new 16" MBP purchases its open until the 15th January or thereabouts.

If you have an open fault call with Apple, what are they recommending? If you've done everything suggested, it will get to the point where you'll have to take it in to a store and given its so new they'll probably just swap it out anyway.

Contacted Apple support, they told me to do this:

1. Reset SMC
2. Reset NVRAM and PRAM
3. Reinstall macOS from macOS Recovery

That's it for now.
[automerge]1578156010[/automerge]
A bit desperate for finding the solution, that's another article

Don't know if it's ok to trust this source.
 
Crap. This happened to me this morning for the first time, after leaving my MacBook Pro unplugged and sleeping over night for the first time. Did you have yours plugged in when it happened? Still 96% battery after it finally rebooted. Hope this isn’t an ongoing issue...
 
Check this thread. The panic string in the log file may provide more info.

It isn't the Bridge OS kernel panic. I had that problem in my 2018. This is something else. I'm also having the wake from sleep problem.

Happens only on battery, if it's plugged into power it sleeps and wakes just fine.
[automerge]1578238560[/automerge]
Crap. This happened to me this morning for the first time, after leaving my MacBook Pro unplugged and sleeping over night for the first time. Did you have yours plugged in when it happened? Still 96% battery after it finally rebooted. Hope this isn’t an ongoing issue...
Same here. Only happens on battery, but happens pretty much every time on battery if I leave it overnight.
 
It isn't the Bridge OS kernel panic. I had that problem in my 2018. This is something else. I'm also having the wake from sleep problem.

Happens only on battery, if it's plugged into power it sleeps and wakes just fine.
[automerge]1578238560[/automerge]

Same here. Only happens on battery, but happens pretty much every time on battery if I leave it overnight.

Interesting. Mine has always been plugged in when I've had the crash and subsequent restart issue. In fact it has been plugged in ever since I took it out of the box. Maybe we're dealing with multiple problems.
 
I left mine unplugged again last night and did not have the issue. Apple support told me it was probably due to a program I had that was trying to run in the background. Possible culprits include istat menus, and universal audio mixer engine. Istat menus was uninstalled before the computer slept last night and it did not have the issue, though I don’t think that really means anything. I’m going to keep leaving it unplugged overnight for a while to see if it keeps happening. I’m not uninstalling universal audio software unless things get really bad, that’s the main reason I bought the computer! I bet it’s a minor bug that will be resolved with a software update soon.
 
I left mine unplugged again last night and did not have the issue. Apple support told me it was probably due to a program I had that was trying to run in the background. Possible culprits include istat menus, and universal audio mixer engine. Istat menus was uninstalled before the computer slept last night and it did not have the issue, though I don’t think that really means anything. I’m going to keep leaving it unplugged overnight for a while to see if it keeps happening. I’m not uninstalling universal audio software unless things get really bad, that’s the main reason I bought the computer! I bet it’s a minor bug that will be resolved with a software update soon.

I leave my laptop open and unplugged from the charger every night and I also run iStat. I don’t think that’s your culprit unless you are possibly running an older version.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.