My Macbook Pro 16" is crashing while its at sleep, when it's getting charged. Can someone please help me with this issue.

Every time it sleeps (while plugged in). The message at the top varies a little. But ultimately it is a kernel panic:

panic(cpu 0 caller 0xffffff801b616487): "AppleIntelFramebuffer::setPowerState(0xffffff86b0774000 : 0xffffff7f9ebcad88, 1 -> 0) timed out after 45973 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

0xffffffa79055bb40 : 0xffffff801af215cd 

0xffffffa79055bb90 : 0xffffff801b05a3c5 

0xffffffa79055bbd0 : 0xffffff801b04bf7e 

0xffffffa79055bc20 : 0xffffff801aec7a40 

0xffffffa79055bc40 : 0xffffff801af20c97 

0xffffffa79055bd40 : 0xffffff801af21087 

0xffffffa79055bd90 : 0xffffff801b6c2c7c 

0xffffffa79055be00 : 0xffffff801b616487 

0xffffffa79055be50 : 0xffffff801b615d69 

0xffffffa79055be60 : 0xffffff801b62d2fe 

0xffffffa79055bea0 : 0xffffff801b614b18 

0xffffffa79055bec0 : 0xffffff801af63545 

0xffffffa79055bf40 : 0xffffff801af63071 

0xffffffa79055bfa0 : 0xffffff801aec713e 

I've got the same problem. Multiple cases opened with Apple. They had me do the full erase and setup as new to rule out the software corruption. Thats not the issue. I get a variation of different panic crashes and resulting error messages. Here is the one from today:

Seep transition timed out after 180 seconds while entering darkwake on way to sleep. Suspected bundle: com.apple.iokit.IOGraphicsFamily. Thread 0x74.Seep transition timed out after 180 seconds while entering darkwake on way to sleep. Suspected bundle: com.apple.iokit.IOGraphicsFamily. Thread 0x74.

Chalk up another case right here. This laptop has been a lemon since I bought it at New Year's. Adobe apps crash left and right with no noticeable performance improvement over my late 2013 MBPr.

I don't know about y'all, but I'm not waiting for a fix. If they're swapping logic boards and touch bars, they're hoping a kitchen sink approach will work. I think this is a classic case of 1st gen Apple Product snakebite.

I'm demanding a refund, and if they're wise, they'll allow it or they're losing a 20+ year professional user.

Verrucktftw, thank you. I personally don’t want a workaround. I want it to work without tweaks because it cost me over $2000. Apple says this isn’t a known issue and that it’s probably hardware. I’ll take their word for it since it’s under warranty.

I called Apple today. They said "reinstall MacOS" and I said "I bet you a beer that won't fix it". A guy from the midwest now has to ship a beer to California. It didn't work. Apple is still in denial.

"Apple is still in denial."

No, you're being unreasonable. You can't expect a support agent over the phone to know exactly what's wrong with your machine. You need to send it to Apple to have them inspect your product. Also you do realize that Apple sells more than just the 16" MBP and there are small issues with other products they sell right? They have to go by customer feedback.

It would be nice if Apple only sold ONE product then they would know right away that something isn't perfect and needs addressing, but since they deal with many products and softwares it's unreasonable for a customer to expect a company to know about every quirk or small issue with every product the company offers. Just like you don't know if you're being an annoying neighbor until your neighbor across the street comes to you face to face to bring it to your attention.

You would think that, unlike an annoying neighbor, the most profitable company in the world could afford to have a quality control department responsible for testing software updates before they reach customers. Perhaps that is unreasonable.

"You would think that, unlike an annoying neighbor, the most profitable company in the world could afford to have a quality control department responsible for testing software updates before they reach customers."

It's a customer's responsibility to report issues with THEIR equipment that they PAID for. It's not a company's responsibility to be mind readers. I hope you realize in this BIG MOST PROFITABLE COMPANY that Apple is made up of humans, right? Money doesn't dictate perfection.

[Edited by Moderator]

OK DPJ - I think you won. You are right. Can we drop this now and talk about solutions to our $3000+ machine crashing problem? (Unfortunately there isn't a "not helpful" button to click under these responses.)

verrucktftw wrote:

• Changing the hibernatemode• value to 0 (default is 3) (value 0 may be not suitable for everyone).

Could you please provide a little more detail about how you did this?

Thank you.

Whelp. Powernap turned off worked for 2 days. Just woke my MBP 16 to discover it had, again, crashed.

For those saying Apple isn't responsible for "every tiny detail", consistently kernel panicking machines is not a "little detail". And in the lead up to this laptop, they had been plagued with several years of physical keyboard problems, and billed this 16" as a true "return to form" for pros, complete with a nice marketing campaign touting its power and stability.

SO, all that to say: we were duped. This machine is not a return to form, it's par for Apple these days. Features and functions we didn't ask for, that don't work as advertised, that will probably be abandoned down the road (looking at you, pointless TouchBar).

I'm experiencing same issue with my 2019 MBP 16" and this is insanely frustrating.

panic(cpu 0 caller 0xffffff801de91b2c): Sleep transition timed out after 180 seconds while notifying clients about upcoming system capability changes. Suspected bundle: com.apple.iokit.IOGraphicsFamily. Thread 0x74.

An Apple support rep has already walked me through a reinstall of the OS with no success on the other side.

Each time this has happened my computer has been asleep with power plugged in. Not connected to external monitor.

Enable Power Nap had been turned off.

Laptop spec:

2.4 Ghz 8-core i9 - 64GB 2667 Mhz DDR4 - Intel UHD Graphics 630 1536MB

So I'm experiencing the same problem. I've had the Mac 12 hours. Plugged it into charge for the first time closed the lid, did some housework, opened the lid and I got this error:

panic(cpu 0 caller 0xffffff801b691b2c): Sleep transition timed out after 180 seconds while calling power state change callbacks. Suspected bundle: com.apple.iokit.IOGraphicsFamily. Thread 0x3c2a4.

Backtracing specified thread

Backtrace (CPU 0), Frame : Return Address

0xffffffa402c0b900 : 0xffffff801b0471e8 

0xffffff83c39c3bc0 : 0xffffff801af433f1 

0xffffff83c39c3c30 : 0xffffff801af41c2f 

0xffffff83c39c3c80 : 0xffffff801b0442e9 

0xffffff83c39c3cc0 : 0xffffff801b043b4b 

0xffffff83c39c3cf0 : 0xffffff7f9ebacced 

0xffffff83c39c3d20 : 0xffffff7f9ebc5fa3 

0xffffff83c39c3d30 : 0xffffff7f9ebafcb9 

0xffffff83c39c3dc0 : 0xffffff7f9ebbbeee 

0xffffff83c39c3e00 : 0xffffff801b6152ea 

0xffffff83c39c3ea0 : 0xffffff801b614c14 

0xffffff83c39c3ec0 : 0xffffff801af63545 

0xffffff83c39c3f40 : 0xffffff801af63071 

0xffffff83c39c3fa0 : 0xffffff801aec713e 

      Kernel Extensions in backtrace:

         com.apple.iokit.IOGraphicsFamily(575.1)[D47CA481-C5E5-3F03-9B04-6634DF5F3121]@0xffffff7f9eba4000->0xffffff7f9ebf4fff

            dependency: com.apple.iokit.IOPCIFamily(2.9)[1B1F3BBB-9212-3CF9-94F8-8FEF0D3ACEC4]@0xffffff7f9b911000

BSD process name corresponding to current thread: kernel_task

Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:

19E287

Kernel version:

Darwin Kernel Version 19.4.0: Wed Mar  4 22:28:40 PST 2020; root:xnu-6153.101.6~15/RELEASE_X86_64

Kernel UUID: AB0AA7EE-3D03-3C21-91AD-5719D79D7AF6

Kernel slide:     0x000000001ac00000

Kernel text base: 0xffffff801ae00000

__HIB  text base: 0xffffff801ad00000

I'm experiencing a similar issus on a December 2019 MBP 16", after upgrading to macOS 10.15.5 (I had skipped 10.15.4, and should have skipped this latest update):

"panic(cpu 0 caller 0xffffff801129169c): Sleep transition timed out after 180 seconds while entering darkwake on way to sleep. Suspected bundle: com.apple.iokit.IOGraphicsFamily. Thread 0x74."

It happens after EVERY sleep when an external EIZO monitor is connected via USB-C.

I'm in general dissatisfied with the power nap / sleeping behaviour of the MBP 16". So many times it was draining my battery for no consistent reason.

What a disappointment!

same crash :(

panic(cpu 0 caller 0xffffff800c891b2c): Sleep transition timed out after 180 seconds while notifying clients about upcoming system capability changes.