MBP 2018 crashed while sleeping

I have the exact same on a Mid 2015 macbook pro on Mojave 10.14.2

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:: 0xc5617ac3 00000031

...

Process: kernel_task [0]

UUID: 56B30885-F9BA-30E8-AD1C-5D59EC243BA9

Architecture: x86_64

Version: Darwin Kernel Version 18.2.0: Mon Nov 12 20:24:46 PST 2018; root:xnu-4903.231.4~2/RELEASE_X86_64

Footprint: 132.06 MB

Start time: 2019-01-16 05:53:54 +0100

End time: 2019-01-16 05:53:54 +0100

Num samples: 1 (1)

...

Binary Images:

*0xffffff7f81122000 - ??? ??? <C5617AC3-A68D-36CE-AC22-7C7C81318961>

*0xffffff7f8156e000 - ??? ??? <FA92A03C-F113-384A-9B1F-B2C52DE7F4D2>

*0xffffff7f81bbb000 - ??? ??? <60380132-AE9F-3720-B7BF-1653155D78BD>

*0xffffff7f81e48000 - ??? ??? <FB5F5585-D0DB-3B4C-A4ED-7E39C196693B>

*0xffffff7f83377000 - 0xffffff7f83408fff IOBluetoothFamily (6009.4.2) <6437483C-5DDE-3E8F-92B5-2F890F3BC952> /System/Library/Extensions/IOBluetoothFamily.kext/Contents/MacOS/IOBluetoothFamily

*0xffffff7f83d60000 - ??? ??? <F677275E-0C32-3CCB-9AE8-FD02558657AB>

*0xffffff7f87075000 - ??? ??? <E8502198-6395-35AA-9DBD-35AD93251D37>

*0xffffff8000200000 - ??? ??? <56B30885-F9BA-30E8-AD1C-5D59EC243BA9>

What is apple doing about this!?

Just to update you, after suffering crashes to black screen or reboots since I bought my MacBook Pro directly from Apple.com 10 months ago, and constantly trying new ideas from the community or waiting for bug fix updates, I finally had the logic board replaced by Apple. This fixed the issue.

I encourage anyone with ongoing crashes that they cannot fix by all the usual methods, to push for a logic board replacement under warranty.

Needless to say, in the end it was not caused by "third party drivers" or anything else, but by Apple selling a faulty product.

I hope this helps others save time, where I did not.

Hi everyone - I've realized that posting here does nothing for Apple getting informed. Instead, I recommend that each of us, when this comes up, send bug report here: https://bugreport.apple.com/web/

The methodology of determining what went wrong is much more robust there. You will be put into contact with engineering to diagnose why this is happening. It is a bit more work but well worth it if it helps squash this most annoying bug.

TLDR: Don't post here. Instead, submit the error messages, together with a sysdiagnose (CMD+OPTION+CONTROL+SHIFT+.[period]) and screenshot to https://bugreport.apple.com/web/.

Hi all, I have a similar situation that reliably occurs each night when I put my Mac to sleep.

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

================================================================
Date/Time:       2019-01-26 08:43:49 +0100
OS Version:      ??? ??? (Build ???)
Architecture:    x86_64
Report Version:  27

Data Source:     Stackshots
Shared Cache:    0x120a9000 625A975A-D48B-352E-AEBF-B45881604FD4

Event:           Sleep Wake Failure
Duration:        0.00s
Steps:           1

Time Awake Since Boot: 66000s



Process:         kernel_task [0]

Architecture:    x86_64
Version:         Darwin Kernel Version 18.2.0: Thu Dec 20 20:46:53 PST 2018; root:xnu-4903.241.1~1/RELEASE_X86_64
Footprint:       71.73 MB
Start time:      2019-01-26 08:43:49 +0100
End time:        2019-01-26 08:43:49 +0100
Num samples:     1 (1)

Then there is a bunch of text from the sample.

Model: MacBookPro12,1, BootROM 180.0.0.0.0, 2 processors, Intel Core i5, 2.7 GHz, 8 GB, SMC 2.28f7
Graphics: Intel Iris Graphics 6100, Intel Iris Graphics 6100, Built-In
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1867 MHz, 0x80AD, 0x483943434E4E4E424C54424C41522D4E5544
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1867 MHz, 0x80AD, 0x483943434E4E4E424C54424C41522D4E5544
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x133), Broadcom BCM43xx 1.0 (7.77.61.1 AirPortDriverBrcmNIC-1305.2)
Bluetooth: Version 6.0.10f1, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SM0256G, 251 GB
USB Device: USB 3.0 Bus
USB Device: 4-Port USB 3.0 Hub
USB Device: Elements 25A2
USB Device: Bluetooth USB Host Controller
USB Device: 4-Port USB 2.0 Hub
USB Device: USB Receiver
Thunderbolt Bus: MacBook Pro, Apple Inc., 27.1

Things to note in my setup:

1. Macbook in clamshell mode (closed)
2. Power cable continually connects macbook to mains
3. HDMI cable continually connects macbook to external 1080p monitor which has a sleep timer or is manually turned off but not disconnected
4. USB RF adapter (Logitech Unifying) remains connected
5. USB 3.0 hub (4x Anker) remains connected
6. Although the OS version field is empty in the report, I have copied the value from the system report

System Version:	macOS 10.14.3 (18D42)

@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

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!

I have a very similar problem with a slightly different error report.

I have been struggling with sleep-wake problems on my 2015 MacBook Pro for several months now.

When I try to wake it after it has gone to sleep, it either (a) takes a very long time to wake up, or (b) requires a hard reset, which also takes a much longer than normal amount of time to complete., both before and after upgrading to Mojave.

The error message reads:

"System Sleep Wake Experienced a Problem"

Comments:

UUID: E0D745B3-FCC7-4D49-A86F-DCCB36691995

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

Failure code:: 0x00000000 00000014

The problem occurs:

-whether I manually put it to sleep or whether it puts itself to sleep

-regardless of how my power save settings are configured

-occurred both in High Sierra and in Mojave, and in Mojave 10.14.1

-continues to happen after I had it serviced by an Apple authorized retailer, who wiped my hard drive and re-installed Mac OS, then re-installed my user files

-continued to happen after I wiped the hard drive again myself, re-installed Mac OS from the web, and did not re-install any of my old data (to avoid any re-corruption).

Ideas??

I've been having similar issues with a MacBook Pro 13" 2018. Crashes around 50% of the time when it goes to sleep.

I actually had the same problems with a 2015 iMac and a 2012 MacBook Pro before that. I've spent a lot of time with Apple Support over the years trying to figure out what the cause could be and not really got anywhere.

The most recent advice was that Rhino (a 3D modelling app) and dropbox were causing crashes. I have currently uninstalled both and while it seems to have improved, I'm still suffering very regular sleep related crashes.

I'm getting pretty fed up if I'm honest.

how did you find that out because i have the same issue

UUID: F6B96A70-B2B8-4BE9-BCF0-0147746DE21B

Stackshot Reason: Wake transition timed out after 180 seconds while calling power state change callbacks. Suspected bundle: com.apple.iokit.IO80211Family. Thread 0x74.

Failure code:: 0x1ae2d173 00000027

Model: iMac18,2, BootROM 166.0.0.0.0, 4 processors, Intel Core i5, 3 GHz, 8 GB, SMC 2.40f0

Graphics: Radeon Pro 555, Radeon Pro 555, PCIe

Memory Module: BANK 0/DIMM0, 4 GB, DDR4, 2400 MHz, 0x802C, 0x344154463531323634485A2D3247334232202020

Memory Module: BANK 1/DIMM0, 4 GB, DDR4, 2400 MHz, 0x802C, 0x344154463531323634485A2D3247334232202020

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x16E), Broadcom BCM43xx 1.0 (7.77.61.1 AirPortDriverBrcmNIC-1305.2)

Bluetooth: Version 6.0.9f2, 3 services, 27 devices, 1 incoming serial ports

Network Service: Wi-Fi, AirPort, en1

Serial ATA Device: APPLE HDD HTS541010A9E632, 1 TB

USB Device: USB 3.0 Bus

USB Device: Expansion Desk

USB Device: USB2.0 Hub

USB Device: USB 2.0 Hub

USB Device: Bluetooth USB Host Controller

USB Device: FaceTime HD Camera (Built-in)

USB Device: USB3.0 Hub

USB Device: My Passport 25F3

Thunderbolt Bus: iMac, Apple Inc., 39.2

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 problem with Mojave too on an early 2015 13-inch MBP with Retina. Latest are installed as well. I also have an Apple Watch and unlocking the computer with it seems to only work intermittently as the Bluetooth Stack seems to stop working.

Here's my error message:

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

Failure code:: 0x00000008 00000014

I also have the same thing:

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

Macbook Pro 13, 2015.

Hi everyone. I also have the sleep timeout problem quite often. (MBP 13 early 15)

My Stackshot:

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

Additionally I also have troubles with my bluetooth being not available after waking up. I suspect there is a common or related reason to those problems.

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