Hi Everyone i am getting the error below and my computer wont login. i have the new 2019 16in its less than 3 . weeks . old.

In my opinion (and I do not speak for Apple, Inc) It sounds like these reports are Mostly a Hardware issue, that the GPU is not responding properly. I think this is a "sample defat" -- a problem that occurs only in a very small number of systems.

But there are so many things that you can ADD that would gum up the works, you need to be able to show the issue with a relatively All-Apple system before anyone will take action.

Remember that Readers here are other Users like you, NOT apple employees. Posting here does NOT notify Apple that you have a problem. To get better results for everyone, be selfish and push your issue with Apple Support. You can start with the Contact Support link at the top right of every forum page.

rn2284 wrote:

Same here. Absolute joke of a company - support were so rude. Casually saying to reinstall everything to test when I just paid my engineer £600 to install every music plugin i have all of which would need licensing again and took days to set up

No one, company or individual, can debug a machine with dozens of add-ons. It needs to be standard all-Apple. The requirements is not "blow away your drive" it is run in an unmodified MacOS.

MacOS can boot from any drive, Internal or external, after you make some adjustment is the T2 chip. You don't have to erase your drive, just use an external drive and install a fresh, unmodified copy on the external drive.

About Startup Security Utility - Apple Support

.

philux, this is the MBP 16" you've had out for repairs?

--

Possible solution (need more tests)

I disabled standby, did the Chrome YouTube HD video test twice, and it woke like normal both times. I'm going to try it overnight and see how that goes. Looks promising. This + a few users still having the problem after an Apple hardware replacement would likely mean the issue is software-related, likely Catalina.

If others want to try: Open Terminal, type: sudo pmset -a standby 0 and then your account password.

To revert the change, just change the 0 to a 1. You can check if it's off or on with: pmset -g

Hey Everyone! Update on my machine. I sent it in to be repaired by Apple. It took 2 days. My machine now works like a champ. I highly recommend to contact Apple ASAP to get your machine repaired if you are getting the GPU kernel panic. The key thing I did was to tell them that I did all the troubleshooting steps including a full reinstall of the OS. Good luck everyone!

The panic mentions an issue with the GPU, but this could also be caused by third party software. Run EtreCheck and post the report here using the "Additional Text" icon which looks like a piece of paper.

Apple engineering is currently looking at my issue since they have had all the diagnostics at this point. They are not convinced its hardware is at fault since it does boot in safe mode. My error is slightly different. I get:

panic(cpu 0 caller 0xffffff7f91021a97): GPU Panic: mux-regs 4 3 3f 1f 0 0 severity 3 WS-ready 1 switch-state 0 IG FBs 1 EG FBs 0:0 power-state 4 3D idle HDA idle system-state 2 power-level 5:0 power-retry 0:0 connect-change 0 : PowerPlay Failed Resume.

So far the temporary work around has been in System Preferences > Energy Saver > Power Adapter > Prevent computer from sleeping automatically when the display is off, setting that ON.

The error seems to occur when coming back from sleep (at least for me anyways). Apple is supposed to get back to me to let me know whether to send the machine back or wait for a software fix.

My specs are:

8-core i9 2.4GHz

64GB 2667 MHz DDR4

2TB SSD

Radeon Pro 5500M 8GB

UPDATE: I created an external boot drive that has NOTHING installed. Within a few hours, I got the GPU panic and sent the capture files to Apple. So this has nothing to do with any software that has been installed by me because there is none.

Lets see what Apple Engineering has to say.

philux wrote:

Macbook Pro 2019 16" crash on sleep and force restart related to GPU Panic.

<macOS Crash Log.log>

<EtreCheck Report.log>

I'm not familiar with some of the items installed, but you should uninstall CleanMyMac by following the developer's instructions. Anti-virus and cleaning apps are not needed on a Mac and they usually cause more problems than they solve plus they impact system performance.

I'm not saying this is the cause of your problems here since so many other people appear to be having these panics, but it may help down the line.

My second time responding to this thread. My first 16" crashed every time I closed the lid/put to sleep after less than a week of owning. I did clean reinstalls, signed into different users, but it kept crashing. I found a couple other people who followed my exact steps and cleaned everything but the crashes kept happening.

To solve this issue, I got a replacement MacBook and now there's no more issues.

HWTech wrote:

m0unt41nman wrote:

In fact Apple Engineering wanted Dropbox removed... yes Dropbox strangely enough.

That is standard procedure when troubleshooting the source of a Kernel Panic (or any issue actually) in order to determine if the Kernel Panic is caused by hardware or software. Uninstalling all third party drivers/extensions or even better yet performing a clean install of macOS (erasing the whole drive and reinstalling macOS without migrating or restoring apps/user folders) is the only way to separate out a hardware issue from a software issue. Just because DropBox is a common app does not mean there couldn't be a bug in the DropBox software which is interacting badly with a driver specific to this particular MBP.

I do realize the MBP 16" GPU Panic is most likely caused by a macOS driver bug or faulty hardware or firmware.

When troubleshooting the source of the Kernel Panics a person must either uninstall all third party drivers/extensions or even better yet perform a clean install of macOS (erasing the whole drive and reinstalling macOS without migrating or restoring apps/user folders). This is the only way to separate out a hardware issue from a software issue. Just because DropBox is a common feature does not mean there isn't a bug in their software which could be causing a panic.

Right...I know all of this... I write kernal extensions and MacOS software for a living :-) My point was in the panic stack trace, there was nothing showing Dropbox or CMM. It mostly had Apple drivers, not intel, and the AMD drivers poke their head in there every once in a while. In fact when mine "randomly" occurs on the Intel being there, the AMDReadionFramebuffer seems to appear in the stack. Dropbox uses nothing with regard to the GPU AFAICT. That's why I thought it was a red herring.

My bets are on hardware since as I mentioned before, I have a friend with the same machine and mostly the same software setup without a single mention of a panic. Another guy recently posted that after receiving his MBP back from Apple that it no longer panics.

I'm not arguing with you or flaming you. I'm just saying we have been down this path with Apple and in this thread (CMM not involved). I would actually try debugging the kernel driver in a VM... but it may still make the entire MBP panic because its likely hardware related which will render a debug session null. If its purely software, the a debug might work.

[Edited by Moderator]

Nope. It did it again. Sorry for wrong alarm.

tbergmen wrote:

As a temporary workaround, I turned off "Automatic graphics switching" off for Power Adapter in Energy Saver settings. This seems to work for now. Will update if it happens again.

https://discussions.apple.com/content/attachment/47482e28-0b68-4fba-9baa-1674f8689f54

I have the exact same issue.

For the moment the workaround i found is to plug alimentation (or unplug it if it was plugged) when the reboot progress bar gets to about 70%. I guess it makes a kind of PowerPlay update that fix the Initialize issue.

The other option is to boot in SafeMode.

As a temporary workaround, I turned off "Automatic graphics switching" off for Power Adapter in Energy Saver settings. This seems to work for now. Will update if it happens again.

... if I close the lid and open it up in a couple of hours (I assume after the MacBook has gone from sleep to hibernation) it always does a cold boot. After I insert the password, I get a black screen and all the fans got 100% for one second. Then it boots again, I insert the password and I get logged in. I always get a crash report from the OS.

Same exact problem here, and I also get crashes while running gpu-intensive apps (Unity 3D). I took it to the Apple store, they ran all diagnostics and everything came back fine, they recommended wiping and reinstalling, I said no thanks and returned it. Am waiting a few weeks before I decide whether to replace or not.

There's another thread over about this or similar crashes on the new 16" Macbook Pro: https://discussions.apple.com/thread/250905859

I have no news about my MacBook, it is still in repairs. Just wanted to share it's specs to see if we can find similarites. I've noticed that the people who do announce their specs in regards to this problem (in this forum post and in others that I've seen) seem to have the 5500M GPU, so I'm wondering if that is the cause of the problem...

Anyway, my specs are:

8-core i9 2.3GHz

32GB 2666 MHz DDR4

1TB SSD

Radeon Pro 5500M 4GB GDDR6