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

Resounding no. I have 10.15.5 + the 10.15.5 supplemental update. Still experience 1+ kernel panic per day with reboot. Happens consistently if the machine falls asleep while connected to an external monitor via usbc (or, also, USBC dock that connects to an external monitor over hdmi). I also purchased a 2nd duplicate 16" MBP of exact same specs and tried it after apple support failed to address the problem. This machine also has the same issue. I have tried both with my migrated data and apps, as well as blank slate just with macos no files or apps added. It's clearly a firmware or HW eng problem, not an isolated incident.

I'd just like to add my own similar experience. MacBook Pro 16, bought in March 2020 so no chances of return, but I'm having this same issue - but irregularly. One day it'll go to sleep and wake up fine. Next day it won't. I can't consistently reproduce the error. I've have numerous calls with Apple (some useless, some escalating it to the senior team. I've done countless PRAM, SMC and all those other resets. They've done a bunch of diagnostics.

Status now? Apple have said I have to partition my Mac, a clean partition no 3rd party software etc. So like OP, Apple are making me do the legwork to work this out. If this option doesn't work, I'll have to wipe my Mac. It's been a nightmare and after spending all this money, I hate this MBP. No updates (10.14 through to 10.15.6) have helped. (Though 10.15.5 did help with a massive battery drain issue).

Rant over, but from my research loads of people have had this issue (across different models and OS versions) yet Apple just make the users do the leg work to fix it/work out the issue.

I bought my MacBook Pro 16 inch in January 2020. I successfully argued my case in July that Apple created the kernel panic issue with macOS 10.15.4. My MacBook Pro 16 inch was running beautifully until the 10.15.3 to 10.15.4 upgrade. I also went through multiple iterations of resetting PRAM, SMC, wiping the hard drive, disk diagnostics, hardware diagnostics, removing all user installed applications, etc. I didn't want to send my MacBook Pro for repair so the engineers could use it for testing to determine how they created the problem. All of that type of testing should have been done before the 10.15.4 OS release. I wouldn't waste your time - none of the iterations I mentioned fixed anything. There are also threads sharing that MBP 16" machines are coming out of the box with the kernel panic issue - totally unacceptable. My MacBook Pro 16 inch was returned for a full refund in July / August. I am now the proud owner of a 27 inch iMac - not a single kernel panic. Apple turned a very bad situation into a good one. I am sad for those that are still dealing with this issue and disappointed that Apple hasn't issued a general recall and stopped shipping new MBPs until the problem is identified and fixed.

An update is available today but no mention about this. Maybe it's fixed now.

I am pretty sure this has only happened since my last software update, I have deactivated the power nap and I guess I will have to wait for this to be fixed on the next software update....

MBP16 10.15.4. I tried to close Safari fully before going to sleep. It's already 3 or 4 days without kernel panic while sleep or wake up.

I'm on public beta 4 and it seems to do the trick. Zero issues in the past few days.

Maybe you should do a clean install. Updates don't work every time

Same here. Brand new Macbook Pro 16'' (1 week old). After updating to Catalina 10.15.4 only when plugged in. Found another thread on the topic here https://forums.macrumors.com/threads/new-macbook-kernel-panics.2228308/. Still no solution, just a workaround (look at one of the last comments).

Let's wait for an update, hope that Apple Support knows about the issue.

I have the same problem with the same Mac & same os x version. As soon as the MBP goes to sleep for too long... it crashes.

Notice that I don't have VirtualBox installed (but I do have parallels, even if it doesn't seem to load a kext).

I checked my loaded kernel extensions and the only ones not "apple related" are Little Snitch & Fuse.

This bug is very frustrating.

I thought supplementary release 10.15.4 solved it for me. But the original problem is actually not solved.

I recently had my new MacBook Pro 16 2019 connected via a single USB-C cable to a CalDigit USB-C Pro Dock, using its power supply and an ethernet cable for network. No monitor connected though.

With this setup and the supplementary 10.15.4 release I didn't experience any kernel panic during sleep with power nap enabled .

However when I go back to the original setup, having only the original Apple power supply connected via Apple USB-C cable and using WLAN only then I get the kernel panics again during sleep when power nap is enabled.

@ClassicII Even after working in technology for the last 30 years, I made an embarrassing mistake in terms of helping to diagnose the situation here - I changed multiple variables at once. Specifically, I deleted but then reinstalled Google Drive File Stream, I disabled Powernap, and I also (accidentally) closed the lid to the machine before going to bed (I normally leave it open and connect to several third party devices and this results in a nightly crash). I’ll do better tonight! See below.... however....

I can report one finding from what I did last night:

With Google Drive file stream re-installed and running, powernap disabled, the lid closed, and not taking any other actions, my machine still crashed this morning. My diagnostic report pointed to PowerPoint as the cause of the crash in this case. In order to connect this back to my original post, Google Drive file stream was still installed (reinstalled), I changed my power nap nap setting to disabled, and I closed my lid as opposed to leaving it open. All of my previous diagnostic reports pointed to Google Drive file stream as the culprit. With a lid closed and power nap disabled, the machine crashed first thing this morning but with PowerPoint listed as the cause instead of Google Drive file stream. Google Drive file stream and PowerPoint were both open at the time of the crash.

I will delete Google Drive file stream from my machine tonight before I go to bed (disconnecting all third party devices, and leaving powernap disabled) to see if I get another crash in the morning.

I’ll report back.

I have Google drive installed AND power nap enabled and still no problems.

What did it for me, was the 5 steps i mentioned above.

When you se Google Drive in the crash reports it is properbly because it is the active process that runs when power nap is enabled.

I think it is the disable/enable powernap that fixes the problem. Properbly a bad State that is set correct when you flip the power nap off and then on.

Same issue here, Trying to disable power nap to see if that helps.

Thanks for sharing your troubleshooting steps, I've tried all except for a complete nuke and pave and after reading your comment I think i'll hold off.

You're not alone partner!

Thank you for confirming this, I think it is obvious it is an upgrade software issue.... minor but annoying and the power nap fix mentioned earlier has patched things up for me in the meantime.... Also 16 inch MacBook Pro