SOLUTION to panic(cpu 0 caller 0xffffff8011a16487): "AppleIntelFramebuffer::setPowerState

Well I just found the solution for my case:

I noticed that someone mentioned that the driver involved in the panic has to do with graphics and sound via HDMI. I recently got a 4K monitor with sound integrated, and after the 10.15.6 update this problem started for me.

I tried the trick of disabling screen dimming and closing the lid and no dice. But when I disconnect the 4K monitor and let it sleep, now it doesn’t happen. What I believe that’s happening is that, when it attempts to switch audio inputs, while asleep the panic his happening.

im going to try setting the audio input to the screen before sleep and see if the problem happens. I’ll report back.

First Aid didn't find anything. The only thing that has worked so far is changing the power settings as described in this thread AND unplugging my power cord whenever I am going to leave my laptop idle. If I do those things, my laptop won't restart.

Hello, had the same problem for a few months now on Catalina OS on a MacBook Pro 2018 15".

I found a fix for it - I installed the BETA version of Big Sur (20A5395g), which is pretty stable and received no panic attack after leaving the laptop to sleep even overnight.

If you want to do it, keep in mind that this is a BETA OS and you are taking a risk by installing it.

If you haven't yet registered as a developer you need to enroll in the program - here.

1. Go to developer.apple.com
2. Click on Discover > macOS > Download and sign in with your developer account or Apple ID.
3. Click on Install Profile to download the new macOS Developer Beta Access Utility to your Mac.
4. Go to Downloads on your Mac and click on the new macOS Developer Beta Access Utility to open it.
5. Double click on the macOSDeveloperBetaAccessUtility.pkg and the installer will run.
6. Once new macOS beta is installed Software Update (in System Preferences) will check to see if there are any updates. Click Update and the latest version will download.
7. You'll see a prompt to install the software, click on Continue.
8. Agree to the Ts&Cs (more on them below).
9. Click Install.

So first night after testing, everything working without issues. I had all external devices connected and closed the laptop and this morning I awoke to a responsive computer without issues.

I'll keep testing and report back if I experience issues, but before the upgrade the issue was persistent, so things are looking good.

That doesn't solve the problem. It just masks the problem.

Your Mac still may have a hardware problem. A new computer that kernel panics should be sent back.

Just install the 10.15.5 update, the issue should disappear with it.

I just recently upgraded to an M1 Mac so I no longer have the issue (at all), but till the last day I had my Intel Mac and since I upgraded to Big Sur, I never again experienced the panic issues.

PS.: I did a clean install of Big Sur and chose to NOT recover any backups, I wen't 100% clean install.

Is this something you can try?

Well I can add my experience to this thread: got a brand new Macbook pro 2020, and the day it arrived ( vanilla - only had google chrome and spotify installed) it kept crashing. I did a clean reinstall + first aid (nothing found) but nothing fixed the problem, it kept crashing when I was leaving my computer for more than 30 minutes idle. I ended up going through the excruciating process to have my macbook replace (trust me you do not want to suffer this) got my new one yesterday and drumroll....SAME ******* PROBLEM!!! So I ended up doing as everyone in the thread has mentioned (turning off the power nap, and disconnecting the power cord when idle,) and so far so good... To me it is still a huge problem that a brand new Macbook pro that I paid over 3.5k is crashing like this. But hopefully this will be fixed with Catalina Update (!)

Same issue here...

Brand new Macbook Pro 2020 with Catalina 10.15.6.

MacBook Pro (13-inch, 2020, Four Thunderbolt 3 ports)

Processor 2.3 GHz Quad-Core Intel Core i7

Memory 32 GB 3733 MHz LPDDR4X

Graphics Intel Iris Plus Graphics 1536 MB

However, trying to install 10.15.6 Supplemental Update which notes this fix:

Fixes a stability issue that could occur when running virtualization apps

Will update afterwards...

did the first aid thing work ??

if so how so I do it, I have today logged a ticket with apple for this, the person was kind but had not come across this either.

Suggested mail repair but im holding off on this as working from home I need the device and can't not have ir for unto 2 weeks !

seems apple needs to get on this quick, if anyone reading this having same issues please log it !! mean you are then cover by consumer law for 6 years as you have logged it under warranty period !

Apple tech support should have know this! My new laptop was about to be sent back.

Definitely interested in this thread.

Brand new (refurbished by Apple) MacBook Pro 16. Every time I leave it idle for >45 minutes, when I come back to it, it has restarted and I get the "Your computer restarted because of a problem" messaged., Contacted apple support, completely erased the hard drive, reinstalled Mac OS, and manually installed a few software apps that I have on my 2015 MacBook Pro... and still experiencing this shut down issue. Apple wanted me to send it back for repair- but it seems like, if this is a hardware issue, it is a BIG hardware issue.

if this is a hardware issue, it is a BIG hardware issue.

It could be. It's not like Apple hasn't received bad hardware from Nvidia before.

If people sit around waiting for a software fix, the bad hardware will never be identified by Apple. If everyone with problems on the new 16" MacBook Pro had them serviced/returned them, we likely wouldn't be still wondering what is going on.

I was reading another thread where someone had sent their max back for repair... only for the problem to still persist. Mine is slated to be sent back, but I figured I would check these discussion boards first, because when Apple Support tech looked at the error logs, it was REALLY quick, and all he ended up having me do was run first aid, and then do the wipe and reinstall. Something made me want to double check if this really was a "my computer only" thing or if anyone else has had this issue.

I never experienced this issue until the last 2 weeks on 10.15.6... really annoying. I'm tempted to install Big Sur beta just to see if its gone there, because I doubt that Apple will fix this issue if it hasn't done so already.