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

Ok, I think found a temporary solution that works for me, but I'm afraid most of you won't like it ... I installed BootCamp and Windows 10. In Windows, so far, everything seems to be working without problems. It's been working while charging, with a full battery on AC and on battery only, also checking in all these power situations whether sleep works. So far no hiccups.

This proves to me that it's not a hardware problem - I've already changed the battery and was contemplating to buy a new charger.

So, for now, I'll be using windows until Apple fixes the problem.

Me too. I found a thread on reddit. If you disable hibernation in terminal, it will fix it.

sudo pmset -a standby 0

Also, if you replaced the original drive with an SSD, OWC posted this:

https://eshop.macsales.com/Service/Knowledgebase/Article/26/785/NVMe-SSDs-Standby-Mode-Issue

Sorry, stlgal: I found it on a Reddit thread. https://www.reddit.com/r/MacOS/comments/dme38s/sleep_wake_failure_in_efi/

To disable hibernation, the command in terminal is: sudo pmset -a standby 0

To re-enable hibernation, command in terminal is sudo pmset -a standby 1

But that's insane you'd have the issue with a brand new MBP. I'd call Apple Support. It's a Catalina bug, and they need to fix it.

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

@Ericz9001 You can get all that information from the command line if you want to check if that is your issue. Its explained in the article below.

https://eclecticlight.co/2019/10/08/which-efi-firmware-should-your-mac-be-using-version-4/

Simply run the apple command line. Get the returned values for the firmware and then validate that the firmware is a valid version for the OS your running. The program simply pulls together alot of information that is available to trouble shoot the MAC but if you would rather be in CLI to troubleshoot yourself then the information to do so is provided as well.

My Standby is set to 0 since 3-4 weeks and I have not seen the issue anymore.

Any sign of an update that will allow us to switch back the standby to as it was? Is there a kind of a beta program where we can follow whether Apple is actually working on this?

thanks!

Similar issue on new 2019 MBP15, less than a month old. Intermittent, not always. Usually happens after a very long nap, more than 12 hours, and body was warm, seems stuck in some process.

Sleep Wake failure in EFI

Failure code:: 0x03000010 0x0000001f

Please IGNORE the below stackshot

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

Tried many things - reinstall MacOS, reset PRAM, reset SMC, turn off FileVault, update to 10.15.5, all failed. Suspect hardware but unsure after reading so many having similar issue. Modified Standby Delay and High Standby Delay to 1800 and 3600, might lessen the time to show symptom, however not showing no-wake after the shorter delays but only after much longer period (probably >12 hours), and intermittently.

There is one way to kind of 'fix' this problem, which is Safe-Boot. Boot into Safe Mode and reboot afterward, laptop wakes everyday without problem for a week, even after very long nap, until my itchy hands did SMC reset and the next morning failed to wake.

Contacted Apple.

I am having the same issue. (Error log below)

MacBook Pro (Retina, 15-inch, Late 2013)

2.3 GHz Quad-Core Intel Core i7

16 GB 1600 MHz DDR3

NVIDIA GeForce GT 750M 2 GB

Intel Iris Pro 1536 MB

I am currently on 10.15.6 but had the issue on 10.14 as well. My issue started after I installed a new 1TB SSD.

Sleep Wake failure in EFI

Failure code:: 0x0171260e 0x0000001f

Please IGNORE the below stackshot

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

Date/Time: 2020-06-04 21:00:01 -0500

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

Architecture: x86_64

Report Version: 29

Data Source: Stackshots

Shared Cache: 0x5c11000 3028322E-C0F7-3102-94AC-7894EACA1D15

Event: Sleep Wake Failure

Duration: 0.00s

Steps: 1

Time Awake Since Boot: 69s

Process: swd [304]

Architecture: x86_64

Footprint: 476 KB

Start time: 2020-06-04 21:00:01 -0500

End time: 2020-06-04 21:00:01 -0500

Num samples: 1 (1)

Thread 0x91c 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) [0x7fff6d2b9cc9] 1

1 ??? [0x10192f454] 1

1 ??? [0x10192f1dd] 1

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

*1 ??? [0xffffff80002c4206] 1

*1 ??? [0xffffff8000985ab7] 1

*1 ??? [0xffffff800089e501] 1

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

Binary Images:

0x7fff6d29f000 - 0x7fff6d2d5fff libdyld.dylib (750.6) <15A0003F-CB33-3A15-BEC2-84E7DD60DAF9> /usr/lib/system/libdyld.dylib

0x7fff6d3fa000 - 0x7fff6d426fff libsystem_kernel.dylib (6153.140.21) <E5593D55-A9BC-3574-A728-9AFC2787E593> /usr/lib/system/libsystem_kernel.dylib

Model: MacBookPro11,3, BootROM 160.0.0.0.0, 4 processors, Quad-Core Intel Core i7, 2.3 GHz, 16 GB, SMC 2.19f12

Graphics: kHW_IntelIrisProItem, Intel Iris Pro, spdisplays_builtin

Graphics: kHW_NVidiaGeForceGTX750MItem, NVIDIA GeForce GT 750M, spdisplays_pcie_device, 2 GB

Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x02FE, -

Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x02FE, -

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x134), Broadcom BCM43xx 1.0 (7.77.111.1 AirPortDriverBrcmNIC-1610.1)

Bluetooth: Version 7.0.6f3, 3 services, 27 devices, 1 incoming serial ports

Network Service: Wi-Fi, AirPort, en0

USB Device: USB 3.0 Bus

USB Device: Internal Memory Card Reader

USB Device: Apple Internal Keyboard / Trackpad

USB Device: BRCM20702 Hub

USB Device: Bluetooth USB Host Controller

Thunderbolt Bus: MacBook Pro, Apple Inc., 17.1

I think I found a solution, which at least suites me. I ran a command "sudo pmset -a standby 0", which as I understand disables deep hibernation. It make battery life shorter as people say, but for my MBP 2017 it is 1-2% per night – maybe it was even the same before, I never noticed it. Anyway, that is ok for me and I do not have crashes now. You can also google other settings for pmset.

PS If you want to bring standby back to default, run "sudo pmset -a standby 1"

Hope this helps someone

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 did all the tests, the engineers suggested and they couldn't work it out. I have to take it to an Apple shop to be looked at when they open 🤷

I typed this into terminal the other day to see if this help. It disables the hibernate mode.

So far, it's not black screened since

sudo pmset -a autopoweroff 0

Anyone else experiencing any improvements on this issue since the latest Big Sur 11.2.2 update? I was mitigating the issue by disabling power naps, wake functions etc. and since the latest update I went ahead and re-enabled all available functions relating to battery/sleep/wake for power saving, so far so good. If this is a fix, I will be very happy that it was addressed, although it will be with some disappointed with Apple for releasing an OS upgrade in such a way that has lead a whole bunch of us to have post in this support discussion to feel noticed - this seems scarily reminiscent of MS windows philosophy of "release first and damage control later" software development and resolution tactics delivered back in the day to enable product releases.

I personally have been using Macs since the first appeared on the market, and updating my Mac OS has usually generated excitement and interest, and in my experience, there were very few to no glitches, consistently. And there were not near as many patches back to back following the OS upgrades as there are now - not sure of the timing of these changes,, but sure feels like a change has occurred.

Keeping my fingers crossed :)

My MacBook Pro 15" (2018) 2.9 GHz Core i9 w/ 32GB of RAM just started having this sleep-wake EFI failure AFTER the 11.2.3 update. I don't recall having this issue prior to 11.2.3. It has happened twice (most recently just a few moments ago) since 11.2.3 installed a few days ago.

Hi, I recently disabled standby and so far has not faced the issue. Can you double check if standby is indeed 0 in system info?