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

I have two macbook's, one model end 2018 and one model begin 2019.

They both suffer from the same problem with a fresh installation (also reset NVRAM, PRAM, SMC).


The crash reason: Sleep Wake failure in EFI

Failure code:: 0xffffffff 0x0000001f


I already contacted Senior Support for this and have a running case for both.


If you run into the same problem, please let me know here.

To trace down the problem more info of different devices can be useful.


If I get feedback that solves it, I'll post it here.



MacBook Pro 15”, macOS 10.15

Posted on Nov 18, 2019 1:33 AM

Reply
Question marked as Top-ranking reply

Posted on Apr 19, 2020 8:00 AM

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.

Similar questions

241 replies

Jun 13, 2020 10:58 AM in response to fortuitousgoofball

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.

Jun 13, 2020 10:59 AM in response to mariusvw

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


Jun 15, 2020 7:09 AM in response to tobiasb_

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.

Jul 12, 2020 2:37 AM in response to MBSEVEN

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



Sep 2, 2020 6:55 PM in response to mariusvw

Same issue. Macbook Air 2014.


Sleep Wake failure in EFI


Failure code:: 0x0171260e 0x0000001f


Please IGNORE the below stackshot


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

Date/Time: 2020-09-02 20:50:03 -0500

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

Architecture: x86_64

Report Version: 29


Data Source: Stackshots

Shared Cache: 0x88c8000 02FD1F49-8D6E-3525-9FBA-C3B631982301


Event: Sleep Wake Failure

Duration: 0.00s

Steps: 1


Time Awake Since Boot: 31s




Process: swd [394]

Architecture: x86_64

Footprint: 360 KB

Start time: 2020-09-02 20:50:03 -0500

End time: 2020-09-02 20:50:03 -0500

Num samples: 1 (1)


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

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

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

1 ??? [0x108de3454] 1

1 ??? [0x108de31dd] 1

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

*1 ??? [0xffffff80002c1206] 1

*1 ??? [0xffffff8000984c37] 1

*1 ??? [0xffffff800089d7c1] 1

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


Binary Images:

0x7fff6f8ce000 - 0x7fff6f904fff libdyld.dylib (750.6) <789A18C2-8AC7-3C88-813D-CD674376585D> /usr/lib/system/libdyld.dylib

0x7fff6fa29000 - 0x7fff6fa55fff libsystem_kernel.dylib (6153.141.1) <2B6311E6-6240-3EF7-8C87-475B66F7452C> /usr/lib/system/libsystem_kernel.dylib

Model: MacBookAir6,2, BootROM 122.0.0.0.0, 2 processors, Dual-Core Intel Core i5, 1.4 GHz, 4 GB, SMC 2.13f15

Graphics: kHW_IntelHD5000Item, Intel HD Graphics 5000, spdisplays_builtin

Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1600 MHz, 0x80CE, 0x4B3445384533303445452D45474345000000

Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1600 MHz, 0x80CE, 0x4B3445384533303445452D45474345000000

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x117), Broadcom BCM43xx 1.0 (7.77.111.1 AirPortDriverBrcmNIC-1615.1)

Bluetooth: Version 7.0.6f7, 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: BRCM20702 Hub

USB Device: Bluetooth USB Host Controller

Thunderbolt Bus: MacBook Air, Apple Inc., 23.6


Sep 2, 2020 10:29 PM in response to mariusvw

I have the same problem on MacBook Pro (Retina, 15-inch, Mid 2015) running MacOS 10.15.6 (19G2021). This is extremely infuriating.


Stack trace:

Sleep Wake failure in EFI

Failure code:: 0xffffffff 0x0000001f

Please IGNORE the below stackshot

================================================================
Date/Time:        2020-09-03 10:54:16 +0530
OS Version:       ??? ??? (Build ???)
Architecture:     x86_64
Report Version:   29

Data Source:      Stackshots
Shared Cache:     0xada3000 E2DD4194-EFA3-3762-90A9-AA1542988300

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

Time Awake Since Boot: 27s



Process:          swd [402]
Architecture:     x86_64
Footprint:        436 KB
Start time:       2020-09-03 10:54:16 +0530
End time:         2020-09-03 10:54:16 +0530
Num samples:      1 (1)

  Thread 0x916    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) [0x7fff71f5ccc9] 1
    1  ??? [0x104fba454] 1
      1  ??? [0x104fba1dd] 1
        1  __stack_snapshot_with_config + 10 (libsystem_kernel.dylib + 135862) [0x7fff720be2b6] 1
         *1  ??? [0xffffff80002c1206] 1
           *1  ??? [0xffffff8000984c37] 1
             *1  ??? [0xffffff800089d7c1] 1
               *1  ??? [0xffffff80002e49e7] (running) 1

  Binary Images:
        0x7fff71f42000 -     0x7fff71f78fff  libdyld.dylib (750.6)               <789A18C2-8AC7-3C88-813D-CD674376585D>  /usr/lib/system/libdyld.dylib
        0x7fff7209d000 -     0x7fff720c9fff  libsystem_kernel.dylib (6153.141.1) <2B6311E6-6240-3EF7-8C87-475B66F7452C>  /usr/lib/system/libsystem_kernel.dylib



Hope this gets fixed soon.

Oct 20, 2020 6:47 AM in response to Dyrhauge

So this issue has been around for some time now and I originally saw it with High Sierra, which was when I upgrade my SDD to larger storage than what came with my laptop. I personally don't see Apple fixing this issue any time soon as it still happens with the latest macOS Catalina on my system.


My question to those still reading these posts, has anyone tired an older macOS to see if the problem existed on an older OS? I know that sounds funny, maybe even stupid, but I only use my old laptop for a quick surf to download a cooking recipe, check emails, things like that. Therefore I'm willing to try to downgrade the OS if it resolves the issue.


Just trying to make lemonade from some Lemons by Apple.



Nov 18, 2020 3:00 PM in response to rico43

I must agree that 11.1 solved nothing. Big Sur installer required space more than my 128gb 2015 Macbook Air SSD had, so I upgraded to WD 500 gb SSD and did clean install of Big Sur. All went well until I closed the lid and put it on battery. After about a half hour it crashed but could be revived with a restart and crash warning. So Apple has put us between the rock (most people with older 128gb Mac laptops can't upgrade to BS if they full sleep functionality) and the hard place of crash on longer battery sleep (less than an hour in my case is enough to do it). I have tried the Terminal solutions here with no luck.

Dec 23, 2020 10:18 PM in response to mariusvw

Hello everyone


i just had the same problem with one of my customer, change the ssd 128 Apple for a transcend 480 in a Mac air 2013 8Gb 13inches, and upgrade OS X from high Sierra to Catalina 10.15.6 ...


i have read all the discussion, don’t arrive to know if there is a link with the new ssd because not an original Apple one, but, many times I ve did this operation on a lot of Mac air 2013-2017 and MacBook Pro retina 2012-2015 and NEVER had this problem on other Apple computers, every time with transcend or indmem ssd


i will try to get the Mac air again, do a clean install of Catalina on a 128gb original Apple (to see if some firmware needs to be install/reinstall) and put again the 480gb transcend one ...


wait and see ...


hope this could help everyone of you

I will post again in 2021 to tell my results

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

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

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.