MBP 2018 crashed while sleeping

Same problem here. 13" MB 2015, retina screen. Error message: Sleep transition timed out after 180 seconds while calling power state change callbacks etc etc.

The reason I switched from Windows to Mac was that I was fed up with error messages and now it's starting all over again... I certainly hope Apple comes with a fix. In the meantime guess I'll have to disable Bluetooth.

I have been having this problem since updating to Mojave too. All apps are up to date. Here is my error log too. Any suggestions?

Stackshot Reason: Sleep transition timed out after 180 seconds while calling power state change callbacks. Suspected bundle: com.apple.driver.AirPort.BrcmNIC. Thread 0x62482c.

Failure code:: 0x00000100 00000014

I'm having the same issues, posting just in case you figure a fix (+ the header of my report for reference on a MBP 2015, 13 inch). Also having the Bluetooth issues someone mentioned.

UUID: 03D7BBA1-2443-43FC-8D20-7FFA303C6CBC

Stackshot Reason: Sleep transition timed out after 180 seconds while calling power state change callbacks. Suspected bundle: com.apple.iokit.IOBluetoothHostControllerTransport. Thread 0x12b71c0.

Failure code:: 0x00000008 00000014

I'm having exactly the same problem on my MacBook Pro (Retina, 13-inch, Early 2015) macOS Mojave 10.14.2

Any suggestions?

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

This last year I've had so many issues. My macbook pro crashes while sleep and my imac bluetooth keeps becoming unavailable. I am so close to giving up and trying my hand with a custom built windows machine and see what happens. Having everything Apple is not what it use to be.

The same issue:

System Sleep Wake Experienced a Problem

UUID: 2AA2F7A8-A471-4374-921D-7395DAF48618

Stackshot Reason: Sleep transition timed out after 180 seconds while calling power state change callbacks. Suspected bundle: com.apple.iokit.IOBluetoothHostControllerTransport. Thread 0x59a47.

Failure code:: 0x00000008 00000014

================================================================

Date/Time: 2019-03-11 18:57:33 +0800

OS Version: ??? ??? (Build ???)

Architecture: x86_64

Report Version: 27

Data Source: Stackshots

Shared Cache: 0x11e6d000 98950A98-6DA0-3B32-9953-B0B05CFEC4DC

Event: Sleep Wake Failure

Duration: 0.00s

Steps: 1

Time Awake Since Boot: 100000s

I have the same issue as everyone else has described. I found a possible solution on other threads that involved among other things completely reinstalling the OS. I showed this to our IT team and they did the rebuild. It's been about a month and today it happened again for the first time since. Obviously that did not solve the issue. Hoping someday Apple will actually look at these unresolved issues threads and provide some input...

I have also used keeping Bluetooth off when not using it as a workaround, but that's not an acceptable solution for me in my view. I should be able to leave Bluetooth on and expect my computer to work in the morning.

It seems a bit more reliable since the last update (it used to do this almost every time the lid was closed for a few minutes, now it's just most overnights), but not fully fixed.

Is this a hardware issue with our Bluetooth modules, or something in macOS???

Has anyone managed luck talking with Apple Support directly?

Hey everyone the reason why your computer is crashing while it's sleep is going to located right in your console's crash log. What's happening is there's a job that that your CPU is supposed to be doing that maintains the system's performance and it attempts to do a lot of these things while you're not actively using the laptop. While it's sleep. The problem is that that you have Malware on your computer that also wants to work without being disturbed by the user but it has it's own agenda (crypto mining, backdoor opening, password logging, network configuring, profile creating, log hiding cough * cough*) Your system is built to be able to switch tasks when needed by other processes that are engaged with labor intensive jobs . But this only works smoothly when there's only system and legit and tested operations happening.

The engine from a 3D modeling program is probably a persistent malware task's dream dream vehicle and if you leave the keys to the car out, it's gonna take the car out for a hypothetical drive every time the computer goes to sleep. There's a ton of data collection from your computer hence the dropbox crashing because someone has to help these idiots transfer stolen the data to their safe spot while the computer is sleeping.

Obviously those are just two examples of the BS that Apple clearly knows is happening and what their computers are being used for whether you're Mojave or not. They could easily come on here and tell you how to stop the madness but they don't think you'll notice the plant telling you nothing is wrong just update your operating system and securities provisions. That and they don't care.

THE SOLUTION: After a clean re-install do not let you computer go to sleep until you knock out a couple safety moves. Disable your spotlight quickly by dropping your HD disk image into the restricted spotlight access. It's the only way for now but it's not all. Go into your Directories Utility app and restrict terminal access to by problem parent process ID's. This is only supposed to give you some more time. But if you watch your console log, after the first time your computer falls asleep a program is loaded that will make it stay awake where it's supposed t be sleep so that it can work in peace without you inturrupting it.

You can probably find the storage folder deep in hidden folder called . You'll need to run a scrip that will show you all hidden files on you home folder. Navigate to a folder called /VAR/log/ and you should see a folder yapping about some like "POWERMANAGEMENT"... In there you'll find ASL files explaining what Apple is letting people hide on your computer and not about to make them stop so don't ask....

09:26:04.808653 -0700 powerd Kernel Idle sleep preventers: IODisplayWrangler

09:28:18.815615 -0700 powerd Kernel Idle sleep preventers: -None-

09:52:45.116911 -0700 powerd [System: DeclUser BGTask kDisp]

18:31:19.255993 -0700 powerd [System: PrevIdle PrevDisp BGTask SRPrevSleep IntPrevDisp kCPU kDisp]

18:30:59.942032 -0700 powerd DarkWake from Safe Sleep [CDN] due to EHC2/HID Activity:

19:08:16.905018 -0700 powerd DarkWake from Safe Sleep [CDN] due to GIGE/Network:

19:09:02.463895 -0700 powerd Entering Sleep state due to 'Maintenance Sleep':

18:53:24.286782 -0700 powerd DarkWake to FullWake from Safe Sleep [CDNVA] due to HID Activity:

12:45:01.994049 -0700 powerd [System: PrevIdle DeclUser BGTask SRPrevSleep IPushSrvc kCPU kDisp]

Have you found an answer? I have an ALMOST identical message to yours. Failure code has a different second string but otherwise the same. Yours is the most similar to mine that I have seen. Frustrating!

Exactly my failure code:

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

Failure code:: 0x9e233908 00000031

Did anyone found a solution?

@HamachiOtaku... thanks so much for explaining the issue. However, for those of us who aren't as tech savvy as you are, what you've explained is simply high-tech way of saying "go get professional help". To explain my statement, you said:

1. Disable your spotlight - OK... how?
2. By quickly by dropping your HD disk image into the restricted spotlight access - Got it. But HOW do I do it?
3. Go into your Directories Utility app and restrict terminal access to by problem parent process ID's - Again, some detailed instructions would be very helpful.
4. If you watch your console log, after the first time your computer falls asleep a program is loaded that will make it stay awake where it's supposed t be sleep so that it can work in peace without you inturrupting it - Thanks. Do I need to do something? Do I need to go watch my console log? If yes, HOW do I do it?
5. You can probably find the storage folder deep in hidden folder called . You'll need to run a scrip that will show you all hidden files on you home folder. Navigate to a folder called /VAR/log/ and you should see a folder yapping about some like "POWERMANAGEMENT"... In there you'll find ASL files explaining what Apple is letting people hide on your computer and not about to make them stop so don't ask.... - Thanks again. But do I need to do anything specific here?

Again, thanks a lot for providing a solution... but for people like me, who know how to follow instructions, and want to fix this issue, any prescriptive steps would really help.

Regards / SM

I have a brand new 2018 i9/Vega20... getting the exact same error as above, every single night :-(

Lately I have been having the same problem. Additionally, I have noticed that sometimes when I open the notebook it will not have gone to sleep at all and the battery will be low

Same thing. And I am on 10.14.3 on a brand new MBP 15" i9.