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.

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.

Well, After many conversations and testing, Apple is finally going to replace my 16" 2019 MacBook Pro with a new one. At first they thought it was a software issue, but after the updates failed to resolve the problem they had me wipe it with a clean install of Catalina and the Failure still continued. So they collected my logs and then came to the conclusion that it was a hardware issue and agreed to replace it. I had just purchased my MacBook in April of this year and this Sleep Wake failure in EFI (Failure code:: 0xffffffff 0x0000001f) happened from day one. Now I'm just hoping the new unit is trouble free. I'll keep you posted.

Yes I'm pretty sure its hardware, since i reinstalled my MBP multiple times, and the error kept appearing instantly even in completely empty MacOS Installs. Apple Support basically confirmed that it needs a logic board replacement. Unfortunately the System is 1 year and 2 month old and therefor out of warranty. Repair price is 800 EUR so its basically easier and cheaper for me to get a new one one trow the old one away. Wish I knew that before I put countless hours in troubleshooting and calls with apple support.

Key takeaway for me is: Apple Support is not worth the time. If you can't figure it out with a little googling and fiddling within an hour yourself, apple support won't either.

I have this same issue. I found it to be one of two things for me: (1) the external monitor i was using can cause my laptop to crash and/or (2) the dongle used to connect to the external monitor. Both of these only started with the catalina.

took MOOOONTHS to figure this out for me.

I switched the monitor and it doesn't happen anymore. next is getting a better dongle.

Hopefully this helps someone!

My problem seems to only happen when I disconnect my iPad Pro that had been connected via USB-C to my MacBook Pro 15 (2018). At first I thought it was only when I had been using the iPad as a second monitor (via Sidecar) and failed to disconnect from Sidecar, but today the failure happened when my iPad had been connected solely for charging.

It appears it will happen any time I disconnect my iPad from the MacBook Pro while the MacBook Pro is asleep - regardless of whether the iPad was connected and used as a 2nd monitor, or connected just for charging.

I had this same issue on my MacBook Pro Late 2013. I did the same thing as everyone else, reset PRAM, etc... and even did a clean install of MacOS. Still had the issue.

I had bought the MacBook Pro used and come to find out the place I had bought it from had replaced the SSD with a non-Apple branded SSD and had used an adapter as it's a standard M.2 SSD. (Apple made their connector proprietary) So I ordered and installed an SSD off of Ebay that was taken out of an old MacBook Pro and reinstalled a fresh copy of MacOS on it. I'm happy to report that I've been using it for the last week without any errors or issues.

I can only assume that MacOS is trying to put the drive into deep sleep and cannot because the drive didn't support those commands. I do say this based on the fact that there's an article out there where some non-Apple branded SSD manufacturers have confirmed this to be an issue and they recommend disabling this deep sleep mode.

There sure are a lot of people in these forums trying to get me to install random software to "fix" my problem...

In case nobody checked the article, it appears this Sleep Wake Failure pertains to SSDs -

When the system wakes, the drive isn't waking as quickly - for a moment, the computer thinks there is no storage medium attached and crashes. OWC is aware of the issue and has been working with Apple Support to get a driver fix available. However, this applies to all SSDs not just OWC. As of reading the article, it appears there IS NO FIX besides disabling "Standby Mode". No amount of free software from the App store will fix this problem. Apple will have to push an update.

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.

So, i have this only when a USB-C Monitor is connected. And it seems like to only appear after i updated to 10.15.5. Very unfortunate. Had to issue the 'sudo pmset -a standby 0' workaround to be able to continue to use my mac. It crashed everytime it went to standby with external monitor connected. Not usable at all. Of Course i tried all the other voodoo before like: Again running the 10.15.5 Combo Updater, NVRAM & SMC Reset, Launchagents & Launchdeamons delete in safe mode and what not. Kinds disappointed, this is the kind of stuff you expect from random windows machines.

Sleep Wake failure in EFI

Failure code:: 0xffffffff 0x0000001f

Please IGNORE the below stackshot

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

Date/Time: 2020-06-03 20:46:26 +0200

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

Architecture: x86_64

Report Version: 29

Data Source: Stackshots

Shared Cache: 0xc6b1000 E0432196-FC5E-3A4D-81C3-F4C25E85E387

Event: Sleep Wake Failure

Duration: 0.00s

Steps: 1

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

Time Awake Since Boot: 22s

Process: swd [321]

Architecture: x86_64

Footprint: 416 KB

Start time: 2020-06-03 20:46:26 +0200

End time: 2020-06-03 20:46:26 +0200

Num samples: 1 (1)

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

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

1 start + 1 (libdyld.dylib + 109769) [0x7fff737facc9] 1

1 ??? [0x109e46454] 1

1 ??? [0x109e461dd] 1

1 __stack_snapshot_with_config + 10 (libsystem_kernel.dylib + 135862) [0x7fff7395c2b6] 1

*1 ??? [0xffffff80002c6206] 1

*1 ??? [0xffffff8000987097] 1

*1 ??? [0xffffff800089f9a1] 1

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

Binary Images:

0x7fff737e0000 - 0x7fff73816fff libdyld.dylib (750.5) <7E711A46-5E4D-393C-AEA6-440E2A5CCD0C> /usr/lib/system/libdyld.dylib

0x7fff7393b000 - 0x7fff73967fff libsystem_kernel.dylib (6153.121.2) <9F9902C9-A46F-3CA9-B7F9-5CCFE98FBF75> /usr/lib/system/libsystem_kernel.dylib

Model: MacBookPro15,1, BootROM 1037.120.87.0.0 (iBridge: 17.16.15300.0.0,0), 6 processors, 6-Core Intel Core i7, 2,2 GHz, 16 GB, SMC

Graphics: kHW_IntelUHDGraphics630Item, Intel UHD Graphics 630, spdisplays_builtin

Graphics: kHW_AMDRadeonPro555XItem, Radeon Pro 555X, spdisplays_pcie_device, 4 GB

Memory Module: BANK 0/ChannelA-DIMM0, 8 GB, DDR4, 2400 MHz, Micron, 8ATF1G64HZ-2G6E1

Memory Module: BANK 2/ChannelB-DIMM0, 8 GB, DDR4, 2400 MHz, Micron, 8ATF1G64HZ-2G6E1

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x7BF), wl0: Feb 28 2020 15:24:56 version 9.30.357.35.32.5.47 FWID 01-9ce4adf3

Bluetooth: Version 7.0.5f6, 3 services, 27 devices, 1 incoming serial ports

Network Service: Wi-Fi, AirPort, en0

USB Device: USB 3.1 Bus

USB Device: Apple T2 Bus

USB Device: Touch Bar Backlight

USB Device: Touch Bar Display

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 Pro, Apple Inc., 47.4

Thunderbolt Bus: MacBook Pro, Apple Inc., 47.4

Hey everyone 👋

I had this problem too with MacBook Pro 16' 2019 after installing Catalina 10.15.4. And I have written about it here. But after update on MacOS Catalina 10.15.5 problem was solved. Maybe it will be helpful for somebody

Happy to report that after getting my MBP back from Apple, it has not suffered any sleep wake failure, that's 4 days problem-free. I can confirm now that if you have a new Mac laptop and exhibit persistent sleep wake failure, it is likely hardware, send it back to Apple.

Hello all,

After dealing with this issue since April, and after many conversations with senior support, Apple finally agreed to replace my 16" Macbook Pro with a new one. This Macbook is all good! I can finally enjoy the expensive device. This is a hardware issue. You'll need to repair or replace.

I know all too well what you're going through. I bought my 2019 16" Macbook Pro in April and had this issue from day 1. After many days, and months of troubleshooting Apple finally agreed to replace the Macbook with a new one. It's not a software issue, it's a hardware issue. My new macbook works great. I just got the new one Saturday, June 27th. They also refunded my Apple Care and I repurchased it so the start date is on June 27th 2020. Good luck!

I wanted to share something that seems to have worked for my case.

I did:

sudo pmset resetdefaults

sudo pmset hibernatemode 25

And then I shutdown my MBP and then did a full SMC reset.

So far so good, issue seems to be resolved.