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

I ordered a MBP 16" in March when I immediately starting seeing the Panics on 10.15.4.

Apple Support decided to exchange my "faulty" device, and I have kept that one on 10.15.3 (as it shipped) until yesterday.

Having made a Time Machine backup, I upgraded directly to 10.15.5. I can tentatively say this MBP 16" doesn't experience any crashes yet, not even on the overnight sleep that used to cause the panics on the first machine.

I will keep you posted in case anything changes.

As I told yesterday 10.15.5 got my macbook to panic again when doing the power nap.

Disabling power nap seems to have "fixed" the problem. Now I will try to enable the power nap again and see if the problem is still solved as I saw it with 10.15.4. Apple. It seems to be a state-problem, that is solved when you flip the power nap off and back on.

Apple... To be quite honest... you should really fix this software problem... you have had months to fix it... Time to write directly to Tim...

OK.... MacbookPro 16 (from march/april): Friday my macs updated from 10.15.4 to 10.15.5 (19F96). That reintroduced the Sleep-Nap-Kernel-Panic (Kernel Panic when sleeping and on power). The disable "Power Nap" trick solved the problem in the weekend.

Then this morning (in EU), my computer did a huge update again. 15 minutes. Did not ask many questions (none). Bum... New version of 10.15.5 was installed: Going from build 10.15.5 (19F96) to 10.15.5 (19F101).

2020-06-02 09:56:35+02 CaspersMBP16 softwareupdated[366]: softwareupdated: Starting with build 10.15.5 (19F101)

2020-06-02 09:56:50+02 CaspersMBP16 softwareupdated[366]: Previous System Version : 10.15.5 (19F96), Current System Version : 10.15.5 (19F101).

Talking about panic.. Apple releases a brand new 10.15.5 three days after the previous one.

Lets hope that 10.15.5 (19F101) solves the problems, because 10.15.5 (19F96) did not!!!

Hey there! Sorry for the troubles! I’d say for this issue, this would be the best article to follow:

https://support.apple.com/en-us/HT200553

This can be caused by a number of things, I’d say if none of the steps fixed it, to contact Apple Support. If this is caused by something new they don’t know about, I’m sure they’d be interested, as nothing reported/nothing fixed. But in my experience, it’s either due to an external device plugged in, or some third party app extension or plugin installed that is conflicting with the operating system or some other program or process.

Especially if this happened after an update that’s probably the case, so updating all third party apps is also best to do if possible. Or uninstalling for testing purposes. Hope that helps.

Hey again, I read the thread, just giving some general advice. Some of which was to contact Apple to investigate, obviously the steps you’ve taken unfortunately haven’t worked, so I’d say that’s a good step to take. They work hard at making their products best they can, complaining won’t fix anything, but working with them may help not only you, but maybe even others. (Although I know not everyone has the time to do so). Just saying, maybe they have more resources than what you can find on google, or, like you said, just wait until it works itself out. Computers cost a lot nowadays, so I get it and hope it works out. If the hardware is ruled out, (Which of course might not be the case), I’d probably take a look at the firmware.....maybe this article can help:

Revive or restore Mac OS Firmware:

https://support.apple.com/guide/apple-configurator-2/revive-or-restore-mac-firmware-apdebea5be51/mac

Considering the situation and isolation done, I’d say restoring the firmware may be a valid step, Hope it works out!

Relevant article:

About the T2 Chip:

https://support.apple.com/en-us/HT208862

Interesting, hope this get's their attention and a fix is developed.

I have the agree that disabling "Power Nap" has had a positive effect, but yeah.. I "hold my breath" at each wake up now..

@GreenBadger... did you try to reset SMC and NVRAM AND disable “Powernap..."?

I would not return my Mac before I had tried that!

From all the reports I get, it seems that it is disabling power nap that does the trick and fix the problem. Some of us has even enabled power nap again, and still no problems.

No problems for me since disabling the powernap, when charging.

Doesn't do it when not charging, so happy to wait for fix, as it was only an annoyance.

Beta 4 fixed for me, and now final release 10.15.5 is out.

Mine is 32MB but I’ve heard of friends of mine with standard config they have the same problem. I have since switch off power nap again and seems to help.

I also have this problem in my MacBook Pro 13'' Early 2015 after updating to 10.15.4, meaning that this problem affects computers with or without T2 chip. Sometimes my computer won't wake up at all. Sometimes the log-in screen will appear but my computer will be completely unresponsive. Sometimes I will be able to log-in but I will receive a message that my computer restarted because of an error. The supplemental update for 10.15.4 has not fixed the problem. Resetting SMC or NVRAM has not fixed the problem. Disabling Power Nap has not fixed the problem.

My MacBook crashes only when it's been in sleep for a considerable amount of time, e.g. overnight. I have never experienced a crash during day after my computer being in sleep for a few hours. I suspect that hard disk does not go to sleep during day but it does during night and this is somehow related to the crash. In Energy Saver settings I disabled 'Put hard disks to sleep when possible' for now and I am going to shut down my computer at night from now on.

I really hope that Apple fix this as soon as possible (this bug has been around for a month now). I am in the habit of updating my system as soon as an update becomes available and I had never such a bad experience with an update before (not even with .0 releases). I do not take Time Machine backups before updating (I used to trust Apple's Quality Control) and I cannot downgrade to 10.15.3. I am really disappointed.

Have been running 10.15.5 with naps enabled for a couple of days now and the problem, for me at least, seems to have been resolved. After coming back to my machine multiple times and waking it up throughout the day and leaving it overnight- no new KPs so far.

The reset method as instructed by Apple Support was the full SMC reset you mentioned

Did you read the SMC Reset article I linked? Holding down the power button is recommended before actually resetting the SMC. You never got to the "full SMC reset" despite what the AppleCare script reader told you. From the article,

Before resetting the SMC, try these steps:

Shut down your Mac.

Press and hold the power button for 10 seconds, then release the button.

Wait a few seconds, then press the power button to turn on your Mac.

I have a 2018 MBP with T2 chip and I have shut down and held down the power button for 10 seconds a couple of times. Nothing bad happened to my Mac.

Edit: also, there is definitely a good possibility that my MacBook might be damaged but as you can tell, most people on this thread have the same underlying problem that tells me it’s not only particular to my case, and it might not be a “damage” issue, rather than a software issue.

I agree that there is an underlying problem with the 16" MBP. I have advised on most of these threads to take them in for service because Apple will never recognize that there is an underlying hardware problem until they get their hands on them and see what is happening. Posting anything on this forum will not raise any concern from Apple. Trying to resolve the problem over the phone will not raise any suspicions.

Can confirm that the update of this morning did not solve the issue (at least not for me, even made it worse as in now if 1 external display goes to sleep in clamshell mode the MBP restarts with the usual panic cpu error). Got a callback from Apple asking about the update and whether it fixed the issue (to which I said no obvs), also got confirmation that the engineers are aware of the problem (affects several users) and that they're working on it. Also, they confirmed it is a software issue rather than hardware.