MacBook Pro 16 2019 10.15.4 Kernel Panic / Reboot When Plugged In -- Help!

I'm still on 10.15.4. Disabling "Power Nap" stop the daily crashes from going to sleep. But after a few days it happened again. This time a slightly different error message through: "panic(cpu 0 caller 0xffffff8007291b2c): Sleep transition timed out after 180 seconds while calling power state change callbacks. Suspected bundle: com.apple.iokit.IOGraphicsFamily. Thread 0xc2e8c."

I wish that Apple would fix this already.

I found I had this issue when I put in a 480gb OWC aura hard drive and updated to 15.4. On my MacBook Pro 11,1 2014 retina.

I reverted back to my old apple Samsung 128gb drive which has 15.3 installed and it stopped.

Here are the links for description in english :

• Reset System Management Controllers (SMC) according to the instructions given here :

https://support.apple.com/en-gb/HT201295

• Reset NVRAM or PRAM on your Mac

https://support.apple.com/en-gb/HT204063

@GreenBadger... I agree with @TheRealCasper. I called Apple Support earlier and the person I spoke to tried to take me down the path of this being a hardware problem. I had to stop her and ask her to listen for a while as I researched this more with her on the phone. That's when I found the info that I just posted below.

This is not a hardware problem. It will be fixed soon, I'm sure. In the meantime, I'd suggest you try the work arounds and look at the diagnostic file (see my post). It doesn't seem like you should need to return your machine.

Good luck!

As you note this seems a fairly widespread problem - has there been any statement at all from Apple? My top of the line Macbook pro 16 inch is a few weeks old and experienced this issue from the time I first got it and installed the 10.15.4 upgrade. I have unchecked the nap feature and don't seem to get the multiple Kernel panics a day I was experiencing in the first few days. This seems a pretty significant issue so I am surprised by the deafening silence from Apple. No attempt to reassure or proactively inform customers who have spent 1000's of dollars buying products and we are left to figure out the issue ourselves on forums such as this.

Just to be clear. Is this a 16” or another build?

Also what version of the OS are they running and are they leaving the laptop plugged in with PowerNap enabled?

the default behavior for MacBooks in Catalina is to have PowerNap disabled while on battery power. So in a number of circumstances a person could go a day or so without seeing an incident depending on how they use their machine.

I have the same issue on my 16" MBP. I just disabled power nap so I'm hoping that'll do the trick. I've already had to get my Mac repaired because it would reboot from a GPU panic when it wakes from sleep, and Apple ended up replacing the logic board and almost all of the internals. It seemed to solve the issue, but I'm really hoping my Mac hasn't broken down twice in less than a year. That doesn't bode well for the longevity of the product once the warranty expires.

So glad I've found this thread. Almost went nuts on this issue. Have had this with my:

• 15" MBP 2015 i7 2.5 Ghz 16GB RAM 2GB Radeon
• 16" MBP 2019 i9 2.3 Ghz 32GB RAM 4GB Radeon 5500M

Sadly don't remember when I installed 15.4 on the 15" but I did so immediately after getting the 16" this week. Same scenario. Connected to USB-C monitor, closed lid, unplugged it after few hours and opened the lid just to report a kernel panic. Logs attached.

I now disabled Power Nap and will report my results. Let's hope this gets fixed soon.

Have installed 10.15.5 and enabled nap settings as per default. Have left the machine a number of times through out the day long enough for it to start napping. Good news - no crashes so far. Will leave over night to see what happens. But positive initial signs that this is fixed.

Maybe just clean install for you.

I am wondering what does it work when someone updates from older version. I stil have 10.15.3 and keep with it till real solution.

My previous MBP16" had this problem but new one on 10.15.3 without that issue. Maybe kernel panic is just soft issue which is not so easy to erase

The power button for 10 seconds is a precursor to actually resetting the SMC. It may resolve the problem. If it doesn't, there are further steps to accomplish the full SMC Reset.

How to reset the SMC of your Mac - Apple Support

Your Mac is damaged not because you held down the power button, but because it was already damaged.

You don't get to talk to the engineers :/ You can ask for a lvl 2 technician tho and if you jump through all the hoops they have for you they will escalate the issue to them.. I've just been calling non-stop for 4 days so Ig the trick is to be persistent.

I feel you, gave my mid 2014 MBP to my gf, still works flawlessly and I've put that thing through the wringer. Something happened in 2015, Apple seems to have made a lot of questionable engineering decisions since then (in terms of producing reliable hardware, from an economical perspective it sure makes sense..). Just keep pushing that's a 3k machine, it's unacceptable that they won't help!

After the second update of the 10.15.5 my computer is fixed. I am back to enoying a solid macbook pro like the older models. After 50+ days i finally enjoying a beast macbook. No wake up panics or the few random freezes i ve had . Im never updating OS again ....

I've got it narrowed down to the fact that mine only seems to crash when it's connected to my external HDMI display. Also I've been noticing, even as I type here, that my keyboard it weird. The cursor seems to jump around, and there are times when it closes me out of the text window on its own. So, one answer is to make sure I don't have anything connected to the laptop when it sleeps, but even this is ridiculous. There shouldn't be any such problem whatsoever. I think I might go ahead and try getting a replacement. Anyone at all had any luck with a replacement? It seems people still report the same issue anyway.