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

And here I was thinking about upgrading to 11.2.3 in hopes it would fix this issue for me. I have the 2019 16" one, and ben having this issue on almost all versions of Catalina and Big Sur, and then again when I downgraded to Catalina...

Really disappointing.

Somethings not right. It’s doing it to thousands of MacBooks and Apple isn’t addressing the issue. Mines currently out of warranty but I’m going to claim under the UK consumer warranty laws. It’s ridiculous. They’re not cheap as everyone knows. They shouldn’t be behaving like this!

It happened to me again this morning, and it happened this morning on my wife's 2020 13" M1 MacBook Pro. The only thing I did overnight was unplug my iPad Pro (USB-C), use it, and then plug it back in (to use as an extra monitor). I'd wonder if that had something to do with it, but my wife doesn't have anything plugged into her MacBook Pro.

I have both computers set to be able to boot from an external drive - I wonder if that combined with the security fix in 11.2.3 is causing an issue? I'll try to change it, but it's a hassle booting into Recovery mode - plus that shouldn't be causing Sleep Wake issues.

They liaised with their engineers but couldn’t find a solution so was advised to take it in for repair. But looking at other response, the logic board was replaced which briefly fixed it, but some have developed the same issue. Due to lockdown I’ve not been able to take it in store for repair and now my warranty has expired. I’m hoping I can claim under the UK consumer laws

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.

I have the new 16". Initially on Catalina, thought it would update and sort the problem when I downloaded Big Sur - but afraid not! This has been happening since I bought the 16" MacBook Pro new in Nov 19.

My failure code is: 0x04000030 0x0000001f

I have the same problem, almost a week back my iMac was unable to boot, with the wheel spinning continuousely after i type my user password, i did a full folrmat of the harddisk and installed a fresh copy.\

it worked fine for over a week, since 2 days bacj it styarted ubruptly shutting down without any warning, just blink and its off

when it reboots i get the below error log

Sleep Wake failure in EFI

Failure code:: 0x00000000 0x0000001f

Please IGNORE the below stackshot

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

Date/Time:     2021-03-31 12:04:59.953 +0300

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

Architecture:    x86_64

Report Version:   32

Data Source:    Stackshots

Shared Cache:    52762DF1-0E55-3F8B-9588-8169E6D0EB95 slid base address 0x7fff20236000, slide 0x236000

Event:       Sleep Wake Failure

Duration:      0.00s

Steps:       1

Time Awake Since Boot: 27s

Process:      swd [320]

Architecture:    x86_64

Footprint:     400 KB

Time Since Fork:  4s

Num samples:    1 (1)

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

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

  1  start + 1 (libdyld.dylib + 87585) [0x7fff20562621] 1

   1  ??? [0x108167454] 1

    1  ??? [0x1081671e8] 1

     1  __stack_snapshot_with_config + 10 (libsystem_kernel.dylib + 143386) [0x7fff2053501a] 1

      *1  ??? [0xffffff80002601f6] 1

       *1  ??? [0xffffff80009698cb] 1

        *1  ??? [0xffffff80008733c1] 1

         *1  ??? [0xffffff80002831c9] 1

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

  Binary Images:

     0x7fff20512000 -    0x7fff20540fff  libsystem_kernel.dylib (7195.81.3) <AB413518-ECDE-3F04-A61C-278D3CF43076>  /usr/lib/system/libsystem_kernel.dylib

     0x7fff2054d000 -    0x7fff20587fff  libdyld.dylib (832.7.3)       <4641E48F-75B5-3CC7-8263-47BF79F15394>  /usr/lib/system/libdyld.dylib

appreciate your support

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.

Why are Apple not acknowledging this issue that thousands of us seem to be experiencing?!

It would appear that some owners get their logic board replaced by Apple for the same issue to happen again.

Due to the lockdowns over the last year my MacBook Pro is now out of warranty so I’m going to see if I can claim under the UK consumer rights act as it’s not fit for purpose. I purchased the MacBook to enable me to edit photographs on the go, but I’m unable to do so as when the MacBook drops below 60 ish %, it needs to be plugged in. It’s ridiculous!

Was hoping to eventually get an iMac but this issue has put me off now 😔

I've been having this same problem for the past few months.

Hardware Overview:

  Model Name: MacBook Air

  Model Identifier: MacBookAir6,1

  Processor Name: Dual-Core Intel Core i5

  Processor Speed: 1.4 GHz

  Number of Processors: 1

  Total Number of Cores: 2

  L2 Cache (per Core): 256 KB

  L3 Cache: 3 MB

  Hyper-Threading Technology: Enabled

  Memory: 4 GB

  System Firmware Version: 117.0.0.0.0

  SMC Version (system): 2.12f143

  Serial Number (system): C02N10J3G083

  Hardware UUID: 143380E9-7E2C-5142-814D-E71467AE8F11

  Provisioning UDID: 143380E9-7E2C-5142-814D-E71467AE8F11

Any help appreciated

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.

Any solutions yet?

I have the same problem... I have an old desktop iMac (27-inch, Late 2012) with Catalina. It works absolutely fine except for the sleep wake prob and failure code 0xffffffff 0x0000001f

When it goes to 'sleep' for more than a few hours the screen blacks out but glows and I can hear the fan working hard... I have to use the power off/on button to restart it each time.

The fan is also working too hard during basic usage...

I can't update the OS system to anything newer as it will only accept Catalina... and i'm pretty sure this started after updating to this OS.

Feels precarious...

I solved my issue by disabling time machine and disconnecting the external hard disk I was using for time machine

not a good solution as I am now running without any backup but at least the problem stopped

I am facing same issue, it's really irritating me. My MacBook pro 2019 is not powering on once it goes into sleep mode.

Even I am connecting power but it is not indicating any power charging.

I did all basic troubleshooting like SMC, NVRAM reset.

Please provide your feedback if anyone else has sorted it out.

I have Catalina

After suffering this issue with my MacBook Pro 2018 Touchbar and not being able to return it due to the warranty expiring during the multiple UK lockdowns, I have decided to sell it on. I have downgraded the OS back to Mojave and the issue has disappeared. Unlike Apple however, I will be advising the buyer of this issue before selling it on 👍🏻