Macbook Pro 16 inch panic (PowerPlay Failed Resume)

I am facing the following panic every morning. The Macbook seems restarted itself every night and failed?


This panic happened from last week suddenly. I tried several ways but the issue is still there.


  1. unplug the external monitor connector after it went sleep.
  2. unplug every lines and make it naked after it went sleep. still saw the panic!!!!


Is anyone facing the same issue with me?


panic(cpu 0 caller 0xffffff7f94d4b97b): GPU Panic: mux-regs 5 3 7f 1f 0 0 severity 3 WS-ready 0 switch-state 0 IG FBs 0 EG FBs 2: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
0xffffff82027d3700 : 0xffffff8010d215cd 
0xffffff82027d3750 : 0xffffff8010e5a3c5 
0xffffff82027d3790 : 0xffffff8010e4bf7e 
0xffffff82027d37e0 : 0xffffff8010cc7a40 
0xffffff82027d3800 : 0xffffff8010d20c97 




MacBook Pro 16", macOS 10.15

Posted on May 5, 2020 3:05 PM

Reply
Question marked as Top-ranking reply

Posted on Jul 13, 2020 6:49 AM

I actually don't think it is strictly a software issue. Several people have said the problem was resolved by a logic board replacement. It may be a software issue in the sense of an incompatibility between the OS and some characteristic of the processor or other hardware, but from my investigation and other peoples' experience, hardware is almost certainly a factor.


The specs for my two 16" machines --one with the problem and one without--only differ in a couple of respects. The one without the issue is a 2.3 GHz 8 core i9 processor, 64 GB RAM and 2 TB SSD and the machine with the problem is 2.4 GHz, 8 core i9, 64 GB RAM and 4TB SSD.


Both have the same graphics card--Radeon Pro 5500M 8GB--and both are running macOS 10.15.5 (19F101). The only apparent differences between the two machines are the processor and the 4TB drives, and the fact that the problem machine was built a couple of months later. Everything else seems identical including Boot ROM and Kernel Version.


Whether or not a coincidence, the problematic machine has the same specs as snowdoniafan's. I do see another poster reported the problem with a 2.3 GHz, 16 GB model, but didn't say what size SSD. As I said, all things considered, including yosefitche's report that a logic board replacement cured the problem, leads me to believe hardware plays some role in this. We will see what happens when I get the new machine back from Apple.


Similar questions

35 replies

Jul 12, 2020 9:04 AM in response to snowdoniafan

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!


Jul 12, 2020 9:36 AM in response to dkim95120

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

Jun 1, 2020 10:07 AM in response to brenden dv

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

Jul 7, 2020 3:49 PM in response to yosefitche

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:

Jul 12, 2020 10:35 AM in response to Grant Bennet-Alder

Sincerely appreciate your attempts to suggest fixes and agree with your points. If they work for some that’s great. They do not work for many unfortunately (there are many similar threads on this and other forums). It should be the case that Apple respond in that way in terms of customer care for the users. It isn’t the case in this case however.


Regarding your point that the workarounds suggested should solve the GPU panics... , the point is that for a significant number of customers those “fixes” don’t work and Apple are now not offering a hardware resolution but are instead alluding to a potential software based fix coming at an undefined point in future. They do not file a bug report, and I have been on with second level senior support twice, both ended with no resolution regardless of how hard I pushed the case.


Couple that with the fact it appears the issue is Deeper and broader than that, and we have some unhappy customers, including me. This forum is another place to gather insight to the broader deeper issue.

Jul 25, 2020 4:12 AM in response to ddbullfrog

its the worst thing can happen to apple.

many will stop buying mac books. . i purchased 10 days ago 2400$. 16 inch macbook pro

and facing this weird auto restart after putting my mac to sleep mode terrible!!!!!!

i dont know already what to do i re-installed system again and nothing helped

when these apple guys, will wake up and come with solution to fix it urgent ????,

its a big scandal !!!!

i have used always apple mac books.

i am speechless how big apple cannot find fast solution ?

Jul 12, 2020 9:41 AM in response to dkim95120

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.

Jul 12, 2020 9:47 AM in response to kennybroh

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.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Macbook Pro 16 inch panic (PowerPlay Failed Resume)

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.