Macbook Sleep Wake failure in EFI (Failure code:: 0xffffffff 0x0000001f)

I had the same problem, and finally found a very odd solution. In my case, after a lot of frustrating work, I traced the problem to an old USB hub I was using on my new mac. Once I disconnected the old USB hub, the problem immediately stopped. In my case, it was surprising and very lucky to discover that the problem seemed to be associated with an attached electronic component. Hope this helps you.

Just got my new 2019 16" MacBook Pro two days ago! I was so excited until the same day I unboxed it I started to notice this problem. 2019 16 macbook pro sleep wake failure 0xffffffff 0x0000001f. I contacted apple and spent a couple of hours on the phone trying everything. I asked if he heard of this issue before and was told not exactly. How can that be true when reading this thread it appears a lot of people are having the same issue. In order for me to use this without having to hard reboot is to shut down the system after use. Not happy with apple right now. other than this pain I love it.

Since i recently swapped out my SSD for a OWC Aura Pro X2, as I posted on here I too been having this issue. Since its the only modification I have done has lead to this problem. I visited the OWC support website and found this link: https://eshop.macsales.com/Service/Knowledgebase/Article/26/785/NVMe-SSDs-Standby-Mode-Issue

Seems like they are aware of the issue and reported to apple. The current workaround is going to terminal and using "sudo pmset -a standby 0". Im gonna try this see if this works

NVMe SSDs: Standby Mode Issue

Created on: January 3, 2020

Last updated: February 25, 2020

Drive type: NVMe SSDs running macOS 10.13 or later (as boot volumes)

• Aura Pro X
• Aura Pro X2
• Aura N 

Please note that some customers have reported an issue with our NVMe based SSDs that relates to use of a lesser known macOS 'Sleep' behavior called ’Standby Mode.' By default, some Mac models will enter Standby mode after they have been sleeping for 3 hours. The issue we are investigating is a system crash which can sometimes occur while attempting to wake a Mac from this Standby mode. Afterward a panic log will be displayed. The top few lines of the log will look similar to the code shown below. 

*** Panic Report ***

panic(cpu 2 caller 0xffffff7f9c8e082a): nvme: "IONVMeController::HandleControllerPowerOff, ShutdownNVMe() completed with status = 0xe00002c9\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-356.30.6/IONVMeController.cpp:2011

While we cannot always reproduce it, we have identified the issues being related to Apple's NVMe system resources. We have submitted a bug report to our contact at Apple, and are concurrently evaluating the possibility of a driver-level solution for our customers. In the meantime, please use the simple workaround below to prevent your system from entering Standby mode when it is sleeping.

Workaround

1. Open the Terminal app
2. Type the following: 

sudo pmset -a standby 0 

1. Press Return
2. Quit the Terminal

This prevents the computer from entering Standby mode while the computer is in normal Sleep mode. From this point, allowing the computer to return to sleep and then waking the computer, should prevent the kernel panic from occurring. Initial findings suggest this will not significantly impact battery power or related issues. The system should behave as it normally does. To confirm that the above setting was properly set open the macOS System Report, select the 'Power' item in the sidebar, and then check the 'Standby Enabled' value. It should say 0.

Hi Team , I am facing this issue from past 1 year, i had number of calls with mac support went to service center and all they did was rolled back my OS to Sierra and worked fine for 8 months and now i am getting same problem. it goes to sleep it wont wake up.

1. Folder with question mark symbol- when this happens i turn off the system and click Option+R then it will give me option to select the startup disc. This work every time.
2. When the system is not used more than 5 hrs it wont turn on you can see the mac symbol is lit.

Then you need to - Reset NVRAM or PRAM on your Mac - > https://support.apple.com/en-us/HT204063

These are the 2 steps i am doing right now and it works, there is no solution from Apple support regarding this error , they say might need to change the mother board with is almost half the price of the mac.

Hope to see a permanent solution for this from any experts. :)

I have the same on a 2019 Macook Air (Retina), 10.15.2 (19C57

Sleep Wake failure in EFI

Failure code:: 0xffffffff 0x0000001f

Please IGNORE the below stackshot

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

Date/Time: 2019-12-26 15:14:12 +0100

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

Architecture: x86_64

Report Version: 29

Data Source: Stackshots

Shared Cache: 0x10cf4000 A9017781-3D05-3E5B-B9CE-DDD70DF7E523

Event: Sleep Wake Failure

Duration: 0.00s

Steps: 1

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

Time Awake Since Boot: 18s

Process: swd [299]

Architecture: x86_64

Footprint: 420 KB

Start time: 2019-12-26 15:14:12 +0100

End time: 2019-12-26 15:14:12 +0100

Num samples: 1 (1)

Thread 0x9fb 1 sample (1) priority 3 (base 4)

<thread QoS background (requested background), thread darwinbg, process darwinbg, IO tier 2>

1 start + 1 (libdyld.dylib + 108541) [0x7fff73f0b7fd] 1

1 ??? [0x101c33454] 1

1 ??? [0x101c331dd] 1

1 __stack_snapshot_with_config + 10 (libsystem_kernel.dylib + 136138) [0x7fff7406c3ca] 1

*1 ??? [0xffffff80002e3206] 1

*1 ??? [0xffffff800099acba] 1

*1 ??? [0xffffff80008b3bc1] 1

*1 ??? [0xffffff8000306467] (running) 1

Binary Images:

0x7fff73ef1000 - 0x7fff73f26fff libdyld.dylib (733.8) <8E2D3DED-0756-37A0-9D55-B9264CA020B4> /usr/lib/system/libdyld.dylib

0x7fff7404b000 - 0x7fff74077fff libsystem_kernel.dylib (6153.61.1) <90F8650F-D3A9-38B3-BB8C-B5D3686393BC> /usr/lib/system/libsystem_kernel.dylib

Model: MacBookAir8,2, BootROM 1037.60.58.0.0 (iBridge: 17.16.12551.0.0,0), 2 processors, Dual-Core Intel Core i5, 1.6 GHz, 8 GB, SMC

Graphics: kHW_IntelUHDGraphics617Item, Intel UHD Graphics 617, spdisplays_builtin

Memory Module: BANK 0/DIMM0, 4 GB, LPDDR3, 2133 MHz, 0x80AD, 0x483943434E4E4E435054414C42522D4E5644

Memory Module: BANK 1/DIMM0, 4 GB, LPDDR3, 2133 MHz, 0x80AD, 0x483943434E4E4E435054414C42522D4E5644

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x843), wl0: Nov 8 2019 11:47:53 version 9.112.2.1.32.5.37 FWID 01-a63bbadf

Bluetooth: Version 7.0.2f4, 3 services, 27 devices, 1 incoming serial ports

Network Service: Wi-Fi, AirPort, en0

USB Device: USB3.0 Hub

USB Device: Mass Storage Device

USB Device: USB 3.0 Bus

USB Device: USB2.0 Hub

USB Device: Plantronics Savi 7xx-M

USB Device: USB 2.0 BILLBOARD

USB Device: USB Billboard Device

USB Device: Apple T2 Bus

USB Device: Apple Internal Keyboard / Trackpad

USB Device: Headset

USB Device: Ambient Light Sensor

USB Device: FaceTime HD Camera (Built-in)

USB Device: Apple T2 Controller

Thunderbolt Bus: MacBook Air, Apple Inc., 47.1

#Metoo

I'm also getting to this same issue with Mac bookpro 2015 version. mine has additional issue where hard turn off in between every 2 to 3hrs for this not getting any error report. below one is, when put in sleep then continue it will not wake as usual. have to press couple of time the power button to up.

------------------------------

Sleep Wake failure in EFI

Failure code:: 0xffffffff 0x0000001f

Please IGNORE the below stackshot

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

Date/Time: 2019-12-28 11:51:53 +0800

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

Architecture: x86_64

Report Version: 29

Data Source: Stackshots

Shared Cache: 0x108d6000 E157B4D9-F0F1-3D59-8492-740F02DE20C1

Event: Sleep Wake Failure

Duration: 0.00s

Steps: 1

Time Awake Since Boot: 17s

Process: swd [266]

Architecture: x86_64

Footprint: 416 KB

Start time: 2019-12-28 11:51:53 +0800

End time: 2019-12-28 11:51:53 +0800

Num samples: 1 (1)

Thread 0x783 1 sample (1) priority 4 (base 4)

<thread QoS background (requested background), thread darwinbg, process darwinbg, IO tier 2>

1 start + 1 (libdyld.dylib + 70661) [0x7fff745f9405] 1

1 ??? [0x10bd13454] 1

1 ??? [0x10bd131dd] 1

1 __stack_snapshot_with_config + 10 (libsystem_kernel.dylib + 135942) [0x7fff74762306] 1

*1 ??? [0xffffff80002e7206] 1

*1 ??? [0xffffff800099b999] 1

*1 ??? [0xffffff80008b4a31] 1

*1 ??? [0xffffff800030a387] (running) 1

Binary Images:

0x7fff745e8000 - 0x7fff7461dfff libdyld.dylib (732.8) <98960E27-A08B-36DA-A5CB-8538B2D6757E> /usr/lib/system/libdyld.dylib

0x7fff74741000 - 0x7fff7476dfff libsystem_kernel.dylib (6153.11.26) <4CE9D54A-A975-348E-B878-EE74EDFC956B> /usr/lib/system/libsystem_kernel.dylib

Model: MacBookPro12,1, BootROM 188.0.0.0.0, 2 processors, Dual-Core Intel Core i5, 2.7 GHz, 8 GB, SMC 2.28f7

Graphics: kHW_IntelIris6100Item, Intel Iris Graphics 6100, spdisplays_builtin

Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1867 MHz, 0x02FE, 0x4544464132333241324D412D4A442D460000

Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1867 MHz, 0x02FE, 0x4544464132333241324D412D4A442D460000

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x133), Broadcom BCM43xx 1.0 (7.77.105.1 AirPortDriverBrcmNIC-1429)

Bluetooth: Version 7.0.0f8, 3 services, 27 devices, 1 incoming serial ports

Network Service: Wi-Fi, AirPort, en0

Serial ATA Device: APPLE SSD SM0128G, 121.33 GB

USB Device: USB 3.0 Bus

USB Device: Bluetooth USB Host Controller

Thunderbolt Bus: MacBook Pro, Apple Inc., 27.1

I got the same error on my iMac 2019 (Failure code:: 0xffffffff 0x0000001f). In addition, often I would have to turn off power to my iMac to be able to reboot. After days of working on the problem (Apple had no idea why this was happening), I discovered that it was my USB hub. It was an older hub, and whenever I plugged it into the back of my iMac I would get this Sleep Wake failure after about 3 minutes and the machine would reboot. When I removed the hub and plugged devices directly into the back of my iMac, everything worked fine.

Same issue. MacBook Pro late 2013.

After looking around I found it is related to the standby mode in which the Mac enters after going to sleep for N amount of seconds. The standby mode is enabled by default but it can be disabled or modified.

Here I found useful information about sleep and hibernation modes and how to modify them: https://www.garron.me/en/mac/macbook-hibernate-sleep-deep-standby.html

Apparently, in my case, the problem happens after the computer enters standby mode. It's unable to wake up. For example, if my MacBook enters sleep mode and in power management settings is "standbydelay 600" (meaning waiting 600 seconds in sleep mode before entering standby mode), my MacBook wakes up without problem only if I wake it up before 10 minutes, but after 10 minutes it crashes.

There are many issues that can cause this, but after running many tests, I came to the last resource recommended. I ran the Apple Hardware Test and apparently my SSD has an issue, which probably is related to Catalina because I think it didn't happen before the update. Although not sure about this, I bought this MacBook used and it came with Mojave but as soon as I got it I updated to Catalina.

The Macbook has no other issues as far as I can see. In the end I just disabled standby mode and the problem disappeared completely, with the only problem that the battery keeps draining during sleep mode, which in principle, is the reason for the stand by mode, to preserve battery.

Having the same problem (mid 2012 MBP running Catalina). Battery will drain like crazy. Seems like it never really "goes to sleep". If the battery is below 40% this is almost a guarantee. When it starts back up I get a double startup. Screen will flash then reboot a second time. Really annoying. Just installed a brand new battery to try to fix the problem but no fix. Here is my screenshot.

Sleep Wake failure in EFI

Failure code:: 0x01310875 0x0000001f

Please IGNORE the below stackshot

I have the same problem on my MacBook Pro non-retina 13" 2012 with SSD (Samsung, replaced it myself) and new battery.

As suggested on Reddit, a workaround is the following:

sudo pmset -a standby 0

But this is not a fix as the Mac will not really "sleep" anymore and battery drains faster. It just prevents the random shutdowns/reboots.

Apple has to fix this, my MacBook is hardly usable like that!

I have the same problem on my MacBook Pro non-retina 13" 2012 with SSD (Samsung, replaced it myself) and new battery.

As suggested on Reddit, a workaround is the following:

sudo pmset -a standby 0

But this is not a fix as the Mac will not really "sleep" anymore and battery drains faster. It just prevents the random shutdowns/reboots.

Apple has to fix this, my MacBook is hardly usable like that!

wb127 wrote:

Having the same problem (mid 2012 MBP running Catalina). Battery will drain like crazy. Seems like it never really "goes to sleep". If the battery is below 40% this is almost a guarantee. When it starts back up I get a double startup. Screen will flash then reboot a second time. Really annoying. Just installed a brand new battery to try to fix the problem but no fix. Here is my screenshot.

Same for me. We have the same MacBook and the same error message. And just like you I replaced my battery a few weeks ago, too!

Same problem here.

MBP Mid 2017, 1TB SSD, 16GBRAM, i7

Issue started after updating on 10.15.4 Catalina. No Problem at all with 10.15.3

And one out of 4 TB3 ports doesn't respond anymore either. No Charging nothing.

And the battery goes extremely quickly empty in idle mode. 4h = -30%

But with the OS running, the battery consumption is normal.

Had charging problems even for a short time, with the power supply connected. It charged for five seconds, five seconds off.

None of these problems were present in 10.15.3.

Same problem after upgrading to 10.15.4 with slightly different error code:

Failure code:: 0x0171260e 0x0000001f

MBP15, 2014

Resetting NVRAM/SMC did not help.

Disabling standby for now:

sudo pmset -a standby 0
sudo pmset -a autopoweroff 0

I've found out that my EFI is not being updated and is stuck at version 149.0.0.0.0 (MBP112 149 201809171514 Release B&I). Reinstalling Catalina did not help. I also tried `efiupdater` (and also bless) with EFI payload from FirmwareUpdater.pkg from Catalina Installer App, which runs with no errors, but after reboot/shutdown the EFI version is still 149. Seems the actual upgrade during reboot is failing, but I have no idea where to find the logs. Is there any other way to force the upgrade?

Hi guys, I just started having the same problem as many others without any visible reason. I googled a lot, tried to reset nvram & smc, I found a way to fully disable hibernation - but that's not a good option. What I discovered for my problem is that it only occurs when Mac is on battery power (without AC connected) and sleeps for a long time – for example if I leave it during the night without charging in sleep mode, in morning I will have a crash. During the short sleeps in daytime (2-3-4 hours) it does not crash! Could anyone suggest a solution, please, as I could not find anything except total disabling of hibernation? Strange that there are many people with that problem, but no any solution or fix ar even any reply from Apple.

MacBook Pro 15 mid 2017