MacBook Pro 16" Kernal Panic During Restart when Plugged into Dual Monitors

Oh... when updating OS you have to enable and disable power nap again. Really weird, but i works.

I have told Apple about this. They called me the other day when my Machine had created a crash report (after updating to 10.15.5). I solved the problem again with flipping power nap on/off. It is properly a wrong state in updated smc/NVRAM thats get set correct when flipping power nap on/off.

I finally have mine fixed... Here's my setup:

• 16" MBP - pretty much loaded
• 1 x 5k 27" LG monitor (new as of January)
• 1 x 45 21.5" LG Monitor (older model from a couple of years ago)

Whenever my MBP went to sleep, the MBP crashed... Not every time, but prolly 70% of the time.

I downloaded "LG Screen Manager" and updated the firmware on both monitors. It's been one week now and I haven't had a crash at all. Occasionally, whenever the MBP wakes from sleep one or the other monitors doesn't turn on, but this is fixed by putting it back to sleep again and then immediately waking it.

Hope this helps at least one of you.

Had the same problem. It's now solved.

Status here

My GPU Panic sleep problem is still solved. I have since installed my video-rendering tools, my developer tools, all my other stuff.

My energy saving stuff is back to normal (standard settings)

Having it gooing to sleep on power, on batteries, forced it to run out of batteries. Did intense GPU-use. Still no problems.

Running 10.15.4

Solution for me was

My brand new macbook pro 16 (Shipped 2. april 2020) also restarted (crashed) over nigth - actually it crashed (Kernel Panic GPU) everytime it went to sleep mode. I had nothing installed except default OSX with updates.

Solution details

1. Reset: Pram & NVRAM (still crashed)
2. Reset: SMC (still crashed)
3. Internet Recovery Command+Option+R (when booting) (Crashed under installation, but continued afterwards)
4. Disabled "Prevent computer from sleeping automatically when the display is off." & "PowerNap.." in Energy Saver settings (Problems disappeared)
5. Two days later I enabled "Prevent computer from sleeping...." and "Powernap..." again (Still no problems)

I don't know if step 1-3 is necessary, but I think so.

So a macbook pro 16 that I almost returned, is now working perfectly - and I'm very happy:-)

gmiles wrote:

...

Now, after submitting and having the same error messages reviewed by Apple Support over the phone, am being told it is a hardware issue and needs repair.

Some Time has gone by, and Apple as a company has had more examples of this failure, and more ability to re-create the problem and understand why it is happening.

This is likely a very unusual failure of the new Graphics chips used for the first time in theses MacBooks. Later versions of the same chip may have this problem fixed.

as the kernel panic does not happen always i have studied the Kernel log and it seems to me it happens always when after waking up from sleep the system makes a call to a specific core of the cpu, it really seems a software bug.

after that i have decided to do proceed as follow in order to avoid the faulty call to the cpu core

• Disabled Powernap
• Enabled prevent computer to sleep if display is off
• disabled put hard disk to sleep
• disabled SIP
• disabled out turn on at lead open (via terminal)

not sure what did the trick, but

now with 2 monitors connected

no more kernel panic, more than a month now

hope this will help you too guys

Hey I had this problem, they did the same to me and gave me a new computer but the issue wasn’t resolved. However with The latest OS update it half fixed it for me. So now I don’t get that problem when restarting or shutting the computer down but I do get a crash “sometimes” when my computer goes to sleep. It’s definitely a software issue. Make sure you update to macOS Catalina 10.15.4 and see if that works for you.

So many have the same problem. It is the disabling of Power Nap that fixes the problem.

I too tried disabling power nap and this fixed it for me!

And an update, with PN re-enbled, I now started to get KP's again. So have switched it back off. No monitors.

My configuration is the same although it is not necessarily related to sleep. It will work fine for days and then lock-up every hour for 6 hours and then work fine for 2 days. Never occurs without the LG Ultrafine detached. Now, I disconnect the monitor when doing anything "important" to prevent data loss. (or use my 2014 13" which is rock solid). Super frustrating but there aren't motherboards from what I have read so am waiting it out and retaining all crash logs.

I recently upgraded to a 2019 16" with the same specs as yours except with 32GB RAM & 2TB HD and was also was experiencing kernel panics and restarts. It would always occur some time after putting the laptop to sleep while still connected to two external displays. This happened a few times, but then I did a random experiment and put the computer to sleep and then closed the laptop lid. For some strange reason, doing that has now eliminated all kernel panics and random restarts after putting to sleep while connected to external displays. Figured this may be helpful for some.

Might be worth doing an SMC reset and OS reload from the Internet. It took about an hour and, I can't promise that it will totally resolve it, but in my case, I went from a restart every hour or two after installing the 10.15.4 supplemental release to no restarts for the past few days. I have been doing this after each OS update and, while it didn't always eliminate the problem, it reduced the frequency on some releases, including this one.

Unplug one of the monitors before you shut down. Uncheck Reopen windows.

Sometimes problems like this have already been seen and solved. Be sure to apply the latest MacOS updates so that any such changes are already incorporated into your system.

That is likely to be the first thing an Apple support specialist will ask for -- they do not want to debug a problem that has already been solved.

Yes; it solves none of it.

The only thing that helps is disabling sleep mode.

After the BS i had to endure with last years model, I don't think that Apple gives a ****. After all, it's only "a small percentage of users" who are experiencing these problems.