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.

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.

m0unt41nman wrote:

CMM has absolutely nothing to do with this... this was tried along with fresh installs of Cataline with NO additional software. There is a serious bug here and its becoming widespread. Right now, I'm leaning towards hardware because a friend of mine has the exact same machine as me and zero panics. Same OS, same firmware on the graphics, cards, etc. Yes, he uses CMM too.

I was replying back to @philux who provided an EtreCheck report showing the use of CMM. If you read my reply I also said I doubted CMM was causing this particular issue since so many people have reported the GPU panics with the MBP 16". Suggesting to remove CMM was to help @philux specifically to minimize future issues since CMM has been shown to cause problems with peoples' Macs (just search these forums for how many systems are fixed just by removing CMM).

HWTech wrote:

I was replying back to @philux who provided an EtreCheck report showing the use of CMM. If you read my reply I also said I doubted CMM was causing this particular issue since so many people have reported the GPU panics with the MBP 16". Suggesting to remove CMM was to help @philux specifically to minimize future issues since CMM has been shown to cause problems with peoples' Macs (just search these forums for how many systems are fixed just by removing CMM).

Right... but if you read my responses, you would note that CMM had

nothing to do with it. It was removed with zero impact. In fact Apple

Engineering wanted Dropbox removed... yes Dropbox strangely enough. So

there is no need to explain.

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.

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]

I was having the same issue with my 3 weeks old MBP 16in, went to the apple store and ended up having to return it and order a new one. Originally they wanted me to pay for the repair but they ended up extending my return period because it seems to be an issue with some of the models. Hope this helps some of you with the same issue, don't waste your time trying to troubleshoot it yourself.

Quick update... Apple support got back to me. Engineering said they needed me to try one more thing on a newly installed MacOS with no 3rd party installs. They wanted me to turn off my Sonos as the streaming wireless may be affecting the computer.

That was my last straw. I told the support to pound sand on that as a Sonos broadcasting on its OWN network (I use a SONOS bridge) will have no impact. I explained that if it did, then they have a serious security issue on thier hands. Imagine crashing GPUs because there is a SONOS on the network somewhere.

He ultimately agree with me and told me he would tell engineering to pound sand. He was in agreement that it was very likely hardware related. He is awaiting a final from engineering.

At this point if i don't hear back from him in 48 hours, I will initiate a chargeback on my credit card and force a refund on them.

Hard to believe since its only 2 months old and I bought Apple Care. They should be handling this a bit more expeditiously.

I'll update when I hear back.

Did anyone experience MacBook shutting down at the initial login screen, if not logging in, just waiting a few minutes?

The fans start accelerating, slowly becoming louder, and then after a few minutes, the laptop shuts down.

My previous 16" did the same thing at the beginning. Later it started crashing, following the 1-sec fans blaring. After that, I couldn't log in at all; the same story, login stops at 65%, restarting over and over again.

Apple confirmed its a logic board issue, and they sent me a new 16". However, I'm concerned I will have to send back the second 16" as well.

8-core i9 2.4GHz

64GB 2667 MHz DDR4

2TB SSD

AMD Radeon Pro 5500M 8GB GDDR6

... 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.

Exactly same issue as mentioned here.

Hardware: MacBook Pro (16-inch, 2019)

It happens several times within 12 hours starting from about 12 hours ago. I have installed nothing within this period of time.

Most of the time, I just use this computer to code and view webpages. I have reset the SMC, but it seems useless.

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.

I've got my 16inch back from Apple Service Provider - there was an error on logicboard, the MBP crashes everytime in switch to dedicated GPU. With the new logicboard it run's fine since last friday - finger crossed.

Similar issue here, differences bolded:

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

Ok, I do NOT have a MBP 16"...I have a 2012 MBP 15" and I have the same issue. If its not plugged in, it tends to crash on wake from sleep. It does occasionally do it while plugged in but majority is when on battery.

I just did a fresh install of Catalina. I had been experiencing the rapid restarting. With a fresh install, It ran better...for about a day.

Backstory. I bought this used off of Mac of all Trades. It had a new motherboard about 16 months ago.... \

Oh, I did notice when I signed into Adobe CC, the processor started working really hard and it would shut down.

I am going to try not letting it go to sleep... the gestapo method of computer using.

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 / let alone multiple final cut pro projects on the go that are a pain to move. The exact same thing happened last year with a maxed out MBP and after months of fighting they refunded. This time they basically said 'do one' - Awful support - when is a rival company just going to come out with a competitive product that is actually well-made. Every time I close the machine it restarts, sometimes turns off mid work flow, screen going weird, touchbar not working randomly, DO NOT TOUCH THE 16 INCH MACBOOK PRO. I don't know about anyone else, but if this (laptop) is your only way to work why do apple assume we can all go without a machine for 2 weeks to get it repaired? Especially After 5 weeks of being brand new machine and costing 6k. Joke of a company. Steve jobs would be ashamed. If your porche or even skoda started cutting out on the motorway after 5 weeks they would bend over backwards.

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

Backtrace (CPU 0), Frame : Return Address

0xffffffa78eecb710 : 0xffffff801c73bb1b

0xffffffa78eecb760 : 0xffffff801c8733e5

0xffffffa78eecb7a0 : 0xffffff801c864e5e

0xffffffa78eecb7f0 : 0xffffff801c6e2a40

0xffffffa78eecb810 : 0xffffff801c73b207

0xffffffa78eecb910 : 0xffffff801c73b5eb

0xffffffa78eecb960 : 0xffffff801ced24f9

0xffffffa78eecb9d0 : 0xffffff7fa09c2a97

0xffffffa78eecba30 : 0xffffff7fa0a7914d

0xffffffa78eecbcb0 : 0xffffff7fa0a476de

0xffffffa78eecbce0 : 0xffffff7fa0a78af0

0xffffffa78eecbd10 : 0xffffff7fa0a62075

ChazThePhoenix wrote:

Ok, I do NOT have a MBP 16"...I have a 2012 MBP 15" and I have the same issue.

ChazThePhoenix wrote:

I don’t have the luxury of Apple care on this 8 year old MBP, which worked great until Catalina

hmmm... are they trying to make me update?

This thread is for issues with the 2019 16" model and from all accounts it looks like the 16" MBPro 2019 has an actual hardware issue. Since you do not have this computer please start your own thread with the pertinent details if you want assistance from the community on sorting out the issue with your laptop. You may want to run EtreCheck and post the report to these forums in your own thread using the "Additional Text" icon which looks like a piece of paper.