Kernel Panic on 16" i9 MBPwRD

Nope. its not solving the problem.

leroydouglas wrote:

There has been a Supplemental update to the macOS10.15.4

see if that resolves your issue:

Download macOS Catalina 10.15.4 Supplemental Update https://support.apple.com/kb/DL2038?locale=en_US

My MacBook is new without much app installed, no external monitor and usb c drive and it still reboot overnight/periodically standby after sleep. I had tried follow Apple Support to reinstall the os, completely reinstalled the harddisk (Shift+Option+Command+R), Safe mode (Shift) and all did not work.

I had referred to jwelsye07 reply to disable 'Enable Power Nap while plugged into a power adapter' and it seems works for me so far. will wait for few more days and will call up Apple support and report the case. Obviously is is disappointing with Apple Support do not confirm this issue yet. Seems this is last for a while.

Is UAudio a Kext from UAD? I noticed in my own log the following:

last unloaded kext at 3036456155703: >!UAudio 322.2 (addr 0xffffff7f93c48000, size 434176)

I do own UAD hardware. However, I have never installed UAD software on this macbook nor have I ever connected my UAD hardware to this macbook. Could UAudio be referring to something else here, besides Universal Audio?

Listing non apple kext:

+1.... Running a (1 day old) MacbookPro 16" i9 2.3Ghz, 5500M 4GB, 16GB RAM, 1TB (higher spec base model) on Catalina 10.15.4

Only got the device yesterday and experienced 4 kernel panics while waking it up from sleep with the lid closed (3 different ones at that...). No external devices or monitors were used. The only thing that may be considered as an external device was a temporary thunderbolt bridge connection to my 2017 MBP 15" to move data over.

The first panic happened last night after about 10min of sleep, where instead of Touch ID I had to enter the password. At that time I only had installed a few Apps from the app store (Logic, Final Cut, Motion, Compressor, Main Stage, Office 365) and some fresh installs of 3rd party software (MS OneNote, Capture One, Steam, BetterSnap Tool, Intel Power Gadget). One process that may have run in the background was probably the icloud Fotos download (130GB in the cloud). Did not save this report.

This is the only crash where the laptop was not plugged in.

The second I experienced this morning when waking it up after the night, showing the following message:

"Sleep transition timed out after 180 seconds while notifying clients about upcoming system capability changes. Suspected bundle: com.apple.iokit.IOGraphicsFamily"

Having read about this issue before, I contacted Apple phone support right away. Standard procedure: Reset NVRAM, Reset SCM, Safe Boot to reset Cache.

=> Sent the device to sleep, crashed again after wake-up 30min later. Following message this time:

"Sleep transition timed out after 180 seconds while calling power state change callbacks. Suspected bundle: com.apple.iokit.IOGraphicsFamily"

So I called Apple support again: Tested for Malware this time, ran hardware diagnostics (first aid on SSD and D-boot), no issues found. Next was a fresh Catalina 10.15.4 install (keeping the data). The friendly lady on the phone told me to return the device if these measures didn't solve the issue, which I can't since I bought it at a 3rd-party vendor in Switzerland. All you can do is send it in for repair to their certified repair shop and hope for the best... -.-

Anyway, after the fresh install I closed the lid and just let it sit there. After about 30min with the lid closed, the fans spun up like crazy for 1s. So I walked over to it, opened the lid: Yet another crash. Message this time:

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

Also, on a MAYBE related note... I experienced some weird behavior related to graphics.

1) In the game Cities: Skylines (Steam), which worked perfectly fine on my 2017 MBP 15" with the same game version and same OS. I hear a clicking noise from the speakers synchronized with a clearly visible frame-drop every second. I didn't however face other popping issues on youtube/iTunes/Logic as seen in other reports, so no clue what's wrong there... Any ideas?

2) When turning off the automatic graphics switch mode the first time, the device lagged badly for a few seconds, as if the Radeon had a hangover when waking up. Since I never experienced any lag before while switching between the graphics cards, I found this behavior to be rather odd.

I'm torn on what to do next. On the one hand, after reading all the reports on the web I somewhat start to doubt the hardware defect theory. On the other hand, looking at the other 2 experienced oddities in combination with the crashes, I can't really shake the feeling of there being a hardware problem. I just want to avoid sending in a brand new device to get a prophylactic motherboard swap for no reason, which may lead to other issues down the road. I hope this makes sense... :)

Any advice is highly appreciated.

Same problem. I do have an apple refurb 2019 16" I9 32 gb Vram 8gb 1tb. I've had this computer for 5 days now. Woke up to the kernel panic error this morning. Fans were running crazy last night after a long FaceTime session then did some LR editing. I'm not at all familiar with code, tech errors, etc but wanted to thank everyone on here who is!

Just disabled power nap on both battery and plug in power. First time MacBook owner, was pretty excited to switch from PC and integrate fully into ecosystem. But at $3k I don't like to see these kind of messages in the morning!!

I believe that I'm having the same issue with my 2019 16-inch MacBook Pro. I've been in contact with Apple Support and I've had two kernel panics since trying a clean MacOS install this past weekend. I submitted a feedback report today with both panic logs and sysdiagnose packages: FB7678326.

I've attached the crash reporter logs from today. One occurred with a Caldigit TS3 dock with a Dell 2720Q display connected using USB-C. The other occurred a few hours after with only the apple power cable connected.

I am glad that you pointed this out. Apologies for my carelessness reading that article, and you're right about its misinterpretation on error messages. It is quite possible that the author came up with that guess because KP mostly happens on MacBook Pro 16'' (i7 or i9), which is also the only MacBook Pro (current generation) with dual graphics cards. Although we cannot fully rule out the possibility of GPU issue, clearly the author cited the wrong case and nothing about GPU could be inferred from that error log.

BTW, my error message is all the same, except that my Mac OS version is newer (macOS Catalina 10.15.4 Supplemental Update (19E287)).

Bug report on Mr. Macintosh blog is probably the most precise and up-to-date one about this KP issue. It avoids potential errors by simply (but accurately) describing problems, instead of making ambiguous guess about the cause. In fact, It is quite impossible to confirm any specific cause from the error report (If not an Apple engineer).

The whole blog is awesome, too. Thank you for recommending! It helps a lot!

I've got this problem too.

• Tried the following:
• SMC reset
• PRAM reset
• New install without deleting
• Clean install via net recovery.
• Tried every combination with and without USB hardware plugged in.
• different Mac Users etc.

((I had Graphics switching always on))

panic(cpu 2 caller 0xffffff800d216487): "AppleIntelFramebuffer::setPowerState(0xffffff86a24b8000 : 0xffffff7f90706d88, 1 -> 0) timed out after 45641 ms"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.101.6/iokit/Kernel/IOServicePM.cpp:5296
Backtrace (CPU 2), Frame : Return Address

panic(cpu 0 caller 0xffffff800e016487): "ATY,Boa::setPowerState(0xffffff86a3711000 : 0xffffff7f915abd88, 2 -> 1) timed out after 45522 ms"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.101.6/iokit/Kernel/IOServicePM.cpp:5296
Backtrace (CPU 0), Frame : Return Address

panic(cpu 14 caller 0xffffff8018a16487): "AppleIntelFramebuffer::setPowerState(0xffffff86adbce000 : 0xffffff7f9bfb9d88, 1 -> 0) timed out after 46023 ms"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.101.6/iokit/Kernel/IOServicePM.cpp:5296
Backtrace (CPU 14), Frame : Return Address

panic(cpu 0 caller 0xffffff801ec91b2c): Sleep transition timed out after 180 seconds while calling power state change callbacks. Suspected bundle: com.apple.iokit.IOGraphicsFamily. Thread 0x8c4bd.
Backtracing specified thread
Backtrace (CPU 0), Frame : Return Address

I think Apple don't know how to handle this problem.

Next: Now i gonna try Powernap off.

After some days without any problems and quit heavy using I think the problem could be solved under certain circumstances:

• MBP 16" with the lowest available configuration. No special graphic adjustments or special software in using, just the standards for office. Power nap is still on. Using with power plug in and without. Multiple times closing and opening the MBP. Sometimes with longer breaks.

After the known kernel panics with opening the book I have done the following steps, which were helpful, apparently at least:

1. SMC/VRAM-Reset
2. Turning of the Mac, waiting a view minutes, turning on.

It seems the low profile MBP 16" (probably the graphic unit) haven't has such a deep problem. Especially these steps helps although the power nap feature is on.

Of course I can't say that it helps anybody with the same kind of MBP 16" but in my case the problem is really solved.

Good luck to anybody!

Thanks for confirming. That’s disappointing to say the least...

It looks like this happened ~4.5 hours after the last boot. If you don’t mind me asking,

1. Do you recall how long the system was awake before this crash?
2. Was the system under heavy load (e.g. managing raw camera files, video files, gaming, etc.)?
3. Was the system plugged in or on battery?
4. Do you have power nap enabled or disabled?

FWIW, I’m getting the same crash regardless of power nap settings, but others have reported improvements/fixes...

Had the same problem, solved it 4 days ago.

Status here

My GPU Panic sleep problem is still solved. I have since installed my video-rendering tools, my developer tools, all my other stuff.

My energy saving stuff is back to normal.

Having it gooing to sleep on power, on batteries no problems so far.

Running 10.15.4

Solution for me was

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.

Solution details

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:-)

NP -- happy to help! I had a similar week-long streak without crashes; certainly made troubleshooting a lot more difficult!

I should probably add a few quick words of caution for anybody else wishing to reproduce this bug by repairing the Photos library:

1. Since the Photos repair (Cmd+Opt while opening) last night, my laptop has crashed every time I wake it from sleep (much like when I first upgraded to 10.15.4). The repair/sync process usually takes ~3-5 days for me (my library has 13k photos/368GB, and my ISP is 400mbps x 50mbps).
2. Be sure to make a backup copy of your Photos library before repairing -- don't rely on iCloud!
3. I'm currently seeing some very strange glitches in Photos.app; the worst is that, if I delete a photo while I'm viewing it, it actually removes the photo immediately preceding it from my library. But I've experienced this on 10.15.0 (RTA has been pending bug fix since December), so it might be an issue with my iCloud library...

I'm curious if the common denominator here is iCloud Photos sync, iCloud storage in general (e.g. iCloud Drive, Messages, etc.), or anything during power nap (e.g. Time Machine). Anyway, I'm about to test with power nap disabled again to see if it impacts the frequency of kernel panics...

I just noticed an announcement in Feedback Assistant with 10.15.5 release notes:

“

macOS Catalina 10.15.5 (19F72f) Release Notes

Notes and Known Issues

Finder

Resolved Issues

• Large data transfers to RAID volumes no longer cause Finder to become unresponsive. (61307708)

“

I haven’t had a chance to load 10.15.5 on my machine yet, and haven’t received a reply to my FBA case since 4/24, so I’m concerned...

@ian.deutsch: Thanks, certainly looks like the same issue; relayed your FB#!

@jensche21: Could you let me know how you reached this specialist? Do you have an enterprise support account? I haven’t been able to speak to anybody beyond a Sr. Advisor (in iOS, macos, creative media and customer relations)... Any tips greatly appreciated!

Actually, it *might* be under this one:

• Fixes a stability issue with uploading and downloading media files from iCloud Photo Library while your Mac is asleep

I can reliably reproduce thIs kernel panic by causing a large amount of data to be uploaded via iCloud photos while the computer is asleep (repairing the library does it for me every time). That said, my laptop has been at Apple for repair (unrelated coffee spill), so I won’t be able to verify until sometime tomorrow...

It’s *unbelievable* how many Catalina bugs I’ve encountered due to Photos. I’m just hoping they’ve also fixed the metadata bug introduced in 10.15.0, but despite all of my open support and FBA tickets, and SERIOUS data loss issues, NOBODY AT APPLE HAS FOLLOWED UP. I gave them steps to reproduce this bug; you’d think they’d at least tell me a fix was released like they promised to do...

Gotta say, I don’t feel entitled to anything special; but after doing so much work to just restore my photos and have a reliable machine, being brushed off by Apple like this is totally unacceptable. If the bugs were in open-source code, I wouldn’t complain, but I can’t keep supporting MacOS if the threat of losing data and functionality for a year or more is always looming. Anybody know how to bring up the larger issues of stability and support problems with Apple in a meaningful way? Like to a VP of engineering?