MBP 16" 2019 CRASHES WHILE SLEEPING

After a fresh install, my laptop won't go to sleep mode anymore, you can even hear the fans spinning when it is "sleeping" and running hot also.

I had to disable Power Nap as a work around so it's better than nothing...If I enable it again, it crashes so bad.

I heard somewhere that Apple is aware of this issue, so, we will see.

I solved the issue by replacing the macbook. Amazon hopefully provided another machine.

First one was manufactured mid october 2019, actual one that I'm using mid december 2019 and it's working flawlessly.

Same identical specs, same backup, same everything.

I'm curious about when the panicking macbook pros 16 are produced!

I took mine into the Apple Store last week. They reinstalled the OS and some firmware and asked me to monitor the situation. I thought that was useless as the same software and same hardware would just produce the same results. I asked them to forward it on to the next level and they did. They are still diagnosing the issue 5 days later. Someone previously in the thread said they had to replace his T2 chip. Will let you know what they do to mine.

I would recommend sending your laptop in for service and don’t let them get away with reinstalling the OS. Same software and same hardware === Same problem. There is likely a hardware issue in a batch as this seems to affect only a subset of 16” MacBook Pros.

UPDATE: I reinstalled the OS after a discussion with e rep from Apple. Tw days later, low and behold...frozen! It crashed again.

I'll follow up with them to see what is next. it, for me anyway, is now obviously an issue with the computer and not the os. My 2015 MBP & 2012 MBP w/SSD are stable. They wake & sleep as they are supposed to. This one does not. It makes no sense that it is software.

#angry

Power nap seemed to be the issue. Got off the phone to AppleCare team last night and they confirmed to me that it is a known issue specific to 16 inch MBP’s and engineers are working on a fix

reinstalling is didn’t work for me until I completely erased HD first

Yup, I used to have one of those. In my case, I got a USB-C to HDMI cable (uni brand) from amazon. I do think some cables are not fully compatible with this machine.

I have not had the problem since I went to 10.15.6.

I have had no issues since the 10.15.6 upgrade, but I also do not have the power nap button checked for batter or plugged in and I am not going to since all is well right now.

Does the machine still wake from sleep ok? I did SMC + NVRAM reset, this fixed the issue for approx 24 hours before my crashes returned.

I have not tried the fresh install yet difficult to do as this is my work machine just need to find the time.

I tried resetting the SMC. It seemed to work for a few hours and then went back to it's troubled state. I'm back to keeping the lid open as I'm using an external screen and all is well. Just a fix, not a solution

Friend of mine and I, both have a MBP 16 with Catalina 10.15.5.

Friend's MBP 16 does not have any issue, he has no external monitor, just the original external power supply.

My MBP ist mostly connected to the LG Ultrafine 5K external monitor (sold by Apple) and is powered by Thunderbolt from the monitor - no issue. When I connect the MBP in another office to the original external powersupply and to an Eizo EV2750 it crashes every time the MBP goes to sleep...

???

I am having this problem, too. Brand new MBP 16", fresh install, deliberately didn't migrate from my 7 year old 15" MBP, but this is happening all the time...

But it does spend most of its time connected to external monitors. I'll start leaving it undocked and see it it happens again.

Edit: This answer in another thread says turning off power nap will prevent the crash. That's less than optimal but has anyone else tried it?

I have power nap disabled, and still got this issue

panic(cpu 0 caller 0xffffff7f9b3d5983): GPU Panic: mux-regs 4 3 3f 1f 0 0 severity 3 WS-ready 0 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 : [3:0:0] GPU Not Found! PCI Config Access Fails!!!

Backtrace (CPU 0), Frame : Return Address

0xffffff8208fd36e0 : 0xffffff801771f5cd 

0xffffff8208fd3730 : 0xffffff8017858b05 

0xffffff8208fd3770 : 0xffffff801784a68e 

0xffffff8208fd37c0 : 0xffffff80176c5a40 

0xffffff8208fd37e0 : 0xffffff801771ec97 

0xffffff8208fd38e0 : 0xffffff801771f087 

0xffffff8208fd3930 : 0xffffff8017ec27cc 

0xffffff8208fd39a0 : 0xffffff7f9b3d5983 

0xffffff8208fd3a00 : 0xffffff7f9bae437b 

0xffffff8208fd3c80 : 0xffffff7f9baac1f5 

0xffffff8208fd3cd0 : 0xffffff7f9bae3c8e 

0xffffff8208fd3d00 : 0xffffff7f9bacbb3f 

0xffffff8208fd3d20 : 0xffffff7f9bacbacf 

0xffffff8208fd3d40 : 0xffffff7f9bacb921 

0xffffff8208fd3d70 : 0xffffff7f9b355faa 

0xffffff8208fd3e10 : 0xffffff7f9b355d08 

0xffffff8208fd3e40 : 0xffffff7f9b35caeb 

0xffffff8208fd3ee0 : 0xffffff8017e2e60d 

0xffffff8208fd3f30 : 0xffffff8017e2cede 

0xffffff8208fd3f70 : 0xffffff8017e2c4d6 

0xffffff8208fd3fa0 : 0xffffff80176c513e 

   Kernel Extensions in backtrace:

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

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

     com.apple.driver.AppleMuxControl2(5.2.4)[39BDDE23-D669-3AF6-ADA4-202A2A1F28A3]@0xffffff7f9b3c6000->0xffffff7f9b3dafff

      dependency: com.apple.driver.AppleGraphicsControl(5.2.4)[9BD821A9-6DDD-37FF-A5E1-EFB8A77A0AD3]@0xffffff7f9b3b9000

      dependency: com.apple.iokit.IOACPIFamily(1.4)[0A7D7382-66FE-391B-9F93-97A996256C25]@0xffffff7f98109000

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

      dependency: com.apple.iokit.IOGraphicsFamily(576.1)[B1C0006F-E1F5-37D9-9548-5F918E92B422]@0xffffff7f9b34b000

      dependency: com.apple.AppleGraphicsDeviceControl(5.2.4)[CD6E2942-2A23-3CE8-9BCA-D5A772667EB8]@0xffffff7f9b3bc000

     com.apple.kext.AMDRadeonX6000Framebuffer(3.0.9)[E9880F7F-25D3-340E-9F59-0FB58854EF20]@0xffffff7f9baa3000->0xffffff7f9bed4fff

      dependency: com.apple.iokit.IOACPIFamily(1.4)[0A7D7382-66FE-391B-9F93-97A996256C25]@0xffffff7f98109000

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

      dependency: com.apple.iokit.IOGraphicsFamily(576.1)[B1C0006F-E1F5-37D9-9548-5F918E92B422]@0xffffff7f9b34b000

      dependency: com.apple.AppleGraphicsDeviceControl(5.2.4)[CD6E2942-2A23-3CE8-9BCA-D5A772667EB8]@0xffffff7f9b3bc000

Same problem as everybody else In this thread, any we have 3-4 MacBook Pro’s in my firm with this issue. All been handed in for repair - each diagnosed differently and each having hardware replacement. But none fixed....super frustrating and a total waste of time and money.

Found a small workaround, which seems a bit ironic, because it relies on Microsoft Word. If you open a Word document and write anything - like please don’t crash - and then don’t save the document, Word simply prevents the crash, because it won’t close until the user decides whether to save the doc or not...

Its funny because it’s true.....