16" MBP GPU Panics

[donawalt]

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

I think this is software that affects the MacBook Pro, as for most (all?) this started after 10.15.4 - it did for me. This MacBook Pro has been rock solid since Nov then this started within a day after the original update to 10.15.4.

 

[MrGimper]

I think this is software that affects the MacBook Pro, as for most (all?) this started after 10.15.4 - it did for me. This MacBook Pro has been rock solid since Nov then this started within a day after the original update to 10.15.4.

That's reassuring, thanks

 

[MrGunnyPT]

I think this is software that affects the MacBook Pro, as for most (all?) this started after 10.15.4 - it did for me. This MacBook Pro has been rock solid since Nov then this started within a day after the original update to 10.15.4.

Guys, I fixed my issue my removing all the LEGACY APPS I had pre 2016.

I just run those on my Parallels VM and everything seems to be working fine.. One of those apps that was giving me panic attacks was Photoshop CS6 for some reason.

 

[SantaCruzDad]

I think this is software that affects the MacBook Pro, as for most (all?) this started after 10.15.4 - it did for me. This MacBook Pro has been rock solid since Nov then this started within a day after the original update to 10.15.4.

Same here - had no problems until 10.15.4, but given all the other reports I was seeing about similar kernel panics which pre-dated 10.15.4 I thought perhaps it might be a latent hardware issue that had started to occur belatedly, and just a coincidence that it happened after the 10.15.4 update.

Of course it's also possible that we are looking at more than one problem - e.g. some people seem to have issues when coming out of sleep - some when playing YouTube videos - and some when running Geekbench 5. Maybe there's a hardware problem *and* a software problem ? For me the problem seems to occur mostly when doing anything GPU-intensive, although it can happen at other times too.

I'm going to hold off for as long as possible, as I need my machine for work every day. If there's a software update that fixes it in the mean time then all well and good, otherwise I'll be one of the first in line when they start to re-open the genius bars.

 

[b.kind]

I just received a refurbished 16" MBP. It came with 10.15.3. Running fine.

I am going to wait for 10.15.5.

 

[CSBBody]

I purchased my base 16” around 6 weeks ago, and have had these panics daily, sometimes 3 x a day, sadly we went into a harsh lockdown, one we currently still under for the lastv5 weeks.

Mine is connected to a dell 3818 external

I switched off the power nap as suggested, and this am, thankfully, the woke right up, holding thumbs it works for a while.

 

[scottish]

I've previously posted in this thread but thought I'd add my comments here too.

I encountered kernel panics almost every day with my November built MBP usually when trying to wake from sleep but occasionally when using the MPB. I sent it in for service with my seller and they replaced the logic board.

Uptime was 49 days until yesterday when I had to restart for some app software updates and at the same time 10.15.4 was installed (though I can't remember agreeing to its installation!)

I just went to open the MBP this morning and got the below error.

"AppleIntelFramebuffer::setPowerState(0xffffff81b9e65000 : 0xffffff7f8e3a8d88, 1 -> 0) timed out after 45991 ms"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.101.6/iokit/Kernel/IOServicePM.cpp:5296"

Hoping it is a software issue this time.

 

[mychi]

Update on my situation:
Engineers said it’s hardware problem for me and arranged the mbp for repair. Service company said it’s been diagnosed and a part is on order.

Recap of my problem:
Working nicely for few weeks after purchase. Initially 1 or 2 boot loop when waking mbp up and then the boot loop became longer and longer, and finally only usable via safe boot. Tried all the resets and reinstalling.

Error message would be GPU panic blah blah PowerPlay failed to resume or PowerPlay failed to initialize. This is running 10.15.4.

 

[AnthonyHarris]

So hats off to visualinventor in the Apple forums. He was able to reproduce this faithfully by running Geekbench 5. He found that its actually the Intel GPU causing this by running the metal tests against the Metal api.

I decided to try this and sure enough, it GPU panics on the Intel GPU with metal right at the start with the Sobel tests. It does NOT panic with the OpenCL or either test against the AMD.

So its the Intel after all.

You can read up on what he did and his findings here as well as how to test this yourself:

https://discussions.apple.com/thread/250905859?answerId=252207020022#252207020022

The errors appear to be in the kernel with a signalHardwareError that point towards IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): IntelAccelerator prodding blockFenceInterrupt.

The signalHardwareError is a strong indicator that this is indeed a hardware problem.

Also, now it makes sense why this does not occur in Safe mode because none of the metal drivers are loaded.

For those having freezing issues etc, I advise you to try this and see if you get similar results (a super low Geekbench score or a GPU panic), of which its time to get your MBP fixed at Apple.

I don't have any of the hardware errors mentioned over at that link, so perhaps it is a software issue for me, but I've been waking up to my machine running extremely hot, sometimes the fans are on, running at what sounds like 100%, and sometimes they aren't, but the machine is always unresponsive and I need to force a restart.

If Apple don't fix the software soon, it will become a hardware issue for those suffering with this. I can't imagine being at such a high temperature (on occasions, for most of the night *possibly* without the fans running) is very good for the internal components.

 

[sa)]

Geekbench 5 has a software problem in 5.1 ON 5.1.1 fixed and the test passes

 

[mcgreen1966]

Hi, so my issues started when i upgraded to 10.15.4, kernel panics and reboots.
I now have the reboot loop issue, with powerplay failed to resume.
I am also running beta 10.15.5 beta 4 (the latest build)
mine does seem to have got progressively worse, with it taking 15mins of boot loops to get to the login screen the other day.
but this all did seems to start with 10.15.4, it was totally fine before this, i have only had the mac for two months.
(feb 2020).
I am not going to try and do the reinstall its a waste of time !! I have spoken to apple and they said send it back for repair but working from home i need it at the moment, so my ticket is on hold, i have the base off the shelf model.
I am going to wait for 10.15.5 full release which apparently is due any day now, and see if this fixes anything.
This is the first bad apple experience i have had to date.
if this doesnt resolve anything, then its back to apple i presume !!

regards
Mark

 

[jessemellon]

I'm been having the same "PowerPlay failed to resume" GPU panic. And multiple times per day, Adobe apps crash if I step away and my laptop goes to sleep. (16" MBP with Radeon Pro 5500M 8GB running Catalina beta 10.15.5.)

 

[cpnotebook80]

I just went back and purchased a refurb and a silver one. So far the 10.15.3 is running smoothly and no fans going crazy or temp rising or kernel panics. My last one I had from last month was bad after I did the update to 10.15.5 and I returned it right away. I waited to check on dell xps and noticed apple released a slew of refurbs and got myself a nice full spec'ed upto 2tb with 64gb. Just don't want to update to the latest OSX right now.

 

[Wise_duck]

hi everybody. I have a problem since installing 10.15.4. I noticed that the problem appears when the MacBook is charging with the lid closed. starts to make noise and warm up then turns off. do you have the same problem? I open the lid it turns on and gives an error. reinstalled the Mac OS did not help I think it is still Catalina, not problems with the hardware

 

[cpnotebook80]

I have no issues and refuse to update from my 10.15.3..on my unit I received few days ago. So far my temps at normal usage is 39'c with and at 1700

 

[corpse_of_steve_jobs]

Hello to everyone who is suffering with this thing guys.

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.

I can't believe i've met someone with the same bad luck as i had! Hello sir! Remember this pain when you realise that next year or two you will spend on clicking Backspace too oh man i mean to just clear the mess it's "Butterfly" creates?

And yeah, then i had the exactly same MacBook Pro - fresh model 16' to finally rock on MacBook!

Three months passed - and here we go. Fool me twice - shame on me i believe. What i'm reading from people trying to get technical support is that instead of giving you high quality service they are trying to brush you off while probably trying to understand if they can avoid spending too much money on another (which one from >20?) recall program. I believe the company used to be better.

_____________________________________

But, let's go fo the news. This thread really helped me a lot and saved me days of investigating the reason of what is happening. So some people tend to think that new Catalina Update will fix things for them. I have new Mac OS Catalina Beta 10.5.5 v.5 and it is installing right now on my "faulty" notebook.

When i will finish writing this text we will see if the latest beta includes this "power software fix".

If not - well, i believe you should dump you MacBook bcz it's too old already and go buy new one. The only hope for quick fix is that they will push it without specific major release as something for emergency. Will they..?

Oh, it's installed. Dont' worry, the same "woooof!" from coolers and then bootloop. It IS hardware guys. And i would not believe every technical support guy you meet because for last years it's about going through the script and lying the one you serve for the needs of the one who pays.

Have a good day and don't worry!

 

[maksimt]

Was sent here from https://discussions.apple.com/thread/250905859?answerId=252705065022#252705065022

I have a machine manufactured in April 2020 that's stuck in a reboot loop. Very similar to Loud2013's issue (https://forums.macrumors.com/threads/16-mbp-gpu-panics.2221004/page-7?post=28317988#post-28317988), mine also started happening after I plugged in an external display and an apple USB-C hub.

Nice Name: MacBook Pro (16-inch, 2019)
Machine Model: MacBookPro16,1
Family name: A2141
Group1: MacBook
Group2: Pro
Generation:
EMC number: 3347
CPU speed: 2.6GHz
Screen size: 16 inch
Screen resolution: 3072x1920 pixels
Colour: Space Gray
Production year : 2020
Production week : 16 (April)
Model introduced: 2019
Motherboard number: Please tell us the motherboard number of this MacBook of you know it.
Memory - flavour: Soldered
Memory - maximum total: 16GB
Factory: C0 (Quanta Computer (Subsidiary = Tech Com) China)



GeekBench 5 scores:
CPU
1025 Single-Core Score
5386 Multi-Core Score

GPU OpenCL
Intel UHD 4955
Radeon 5300M 22805

GPU Metal
Intel UHD 630 4751
Radeon 5300M 23705

 

[PeterJP]

I got myself a refurb 2.3GHz with 5500M/8GB upgrade about 3 weeks ago. I just received the Powerplay Failed Resume for the first time today. I worked in clamshell mode yesterday, whereas I usually don't use an external screen. But after that, I unplugged it, left it for a few hours and continued working (without external screen) without a problem. It only happened when I turned it on just now. Will watch it and document as I go along, just in case.

 

[maflynn]

Powerplay Failed Resume

You seem to be in the same boat as many others with the GPU KPs - not sure there's really anything you can do

 

[PeterJP]

You seem to be in the same boat as many others with the GPU KPs - not sure there's really anything you can do

Maybe that's why it was in the refurb shop

 

[maflynn]

Maybe that's why it was in the refurb shop

probably, but is the issue due to defective hardware or software? Going through this thread it almost seems like a software issue, but in all honesty, I have no idea

 

[PeterJP]

probably, but is the issue due to defective hardware or software? Going through this thread it almost seems like a software issue, but in all honesty, I have no idea

The good news is I'm still on 10.15.3 and I won't be updating soon.

 

[PeterJP]

I got the same again this morning. I haven't done anything special, just closed it and let it sit overnight. I will go to Apple with this.

Is there any way to get back the crash data from yesterday? I took a screenshot today but forgot that yesterday.

[Edit] Found the log files in /Library/Logs/DiagnosticReports/ProxiedDevice-Bridge. They were helpfully named "panic-full-(timestamp in UTC).ips". They're almost 2MB plain text each, so they should contain some info. They also contain the Powerplay error. I was a bit confused at first by the timestamp, as in local time I was still working when the second crash would have happened. When I realised it was UTC, it was after I stopped for the evening.

I will now contact Apple and try to get it swapped. For refurbs, they do a 2 week exchange policy here, but it's been just over 3 weeks. 1 year warranty, though. Wish me luck!

[Edit2] Just got back from a call with Apple. Well, technically it's an intermediary company here, but as close as it gets. They explicitely stated it's a software issue. Apple is aware of it and is working on it. Advice for my current situation is to shutdown at night. If it escalates and starts crashing while working, I should call them back. Despite being 1st line support, the lady did her research pretty well while I was on hold and also knew the issue was known to escalate in some cases. So I'll do what she says and hope it stabilises until it gets fixed...

 

[PeterJP]

Has anybody tested if 10.15.5 fixes this?

It's getting a bit worse and crashes now even with just a few hours of sleep, but it's not affecting my regular work yet.

 

[mdparthi]

It does not fix in 10.15.5 for me. Its worsen and now I able to login only through safe mode.. After multiple restart it boots otherwise it's going on and on restarting. This is really frustrating.