Mac Book pro 16 crashing

Had the same problem

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.

Having it gooing to sleep on power, on batteries

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:-)

All I had to do was disable "PowerNap" to Prevent computer from sleeping automatically when the display is off. (Problems disappeared).

system Preferences > Energy saver ...

... turn off dark wake and similar obscure sleep settings. Remember there are two sets of settings, one for battery and one for Power adapter.

If it still panics after that, post the entire panic report if possible.

Safe Mode is called Safe Mode because it does not damage or change ANYTHING. It is SAFE.

Hold shift at startup, and your computer will start to boot up, then spend five minutes doing a disk directory check, then demand your userid and password to proceed. ONLY a minimal set of Apple-only extensions are loaded, and defaults are assumed for everything. Screen re-draw will be wonky and slow, but ultimately correct.

Things that work OK in Safe Mode, but not in regular mode are caused by "something you added".

What should I do? As I said before I had kernel panic panic(cpu 0 caller 0xffffff8011291b2c): Sleep transition timed out after 180 seconds while notifying clients about upcoming system capability changes.

Had because after disable power nap and prevent monitor.... everything works fine. One disadvantage is that after hibernation I can turn on Mac only with power button. Anyway that’s fine for me. I can work with these settings. Anyway I have still opportunity to send it back. Time till Friday. What would you do? Return or not?

It looks like software issues. I disabled power nap and prevent comp from sleeping when display is off and it works.

OK, graphics crash on wake from sleep, we get it.

It's the same solution. As a work-around, Turn off Power Nap. and wait for the software update that fixes the underlying issue.

Send it back. Apple isn’t having a problem with a huge percentage of the computers, just a small number. The chances of getting another bad one are slim, and if you do, return that one as well. Some have had success with various fixes; if you don’t, return it.

Anyway I don’t know what to do. I had this kernel panic error but turning off power nap and prevent monitor... works for me. I can live with that so maybe I shouldn’t take any risk

"All I had to do was disable "PowerNap" to Prevent computer from sleeping automatically when the display is off. (Problems disappeared)."

There's already a setting in Energy Saver that does that.

Yes I updated 2 days after it was posted. No problems. Just spent 14 hours straight editing in Final Cut Pro X without a hitch.

The return policy exists so that you do not have to live with a machine that is not good for you.

DO NOT live in fear. If this machine does not suit you, return it!

Today I turn back on power nap and no error at the morning. Before that I've changed few setting in Parallels. As I said Parallels was mentioned in kernel panic so I thought that could be a problem.

I had this same issue on a brand new 16" (received on April 27). I tried every solution I could find, but none of them worked. I ordered a new one, got it on May 1, and will ship out the first machine as a return today. The error code my crashes returned began with "CPU Machine Check Architecture Error Dump," which seems to point to a hardware issue.