New 16” MBP Random Restarts and LockUps

Just an update on my progress. My prior MacBook would unexpectedly freeze for 10 seconds, then the fans would go 100% for 5 seconds, and the machine would then power off or restart. I would check the logs after this issue and get a "bad magic" kernel panic. They sent me a brand new replacement. This issue seems to be resolved with a brand new replacement. This is a hardware issue (unless you're having panics due to the most recent version of Catalina). If you're having kernel panics, bad magic issues, or unexpected shut downs/reboots, then I'd recommend to get a replacement as soon as possible. This is the only way to resolve this issue.

I spent countless hours troubleshooting the issue with Apple and sending it out for repair twice. The first repair, they only reinstalled MacOS and updated my T2 firmware. This didn't resolve it. The second repair, they replaced my Touch ID Board and Logic Board. This also didn't resolve the issue. I then requested a new replacement (since I'm still within my warranty). They approved this and were able to send me this brand new replacement. This replacement does NOT have any issues and now the issue is resolved.

Please keep in mind that Apple (US) will only send a replacement after a certain number of repair attempts (usually 2-3 attempts), if you're past the 14-day return date. So please make sure to get started on the repair process and after the second/third repair, ask for a replacement. This is the only way to resolve the issue. It was the only way for me to resolve the unexpected shutdowns and reboots with "Bad Magic" kernel panics. I have read prior that this is the only way others have fully resolved this issue. I hope you all have the same success as me!

After easily reproducing the problem without any external devices (or often even power supply) connected, I returned mine under the 14 day return limit. Before returning, all I had to do was put it to sleep a few times to see it reboot. I tried re-installing the OS via Internet Recovery, clearing NVRAM, reformatting the drive and starting from a stock OS, and any Energy Saver settings I could think of. Every experiment resulted in a reboot after wakeup from sleep within 2 or 3 attempts.

The new MacBook (same specs as the previous) has been performing like a champ after 3 days with all the same configuration. We'll see if the issue pops up again on this new computer.

So just an update on my progress. I’ve posted his prior but I want to give everyone a refresh just in case you don’t hear back from me due to the issue being resolved. I’ll keep you all updated if the issue seems resolved after I use my MacBook for a month or so. 

I purchased my 2019 16” MacBook Pro on 12/08/2019. Immediately after buying it, the MacBook had issues. MacOS would freeze completely, the mouse cursor couldn’t even move during the freeze for about 10-20 seconds. Then the fans would start going full speed and get very loud for about 5 seconds. Then the system would automatically shut down or reboot. I then got curious about this reoccurring issue so I posted here on 12/12/19 about having this issue. 

For my first time around, Apple had me do the following:

1. Reinstall MacOS and restore from a time machine backup. The issue still occurred. 
2. Reinstall MacOS and don’t restore from a time machine backup. Manually reinstall applications as needed. The issue still occurred. 
3. Drive two hours to have a Genius review the MacBook. He suggested that I again reinstall MacOS but couldn’t diagnose the issue. He pushed the possibility of it being hardware related. He asked that I mail in my laptop for repair if the issue happens after another reinstall. 
4. Reformatted the Macintosh HD and reinstalled MacOS from a USB flash drive mounted with the most recent MacOS Catalina image I downloaded from the MacOS App Stored, which is signed by Apple. The issue is still occurring. 
5. Apple sent in a repair request to send my device out for repair. It took three business days for me to get it repaired and receive it back. According to their repair notes included with the repaired MacBook, they only “reinstalled MacOS” which I find humorous because I’ve done this multiple times already per their instructions!

I then had the issue again following the first repair. I called Apple and they actually collected console logs this time from the MacBook. I was getting “Panic” logs saying “Bad Magic” during these unexpected shutdowns and reboots. 

They sent the device out for repair again on 04/01/2020. It took four business days (should have only been three but UPS had a technical issue) and I got it back today, 04/04/2020. They replaced the Logic Board (item #605-06150) and the Touch ID Board (item #605-06552) due to a “Kernel Freeze” symptom. They also clean installed MacOS and it shows that my device passed hardware testing. 

So I’ll be testing this repaired device for a month or so and will see if the issue happens again. If it happens again, I’ll probably get a full replacement or ask for a refund from Apple due to their Warranty terms. 

I’ll keep you all updated if the issue seems resolved or if I have any issues after a month. 

The work-around proffered by Apple support is to turn off Power Nap in both sides of the Energy-Saver control panel.

10.15.5 was supposed to include a fix for this problem, but appears to have only fixed a small special case, so many users say the problem remains, and one still needs to turn off Power Nap to survive without kernel panics.

I contacted Apple Support yesterday afternoon for the same problem with my new MacBook Pro 16. When I said that I had received a crash message of “Bad Magic!”, the rep immediately asked if the rest of the message was “(flag set in iBoot panic header), no macOS panic log available.” He obviously had been advised that the problem existed.

He told me that this could be a software problem because of “corrupt installation”—his words. He advised me to reinstall the OS (10.15.2), but to reinstall via Internet Recovery (Shift + Option + Command + R) rather than the laptop’s Recovery partition. I was not advised to wipe the drive, so all of my files stayed in place.

It’s too early to declare it’s fixed, since I’ve spent more time opening presents and feasting than playing with my computer, but I’ve used it for several hours, left it sleeping overnight (it would crash and restart after sleeping on occasion before), and started up and shut down multiple times to see if I could produce a crash. I haven’t had any problems so far. The fans seem to run less often and quieter now also.

So I’m keeping my fingers crossed. Since my files weren’t lost and it only took 45 minutes or so, I thought it was worth a shot. If the problems persist, I have a Case # and a return can be made.

C.

Mine will be replaced after 6 weeks of fight with premium repair service.

No pram or smc reset helped, no installation or safe mode helped, there were no peripherals, no external stuff, no third party apps or drivers.

Even a clean factory installation with the latest everything made the computer reset when woke up from sleep state.

After 6 weeks of struggle, I have been promised to replace. Guys, make Apple replace your 16" devices as well. They should, it is not a software bug for sure...

So I haven't had this issue since I've received the 2019 MacBook Pro 16" back from Apples repair center. Before I sent it off to get it repaired, I took screenshots of all my hardware/software under System Report and pictures of my MacBook to see what they all did prior to sending it back to me.

They said that they only "Reinstalled MacOS" on the repair paperwork but I did notice when doing comparison with my screenshots to the MacBook now, that my Apple T2 Security Chip now has a different firmware version. So they reinstalled MacOS and also updated my T2 Security Chip firmware to a higher version. No other firmware versions changed and nothing else was different. I reformatted and reinstalled MacOS once I received the MacBook Pro back from the repair center and the T2 Security Chip firmware is still the version they updated it to, which is higher than what it was originally.

My MacBook Pro has not been having these issues since they did this and I've put around 40 consistent work hours into this laptop with a very large volume of applications running at once, taking up a lot of resources.

When I sent in the MacBook and received it back, it had the same version of MacOS on it, which was the most recent version at that time. So there was no MacOS version difference. Just only a difference in my T2 firmware version. I believe their T2 Security Chip firmware update resolved my issue, but only time will tell.

The most effective way to know for sure if it's a problem with either the OS or the computer itself is to fully erase the drive, reinstall macOS Catalina and do not install any additional softwares and do not connect it to any equipment. If it's only 3 days old then it's imperative that you do proper troubleshooting during your 14 day return period. If all else works after doing the full erase and install then connect it to external devices one by one and test it. If that's fine then install your software one by one testing each one.

Hey all, just wanted to post an update as I've fixed the issue for ME and I think it is a combination of software/hardware.

As many people recommended, I disabled automatic graphics switching and power nap, although I think the first is the culprit. There is a controller issue (verified by others) when the computer switches from intel graphics to AMD graphics so by leaving AMD graphics on 100%, the issue has disappeared.

Hope that helps!

I disabled sleeping when the display is asleep, and it hasn’t happened since. I believe this is related to something that happens when the computer wakes up, in my case both times it was try to access a tv show or movie from an appleTV.

My Macbook Pro 16" also was freezing and restarting frequently. I noticed that always when it happening google chrome was running. So I removed google chrome and now it isn't happening almost two weeks.

Before that when I chat with apple support they said one of the installed programs is not fully compatible and I think it was google chrome.

So I decided don't install google chrome until the next Catalina update and hope the update will fix this issue.

Having the same issue on my 16 inch MacBook Pro. I just updated to 10.15.2 in hopes of solving the problem but it persists. Whenever I close my Mac to put it to sleep, a few minutes later, the fans will run high then silence. I open my laptop and it shut off, indicating a kernel panic. I turn it on and get the “your Mac has restarted because of a problem.”

It turns out, when my USB Hub isn’t inserted after putting it to sleep, it doesn’t crash. Tested for over a week now. So for me it only happens when my hub is plugged in..not sure how to fix this problem. Nor do I have chrome installed, as some users said was an issue.

BAD MAGIC is a known problem, and Apple Support should be able to help you with it.

Some readers reported theirs was solved with an update to the T2 firmware (one said this was done By Apple) so be sure you have applied ALL software updates.

I did reset SMC and Turn OFF <Automatic Graphics Switching> in [System Preferences][Energy Saver].

So both of graphics processors will always active (Intel & AMD Vega).

Crash problem was gone for few days. But my MacBook run little warmer.

Try it for yourself and see if you could reproduce same result.

Cheers !

"Time to erase and re-install."

That's what I was about to recommend. It sounds like a corrupt file that is causing that. After a doing a full erase and install of the OS I tend to recommend to people not to install any additional apps and test it out for a couple of days first, install their apps one by one rather than dumping all your files back on. This is the simplest way to be sure if the additional applications being installed may be causing the issue. I'd also recommend to avoid any 3rd party software utilities that modify the system such as Fan Control or Coconut Battery. I would keep it simple until the issue no longer shows up.