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

@Timecop: yes I've only had the issue since the update. No 3rd party extensions and no devices plugged in. The crashes are becoming more frequent. I've reset PRAM and turned off the power nap setting as well.

I have the exact same issue which is seriously killing my productivity and stressing me out since this device is pretty expensive and I was excited to use it.

MacBookPro16,1

8-Core Intel Core i9 2.4 GHz

32 GB

2 TB

Catalina 10.15.4 19E266

Will try the PowerNap hack but my hopes aren't high since it also crashes randomly while running (display on).

I had same problem before and after the supplementary update 10.15.4.

Supplemental update did not fix the kernel panic.

Disabling power nap doesn't work for me.

I have a MacBook Pro (16-inch, 2019)

• Monitor Dell U2719DX
• Magic mouse 2
• Magic keyboard

I have a MacBook Pro (16-inch, 2019)

• Monitor Dell U2719DX
• Magic mouse 2
• Magic keyboard

Same problem here, MBP 16 2019 10.15.4

kernel : Darwin Kernel Version 19.4.0: Mon Mar 2 20:38:56 PST 2020; root:xnu-6153.101.6~2\/RELEASE_ARM64_T8010

macOSPanicString: panic(cpu 0 caller 0xffffff8009c91b2c): Sleep transition timed out after 180 seconds while notifying clients about upcoming system capability changes. Suspected bundle: com.apple.iokit.IOGraphicsFamily. Thread 0x74.

+ feedback report

+ crash report

Hope this problem will touch apple engineers.

I still have a ticket open with apple support, and I tried to point the support person to this thread, but he wasn't interested and didn't feel inclined to forward the problem to the engineering department. See my first post in this thread. The engineers should be aware as they continue to receive the kernel panic reports.

This is a bit offtopic, but still:

Apple support in Germany seems to be completely overloaded. A friend of mine bought a MacBook Pro 16, i7, three weeks ago. When trying to move his user data with the migration assistant it always failed. He spent initially more than an hours with Apple support and they couldn't help. He also tried to buy apple care for his new machine online. It failed with an error message that his machine (2 weeks old) isn't qualified. He called Apple support about it, gave them his telephone number and they promised to call him back within two minutes. That has been a couple of days ago and they never called back. Lately he hasn't been able to reach anyone on the phone, queues are too long.

I'll help him to move his data using desktop sharing. But this isn't how it should be. For a long time my experience with Apple support and service was a decent one. At least for the moment that has changed.

I've had a brand new MacBook Pro 16 inch for 36 hours... I'm having the exact same problem... I've been an Apple guy since Apple II+ (1983) --- This is the first epic fail I've experienced with Apple... I have to do all my work virtually now... And I shelled out big $$$ for a more powerful Mac, and it keeps doing this.... Pretty disheartening that this issue has been happening awhile and they have not fixed it.

I exactly experienced the same situation as yours, with Macbook Pro 16, i7, 32GB. And I totally agree your assumption that it is power nap, because the same bug doesn't appears for plug-off in my case.

I have the same problem. My MacBook pro retina is from late 2015. It has now crashed 8 times since updating to 10.15.4. The machine seems to crash (not always) when i close the lid. It runs the fan 100% when i open it up. I have tries to reset SMC (did not help).

Hello @riley0502 .... I have an iMac, not a MacBook Pro ... yes I tried to reset the SMC and NVRAM without resolution ... being an iMac, probably still a software issue? The reason is I can return it and get my money back still ... rather than them trying to 'fix it.' I can get a new one later once all the issues are figured out.

Jeff

I can confirm that too. Same situation here. Brand-new MBP 16 about one month old started crashing form the beginning without any software installed than the one that comes by standard. I re-installed MacOs 10.15.4 and the crashing did not stop.

Since I did the steps mentioned by my post above I did not experience any crashes for several days now!

I will keep you updated, if this is permanent.

For what it’s worth, I am now on my second 16” and both are experiencing this issue.

my first one kernel panicked when on and working, during things like zwift app rides, premiere video exports, and Cisco webex video calls - even after a complete reinstall of OS without using a time machine backup. I have not extensively tested the second one yet, but it has been crashing.

I don’t know if it is hardware or software, but I have done all those things except turning off power nap and the issue has persisted. I’ll be trying the power nap trick today. I’ll report back.

thanks

My crash on wake went from:

panic(cpu 2 caller 0xffffff8006c16487): "AppleIntelFramebuffer::setPowerState(0xffffff834eecd000 : 0xffffff7f8a1c7d88, 1 -> 0) timed out after 45993 ms"@/

to:

panic(cpu 0 caller 0xffffff800a491b2c): Sleep transition timed out after 180 seconds while entering darkwake on way to sleep. Suspected bundle: com.apple.iokit.IOGraphicsFamily. 

Just read your post after restarting my brand new machine after yet another Kernel panic crash. All I can say is - do not make the mistakes I did and think very carefully before you spend thousands buying a new macbook pro and/or upgrade your OS - at least until Apple comes clean about what the problem is and gives their customers an indication of how and when it will be fixed.

I'm very disappointed that I've spent 4k on a defective product, and I need a "Workaround" to use it. And still no fixes from Apple after so long. I assume some hardware issue is related and they don't want to start a repair program until they are completely sure what's going on. I have other issues also like glitchy screen (looks like graphic card related), cracking speaker noise, etc. If it's only an OS issue it doesn't make sense to me it's taking so long to fix.