Question: Q: Kernel Panic on 16" i9 MBPwRD

NOTE: THIS ADVICE IS NOT FROM ME, I FOUND THIS FROM ANOTHER APPLE SUPPORT FORM. USE AT YOUR OWN RISK

Sleep issue are often sorted by

resetting the SMC https://support.apple.com/en-us/HT201295

If no resolve—

Try a SafeBoot https://support.apple.com/en-us/HT201262

Takes noticeable longer to get to the login screen, does a 5-15 minute disk repair before it fully boots up, and certain system caches get cleared and rebuilt, including dynamic loader cache, etc. Login and test. Reboot and test

This test will tell you if third party interference; extensions etc are not loaded in safe boot mode.

If you still need further assistance—

To get a good look at your System config. for conflicts or issues, you can run this trusted utility http://etrecheck.com

If you need help interpreting the report you can post it here in its entirety in the "Additional Text" box in the editing toolbar below, in your reply.

You can set its preference to "Allow full Disk Access", with this you get a digest of issues from the last 7 days that are saved in your system.

AppleSupportOntario wrote:

NOTE: THIS ADVICE IS NOT FROM ME, I FOUND THIS FROM ANOTHER APPLE SUPPORT FORM. USE AT YOUR OWN RISK

Sleep issue are often sorted by

resetting the SMC https://support.apple.com/en-us/HT201295

If no resolve—

Try a SafeBoot https://support.apple.com/en-us/HT201262

Takes noticeable longer to get to the login screen, does a 5-15 minute disk repair before it fully boots up, and certain system caches get cleared and rebuilt, including dynamic loader cache, etc. Login and test. Reboot and test

This test will tell you if third party interference; extensions etc are not loaded in safe boot mode.

If you still need further assistance—

To get a good look at your System config. for conflicts or issues, you can run this trusted utility http://etrecheck.com

If you need help interpreting the report you can post it here in its entirety in the "Additional Text" box in the editing toolbar below, in your reply.

You can set its preference to "Allow full Disk Access", with this you get a digest of issues from the last 7 days that are saved in your system.

I'd be curious to know this other " ANOTHER APPLE SUPPORT FORM." and if you could site the specific link.

IGNORE THIS MESSAGE

Unfortunately, I can confirm the issue persists in 10.15.4.

I have the MacBook Pro 16 2019 i9 16GB 1TB w/ this exact issue. I also posted my bug report a little while ago.

I hope an Apple engineer see this post too and can fix this issue in 10.15.5.

I hope an Apple engineer see this post too and can fix this issue in 10.15.5.

If only they read these posts.

I have the exact same issue after 10.15.4. I'm currently trying to work with apple support as the kernel panics appear to be due to a timeout in the Intel graphics driver's power state handling. That said, I just noticed that both of us have the latest Universal Audio driver (I have a UAD Apollo Twin). That said, I haven't actually connected any device in several days, and I've had at least 4 identical crashes since the update...

I've lost faith in Apple Support being able to work with engineering to resolve issues that go beyond the basic script of steps. I've had 15 tickets opened for various iOS and MacOS issues (I lost ~1k photos, 20GB iCloud Drive, missing iMessages and SMS on my iPhone, missing vCards, and other horrible problems). I've wasted >100 hours on the phone, and so far I only have 3 RTAs (none of which have been fixed in the latest updates), and Creative Media decided an appeasement would be easier than recovering my photos (or even figuring out why I'm experiencing so many iCloud issues)... But I digress, and apologies for the rant.

I'll try to uninstall the. UA drivers and post back here if there's any consistency. In the mean time, if anybody else is experiencing this same crash in AppleIntelFramebuffer::setPowerState(), could you post if you do or do not have the UAD audio interface driver installed?

Here's my latest crash log -- HTH!

I also have the same problem. When the Mac is asleep, and I open the lid, nothing happens. I have to restart, and then get this error. Called Apple support - reset NVRAM and SMC, the usual, and then they are looking to have me do an OS reinstall.

Well at least its likely not a personal hardware issue or a piece of software doing it if the community has similar issues.

I have exact same issue too. My MBP 16 crashes every time I connect it to external monitor. Sometimes it restarts and give me message "... MBP was restarted because of problem..." or I'm not able to wake it up from sleeping mode.

Hi there.

I have the exactly same error. Additionally, my MacBook Pro 2019 16'' i7 16GB is overheating every time to more than 70º C.

Any solution for this problem?.

panic(cpu 4 caller 0xffffff8009816487): "AppleIntelFramebuffer::setPowerState(0xffffff81b8997000 : 0xffffff7f8cdf3d88, 1 -> 0) timed out after 45960 ms"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.101.6/iokit/Kernel/IOServicePM.cpp:5296

Backtrace (CPU 4), Frame : Return Address

0xffffff922e563b40 : 0xffffff80091215cd 

Complete error is attached.

Best thing to do would to be contacting Official Apple Support

I have the exact same problem with sleep. Mine just started with the "upgrade" to 10.15.4 though and wasn't an issue before. MBP 16" 16GB, 1TB, i9. Purchased December 2019. I did contact Official Apple Support. The only advice I received was to reinstall MacOS. I'll try the SMB trick first before I go to the last resort. Especially since this just started with 10.15.4, and I doubt reinstalling the same OS will have any effect.

Agreed.

Just to follow up, I removed the Universal Audio software and kexts from my system, but it had no impact on this bug.

So far, I’ve tried everything support has suggested (reboot to safe mode, reinstall macOS), but obviously this had no impact on the bug introduced in 10.15.4.

I also submitted sysdiagnose data 3 days ago, but can’t get my Sr. Advisor (or anybody at Apple) to follow up. They’ve missed 2 callbacks, and I wasted 1.5 hours on the phone trying to get an update. Every rep I’ve talked to (except the first one) has denied this is a known issue, and claimed I’m the first one they’ve talked to about this problem.

I really wish Apple would at least acknowledge this issue so others don’t have to waste so much time eliminating variables. That said, I think it’s still worth calling support to report the problem and ask them to escalate it so they know it’s impacting everybody (or most people). I’m on my 3rd 16” MBP i9 w/ 2TB SSD since December.

Best of luck to everybody...