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.

I have the issue with Radeon Pro 5500M on MBP 16 inch. I tried all solutions (reset everything and reinstall them) and nothing worked.

I brought the computer to Genius Bar several days ago, they ran a basic test and there is no hardware damage. Therefore, they just replaced the logic board for me. I have not get back my computer yet, once I get back the machine, I will test and feedback here.

I ’m in China, I have the same problem, but unfortunately, the fault occurred during the epidemic. At this time, the customer service did not provide an effective solution, which also exceeded the time limit for return and exchange. I think it is caused by Apple ’s design defects. If it ’s a big problem, maybe Apple should recall

Feedback here: I got my MacBook Pro back for 2 days, the Apple changed the entire logic board and the Touch ID module. Everything works fine now.

Hardware: MacBook Pro (16-inch, 2019) with AMD 5500M

Guy from Genius Bar recommended me not recover the data from Time Machine because some "bad settings" might lead to this problem, but I recovered all the files and nothing bad happened. So I suppose this is just a hardware issue, any reset might not help.

Maybe apple should check the design of logic board, because this seems not to be a individual problem. I know 3 or 4 guys in China having the same problem.

Hello,

same issue with one of my users. Seems to happen when device is awakened from sleep, must be restarted, problem persists. Funny thing is I also have a 16 with no issues, BUT I have the top end video card, and user has the standard version-what version video card have you?

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.

oneeyedboxer wrote:

I noticed every time there is an update release this thread get reopen. My recommendation to others is not to update till Apple addresses us all in this forum .

Apple is not here. This forum is regular users helping other users. If you want Apple to assist you, then click on the "Contact Support" link at the top right of this page and open up a support ticket for your system.

Apple promises to repair or replace, at Apple's discretion, any parts found to be defective in materials or workmanship for the duration of the warranty period, or its extension by AppleCare PLUS.

They very seldom replace your entire computer. However, if they replace the mainboard during a repair, it also includes the Processor, RAM, and graphics chips as well as the boot drive. You then DO essentially have a new computer.

from the extensions listed, you appear to have added some additional AMDRadeon drivers (I have never seen these listed first, that is the position for non-Apple extensions).

loaded kexts:

@kext.AMDRadeonX6000 3.0.8

@kext.AMDRadeonServiceManager 3.0.8

>!AGraphicsDevicePolicy 5.1.16

You will need to remove those and reproduce the issue without them before contacting Apple at 1-800-APL-CARE or using the Contact Support link at the top of every forum page.

This app is good for spotting bad kexts and removing them:

https://objective-see.com/products/kextviewr.html

Currently spending my evening formatting my replacement mbp 2019 16" for what feels like well over 100 times since Novemeber 2019 with these machines. 5 months now without a fix or even a hint from Apple as to what is making this one of the most unstable macbooks ever.

philux wrote:

5 months now without a fix or even a hint from Apple as to what is making this one of the most unstable macbooks ever.

Just a friendly reminder: I hope you and all the others on this thread have contacted Apple directly since Apple is not here on these forums. Unless users contact Apple directly nothing will ever get resolved and Apple will not be aware of the underlying hardware issue.

If users have contacted Apple directly and visited an Apple Store or an Apple Authorized Service Provider without having the issue resolved after so long, then users should be checking their local consumer laws for possible methods to resolve the issue.

Yeah kextviewer is an easy way to see that those were apple kexts.

As someone that's had apple go through multiple mbp pro 2019 16" machines (requesting a format before), look at crash logs in a fresh install and determine something is wrong then issuing replacements, this situation is highly frustrating.

I think it would be best if owners of the mbp 2019 16" only commented. Nothing worse than buying a super expensive machine for it to freeze & restart. My latest replacement did that out the box with nothing installed and has continued to do so. I formatted again in preparation for my next call from apple but in reality phone support can't help and my next step will be to drop it off to the repair center again.

Like when I said 5 months without a fix apple have replaced my logicboard multiple times, and even issued me a full replacement. Stuck in a loop of no refund. I think the only correct thing I read in above statement was consumer protection laws, which in my country need to be backed by a court case. Last time I went to court was never so thanks for the advice and thanks apple.

I'm having the same problem. My computer reboots at least once a day. This is my 2nd 16 inch macbook pro. My first laptop was doing the same thing and then fully died where it could not be turned on. Took it to the apple store and they sent it in for repairs. A month and change later, I got a brand new laptop and now I'm having the same issues again:

MacBook Pro (16-inch, 2019)

2.4 GHz 8-Core Intel Core i9

64 GB 2667 MHz DDR4

Intel UHD Graphics 630 1536 MB

4 TB drive

Really disappointing for such a high end laptop.

I can't say for sure, but a clean install of 10.15.4 on my latest mbp 2019 16" seems to have done the trick...I've only been using it for a day though, lol.

When my replacement unit first arrived, it came with 10.15.3 preloaded with a freeze & restart without installing anything, then I installed 10.15.4 over the top. It was still freezing & restarting.

Then I formatted the macbook with command + R at boot, when in internet recovery I first went in to Disk Utility and erased the internal nvme by right clicking on each container and selecting "delete APFS container" for both partitions. Then I erased the disk to be sure. After that, I then installed 10.15.4 fresh.

Since doing that, I have been using the macbook heavily with most of my software installed but no crash.

It's a pain to have to constantly format for something that may have been fixed in 10.15.4 with previous 10.15.x versions of Catalina not running in a stable manner on the system, but give it a try. What amplifies the situation is apple's total lack of recognition on the issue, you are stuck proving to them it crashes and then their only recourse of action is to replace your system or logicboard.

This issue could be better addressed, especially since at this current point of time this is apple's 'best macbook' and users are left spending countless hours on the phone and driving to stores/repair centers for what may have been something addressed in 10.15.4 with a totally clean install.

Ok, Yesterday my mac was repaired. Motherboard was replaced. Today I had CRASH, when mac was sleeping, it looks like previous issue... oh my

in terminal:

log show --predicate 'eventMessage contains "Previous shutdown cause"' --last 24h

kernel: (AppleSMC) Previous shutdown cause: -20

Hello Everybody !

I have the same problem. I have a Macbook Pro 16", 2019 for just one week and start having problems.

The problem is the same you have all tell in this post.

I don't understand why apple haven't fixed it yet. I mean, this is a very high end laptop that is bought by demanding people that want the best in a equipment, customer service and technical service, and certainly apple is not delivering it...

I really hope this can be solve ASAP.