crashed due to AppleIntelFramebuffer

panic(cpu 2 caller 0xffffff8006816487): "AppleIntelFramebuffer::setPowerState(0xffffff834e993000 : 0xffffff7f89db2d88, 1 -> 0) timed out after 45958 ms"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.101.6/iokit/Kernel/IOServicePM.cpp:5296


MacBookPro16,1

Mac OS version:

19E266 (catalina 10.15.4)

MacBook Pro with Touch Bar

Posted on Apr 1, 2020 11:03 PM

Reply
49 replies

Apr 28, 2020 10:55 AM in response to yuanshiming

Has everbody tried to remove the PowerNap option as describe for both battery and when plugged?

This completely resolved the problem in my case. Never had it anymore. Not any of the other options ("prevent from sleeping", etc.). Just "Power Nap". Power Nap needs to be off. Don't forget to switch to plugged version and turn it off there as well.

There are many threads for this topic and in most cases turning off power nap has resolved the problem. I did not have a crash in the last 2 weeks now. Before it crashed *every single time* that I put it to sleep.


May 6, 2020 3:50 AM in response to mifisa

I have the exact same issue with my 16 inch Macbook Pro that I got just last week. Running MacOS 10.15.4 with an external monitor plugged via USB-C. Turning off Power Nap did not fix the problem for me. Unplugging the monitor before the computer goes to sleep does solve the issue so I'm fairly confident in saying this is a problem with MacOS bugging out while attempting to wake an externally connected monitor.


What I ended up having to do as a workaround is to set "Turn display off after" to Never and turn on the "Prevent computer from sleeping automatically when display if off" setting in Energy Saver. Now at the end of my work day, I put the computer to sleep manually and turn off the monitor manually. When I start my day, I wake the computer then turn on the monitor manually. It's a pain but it beats dealing with a computer that rebooted every single time I come back to it.


Someone earlier on this thread suggested that public beta 10.15.5 fixed this issue for them. This is my main work machine so I'm not going to try the beta, but I've got my finger crossed hoping the final version fixes this problem in the upcoming weeks.

May 9, 2020 8:51 AM in response to mdm76012

update - Seems my issue is similar to the ones people describe with relation to an attached accessory. I had an off brand port replicator type device connected - would charge at night plus had a network and HDMI connection. Stopped using it and no more reboot issue. Now I have another issue with losing WIFI every day - but that is going to be another post.

Apr 2, 2020 7:24 AM in response to yuanshiming

yuanshiming wrote:

<crash report.log>
panic(cpu 2 caller 0xffffff8006816487): "AppleIntelFramebuffer::setPowerState(0xffffff834e993000 : 0xffffff7f89db2d88, 1 -> 0) timed out after 45958 ms"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.101.6/iokit/Kernel/IOServicePM.cpp:5296

MacBookPro16,1
Mac OS version:
19E266 (catalina 10.15.4)



Kernel Panics are predominately caused by hardware faults or faulty third-party kernel extensions.




If your Mac spontaneously restarts or displays a ... - Apple Support

https://support.apple.com/en-us/HT200553


You can post your Kernel Panic report in their entirety here, preferable three separate reports in three separate "Additional Text" box (see menu below) for ease of reading and comparison. A single report may be useful but does not establish a trend for a meaningful diagnosis.


Kernel Panic reports can be found /Library/Logs/DiagnosticReports

From the Finder>Go>Go To Folder, copy and paste:

/Library/Logs/DiagnosticReports


ends in .panic post the whole report.


Apr 10, 2020 1:04 AM in response to Jose Phillips

Same issue here with macOS 10.15.4 (19E287) and a brand new 2019 MBP 16" 2.4Ghz 8-Core i9, 32GB, Radeon Pro 5500M 8GB. It only appears to happen when I have my external displays (2x LG 27UD88) connected and only when coming out of a power saving mode. I have never seen it happening while working, so I have disabled all power saving and just turn off my displays by hand for now to see if that could be a workaround until they fix it.

Apr 11, 2020 4:01 AM in response to cvkordenoordt

So after about 1,5 days I think I can confirm that the issue does not occur at all after setting the "Turn display off after" setting to "Never" in Energy Saver settings.


Manually turning off my displays is a lot less annoying for me than having to recover from a crash after every time I leave my desk for a while, so leaving it like this until the issue is properly fixed.

Apr 9, 2020 8:58 AM in response to littlefooch

Yes still a problem with macOS Catalina 10.15.4. Drives me crazy. I've got MBP (16-inch, 2019), 2.4Ghz 8-Core i9, 32GB, Radeon Pro 5500M 8GB connected to 2x daisy-chained 27-inch Apple Thunderbolt displays via Apple Thunderbolt 3->2 adapter. This setup used to work fine in my previous MBP laptos (with previous macOS versions) and it worked fine with this new MBP 16" with Catalina until for about few weeks ago it started doing this CPU panic with "AppleIntelFramebuffer::setPowerState". I've sent multiple crash reports to Apple already.


This is especially frustrating as I having external monitors in your MBP has always been an annoying experience, but I'm intentionally using Apple-only hardware here (the displays & the adapter) to avoid these sorts of issues.


Apple fix this. ASAP.



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

crashed due to AppleIntelFramebuffer

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