Macbook Pro 16 inch panic (PowerPlay Failed Resume)

I am having the exact same issue with the exact same problem report.

This is clearly a bug in MacOS 10.15.4. I was just using the machine, closed the lid, came downstairs and when I opened the lid the system rebooted and displayed this report. Machine was 100% charged.

C'mon Apple.... this is really a problem.

Frustratingly, a lot of 2019 16 inch MacBook Pro users are having similar problems, myself included. It has been an ongoing issue for months that Apple has failed to resolve. If you adjust your energy preferences as recommended in the below thread, you will probably see an improvement.

https://discussions.apple.com/thread/251244835

Hey there ddbullfrog,

Thanks for reaching out to Apple Support Communities. I understand your Mac is restarting unexpectedly. I’ll be happy to help with this.

If your Mac is restarting because of a problem, start by checking your software:

• ‘Install all available software updates.
• If your Mac suspects that a particular app caused the restart, it might ask whether you would like to move the app to the Trash. Click Move to Trash, then contact the software developer to see if a software update is available.
• Use safe mode to try to isolate the cause of the issue.
• Reinstall macOS. If the issue continues after reinstalling macOS, check your hardware.’

If the restarting continues and those steps have no impact on this, check your hardware:

• How to use Apple Diagnostics on your Mac

Take a look at this link for more details and let me know if this helps:

• If your Mac restarted because of a problem

Regards.

I bought my machine April (2020). Seemed to work fine at first, but started crashing more and more after a few weeks. I can't recall if there was any OS update at the time. Went to Apple Genius last month (June) and was told it was a known problem and to wait for software update. He even gave me the idea it was well noted online so I could've found out myself, which is true in the sense that it was noted by end-users, consumers. Though I found no announcements from Apple itself. Then I couldn't stand it anymore so I called Apple support again (July) and they made an appointment for me to bring my machine in for repair, telling me there were no known problems. Why Apple won't acknowledge the problem is certainly scandalous. Let's find out!

Seems fine after a couple days, after logic board & touch ID pad replacement. I ended up buying Mac Air as well for backup while machine was in repair, 2 weeks. I can't be without a computer. We'll see if this holds up.

Hi Brenden,

I followed your instructions, and eventually erased my disk and reinstalled Mac OS using macOS Recovery. And I'm still getting these kernel panics on wake from sleep.

panic(cpu 6 caller 0xffffff7f91868983): GPU Panic: mux-regs 5 3 7f 1f 0 0 severity 3 WS-ready 0 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.

I contacted Apple Support, and they told me to bring it in for repair, which is a huge pain now since the stores are closed. Was hoping for a solution I could try at home.

(2019 16-inch MacBook Pro, base model)

Thanks,

YK

It could be a faulty logic board.

I ended up bringing the machine in for repair at an Authorized Apple repair specialist in NYC, and they replaced the logic board and Touch ID button, and I haven't had the issue since. It's been about two weeks.

I am having the same exact problem. Happens ALL THE TIME. Any time I step away from the computer when I come back it has faulted and has to be re-started. Stack Trace here FYI.

panic(cpu 0 caller 0xffffff7f928bd983): GPU Panic: mux-regs 5 3 7f 1f 0 0 severity 3 WS-ready 0 switch-state 0 IG FBs 0 EG FBs 1:0 power-state 0 3D idle 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

0xffffff83cbd7b700 : 0xffffff800e91f5cd 

0xffffff83cbd7b750 : 0xffffff800ea58b05 

0xffffff83cbd7b790 : 0xffffff800ea4a68e 

0xffffff83cbd7b7e0 : 0xffffff800e8c5a40 

0xffffff83cbd7b800 : 0xffffff800e91ec97 

0xffffff83cbd7b900 : 0xffffff800e91f087 

0xffffff83cbd7b950 : 0xffffff800f0c27cc 

0xffffff83cbd7b9c0 : 0xffffff7f928bd983 

0xffffff83cbd7ba20 : 0xffffff7f92c7137b 

0xffffff83cbd7bca0 : 0xffffff7f92c3d4d4 

0xffffff83cbd7bcd0 : 0xffffff7f92c70cf8 

0xffffff83cbd7bd00 : 0xffffff7f92c58b3f 

0xffffff83cbd7bd20 : 0xffffff7f92c58acf 

0xffffff83cbd7bd40 : 0xffffff7f92c58921 

0xffffff83cbd7bd70 : 0xffffff7f925a3faa 

0xffffff83cbd7be10 : 0xffffff7f925a3d08 

0xffffff83cbd7be40 : 0xffffff7f925aaaeb 

0xffffff83cbd7bee0 : 0xffffff800f02e60d 

0xffffff83cbd7bf30 : 0xffffff800f02cede 

0xffffff83cbd7bf70 : 0xffffff800f02c4d6 

0xffffff83cbd7bfa0 : 0xffffff800e8c513e 

      Kernel Extensions in backtrace:

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

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

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

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

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

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

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

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

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

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

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

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

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

BSD process name corresponding to current thread: kernel_task

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

Mac OS version:

19F101

Kernel version:

Darwin Kernel Version 19.5.0: Tue May 26 20:41:44 PDT 2020; root:xnu-6153.121.2~2/RELEASE_X86_64

Kernel UUID: 54F1A78D-6F41-32BD-BFED-4381F9F6E2EF

Kernel slide:     0x000000000e600000

Kernel text base: 0xffffff800e800000

__HIB  text base: 0xffffff800e700000

System model name: MacBookPro16,1 (Mac-E1008331FDC96864)

System shutdown begun: NO

System uptime in nanoseconds: 13323523138306

last loaded kext at 13199478026142: >!UAudio 323.1 (addr 0xffffff7f95cbe000, size 434176)

last unloaded kext at 257461463935: >usb.!UHostPacketFilter 1.0 (addr 0xffffff7f911e5000, size 24576)

loaded kexts:

I went to Genius Bar last month (about June 16) and was told that this was a known problem and to wait for an update. Meantime, turn off graphics switching in Energy Saver settings. So why no acknowledgement from Apple ? Or timeline for fix ? I've seen threads on this that go back to December 2019. This is a $3k+ machine. A real scandal !

Disabling graphics switching has not resolved the problem for me. I'm amazed this isn't a more well publicised issue as many people seem to be having the problem.

As above, some people report having their logic board replaced, and some say it fixed it while some say it does not (check other forums for that info). Some report that 10.15.6 Beta 4 Fixes it, but I have tried that and it did not fix it for me.

I am still having the same problems on the latest Catalina 10.15.5 and have tried fully formatted re-installs, SMC & PRAM resets etc and every combo of power settings all to no effect. I have also tried Windows under bootcamp and still get issues.

The on board hardware diagnostics do not report a problem. Apple support when I contacted them suggested there is a software fix in the pipeline but can not give a date and only give taking it in to a Genius Bar as an option (difficult during Covid).

FYI, things got so bad that my machine will now only boot in safe mode. I contacted Apple Support and am sending it back to them for repair--the local stores are closed and the local independent authorized repair facility said that's all they would do anyway.

Coincidentally, I originally bought another 16" and decided I wanted to upgrade the drive and processor. Apple had me order the new machine and I was then going to send the original machine back for a refund. Fortunately, I hadn't done that when the problems started on the new one and when they told me to send it in for repair Apple extended my return date. Interesting to note this machine does NOT have the problem....

Interesting, that’s exactly when I bought mine. Although, seems like there are others that have had the issue for longer.

In fact, when I bought I did research online for any problems with the MacBook Pro 16 (which by then had been out for a few months) and unfortunately did not find these few threads.

Very odd that there is such an inconsistent and poor position from Apple on this.

Very interesting point of reference that you have two 16’s (with slightly different specs), one with the issue and the other without.

I doubt that it’s a spec related issue as I’ve seen many messages from folk with base spec machines also having issues.

I have also found that if it panics on wake it then enters a failed boot cycle until you boot into safe mode. After that it’s then a 50/50 chance for me whether it will then successfully boot into normal mode.

For reference, mine is the 2.4 ghz “HK” processor variant, 5500M 8GB GPU model. I doubt that memory and storage could be the issue but for the record it is 64GB and 4TB.

The current work-around proffered by Apple support is to be sure you are running 10.15.5 fully update to build 19f101,

then disable

System preferences > Energy saver ...

Power Nap ...

in both battery and Power adapter settings

if that does not resolve the issues, you have a unique problem, and should use the "Contact Support" link to get additional guidance or arrange for service, as appropriate.

.

Reading these threads in detail as I have, there are a large number of customers who have tried the basic* “disable power nap”, “workaround”, and found it to not resolve the issue.

I and others have tried this and all other suggestions eg disabling graphics switching, enabling / disabling prevent wake.

On call with Apple support I ran through this as others have and they do at least acknowledge it as an issue (albeit, claiming it as a software issue, of which I am not convinced).

I do not think it is accurate or fair to describe this as a unique problem. There are many who have the same issue and have invested significant hours trying the same suggestions in good faith.

*As you will know from my other thread I have tried this and all other posited workarounds. In fact, I’ve also tried pmset config to disable hibernation altogether, increase those specific timeouts, hardwire dGPU or iGPU only and no resolution. And to recap, this is the case from a clean install, where onboard hardware diagnostics does not fail.