Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

16" MBP GPU Panics

Update:
It's been over a month since i had the 'bad magic' kernel panic & restart..

I do remember installing Blizzard's Starcraft(the free version) on it a day or two before it crashed. Blizzard's site says they dont support installing on a drive with FileValut turned on (mine does). I wonder if that might have caused some "bad voodoo".

However, I did do a clean install of 10.15.4 (boot into recovery, erase HD, install latest OS), last week, and its been fine since then. Hope it stays like that. *knock-on-wood*

Cheers

PS>>I suspect(and i have no proof of this), this could be an issue with APFS.
 
Ugh.
Can't say I enjoyed reading this thread – my 2012 rMBP's keyboard has started acting up again out of the blue two days ago (no joke: keyboard went from working perfectly OK to no 8, i, k, "," and arrow keys while I was sitting outside discussing selling the rMBP to a neighbor!), and now I'm on the fence again reading about the 16".

This episode strongly reminds me of a few years ago, when I had quite persistent system freezes and crashes, almost certainly due to switching between the rMBPs dGPU and the iGPU. These went away after some OSX update.

What I do wonder is: how widespread these crashes are on the 16". Reading around here I have the impression most folks are very happy with their 16". Of course this doesn't help those that have these kind of errors, which does make me hesitant to pull the trigger, knowing that a mythical Apple CPU might be not too far away in the future.
 
Add me to the list (2.4 GHz, 32GB, 1TB SSD, bought in Dec 2019).

panic(cpu 6 caller 0xffffff7f97ff497b): 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 15:0 power-retry 0:0 connect-change 0 : PowerPlay Failed Resume.

I'm also a person who suffered thru the misery of having a 15.4 with the bad keyboard that I paid $3500 for. I took a bath on that computer, selling it for a $1500 loss so I could buy a new 16" when the came out. And now, I'm back in the same position as before: I have a non-functional machine and my only option is to send it back to get another machine with the exact same fatal design flaw. And further, calling support just results in them making you jump through hoops they know aren't going to work while they gaslight you by telling you they are unaware of any common problem.

I've been upgrading from Mac to Mac since 2001. And for the first time ever, I spent a few hours investigating Windows Laptops. Unfortunately I haven't found anything that's an obvious candidate, but you sure can get a lot more computer for a lot less money--and since I wouldn't have to run a second operating system in a VM, I would need much less machine.

If Apple can lose a customer with my level of loyalty and clearly not even care, it's time to unload my Apple stock.
 
  • Like
Reactions: overlof and SantaCruzDad
This has happened to my MBP16 several times over the last few weeks but with increasing frequency. Until today I only ever saw the problem when returning to the MBP in the morning to start work. Overnight (while sleeping) it had restarted. So I had to reset all my apps / windows before getting to work. A right pain in the ***. Today it happened when I went to make a call. MBP went to sleep. Came back, mouse pointer moving around OK but no apps responding. Main menu not responding. Nothing. A minute later the mouse pointer disappeared followed by a considerable "whoosh" noise from the fan and the MBP restarted. Error report on re-start duly sent to Apple. For the 4th time this week.

Does this sounds like what others are experiencing? Reading the thread I think so. Also worth noting that I never experienced this problem before I connected my MBP16 to a new Philips 346B ultra widescreen monitor that is USB-C, so I power the MBP via the monitor using USB-C. I also read on this thread that some think connecting via USB-C monitors / docks may be causing the issue.

My MBP16 - 2.3GHz i9 ; 32GB RAM ; 1TB SSD ; AMD Radeon Pro 5500M 4GB.
 
So today I had my first "Powerplay failed to resume" error. Out of curiosity I ran the intel test earlier today on GB5 and did not trigger the cpu panic. So I think we can rule that out as a means of reliably triggering the test or at least it did not in my case. Besides a couple bad magic crashes which occurred when plugging in peripherals, I haven't had any GPU related issues with this computer I bought in December. Im really hoping this is a driver issue or something related to 10.15.4 since it seems like its a different issue from the one OP discussed. Piece of **** update and they will never fix the audio issues either. When it finally comes time to buy a new computer Im' going Windows.
 
Last edited:
dang it - same problem here. Just ran GB metal on IGPu. MacBook restarted.

panic(cpu 0 caller 0xffffff7f983594c2): "Graphics firmware encountered an exception (eip: 0xddf5, fault #: 0xd)\n"@skl/sched3/IGGuC.cpp:865
Backtrace (CPU 0), Frame : Return Address
0xffffff9241c3bb70 : 0xffffff8013b215cd
0xffffff9241c3bbc0 : 0xffffff8013c5a3c5
0xffffff9241c3bc00 : 0xffffff8013c4bf7e
0xffffff9241c3bc50 : 0xffffff8013ac7a40
0xffffff9241c3bc70 : 0xffffff8013b20c97
0xffffff9241c3bd70 : 0xffffff8013b21087
0xffffff9241c3bdc0 : 0xffffff80142c2c7c
0xffffff9241c3be30 : 0xffffff7f983594c2
0xffffff9241c3be80 : 0xffffff7f982cfcc4
0xffffff9241c3bee0 : 0xffffff801422eb6d
0xffffff9241c3bf30 : 0xffffff801422d43e
0xffffff9241c3bf70 : 0xffffff801422ca36
0xffffff9241c3bfa0 : 0xffffff8013ac713e
Kernel Extensions in backtrac


Guess it's time to return it.
Mine was built on:
Production year : 2019
Production week : 46 (November)
Model introduced: 2019

Quanta


In everyday use I had zero problems so far I love this machine.


Edit: with fans at 100% it went ok with GB 5 test
Edit2: test with default fans also went well. I've run it now multiple times, no probs at all - I mean it slows down to the point where it is not usable but it does recover after a 45sec or so.
5500m 4GB worka ok on both GB 4 and 5. Not sure what to do next. whether I should return it or keep it...dang it 😖

MacBook Pro (16-inch Late 2019) - Geekbench

Benchmark results for a MacBook Pro (16-inch Late 2019) with an Intel Core i9-9880H processor.
browser.geekbench.com
Face detection - 0pts.

Does any of you knows if this is a bug with OS/GB or a hardware issue? Error suggest a bug in the igpu FW
 
Last edited:
To add ot my above post, I've done metal test on IGPU on GB4. no problems, slowdown etc. All good.
I think it's a problem with software

MacBookPro16,1 - Geekbench Browser

Benchmark results for a MacBookPro16,1 with an Intel Core i9-9880H processor.
browser.geekbench.com
Zrzut ekranu 2020-04-22 o 15.13.57.png
 
Add to me to the list as well: GPU panic, PowerPlay failed to initialize and PowerPlay failed to resume. Base model 16 inch with 5300M. It was working fine for few weeks but now experiencing crashes and boot loops when:
-wake from sleep
-startup
-restart
Additionally, it will crash when trying to shutdown on battery (via clicking on the apple logo at the top left corner and choosing shutdown). Pop up window with countdown to confirm if want to proceed shutdown will appear, don't select either cancel or shutdown, wait a few seconds and it will crash and restart. Not sure if related or bug from MacOS 10.15.4. I get the same GPU panic log when logged back in.

Tried all the resets, erasing my drive and reinstalling MacOS. On the phone with Apple Support for 2 hours, and sent in my logs and video of the boot loop.
 
mychi said:
Add to me to the list as well: GPU panic, PowerPlay failed to initialize and PowerPlay failed to resume. Base model 16 inch with 5300M. It was working fine for few weeks but now experiencing crashes and boot loops when:
-wake from sleep
-startup
-restart
Additionally, it will crash when trying to shutdown on battery (via clicking on the apple logo at the top left corner and choosing shutdown). Pop up window with countdown to confirm if want to proceed shutdown will appear, don't select either cancel or shutdown, wait a few seconds and it will crash and restart. Not sure if related or bug from MacOS 10.15.4. I get the same GPU panic log when logged back in.

Tried all the resets, erasing my drive and reinstalling MacOS. On the phone with Apple Support for 2 hours, and sent in my logs and video of the boot loop.
Click to expand...
I don’t thinks the power play panic is the same GPU panic. The GPU failure which is fixed by replacing the logic board has a totally different panic log. I have a friend who got this after updating to 10.15.4 on a pre t2 MacBook Pro. I also had sleep wake issues and this kernel panic after 10.15.4. It looks like Apple messed up their power management in an update. Turning off power nap fixed the crashing
 
Tried turning off power nap and it is still crashing.

Update: it finally happened, the mbp didn't make it to the login screen despite 1 hour + of boot loop. Only managed to get in via safe mode.
 
mychi said:
Tried turning off power nap and it is still crashing.

Update: it finally happened, the mbp didn't make it to the login screen despite 1 hour + of boot loop. Only managed to get in via safe mode.
Click to expand...
I hope this doesn’t happen to mine then
 
mychi said:
Tried turning off power nap and it is still crashing.

Update: it finally happened, the mbp didn't make it to the login screen despite 1 hour + of boot loop. Only managed to get in via safe mode.
Click to expand...

I hate to tell you but, yours is experiencing the hardware issue.

Call Apple and if they put you through the rigamarole (Reinstall OS, blah blah), just ask for a repair box. Be sure to tell them you want a LB manufactured March or later. If they give you a tough time, email Tara Bunch and tell her you want it fixed... thats teh executive team.

Good luck.
 
Can one still downgrade the osx to last year’s, from Catalina? Wondering if that would cure all these issues and maybe it might be the OS X itself
 
Id like to note this is a common issue with AMD gpus for awhile in the desktop area. AMD drivers need to catchup.
 
cpnotebook80 said:
Can one still downgrade the osx to last year’s, from Catalina? Wondering if that would cure all these issues and maybe it might be the OS X itself
Click to expand...

I don't think that's possible on the 2019 16" MacBook Pro ?
[automerge]1587978458[/automerge]
One thing I'm noticing is that I can now tell when a panic is imminent - cursor movement starts to become somewhat jerky and the fans start to increase - that means time to save whatever I'm working on and reboot before I get an actual panic. (Just thought that might be helpful for anyone else who is suffering with this problem.)
 
Last edited:
I had my first Kernel Panic this morning. I left my 16'' on last night and just shut the lid as I wanted to see how much battery it uses at night in stand by mode. I noticed my 2015 15'' uses 0% and retains a full 100% battery charge over night. I opened the 16'' and noticed it had restarted. Is there a fix for this? Both batteries are 'new' and have about 12 cycles each.

522AF46A-9FC9-47DD-9FF5-1A806096BD86.png
 
Hey guys,

I have exactly the same issue with my 16" MBP and have been putting off contacting Apple due to not having a machine for ages.

GOOD NEWS - I contacted Apple today expecting to send my machine in and they said I need to continue with the workarounds for now. I was like 'WHAT?, I want my machine fixed!" However, it seems this is a software issue and they have stopped setting up repairs because a fix is on the way. This is what she said:

Yes be on the look out for a new update. The engineers stated “Thanks to everyone who sent the data we have identified a fix for the next software update.”

Hopefully this fix is imminent and should relieve some of your worries about having to send in your machine for repair. Hope this helps 👍
 
  • Like
Reactions: SantaCruzDad
Another panic for me, 16" MacBook Pro 2019, 10.15.4. Happened as soon as I opened the lid this morning. I sent the report to Apple.

panic(cpu 4 caller 0xffffff801e616487): "AppleIntelFramebuffer::setPowerState(0xffffff86b37d9000 : 0xffffff7fa1ba8d88, 1 -> 0) timed out after 45984 ms"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.101.6/iokit/Kernel/IOServicePM.cpp:5296
Backtrace (CPU 4), Frame : Return Address
0xffffffa79896bb40 : 0xffffff801df215cd
0xffffffa79896bb90 : 0xffffff801e05a3c5
0xffffffa79896bbd0 : 0xffffff801e04bf7e
0xffffffa79896bc20 : 0xffffff801dec7a40
0xffffffa79896bc40 : 0xffffff801df20c97
0xffffffa79896bd40 : 0xffffff801df21087
0xffffffa79896bd90 : 0xffffff801e6c2c7c
0xffffffa79896be00 : 0xffffff801e616487
0xffffffa79896be50 : 0xffffff801e615d69
0xffffffa79896be60 : 0xffffff801e62d2fe
0xffffffa79896bea0 : 0xffffff801e614b18
0xffffffa79896bec0 : 0xffffff801df63545
0xffffffa79896bf40 : 0xffffff801df63071
0xffffffa79896bfa0 : 0xffffff801dec713e

BSD process name corresponding to current thread: kernel_task
Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
19E287

Kernel version:
Darwin Kernel Version 19.4.0: Wed Mar 4 22:28:40 PST 2020; root:xnu-6153.101.6~15/RELEASE_X86_64
Kernel UUID: AB0AA7EE-3D03-3C21-91AD-5719D79D7AF6
Kernel slide: 0x000000001dc00000
Kernel text base: 0xffffff801de00000
__HIB text base: 0xffffff801dd00000
System model name: MacBookPro16,1 (Mac-E1008331FDC96864)
System shutdown begun: NO
 
I've just ordered a 16" 2.4 i9 32GB 2TB 8GB GPU from the Apple Refurb store. Hoping whatever the issue is has been fixed? Don't really want to have to return it as it's a £500+ saving buying it refurb :(
 
Chrjy said:
Hopefully this fix is imminent and should relieve some of your worries about having to send in your machine for repair. Hope this helps 👍
Click to expand...
Not to pour cold water on your hopes, but they basically said the same thing for the T2 bridge crashes, and that took years. Hopefully this will be an easier fix for you guys
 
  • Like
Reactions: g75d3 and Chrjy
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back