429 Too Many Requests

I finally called Apple Support about this problem, having suffered the freezing and other GPU problems since the first day. After putting me on hold and checking with her supervisor, she did confirm this is a known problem with the MacBook Pro 16 Inch models. She did remote into my MacBook to verify the model and hardware configuration (specifically looking at the AMD Radeon Pro 5500M 8 GB GPU). She created an appointment at my local Apple Store and I will be given a new computer (not refurb). I did ask if Apple has identified the specific problem, and she told they have and all new models have the issue resolved.

It seems this was/is a hardware problem (not software) and replacing the computer is the only solution.

I will be replacing my Space Gray MacBook Pro 16 Inch tomorrow at the Apple Store. I hope this will resolve the problem.

I suggest others contact Apple Support and get their computer replaced.

Good Luck…

My model config is…

Space Gray

MacBook Pro (16-inch, 2019)

2.4 GHz 8-Core Intel Core i9

32 GB 2667 MHz DDR4

1TB Macintosh HD

AMD Radeon Pro 5500M 8 GB

Intel UHD Graphics 630 1536 MB

Darn it ... took too long to post: reposting.

Interestingly I too have a Space Grey MacBook Pro that was "custom".

My specs are: i9 2.3ghz, 32gb Ram, 1TB storage, AMD 5500m 4gb

It took 4 days to troubleshoot but I believe I have a reproducible way to test the Intel 630 UHD GPU issues people are having.

1. Download Geekbench 5 (I used version 5.1.0)
2. Select "Later" when the dialog pops up about paying for it. You'll be testing in "Tryout Mode"
3. Look the the left of the program and you'll select the "Compute" Benchmark
4. Select Compute API: METAL (OpenCL doesn't error out but Metal does.)
5. Select Computer Device: Intel UHD 630 Graphics
6. Open the Console Log app BEFORE YOU run the GEEKBENCH 5 test
7. Select "Errors and Faults" from the Console log app. It should be at the top.
8. Start the GeekBench test.
9. Watch all the red dots proliferate the Console Log app. Most of them will be IntelAccel errors. Many times you will likely see the internal GPU restarting as evidenced by the attached screenshot. Look for signalHardwareError in your logs.

Here is my video of the whole thing. https://youtu.be/Rxh3wATgPOA

During my 7 minute video I try to select the "About the Mac" it takes almost 3 minutes for the window to render while the test is running. You can see in the Activity Monitor in the video it showing as unresponsive.

I truly hope this helps folks - and I wish you all luck. I love Apple and their products. This is obviously something they need to admit and get ahead of because this is turning into something that appears to be a real issue.

My laptop is currently at Apple repair awaiting a logicboard (MLB).

Edited because I hit post too quickly.

Since my last post I have been testing a workaround by disabling the Automatic graphic switching feature so my MacBook is only using the AMD card and so far so good haven't had a single freeze since then. I have been coding and edited over 450 photos these days flawlessly as it should be.

If you would like to give it a try:

System Preferences > Energy Saver

And uncheck the Automatic graphics switching.

Good luck.

Hope Apple fix this issue as soon as possible, in the meanwhile I will keep my current config.

NOTE: This should be a temporary solution as it will drain your battery faster because the system will be always using the must powerful graphic card even for simple tasks.

This is hardware folks. Apple just got back to me... my laptop is awaiting a part in order to fix this GPU panic problem. The hardware has been confirmed defective. Your best course of action is to get it to Apple to fix. There will not be a software fix for this according to my Apple engineer.

The only work around at this state is safe mode. That is the only consistent way to prevent this from occurring because it prevents the software that enables the AMD to occur. This is why the OS is hobbled in safe mode. Its a short term fix and forget about running Adobe products, etc that use the AMD GPU in safe mode. Safe mode will only allow you to do the bare minimum with your computer.

Don't try the standby hacks as they don't work when plugged in. Disabling graphics switching doesn't work as well... only for a short time, but you will eventually tickle the problem and it will panic at some point. This has consistently happened to me when its plugged in. I also know when its going to occur as I have iStat menus and I watch it flip the "I" to "A" in my menu and not too long after that the freeze/GPU panic/reboot occurs with the usual error.

The bottom line is that this is a hardware issue and the longer you wait to get this to Apple, the longer you will delay getting this fixed.

If people are getting their hardware back and it still panics, then Apple has a much bigger issue and it just may be good to get a refund by doing a chargeback on your credit card. Their 15 day policy means nothing to your credit card company. So you have that as an option. For the guy who is on his 3rd, I would most certainly do this and consider another company laptop for now. This is not worth it IMHO. They get 1 fix for me. After that, its chargeback time if I see this happen again.

I hope everyone can get this fixed because this is really bad.

I've got gfxCardStatus installed, and it's helpfully identified where the problem is.

Seems like Catalina's got a bug when switching between the integrated and discrete GPU. At first I thought my AMD Radeon R9 M370X was acting up, as I was getting kernel panics when running software that switched to it, like iMovie or Chrome with video. But checking the Console.app, the error happens whenever a context switch request is made, even if gfxCardStatus prevents the switch from happening. HOWEVER, no kernel panics if I use gfxCardStatus to keep the machine locked to EITHER the integrated or the discrete GPU. Panics only happen during the switch.

kIOReturnNotReady is thrown if the DMA command has not been prepared, which points to a bug in Catalina's GPU switching code.

Hopefully someone at Apple will read this and fix the glaring bug.

So just an update on my progress. I’ve posted his prior but I want to give everyone a refresh just in case you don’t hear back from me due to the issue being resolved. I’ll keep you all updated if the issue seems resolved after I use my MacBook for a month or so. 

I purchased my 2019 16” MacBook Pro on 12/08/2019. Immediately after buying it, the MacBook had issues. MacOS would freeze completely, the mouse cursor couldn’t even move during the freeze for about 10-20 seconds. Then the fans would start going full speed and get very loud for about 5 seconds. Then the system would automatically shut down or reboot. I then got curious about this reoccurring issue so I posted here on 12/12/19 about having this issue. 

For my first time around, Apple had me do the following:

1. Reinstall MacOS and restore from a time machine backup. The issue still occurred. 
2. Reinstall MacOS and don’t restore from a time machine backup. Manually reinstall applications as needed. The issue still occurred. 
3. Drive two hours to have a Genius review the MacBook. He suggested that I again reinstall MacOS but couldn’t diagnose the issue. He pushed the possibility of it being hardware related. He asked that I mail in my laptop for repair if the issue happens after another reinstall. 
4. Reformatted the Macintosh HD and reinstalled MacOS from a USB flash drive mounted with the most recent MacOS Catalina image I downloaded from the MacOS App Stored, which is signed by Apple. The issue is still occurring. 
5. Apple sent in a repair request to send my device out for repair. It took three business days for me to get it repaired and receive it back. According to their repair notes included with the repaired MacBook, they only “reinstalled MacOS” which I find humorous because I’ve done this multiple times already per their instructions!

I then had the issue again following the first repair. I called Apple and they actually collected console logs this time from the MacBook. I was getting “Panic” logs saying “Bad Magic” during these unexpected shutdowns and reboots. 

They sent the device out for repair again on 04/01/2020. It took four business days (should have only been three but UPS had a technical issue) and I got it back today, 04/04/2020. They replaced the Logic Board (item #605-06150) and the Touch ID Board (item #605-06552) due to a “Kernel Freeze” symptom. They also clean installed MacOS and it shows that my device passed hardware testing. 

So I’ll be testing this repaired device for a month or so and will see if the issue happens again. If it happens again, I’ll probably get a full replacement or ask for a refund from Apple due to their Warranty terms. 

I’ll keep you all updated if the issue seems resolved or if I have any issues after a month. 

Just an update on my progress. My prior MacBook would unexpectedly freeze for 10 seconds, then the fans would go 100% for 5 seconds, and the machine would then power off or restart. I would check the logs after this issue and get a "bad magic" kernel panic. They sent me a brand new replacement. This issue seems to be resolved with a brand new replacement. This is a hardware issue (unless you're having panics due to the most recent version of Catalina). If you're having kernel panics, bad magic issues, or unexpected shut downs/reboots, then I'd recommend to get a replacement as soon as possible. This is the only way to resolve this issue.

I spent countless hours troubleshooting the issue with Apple and sending it out for repair twice. The first repair, they only reinstalled MacOS and updated my T2 firmware. This didn't resolve it. The second repair, they replaced my Touch ID Board and Logic Board. This also didn't resolve the issue. I then requested a new replacement (since I'm still within my warranty). They approved this and were able to send me this brand new replacement. This replacement does NOT have any issues and now the issue is resolved.

Please keep in mind that Apple (US) will only send a replacement after a certain number of repair attempts (usually 2-3 attempts), if you're past the 14-day return date. So please make sure to get started on the repair process and after the second/third repair, ask for a replacement. This is the only way to resolve the issue. It was the only way for me to resolve the unexpected shutdowns and reboots with "Bad Magic" kernel panics. I have read prior that this is the only way others have fully resolved this issue. I hope you all have the same success as me!

I just wanted to post an update on my progress just in case anyone is wondering. I've responded to myself each time I posted so you can easily click back through my old posts by clicking the "in response to BretFromApple" at the top of my posts.

Apple sent me a brand new replacement and this resolved my issue. This was the only thing that could have resolved my issue. Some people report going through two or more replacements until finally getting one that works without issues. Don't spend your time trying to fix this issue yourself if you had the same issue as me. Please contact Apple and start the repair process to get closer to getting a replacement. The good part is that once you get a replacement, you get 14 days (in the US) to return the product. So you'll know within 14 days if your new MacBook is having the same issues and just get another replacement. You can keep doing this until you get one that works (if that's even needed). This is my first replacement and works great.

My prior MacBook would unexpectedly freeze for around 10 seconds, then the fans would spin at 100% for around 5 seconds, and the machine would then power off or restart. I would check the logs after this issue and get a "bad magic" kernel panic or some sort of other similar kernel panic.

I spent around two to three months working with Apple and I went through two repairs where the issue was not resolved and it kept shutting down or rebooting. During these repairs, they reinstalled MacOS, updated my T2 firmware, replaced my Touch ID Board, and replaced my Logic Board. This didn't resolve the issue.

My prior MacBook must have been a lemon because this brand new one has absolutely no issues at all. I've had it now for almost a month and have used it extensively for production. This new MacBook is how my first MacBook should have been but I somehow ended up with a lemon on my first purchase.

Anyways, I hope you all get this issue resolved like I did! This will be my last post on this forum unless I come across the same issue in the future with this new MacBook, which is very unlikely. Good luck all!

My MBP 16" had issues with USB ports back in March, and I couldn't even charge the computer. I sent it to Apple, and they changed the logic board. When I got my MBP back it started to restart every time it went to sleep. I talked to Apple multiple times over the phone about this issue, and they gave me very basic instructions (resetting PRAM and SMC blah blah) and work arounds (disabling power nap, graphic switching, etc). Nothing worked for me, and I wasn't convinced that it was a software issue since I had the same problem on 10.15.15, 10.15.16 BETA, 11 Beta (Big Sur). I basically told the customer rep to set up the repair even if they end up doing nothing since this is a "known software issue". I got my MBP back today with new logic board installed, and I haven't had a single restart so far. Mine was consistently getting GPU Panic, so if yours have the same issue, set up a repair even if they tell you that they might not do anything.

I HAD exactly the same issue with my 2019 MacBook Pro 16, Intel i9 2.3GHz, 1 TB SSD, Intel UHD Graphics 630 1536 MB, AMD Radeon Pro 5500M 8 GB.

Stuttering while typing, watching videos, simply scrolling a web page...

Switching to the dedicated graphics card makes it much better but drastically reduces battery life.

Then I found https://chromeisbad.com. I had Chrome installed on my system but was only using Safari. I followed the steps to completely uninstall Chrome and the stuttering problem immediately went away.

This is unbelievable. We all were blaming Apple for bad graphic card drivers, returning hardware and so on...

The problem is caused by Googles keystone stuff which is always active even if you are not using chrome.

Give it a try and please report here if that helps you too.

I'm so happy my MacBook is running smooth now!

I used to get the full-on freezes occasionally, but that seems fixed after I reset NVRAM and SMC.

I am still getting occasional freezes a few times an hour on the integrated GPU only. Just got one now while viewing this thread in Firefox. The screen freezes for 5-10 seconds, but audio continues to play in the background. On longer freezes, I notice that closing the lid and reopening seems to "fix" it.

I tried running with the discrete GPU all day yesterday and experience zero freezes, which really makes me think something is up with the integrated GPU or its driver.

Some folks have thought this may have something to do with graphics card switching, but I installed gfxCardStatus to monitor the card currently in use and haven't seen a correlation between freezing and switching.

Firefox 71.0

macOS 10.15.2

2.3 GHz 8-Core Intel Core i9 / 32GB RAM / 1 TB HD / AMD Radeon Pro 5500M 4 GB / Intel UHD Graphics 630 1536 MB

I think there is really an hardware pb with this issue.

I was facing it starting from the first hour, and at least 1 or 2 times a day. (complete freeze, touchbar and sound working, force restart mandatory)

After a few days, I have returned the computer and bought a new one.

No issue after a full day on the new one.

Only difference, i still haven't updated catalina (still on 10.15.1)

AGS turned off only works for a certain amount of time unless you have it locked to your Intel GPU. Turning off my AGS makes it AMD and its just a matter of time until something tickles it and it resets.

I have noticed that keeping it on the Intel and not having it go to AMD prevents the panic from happening. Things I have tried was to prevent the computer from going to sleep (Energy saver) and turning off the screen saver (set to none), and do not use any apps that require the AMD. This stabilized the computer and no further panics occurred.

As an experiment, I tried to launch Adobe Illustrator and sure enough, within 5 seconds, I get the freeze, high fan, black screen, reboot. Same panic occurs - GPU panic Powerplay failed to resume. So this is definitely is centered around the AMD GPU getting switched on. This may possibly why people get into the boot loop as something launches in your login that turns on the AMD GPU... thats just a hypothesis. I think if someone can somehow prevent the computer from auto opening applications on boot, they may get bast the boot loop. Its just a thought.

Some things I noticed...

The GPU heat had nothing to do with this. It was around 90-100f (fahrenheit NOT celcius). That's the average for the entire machine chips (thank you iStat menus). I also noticed that this didn't happen to me until AFTER 10.15.2 update was installed. This did not happen to me with 10.15.1. I'm not sure if there is a correlation. If anyone has this problem and has 10.15.1, please chime in as I'm hoping that is not a red herring.

Apple Engineering is still looking for me. My bets are on software as this is getting super widespread. But we will see...

I made a little headway on this. This is not a guarantee fix as I have only tested this for an hour or so and I have not gotten any reboots or panics and am able to fully utilize the AMD graphics card, dynamically switch, etc. I have forced sleep and wake up, closed/opened the cover, and so far so good. I can't get it to panic, but this really needs to tried over a few days. I would really like others to try. Here is my history...

I noticed that this does not happen in safe mode. So I needed to find the difference. I looked at the normal login's kexts that are loaded which seem to be associated with AMD. I opened terminal and did a sudo kextstat | grep AMD. It gave me the following:

com.apple.kext.AMDSupport

com.apple.kext.AMDRadeonX6000Framebuffer

com.apple.kext.AMDRadeonServiceManager.kext

com.apple.kext.AMDRadeonX6000HWServices

com.apple.kext.AMDRadeonX6000

com.apple.kext.AMDRadeonX6100HWLibs

But when I boot in safe mode, it only lists:

com.apple.kext.AMDSupport

com.apple.kext.AMDRadeonX6000Framebuffer

So I started to assume that it had to be software and one of the kexts that are not in safe mode must be the culprit. I didn't want to touch the AMDRadeonX6000* named kexts at first as I felt they were core. You can't really unload any of them except for com.apple.kext.AMDRadeonX6100HWLibs, which if unloaded, it just doesn't allow the AMD GPU to activate and it will hang any application that attempts to use. So I decided to try com.apple.kext.AMDRadeonServiceManager.kext. Again it won't allow you to unload it because of interdependencies, but you can certainly disable it.

To disable it, you need to boot into recovery mode (reboot and hold down the Command-r). Once in recovery mode, open disk utility and mount your main disk It may ask you to type in your password to decrypt it. Mine is called "Mac OS". Exit disk utility and then under the Utilities menu, select terminal. Once in terminal, type "cd /Volumes/Mac OS/System/Library/Extensions" and hit enter. Remember "Mac OS" is the name of my drive, yours may differ. Once you have done this, type "mv ./AMDRadeonServiceManager.kext ./AMDRadeonServiceManager.kext.orig". This essentially renames that file to prevent it from loading. Once done, exit the terminal and restart the computer.

So far, its appearing that the AMDRadeonServiceManager.kext is the problem. I honestly don't know the impact on the system having it disabled, but at this stage I haven't had any reboots. I think I need more time to be sure this temporarily fixes it. You can put it back to normal by following the above but type in "mv ./AMDRadeonServiceManager.kext.orig ./AMDRadeonServiceManager.kext" instead.

If others want to try, please do so and report back. This may not be the issue nor a fix. So YMMV. Do this purely at your own risk and I am not responsible if you mistype something and prevent your system from booting. Only do this if you are comfortable in terminal and using UNIX commands.

I'll report back in the next day to see if my system has stabilized.

Something that I didn't mentioned in my previous post is that in addition to disabling the Automatic Graphic Switch I also have my Touch Bar configured as Expanded Strip, showing the old function keys statically instead of showing dynamic content (App Controls).

I decided to share this because few days ago I decided to switch back to the default Touch Bar configuration with App Controls that change depending on the app or activity that you are doing and few hours after enabling it my laptop fans went crazy and the whole system got unresponsive so I had to reboot it using the power button, as soon as it booted again I changed my Touch Bar config back to Expanded Strip and everything is working again.

So if I have Automatic Graphic Switching turned on or my Touch Bar set to App Controls my system is almost un usable having to manually reboot at least 2 or 3 times per days.

Another thing that I noticed while testing with Automatic Graphic Switch turned on today is when the Intel graphic card is in use even basic system are bit laggy, like switching between spaces or get in / out of full screen, everything works great when the AMD 5500M 8GB is in use (I left the automatic graphic switch turned off)

I am running the latest OS version 10.15.3 (19D76).

ondrejc,

Even though you purchased two weeks ago, it is likely the model you have was part of the original shipment and sitting in inventory. There is no way to know for sure, but your best bet is to call Apple, get a support case and have it replaced (with a new computer, not refurb). Or you take it back for a refund/exchange if you are still within return period. But, I would be concerned if the store replaces it with an older (un-repaired unit).

I don't have a good answer for you. Call Apple and see what they say. No point exchanging for another defective unit.....

The GOOD NEWS IS...Apple is finally acknowledging the problem.....

No more guessing. It is a hardware problem with no software fix. You need to have it replaced with a FIXED unit.

Good luck and let us know what Apple is saying. I am curious is we are all being told the same thing.

gargvishal wrote:

I had a MBP16 Grey i7 16 GB 512GB. It worked OK with very few crashes (once in 2-3 days) in the first few weeks but after 5-6 weeks use it started crashes every 10-15 minutes. I could see that the crash frequency was increasing with usage. I reinstalled the OS 3-4 times and did all what was told by the Apple support. Finally Apple took it back for refund. I again purchased the same configuration but this time in silver colour. I have been using it for 3 days and no crash so far. However, when I ran Geekbench 5 with Compute API: METAL and Computer Device: Intel UHD 630 Graphics, as suggested by @visualinventor, I am getting similar error in the Console Log app. When I change the Device to AMD there are no errors. So I have a laptop which is not freezing but giving errors running Geekbench 5. Will start freezing after a few weeks of usage?

Your LB is defective. Waiting and hoping is not going to help you. Yes, it gets worse and you will begin to get panics and reboots as time goes on. You are highly recommend to contact Apple and open a support case. If you have a custom MBP, you will have a heck of a wait due to LB shortages, so you may just open the case and tell them to contact you when the LB part is in. Since China production is fully running at this point, I expect shortages to lessen.

Your work around for this right now is to go into System Preferences/Energy Saver...turn off "Automatic graphics switching" and turn on "Prevent computer from sleeping automatically when the display is off" on the Power Adapter tab. This works ONLY on power and you will likely get issues when on battery. But at least you can fully use your machine on power without these issues in the short term.

I hate to tell you this, but if it is the kernel panic with the Powerplay failed to resume, it’s not a coding bug. It’s a hardware issue and was confirmed by Apple. I suggest that you follow the thread over at MacRumors as it goes very deep into the issue.

if it’s a coding bug, everyone should have it. Mine had the issue. I sent the machine to Apple. They confirmed it was hardware. Logic board was bad. They gave me a new computer. Not more panics. It’s hardware.

So I haven't had this issue since I've received the 2019 MacBook Pro 16" back from Apples repair center. Before I sent it off to get it repaired, I took screenshots of all my hardware/software under System Report and pictures of my MacBook to see what they all did prior to sending it back to me.

They said that they only "Reinstalled MacOS" on the repair paperwork but I did notice when doing comparison with my screenshots to the MacBook now, that my Apple T2 Security Chip now has a different firmware version. So they reinstalled MacOS and also updated my T2 Security Chip firmware to a higher version. No other firmware versions changed and nothing else was different. I reformatted and reinstalled MacOS once I received the MacBook Pro back from the repair center and the T2 Security Chip firmware is still the version they updated it to, which is higher than what it was originally.

My MacBook Pro has not been having these issues since they did this and I've put around 40 consistent work hours into this laptop with a very large volume of applications running at once, taking up a lot of resources.

When I sent in the MacBook and received it back, it had the same version of MacOS on it, which was the most recent version at that time. So there was no MacOS version difference. Just only a difference in my T2 firmware version. I believe their T2 Security Chip firmware update resolved my issue, but only time will tell.

I solved my problem.

My brand new macbook pro 16 (Shipped 2. april 2020) also restarted (crashed) over nigth - actually it crashed (Kernel Panic GPU) everytime it went to sleep mode. I had nothing installed except default OSX with updates.

1. Reset: Pram & NVRAM (still crashed)
2. Reset: SMC (still crashed)
3. Internet Recovery Command+Option+R (when booting) (Crashed under installation, but continued afterwards)
4. Disabled "Prevent computer from sleeping automatically when the display is off." & "PowerNap.." in Energy Saver settings (Problems disappeared)
5. Two days later I enabled "Prevent computer from sleeping...." and "Powernap..." again (Still no problems)

I don't know if step 1-3 is necessary, but I think so.

So a macbook pro 16 that I almost returned, is now working perfectly - and I'm very happy:-)

So far what we have found that manufacturing dates have played a role in this. Pre-March seems to have a higher chance of the problem. Getting a Logic Board replacement seems to only be effective if you get a > March board. Those who have seen this problem re-occur have gotten pre March boards as replacements. My replacement was a March 3 manufacturing date and have no problems at all with this one.

Anyways. I would tell Apple support to be sure the new logic board is manufactured March or later. That will increase your chance of a fix.

Good luck. This is not a pleasant fix. Also thank you for reading the entire thread. It will give you a strong foundation to get this fixed. Knowledge is power.

The panic messages that seem to be related to hardware issues have been discussed earlier in the thread, so I'd read back through to see exactly which ones.

I'm dealing with the "PowerPlay Failed Resume" panic at the moment. This particular panic, per Apple, could be hardware or software. They're just not sure, yet.

Others in the thread, though, have reported it is indeed hardware, and the only fix is to have the hardware replaced w/ a logic board and/or whole system that was manufactured in March of 2020, or later.

Do you know when your hardware was manufactured? (You can install "coconutBattery" for an easy way to find out...)

My new 16" MacBook pro always crashed at night and tended to crash after sleep. I contacted Apple Support, they suggested that an update to the operating system should fix this, given that my logs had similar messages as those outlined in this thread (specific kernel panic messages). They indicated that, in the meantime, disabling power nap might work. It did. No crashes since turning off power nap in energy saver preference. Naturally, waiting for an update to fix this issue because power nap is a great feature of macs.

I had tried numerous fixes prior, utilities, reinstall system, etc... Turning off power nap was the only way to stop the crashes and odd behaviors.

For what it is worth, I also have one of the first 16" units shipped and after the 10.15.4 supplemental OS update, (4/24) it was crashing every 5-10 minutes. I did not wipe my data or programs but I did perform a SMC reset and reinstall of the OS from the WEB and it has been stable since then.... the longest span of uptime since November. I always use an external 5K display and I have graphics switching disabled. I had performed the same steps with earlier releases including 10.15.4 (prior to the supplement) without the same success. Your results may vary but it was an hour well spent for me.

I had a similar problem. Just random hangs for 2-10 seconds, sometimes up to a minute. In rare cases, this could result in a reboot if the video system does not start responding. If you disable Automatic graphics switching, the problem does not occur.

3 replacements of the logic board did not fix the problem and Apple issued a refund a few days ago.

P.S. You will not find any logs related to this problem, the diagnosis also does not find the problem.

You can record a video of your problem. Also open “About this mac” while recording so that they see the system version and your serial number.

Do not delay the solution of the problem, otherwise you risk subsequently solving it at your own expense.

You aren't speaking to Apple here. Your machine is under 1 year of standard AppleCare for hardware issues.

Random freezes can be due to:

1. Filevault needing to encode.
2. Backup software running.
3. Third party optimizers. Mackeeper and Advanced Mac Cleaner and zeobit and macpaw software are actually malware and should be removed by a Mac malware removal expert.
4. If the machine gives you a four language screen telling you it needs to restart and automatically restarts, and you have nothing connected to the machine besides power, and have no third party applications installed, then you likely have a hardware issue which Apple Diagnostics usually can detect: https://support.apple.com/en-us/HT202731 when it can't that doesn't mean there isn't one.
5. If your hard drive is over 85% full, open some room by copying stuff to the cloud, flash drives and external hard drives. Your system's swap files may be running into each other when this happens.
6. https://discussions.apple.com/docs/DOC-250002463 Etrecheck is able to quickly diagnose the causes of freezes, and if you post the results here as directed, someone here can usually tell you where to start looking.

Edit: I just noticed this is a 32 page thread. Folks, please start a new topic thread so you can get focussed attention. Otherwise we will be all over the place trying to solve problems for difficult people.

m0unt41nman wrote:

[...]

People who have gotten faulty hardware who have gotten full replacements no longer have the problem. I am one of these people. I have have no panics (Powerplay failed xxx) and I have the same software as you.

[...]

Your best course of action is to get it replaced. [...]

Agree with everything this bit in particular is very helpful.

Any idea if it's possible to request a replacement rather than repair? It rubs me the wrong way to get a "repair" on a brand new machine, e.g. 3 days of use in my case. I.e. if the device that was sold to me was sold in a "needs repair" state, I feel like I should get a brand new device since I didn't agree to buy a "needs repair" device.

Has anyone had any luck with getting a replacement without wasting time with logic board "repairs"?

Had the same issue with my new macbook , a week after I purchased . I gave it to the customer care of apple with recording of my issue . Initially , they couldn't find the issue but later they understood my issue and changed the logic board with RAM under apple care protection plan. Now it's working fine

I always thought it was a software issue (and in the deep of my heart I still do) but three weeks ago I finally decided to take the my mbp to apple care. They finally replaced logic board including memory, processors and hard drive.

Of course the first thing I tried was doing something that enables the discrete gpu by attaching a second screen, open an Adobe software and doing GPU benchmark with Metal API in Geekbench 5, all things that were causing display freezes and reboots.

With gfxCardStatus I saw that the external GPU was actually activated everytime and I don't experienced any freeze, any reboots and any glitches, even on Chrome.

I still don't know what was the problem but I'd bet a dime to a bad update, maybe back in december 2019, that downloaded faulty drives for the external graphic card and this caused those hardware issues.

I wanted to share my experience, hoping I will never need to post again into this thread.

FYI my setup is:

MBP 16-in, 2019

2.3 GHz Intel core i9 8 core

32 GB 2667 MHz DDR4

Intel UHD Graphics 630 1536 MB

AMD Radeon Pro 5500M 4GB

MacOS Catalina 10.15.7

This issue is related to GPU switching. Turn off dynamic GPU switching to stop this from happening in the meantime, until Apple's able to come up with a proper fix.

My MacBook Pro 16" has the same problem.

Abnormal shutdown after sleep, error reports:

"Panic(cpu 4 caller 0xffffff7f910d997b): 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 15:0 power-retry 0:0 connect-change 0 : PowerPlay Failed Resume.

"

pmset -g log > ~/data/temp/pmset_log_20200509_2

2020-05-04 09:51:55 +0800 ShutdownCause SMC shutdown cause: -20:

2020-05-04 09:51:55 +0800 HibernateStats hibmode=0 standbydelaylow=0 standbydelayhigh=0 0

Sleep/Wakes since boot:0 Dark Wake Count in this sleep cycle:2

2020-05-04 09:51:55 +0800 Sleep Entering Sleep state due to '': Using AC (Charge:0%)

2020-05-04 09:51:55 +0800 Failure Failure during wake: PEG0() : Some drivers failed to handle setPowerState

Sleep/Wakes since boot:0 Dark Wake Count in this sleep cycle:2

log show --predicate 'eventMessage contains "Previous shutdown cause"' --last 24h

Filtering the log data using "composedMessage CONTAINS "Previous shutdown cause""

Skipping info and debug messages, pass --info and/or --debug to include.

2020-05-10 18:13:12.592035+0800 0xc9       Default     0x0                  0      0    kernel: (AppleSMC) Previous shutdown cause: -20

2020-05-10 18:42:47.462838+0800 0xc9       Default     0x0                  0      0    kernel: (AppleSMC) Previous shutdown cause: -20

2020-05-10 20:56:34.822806+0800 0xc9       Default     0x0                  0      0    kernel: (AppleSMC) Previous shutdown cause: 5

2020-05-10 22:49:56.754095+0800 0xc9       Default     0x0                  0      0    kernel: (AppleSMC) Previous shutdown cause: 7

2020-05-11 07:06:21.070393+0800 0xc9       Default     0x0                  0      0    kernel: (AppleSMC) Previous shutdown cause: -20

2020-05-11 07:54:21.367612+0800 0xc9       Default     0x0                  0      0    kernel: (AppleSMC) Previous shutdown cause: -20

2020-05-11 08:14:24.568634+0800 0xc9       Default     0x0                  0      0    kernel: (AppleSMC) Previous shutdown cause: -20

2020-05-11 09:31:11.427823+0800 0xc9       Default     0x0                  0      0    kernel: (AppleSMC) Previous shutdown cause: 5

2020-05-11 10:11:46.969820+0800 0xc9       Default     0x0                  0      0    kernel: (AppleSMC) Previous shutdown cause: -20

Control Center panic log shows:

{"caused_by":"macos","macos_version":"Mac OS X 10.15.4 ","os_version":"Bridge OS 4.4 (17P4281)","macos_system_state":"running","incident_id":"563E3A24-6F70-4DBA-885B-298E49F6CCE3","timestamp":"2020-05-11 00:14:15.00 +0000","bug_type":"210"}

....

...

"build" : "Bridge OS 4.4 (17P4281)",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2020-05-11 00:14:14.97 +0000",

"incident" : "563E3A24-6F70-4DBA-885B-298E49F6CCE3",

"kernel" : "Darwin Kernel Version 19.4.0: Mon Mar 2 20:38:56 PST 2020; root:xnu-6153.101.6~2\/RELEASE_ARM64_T8010",

"macOSOtherString" : "\n** In Memory Panic Stackshot Succeeded ** Bytes Traced 362096 **\n",

"macOSPanicFlags" : "0x4",

"macOSPanicString" : "panic(cpu 6 caller 0xffffff7f8eb0a97b): 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 15:0 power-retry 0:0 connect-change 0 : PowerPlay Failed Resume.\n\n\nBacktrace (CPU 6), Frame : Return Address\n0xffffff81fbe03700 :

======

I have tried:

1) reinstall MacOS, 10.15.4. (not swap ssd, I think swap SSD is only left thing to try :-( )

2) disable Power Nap

3) Never use Chrome

3) Disable Graphic Switching

4) pmset -g standby 0

5) disconnect all USD/TB devices

6) reset SMC and NVRAM/PRAM

7) login with a new user

What's I found is that the problem doesn't occur in Safe mode. It only occurred in normal login mode. So I guess there may be some driver issue. I checked the install.log in /var/log directory, iBridge version updated automatically before manually update to MACOS 10.15.4 and before Mac runs into this problem. So I highly double it is caused by Apple software bugs.

So I stopped using Google Chrome this weekend, ran Firefox with a bunch of youtube videos, then playing a movie on VLC, having iMovie on the Background, and today ran Unity and I haven't had the problem for the last 1.5 days.

I also tried on battery and on power source, computer on a cushion so it'd get warmer more quickly and no pb so far.

I'm using Catalina 10.15.2.

Laptop is:

6-cores 2.6Ghz i7

512 GB

16 GB RAM

Radeon 8GB

Chrome: 79.0.3945.130

I'll try to use Chrome again see if the problem shows up and then update Catalina / Chrome. I'll keep you posted

Ok, try this. Boot machine with the shift key pressed(safe mode, if you have "filefault" enabled press shift key again after entering your password). Let the machine stand for a few minutes in safe mode then reboot, press alt command p and r to reset pram.

Now test your machine.

Please let me know if this fixes anything.

Yep indeed it is HW. I just escalated my case to the executive team because I was not getting any feedback for what they are waiting on. They finally got back to me and gave me more info.  They are waiting on a logic board.  I guess they are plumb out of them and they need to get it from China.  They confirmed the GPU failure is caused by the logic board and is indeed required to fix. They said part of the delay is when you have an upgraded GPU, memory, SSD, its configured as a customization and they need a matching logic board.

So for those hoping and waiting... don't hope for a software fix. This is a hardware problem and its confirmed by Apple.

Restart on wake is generally the GPU panic issue and is evidenced by a dialog box after reboot stating a problem has occurred and if you want to send it to Apple. If that is what you have it’s the bad problem and the freezing usually occurs before the panic issues. So I would assume you have the worst problem and it’s hardware related. You are recommended to get it to Apple and get it repaired.

Mine failed before taking to the apple store and I just showed them my video I took. All you need to look for in the activity monitor logs is the signalHardwareError ... GPURestart. Show them that, it's definitive proof.

I should have my repaired machine tonight.

This almost mirrors the chain of events that happened with my 2019 16’ MBP! Spent hours on the phone with Apple support, re-imaged multiple times, etc. & at the end of the day I received a full refund from Amazon (they were excellent)! I then purchased a MacBook Air & haven’t had one single problem! It’s HW, Apple refuses to admit it, literally hundreds (if not thousands) of MBP owners are experiencing the same issues & it won’t be fixed by some miracle SW update no matter how long you wait! Do what you can to get your money back people, that’s your only hope to “fix” this problem unfortunately!!!

For me I got this same problem at first day using my macbook pro 16inch; you can open you activity monitor, and search the name of process highly occupying cpu, for me its a process related to icloud, 160%!! and I shut down the icloud service, which i pay for 100g, on my computer. And no freeze nor shut down later. You can try shutting down the icloud service.

Apple escalated my case to Engineering, and they determined from my logs that the freezes were correlated with the Superhuman email app. Something to do with a 'Video Wake Lock' event.

Does anyone who's also experiencing these freezes also have Superhuman installed?

kinkarso wrote:

Apple escalated my case to Engineering, and they determined from my logs that the freezes were correlated with the Superhuman email app. Something to do with a 'Video Wake Lock' event.

Does anyone who's also experiencing these freezes also have Superhuman installed?

Haha ... yeah... don't let them tell you this. Send it in. Its a hardware problem. They tried to tell me that mine was due to the MBP being on the same network as a Sonos. I laughed myself silly when I heard that.

Its hardware. I sent mine in, they verified a faulty logic board, and they sent me a new laptop. Everything has been working more-or-less fine since.

Remember this... if its freezing for everyone, its likely software. If its freezing/panicing for a few, its likely hardware.

I wish people would read this entire thread... its clear that its hardware.

Bad Magic != the GPU issues discussed in this thread.

Powerplay failed to resume/initialize is the hardware problem and will not be fixed by software. If you got those, expect those panics to return. Other GPU style panics, YMMV for whether its software or not.

I wouldn't make a blanket statement telling people there is a fix for this without explaining the actual panic. That gives a false hope. The Powerplay failed to resume/initialize was confirmed by Apple as a hardware problem and will require a recent logic board manufactured March or later.

It’s hardware. Been through this with them. Had the executive team tell me and it’s been stated numerous times in this thread.

You need to send it in. You need a new logic board.

if it’s software, we all have the problem. If it’s hardware, only some of us. You are in the some of us category. My new replacement from Apple does not have this problem.

Umm... but I’m not wrong. :-). Read the thread :-)

Look at it this way. Why does my machine work but yours does not? If it’s software, shouldn't mine panic too? Why do a majority of the MBPs work fine, but only some don’t? That’s strongly evident of hardware or something in common between those few.

I have been through this. Philux has been through this to an extreme. It was claimed by Apple it is hardware... at the executive level.

if you have the panic, you will see. It’s hardware and you will get it replaced. If you don’t, your panics get worse. It gets to the point where only booting in safe mode gets you in.

im not here to argue with you or fight about it. I came here to share the experience and help others because many are waiting and hoping for a magic software fix.

Hey... if Apple can offer a software fix that somehow fixes these minority of MBPs, great. But I have a feeling you may panic your way to your warranty running out by waiting and then you will pay for that logic board.

Good luck!

I have read the 24 Pages and I disagree with your conclusion.. so far.. CPU/GPU panics is not always related to only hardware. Thise can be caused by problems in the Kernel. I had both Bad Magic AND CPU/GPU Panic. On a fresh new 10.15.4 with no ekstra software installed. 13 crashes in 24 hours.

After reset NVRAM and SMC, reload OS, and disable Power Nap (and the day after enabling Power Nap again), I have been running straight for 9 days without one single crash, on 10.15.4. All my software has been installed, and the MacBook has been transported and sent to sleep 100 times. No problems.

it was shipped from china 2. April 2020.

I think I found the culprit for my random freezing. I used to experience random freezing at least once a day, even when im not doing anything. System is idle. In all of that instances, Viber is open and seems the first one to freeze.

Ever since uninstalled Viber, my machine has been super stable for 2 weeks now. No random freeze anymore.

Im not sure why this has fixed my issue, but this just goes to show that, at least for me, this is not hardware issue.

Just stumbled upon this thread while trying to diagnose issues with my own 16" MBP. 2.6/I7 machine with 32GB of Ram. Purchased in November, arrived in December, but my corporate IT was not ready to support Catalina so it sat from January until May waiting and waiting -- but finally they were ready to support Catalina so we got it all set-up and I started using it at home over the past 2 weeks. Hallelujah, I have missed you Mac! But this morning I got a screen freeze, fans to 100%, and on reboot after login, black screen fans to 100% reboot. I was eventually able to boot into safe mode and have seen both PowerPlay issues in my logs. I called Apple and they're sending me a package to send this back for the logic board replacement. Meanwhile, after letting the machine sit for a few hours, it actually booted without issues. I assume I should just follow-through and send it for repair once the box arrives and that just because it is working now is no indication that it will continue to do so...

I have the same problem - randomly freezing and noticed more of a display issue....... I have tried it all and this is the only thing that has helped in 2 days. This maybe a work around until apple decides to fix it.

-system preferences

-energy saver - (battery)

1-UNCLICK Automatic graphic switching

2-UNCLICK -ALL - BUT slightly dim display - check mark this

3-Turn dispaly off .............slide to NEVER

-energy saver - power adapter

1-unclick - put hard disk to sleep

2-unclick - enable power nap

3-Turn display off...........slide to NEVER

hope this helps it does for me -

I was hoping this could be addresses by a software update. It cannot. Mine is for my business. Started July 9 first call. They next day aired a box I sent back arrived Friday returned today before lunch Monday!

new logic board

new ram

new video

touch pad

new ssd

my

machine is only 93 days old and like mint. Used strictly for work. Not moved just taken home. Hardware failure is causing the kernel panics. It is suppressed but still is a broke machine when u manipulate the energy setting for video and power settings. Apple stepped up to the cause. Hope we r good out of the gate. I did not Restore a back up downloaded apps and software like a new machine. Works like a champ. 🙏

My MBP 16" Cataina 10.15.6. is saved!

After 10 month of kernel panic torture my IT colleague found a way out:

There were two or more board partition on the disk, we erase them all and set a brand clean instalation, and...

now it really works!

Yes, Im not 100% sure if helped this or other cause, but after trying E-v-e-r-y-thing, this seems to work.

i had the same problem. After sent back to the vendor, the logic board replaced and since then not a single kernel panic, not a single freeze and the crash report empty. It certainly helped at least for now...

You should bring back the laptop and take a new one.

I have done that and no more pb at all.

For me it's hardware because my usage is the same on both. Same apps, same os versions, same settings...

Is the error code same as "Previous shutdown cause: -20". ?

The test step is :

1) Open the Terminal Window

2) run "log show --predicate 'eventMessage contains "Previous shutdown cause"' --last 24h"

I have same issue and returned the laptop to Apple and they replaced the logic board and it is working fine for last 24 hours.

I ave also found that to be a satisfactory work-around. My 16" has not crashed since I turned-off dynamic GPU switching and the number of instances where the fan speed increases (without a crash) while connected to a single 5K LG display has also decreased.

At Apple Support’s advice, I reset my MBP’s NVRAM/PRAM and haven’t experienced the issue in some time (though if that doesn’t help, we need to make a very loud and public demand that Apple fix this and in a timely fashion)

Randomly, mine is now working.

I had masses of freezes/crashes. Then realised Spotlight was eating resource/battery. Seemed to be a conflict with my BitDefender AV. I let BitDefender do a full scan - it had never finished a full scan before (due to scanning google drive - which I've now excluded). Once completed, and re-built spotlight index, performance & battery are much better, and I've not had any crashes since.

Could be unrelated, but might help others...

Mine sometimes randomly shuts down.

Can be once a week. Can be three times a day. I can sometimes work on high performance apps without a hitch. Sometimes, I can't and it all comes crashing down. I basically get a "GPU kernel panic" error message. I'm sure most people here get the same one.

I can't put my MacBook to sleep anymore. I used to be able to but can't anymore, not without it restarting or shutting down completely with that same darn "Your Mac was..." blah blah message. And same, exact same, error log.

I used to think this was a software issue. But I don't think it is. I think it's mostly a hardware issue.

I think Apple pushes the boundaries when it comes to industrial design, and they wanted something that was elegant and beautifully powerful beyond measure with the 16".

I think the problem is in the assembly process. There must be some small aspect or part of the assembly process that has to be done 100% right, no margin for error, or it causes a butterfly effect, and eventually causes a major problem with the GPU and other aspects of the machine.

Perhaps the solution is removing the GPU. I don't know. But that would defeat the point.

The point is, it does the equivalent of Windows blue screening EVERY time I close the lid for more than a few minutes.

EVERY TIME.

I don't think these machines are repairable. I think one has to pray to whichever deity one deigns to worship to, and insist on a completely new, fresh out the box machine, and hope the intrinsic design flaw is not present there.

I also think that over time, the issue will worsen and the machine's lifespan will shrink drastically.

But seriously, if a Mac can't have it's lid shut without it "blue screening" (kernel panicking), then it is, by definition, an intrinsically defective product and thus can't be repaired but only replaced. If it happens a second time, then insist on your money back and carefully consider how much brand loyalty is lost when the words, "It Just Works", as a selling point, are no longer true.

This is serious brand damage.

I'm going in tomorrow to have mine replaced for a completely new unit. I won't take no for an answer. In my country of origin, we have at least six months grace when it comes to defective products. Especially as "The Butterfly Effect" may only make itself known a month after the fact.

Chaos and Design. It's almost beautiful.

The new update came out today! Hmmmm, I’ll try it out but I already fixed the problem when connected to power by doing the SMC resets & changing the power settings:

System Preferences > Energy Saver

And uncheck the Automatic graphics switching."

It only gives me these messages now when it sleeps under battery use! I canceled my Apple appointment because they will just want to reimage anyways & I already tried that with NO SUCCESS!!! I’ll just live with the mess...

Not sure how to search topics here, so sorry if this was posted before, but are you all having wake issues as well? I haven't experienced crashing other than when waking from sleep. Quite a few of us are dealing with this and getting kernel panics.

If anyone wants to run some tests... on battery power: load up Chrome, go to YouTube and play an HD video in fullscreen for a minute or so. Pause the video and keep it full screen. Close the lid. Wait 10 minutes or so, and open it back up. It should crash if we have related problems. If it gives you an error/report dialog on startup, hit Report then let us know what it says. You can cancel the report.

Now try disabling standby and doing the same test above a few times:

Start Terminal

Then type: sudo pmset -a standby 0

Enter your password

To revert this just use 1 instead of 0. You can verify it's off/on by typing pmset -g

This probably won't fix random crashing while using the Macbook, but it's a start if we fix one problem.

It took 4 days to troubleshoot but I believe I have a reproducible way to test the Intel GPU issues people are having.

1. Download Geekbench 5 (I used version 5.1.0)
2. Select "Later" when the dialog pops up about paying for it. You'll be testing in "Tryout Mode"
3. Look the the left of the program and you'll select "Compute" Benchmark
4. Select Compute API: METAL (OpenCL doesn't error out but Metal does.)
5. Select Computer Device: Intel UHD 630 Graphics

Same here - crashing on wake. Disabling power nap "solved it". I've been running it like this a few months now and get the occassional crash on wakeup, but it's maybe once or twice a week now instead of every time. No other problems. I can live with this I guess. I'll get extended care, and if it turns out to be hardware, they get to fix it. Hopefully if it's hardware, we'll see a recall at some point.

Probably my last Macbook. The quality isn't there anymore.

Same with me. I started crashing when it went to sleep mode but suddenly it started crashing every 5 minutes. So I took it back to the store and they replaced with another one. So far, so good (after 3 hours of use). LOL. I'll purchase Apple Care for sure.

A fresh full install has been proved useless. Since the latest update 10.15.15 doesn't resolve this issue. The only way is to go to Apple Genius Bar and ask them replace the logic board, and ask them install the MacOS version 10.15.1.

a brody wrote:

1. Jackhans,

Since you have found this to be the case, I would recommend:

Calling AppleCare and getting a case# for your case.

2. Request that they allow your case# to be shared with others, so they can refer to it.

3. Suggest that people with such cases be allowed to send their Mac in to AppleCare to get the logicboard replaced and reinstalled with 10.15.1 like yours did. Clearly, in the event of COV-ID, the mail in should be possible for such a repair.

4. Let them know 10.15.5 does not solve the problem. This suggests that for people who need 10.15, they will need to use Firefox or Chrome since the latest security is not available on 10.15.1, but is on 10.14.6's latest security update and 10.13.6's latest security update. Perhaps even suggest a version of the security update be made strictly for 10.15.1, until they can figure out why certain logicboards are having trouble with cameras.

I get that this maybe seems unreasonable, but I really just want to Shibboleth and for Apple to forego the whole process of going through their whole AppleCare process, getting forced to downgrade or try other software fixes, going through resetting my SMC and PRAM for the Nth time, leaving me without a computer for days to a week one or several times to replace the logic board, and so on, and just send me a new MacBook Pro, let me image it from TimeMachine, and return the old one.

They have over a hundred billion in the bank and IDK how many tens of thousands I've spent personally on MacBook Pros, PowerBook G4s, MacBook Airs, iPhones, iPads, AirPods, etc, and IDK how many hundreds of thousands they've gotten from me buying those things for my companies and encouraging friends, family, and colleagues to buy their stuff, and IDK how many times I've defended the company putting my reputation on the line saying «they're not over-priced; they're worth it !»

Now I have a ~$5k computer that is broken and my only hope for resolution is to waste hours on the phone and weeks of back and forth and being without a computer under the hope that maybe maybe they'll manage to fix it.

I'm just livid.

My MBP16 has this problem. Fortunately, all AppStores close, and I had to bring my MBP16 to a repair shop, which can formally repair Apple's devices.

My MBP16's problem had physical memory error, so the shop exchanged some parts.

And he said:

1. Only MBP16 with Core i9 has this problem. MBP16 with Core i7 doesn't have this problem. His hypothesis is that program for Core i9 is not enough, especially for external graphic card.

2. My MBP16 had physical memory error, which is permitted by Linux system.

I think that some kernel panic occurred in my MBP16 and its physical memory was harmed, which caused for many kernel panic.

Now I have repaired MBP16, but use it by no sleep mode, no automatic graphics switching (why does it turn on after reboot??). No problem now. But I'm afraid of using MBP16. I think that Apple must compensate our time and mental stress ... !.

nkutomi wrote:

My MBP16 has this problem. Fortunately, all AppStores close, and I had to bring my MBP16 to a repair shop, which can formally repair Apple's devices.

My MBP16's problem had physical memory error, so the shop exchanged some parts.

And he said:

1. Only MBP16 with Core i9 has this problem. MBP16 with Core i7 doesn't have this problem. His hypothesis is that program for Core i9 is not enough, especially for external graphic card.

Unfortunately that shop was not correct. i7s have had this problem too.

I hope you didn't have to pay for the repair. You do know Apple will send a box to you to send to their repair facilities at no cost to you (at least in the US)?

Ok, so got mine back today from being repaired, new logic board, with 10.15.5 installed and it works totally fine.

So mine was definitely a hardware issue.

Lets see how long it lasts !!

if anything changes over the next couple of months i will report back here.

Cheers

Mark

(Replying to myself, see my previous post for context, my 16" MBP was stuck in a reboot loop)

I managed to get the vendor I bought my 16" MBP to issue me a replacement machine with the exact same specs (base everything: i7, 16, 512, 5300). The replacement machine came with 10.15.4; I've since upgraded to 10.15.5 supplemental update. The replacement machine has had no issues at all for over a week now on both 10.15.4 and 10.15.5 unlike my first machine.

My faulty machine was manufactured on week 16 2020 at factory C0. My replacement machine was manufactured on week 20 2020 at factor C0.

As most of you in this thread can imagine, having a machine that you can trust to be stable is a completely different experience than one that can restart on you at any time. It's like having a huge weight lifted off your shoulders. I seriously feel your pain if you're stuck with a broken 16" MBP. The issues described in this thread are definitely hardware issues. I don't understand why Apple doesn't step up and offer completely new replacement devices to those affected by the hardware issues here. If I didn't get so lucky with my vendor (e.g. if I bought directly from Apple) I would have been screwed.

@NoahC

I’m sending mine in today! I reinstalled the OS to make support content it wasn’t the problem. Of course at first you’re like wow everything feels smoother ,but just running geekbench 5 on metal with the intel gpu targeted I get the same intelaccelerator prodding error in the console logs and the fan is back to go 100% definitely send it in. if you have to get a new mac it wont be to big of a deal to setup.

If issues persist after the update and you have correct graphics card, then you have a logicboard issue with the computer. Could be RAM related, and might not even appear under Apple diagnostics, but if you erase and restored the operating system, ran the updater, and it still had an error with Apple only installed software, then I would focus on it being a hardware issue. This is why you purchase AppleCare. As well designed as the machines are anything from a power surge to a spill to an improperly connected or disconnected cable could create issues. You also need to make sure you are using only the correct wattage power brick for make, model, and age of the computer in question. If all that has been ruled out as a cause, then RAM is the probable cause since no test can 100% verify RAM is good, it can only tell you if it is bad.

well - i can duplicate now - if u take the energy saver and manipulate to never sleeping or screen always on where is does not go into a low power, reduced power state it works flawless but this is putting a band-aid on it - If you have anything plugged into the usb-c ports even the power adapter this triggers mine when u have the energy saver set to defaults - if u back up or use any of the usb-c ports like i said even charging this replicates my to freeze or restarts ...... so i have run mine since yesterday with no usb-c ports using anything and no power adapter until needed - charging back from 5% at 37% crashed - hard reboot and 78% crashed got to 100% unplugged and no crashing - just copied the data with apple diagnostic tool and sent to them .....this is not what a new macbook is suppose to be like when i run my business off of it .........just to me sounds like a hardware issue?

@jary144

Evidenced is screen shot log failures while running geek bench 5 , support will ask the “did you reinstall Catalina not from a backup?” If you did and still experiencing the crashing it’s covered under 1 year warranty.

got my logic board done like a month ago and it works like it should right now fingers crossed 🤞

Hello, I have been experiencing these micro freezes/stutters of my cursor since I bought my Macbook Pro 16'' in June. The problem occurred whenever I was on the integrated Intel GPU.

I thought it would have really been the drivers that caused the issue. But yesterday I tried out Microsoft Edge as a browser as I wanted to have more privacy than with Google Chrome. Since I have completely closed Chrome (not closing the window only and running it in the background!!) the stuttering has disappeared!

I am not sure if shutting down Chrome did the trick... Nevertheless, Chrome is known to be resource intensive and there have been other issues reported with Chrome and this laptop. Maybe some of you can give it a try to elaborate if this is a solution.

Please note, I have also shut down Safari as well and I am using Microsoft Edge as a browser only.

Hope I could help.

Thanks, I agreed! It's HW! Mind got so bad it wouldn't even start in Safe Mode any longer! That KO criteria for me, back it went, and I couldn't be happier after 2 weeks of ****...

When we’re these established as hardware issues? Me and another friend just started getting these after a Catalina update and turning off power nap fixed it.