MBP 16" 2019 CRASHES WHILE SLEEPING

I did the PRAM and SMC reset with no luck. I did the disk utility repair. I am not going to erase the hard drive and start over.

It does appear that it happens when connect to an external monitor. Obviously something changed with one of the last two updates. I did not have any issues until about 3 or 4 weeks ago and have not added any software.

Apple needs to send an update out to fix this.

I am in the same situation with my 16 inch MBP. I plug in to 34inch display via HDMI dongle and close lid with bluetooth apple keyboard/mouse and speaker. The shouldn't be an issue, but is, in that I have to reboot every time I walk away for more than <x time for computer to go to sleep> because it crashed -- life long Apple user and very disappointed.

I know! I've been waiting for a fix myself. I have talked to apple support on the phone, in store at Genius bar, no one can help. I don't want to erase my entire computer. XCODE is buggy enough to have to reinstall all the things it requires will eat up a day at least.

Apple, we need a fix ASAP!

Yes, my MBP 16 is still crashing, whatever solution I try.

And I will NOT erase everything another time (my MBP has 2 weeks of life)... too much work to do...

Apple has to solve the situation directly...

Brand new Mac Book 16 with the latest Catalina (MacOS X 10.15.5 (19F101)) is now crashing every single time it goes into sleep mode. The kernel panic seems to be in the same place every time. I hope there's a software update to fix this.

If i connect this issue to the kernel_task process that keeps on stealing over 1000% of my cpu cycles without a given reason (even after boot, with no app running and no kext drivers...), i can only say - with sorrow - that this premium hardware (and price) deserves more, a lot more... Hope these issues will be solved in days, not months!

The crash appears to be in the graphics system. I have the lid closed and it is connected to an external monitor. This is happening every single time the computer sleeps. I'm getting concerned about file corruption.

panic(cpu 2 caller 0xffffff800229167c): Sleep transition timed out after 180 seconds while calling power state change callbacks. Suspected bundle: com.apple.iokit.IOGraphicsFamily. Thread 0x2d21.

Backtracing specified thread

Backtrace (CPU 2), Frame : Return Address

0xffffff81fd1f3900 : 0xffffff8001c458f8 

0xffffff92268d3bc0 : 0xffffff8001b413f1 

0xffffff92268d3c30 : 0xffffff8001b3fc2f 

0xffffff92268d3c80 : 0xffffff8001c429f9 

0xffffff92268d3cc0 : 0xffffff8001c4225b 

0xffffff92268d3cf0 : 0xffffff7f857b2ced 

0xffffff92268d3d20 : 0xffffff7f857cbf93 

0xffffff92268d3d30 : 0xffffff7f857b5cb9 

0xffffff92268d3dc0 : 0xffffff7f857c1edc 

0xffffff92268d3e00 : 0xffffff8002214d8a 

0xffffff92268d3ea0 : 0xffffff80022146b4 

0xffffff92268d3ec0 : 0xffffff8001b61565 

0xffffff92268d3f40 : 0xffffff8001b61091 

0xffffff92268d3fa0 : 0xffffff8001ac513e 

      Kernel Extensions in backtrace:

         com.apple.iokit.IOGraphicsFamily(576.1)[B1C0006F-E1F5-37D9-9548-5F918E92B422]@0xffffff7f857aa000->0xffffff7f857fafff

            dependency: com.apple.iokit.IOPCIFamily(2.9)[BE052F4D-9B80-3FCD-B36D-BACB7DEE0DF2]@0xffffff7f82512000

BSD process name corresponding to current thread: kernel_task

Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev

Did all the recent updates. Still crashes. No external monitors connected. Now it restarts, I load a program, then it freezes and crashes and restarts again. It’s been happening since first week of may

interesting discussions - I have the crashes with an external BenQ SW271 using USB-C cable. I I knew it would work with A2119 it would be some kind of fix, still I hope this will be solved with an update.

Btw, is there any evidence that apple follows this thread and is trying to fix these issues?

Are you using a TB3 hub? The reason I'm asking is I'm actually using my old OWC TB2 hub via a TB3->TB2 adapter.

I'm wondering if that has anything to do with it.

I agree about 10.15.5. Very disappointing.

This is ridiculous. I'm having the same issue - at least with external monitor with a dongle. And the fans are loud all the time - I really thought that a new Macbook Pro would perform better than this joke of a machine.

I can sure it s not caused by USB-C, I tried without any peripheral hub ( only using batteries, turn off bluetooth ). The crash happen in 2 cases:

1. Using Sleep function
2. Fold the screen

100% crash.

Terrrible

I bring it to local apple services, they say it caused by batteries was damaged, they suggest to change batteries with 500 USD

Terrrible Price!!!!

My lap is 2017 macbook Pro

Have any one have same problems ?

I'm hopeful that the issue is resolved, and while I know software/hardware is hard and never perfect, there are two takeaways FOR ME; (1) the fact that this significant an issue passed quality testing on a $3,000+ laptop that is Apple's flagship notebook, considered a 'premium' product, and (2) the fact that it took nearly 4 months to get a fix.

If you market yourself as a 'premium' brand and charge 'premium' prices, then you need to deliver a 'premium' product AND 'premium' support. When inevitable mistakes are made, they need to be addressed immediately.

A BASE 16 MBP is $3k (easily can add thousands more in upgrades); add in a second Apple monitor $5k (not to mention the necessary appendages (aka adapters) required to connect anything) and you're looking at a BASE $8k system that would crash constantly for 4 months until a fix was issued.

FOR ME, that is unacceptable.

I agree with this completely. It’s frustrating enough that Apple does not offer a native docking solution given that it is such a common thing to do, but to have a critical issue that renders the computer almost unusable at a desk workstation for PRO users and then to leave it unaddressed through several patches is very frustrating.

NOPE APPLE DIDN'T ****, for you fix things you need get your head out of your ***. doesn't look like apple just care about the bottom line their pocket not customers. SAD WTF APPLE GET YOUR HEAD out of your ***.