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

Mar 7, 2020 8:43 AM in response to ignathesinger

Sleep Wake failure in EFI


Failure code:: 0xffffffff 0x0000001f


Please IGNORE the below stackshot


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

Date/Time: 2020-03-07 11:22:35 -0500

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

Architecture: x86_64

Report Version: 29


Data Source: Stackshots

Shared Cache: 0x7e59000 F6A2218D-AB79-3433-B934-67875204E8A3


Event: Sleep Wake Failure

Duration: 0.00s

Steps: 1


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


Time Awake Since Boot: 24s




Process: swd [449]

Architecture: x86_64

Footprint: 484 KB

Start time: 2020-03-07 11:22:35 -0500

End time: 2020-03-07 11:22:35 -0500

Num samples: 1 (1)


Thread 0xa62 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) [0x7fff6da8acc9] 1

1 ??? [0x10c92a454] 1

1 ??? [0x10c92a1dd] 1

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

*1 ??? [0xffffff80002c8206] 1

*1 ??? [0xffffff8000987337] 1

*1 ??? [0xffffff800089fd41] 1

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


Binary Images:

0x7fff6da70000 - 0x7fff6daa6fff libdyld.dylib (750.5) <B4754829-FE9F-3B8B-8DBF-7C0102BD059E> /usr/lib/system/libdyld.dylib

0x7fff6dbcb000 - 0x7fff6dbf7fff libsystem_kernel.dylib (6153.101.4) <A04C63E1-0FFB-349E-837D-C9ECCD5033AD> /usr/lib/system/libsystem_kernel.dylib

Model: Macmini8,1, BootROM 1037.100.348.0.0 (iBridge: 17.16.14244.5.5,0), 6 processors, 6-Core Intel Core i7, 3.2 GHz, 64 GB, SMC

Graphics: kHW_IntelUHDGraphics630Item, Intel UHD Graphics 630, spdisplays_builtin

Memory Module: BANK 0/ChannelA-DIMM0, 32 GB, DDR4, 2667 MHz, SK Hynix, HMAA4GS6MJR8N-VK

Memory Module: BANK 2/ChannelB-DIMM0, 32 GB, DDR4, 2667 MHz, SK Hynix, HMAA4GS6MJR8N-VK

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x7BF), wl0: Feb 11 2020 11:57:54 version 9.30.357.34.32.5.46 FWID 01-5f73071d

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

Network Service: Ethernet, Ethernet, en0

Network Service: Wi-Fi, AirPort, en1

PCI Card: pci144d,a808, sppci_nvme, Thunderbolt@197,0,0

USB Device: USB 3.1 Bus

USB Device: Apple T2 Bus

USB Device: Headset

USB Device: Apple T2 Controller

Thunderbolt Bus: Mac mini, Apple Inc., 47.4

Thunderbolt Bus: Mac mini, Apple Inc., 47.4

Thunderbolt Device: Portable SSD X5, SAMSUNG ELECTRONICS CO., LTD, 3, 35.1


Mar 8, 2020 1:53 PM in response to wb127

You've pretty much described my case, except that I have a MB Air 2013. I also taught my battery was dead and installed a new one. Recently, I also made a clean install of OSX (didn't restore from Time Machine), but the problem remains. I also think this started happening to me after I installed Catalina.


Besides this, I'm also experiencing an even more annoying problem - when I charge my laptop while working and the percentage gets above 40%, the computer randomly shuts off - it seems to me it goes to sleep, but it won't wake up easily, it does not respond to keyboard, touchpad or power button for about a minute or two. My temporary solution for now is to disconnect the charging cable when that happens and I work on battery.

Apr 19, 2020 4:44 AM in response to mariusvw

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.

Apr 20, 2020 9:14 PM in response to Mihahn

Same here, same MacBook, same error message, same replaced Samsung SSD, same new battery. Mine is the i7 version. I assumed I was just going to deal with this until they tell me my laptop is vintage and I need a new one to fix it. Catalina did seem to be the start of my problems. Word on the street- Even the new 16" MacBooks are doing this, so a new one won't even fix this bug.

Apr 22, 2020 11:12 AM in response to Fadukes1

I received a call from Apple support and was told that the engineers are now aware of this problem and are working on an update. There's no ETA on this update but for now there's nothing they can do. This is very frustrating forking out a lot of cash for an upgraded 16" Macbook Pro that I only had for a few days and there's a problem like this. He apologized and that was it. Just thought I'd pass this on.

Apr 27, 2020 2:46 PM in response to mariusvw

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.



Apr 27, 2020 6:17 PM in response to mariusvw

I have a MacBook Air, 1.7GHz i7, 13" Mid-2013, 8GB RAM, OWC "Aura Pro" SSD 480GB, with the same exact message. When it's off, and I turn it on, it usually boots normally. If it's asleep, and I open it, it will boot twice, and then say, "Your Mac was restarted because of a problem" same exact error code as yours. This machine was "Frankensteined" as an Apple tech would say--it originally was a 4/128, but I bought an 8GB board from PB Medic, and more storage from OWC/MacSales.com.

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.