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

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 also have a Macbook Air 2019 with the same problem, even when I open my Mac turned off it doesn't turn on after 1 minute even if I press the on button, technical support says they have a lot of report but none of them have solved that. I have also noticed that sometimes the screen goes and appear a lot of horizontal lines, like if I unplug the screen cable or flex I don't know if it's related.

same issue.

___________________

MacBook Pro (Retina, 13-inch, Mid 2014)

2.8 GHz Dual-Core Intel Core i5

8 GB 1600 MHz DDR3

____________________

Sleep Wake failure in EFI

Failure code:: 0x01511d0e 0x0000001f

Please IGNORE the below stackshot

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

Date/Time: 2020-06-06 11:00:41 -0500

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

Architecture: x86_64

Report Version: 29

Data Source: Stackshots

Shared Cache: 0x2289000 392C6031-6385-344F-9FE6-7A546A529F87

Event: Sleep Wake Failure

Duration: 0.00s

Steps: 1

Time Awake Since Boot: 34s

Process: swd [286]

Architecture: x86_64

Footprint: 392 KB

Start time: 2020-06-06 11:00:41 -0500

End time: 2020-06-06 11:00:41 -0500

Num samples: 1 (1)

Thread 0x76b 1 sample (1) priority 2 (base 4)

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

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

1 ??? [0x1063f2454] 1

1 ??? [0x1063f21dd] 1

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

*1 ??? [0xffffff80002c6206] 1

*1 ??? [0xffffff80009870b7] 1

*1 ??? [0xffffff800089f9c1] 1

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

Binary Images:

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

0x7fff6937a000 - 0x7fff693a6fff libsystem_kernel.dylib (6153.121.1) <84D09AE3-2DA8-3F6D-ACEC-DC4990B1A2FF> /usr/lib/system/libsystem_kernel.dylib

Model: MacBookPro11,1, BootROM 157.0.0.0.0, 2 processors, Dual-Core Intel Core i5, 2.8 GHz, 8 GB, SMC 2.16f68

Graphics: kHW_IntelIrisItem, Intel Iris, spdisplays_builtin

Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343531533641465238412D50422020

Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343531533641465238412D50422020

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

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

Network Service: Wi-Fi, AirPort, en0

USB Device: USB 3.0 Bus

USB Device: Apple Internal Keyboard / Trackpad

USB Device: BRCM20702 Hub

USB Device: Bluetooth USB Host Controller

Thunderbolt Bus: MacBook Pro, Apple Inc., 17.2

Same here

Mid 2012 Macobook Pro 13" with i7 proc

originally diagnosed as an SSD issue so swopped SSD with a new one

Then diagnosed as the HDD cable but still same problem after changing.

With hindsight I think it may have started around the time I installed Catalina

SMC resent appeared to work for a few days but no longer.

Any response from Apple yet

Mine have wake issue also, relatively new machine, made appointment with Genius bar next week.

Doing final trial and continue observation, notice a very strange coincident. I remove all data on SSD and reinstall fresh Catalina, did not install any other apps and not setting up any email account. Let it sleep flat on desk, a bit surprise no problem waking up even after long nap the last few days. Earlier today put the Mac on a tilted stand, around 35-40 degree, put to sleep, unable to wake. I've always put it on this stand previously and continue having problem waking up, only the last few days left it flat on desk as I'm preparing to send it back to Apple, and put my old MBP on the stand instead. Old MBP running Sierra, no wake issue.

Can't have anything to do with sleep orientation, right?

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.

This is interesting. Im using an external Dell as well (U3219Q) and first i suspected its happening only when it wakes while connected to the Dell. But in the meantime it happens without the external Monitor as well.

I even tried restoring to 10.15.4 but it still happens, suspecting a kind of firmware or something gets updates while installing 15.5 that causes this.

Im also getting this Error now when i restart my MacBook...

panic(cpu 0 caller 0xfffffff0214553dc): x86 global reset detected

Debugger message: panic

Memory ID: 0xff

OS version: 17P5300

macOS version: 19F101

Kernel version: Darwin Kernel Version 19.5.0: Tue May 26 20:16:42 PDT 2020; root:xnu-6153.121.2~1/RELEASE_ARM64_T8010

Kernel UUID: 123C59BB-125A-31AF-A916-AAF729BE6BE8

iBoot version: iBoot-5540.125.4

secure boot?: YES

x86 EFI Boot State: 0xd

x86 System State: 0x0

x86 Power State: 0x0

x86 Shutdown Cause: 0xbd

x86 Previous Power Transitions: 0x70707060400

PCIeUp link state: 0x1614

Paniclog version: 13

Kernel slide: 0x000000001941c000

Kernel text base: 0xfffffff020420000

mach_absolute_time: 0x418dfd2e3

Epoch Time: sec usec

Boot : 0x5edce33c 0x000f25ac

Sleep : 0x00000000 0x00000000

Wake : 0x00000000 0x00000000

Calendar: 0x5edce613 0x000cda83

Panicked task 0xffffffe0007e8e00: 2982 pages, 215 threads: pid 0: kernel_task

Panicked thread: 0xffffffe000bd9a68, backtrace: 0xffffffe010f234b0, tid: 335

lr: 0xfffffff020ce4764 fp: 0xffffffe010f234f0

lr: 0xfffffff020ce45c0 fp: 0xffffffe010f23560

lr: 0xfffffff020dff1e0 fp: 0xffffffe010f23610

lr: 0xfffffff0212ad62c fp: 0xffffffe010f23620

lr: 0xfffffff020ce3f28 fp: 0xffffffe010f23990

lr: 0xfffffff020ce4280 fp: 0xffffffe010f239e0

lr: 0xfffffff021b1a934 fp: 0xffffffe010f23a00

lr: 0xfffffff0214553dc fp: 0xffffffe010f23a30

lr: 0xfffffff02144680c fp: 0xffffffe010f23aa0

lr: 0xfffffff021448734 fp: 0xffffffe010f23b50

lr: 0xfffffff021445f44 fp: 0xffffffe010f23be0

lr: 0xfffffff02140d3a8 fp: 0xffffffe010f23c10

lr: 0xfffffff02121b5d8 fp: 0xffffffe010f23c50

lr: 0xfffffff02121ae5c fp: 0xffffffe010f23c90

lr: 0xfffffff0212b8514 fp: 0x0000000000000000

I opened a ticket via Chat with apple, the agent was not very helpful and told me that this could only be handled via phone. So they wanted to call me back within an hour. Hour later a received an automated robo-call that told me to wait. After 10 minutes there was an agent wo told me that this would need to be handled by technical principal and the current wait time is over an hour. He then suggested it would be better when they call me back on monday. (It was late Friday). I agreed, they never called back.

I'm an Apple user for 15+ years, never had such a bad experience.

I was having this issue on Mojave. I upgraded to Catalina to see if that would rectify the issue. Still happening. I do believe it is an issue with SSD though. My issue started after I replaced my drive.

It offers the same standby workaround as everyone else eventually suggests - it also explains that all SSDs are prone to this issue. If you do the digging into my previous posts you'll see that I was getting the same error message and resultant research brought me to that OWC article. There IS another somewhere that mentions the EFI sleep wake failure. But if people are looking for a temporary solution and some sort of explanation, the article provides that.

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

I'm having the same issue, though mine seems to be specific to when the battery gets low and the system tries to Sleep. When I get down to 10 min remaining on my battery I get the system notification that my Mac will soon go to sleep if I do not plug it into a power source. I have never stuck around to watch what happens when the system "goes to sleep", but I can tell you what happens when I try to turn my Mac back on: The system powers on by itself as soon as I plug it into a power source, even if the lid is closed, and I hear the boot up sound. The screen is white for a few seconds, then it automatically reboots (with boot up sound). It repeats the last step another time. I finally get to my log in screen and can get to my desktop. All of the applications and windows that were open before the system crash begin to open up. Then I get the error message: Sleep Wake failure in EFI. Failure code:: 0x01790875 0x0000001f. I have a 2012 MBP with a fresh install, reset all the types of RAM and SMC, it has all of the latest software updates, and some hardware upgrades. I had this exact same problem with a prior 2012 MBP, exact same model. It makes me believe the issue is rooted in the software. I'm glad to know its not specific to my old MBP, and it would be awesome if Apply could figure out the bug.

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.

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.