Laptop keeps shutting down - Error: Sleep Wake failure in EFI

Hi,


After closing the lid on my laptop (MacBook Pro 13" late 2013) or leaving for a while (+20 minutes), my laptop shuts down automatically. So when continuing work, it has to do the 'long startup'.


I believe it started after updating to 11.6.6, but i'm not sure. Error message below:


I tried several 'solutions' found online like resetting SMC and PRAM. No result.


Hope someone can help!


Thanks


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


Sleep Wake failure in EFI

 

Failure code:: 0x00000000 0x0000001f

 

Please IGNORE the below stackshot

 

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

Date/Time:        2022-06-09 10:55:06.832 +0200

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

Architecture:     x86_64

Report Version:   32

 

Data Source:      Stackshots

Shared Cache:     AF4F8B1D-58F9-39DD-9C0F-74C5BEB2E392 slid base address 0x7fff202da000, slide 0x2da000

 

Event:            Sleep Wake Failure

Duration:         0.00s

Steps:            1

 

Time Awake Since Boot: 62s

 

 

 

Process:          swd [321]

Architecture:     x86_64

Footprint:        332 KB

Time Since Fork:  21s

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 + 89917) [0x7fff20603f3d] 1

    1  ??? [0x103cd6454] 1

      1  ??? [0x103cd61e8] 1

        1  __stack_snapshot_with_config + 10 (libsystem_kernel.dylib + 146918) [0x7fff205d5de6] 1

         *1  ??? [0xffffff80002301f6] 1

           *1  ??? [0xffffff800093ea2e] 1

             *1  ??? [0xffffff8000848b11] 1

               *1  ??? [0xffffff80002534ff] 1

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

 

  Binary Images:

        0x7fff205b2000 -     0x7fff205e1fff  libsystem_kernel.dylib (7195.141.29) <115FB506-5540-3F70-9010-2EE4DE8AA1D8>  /usr/lib/system/libsystem_kernel.dylib

        0x7fff205ee000 -     0x7fff20629fff  libdyld.dylib (852.2)                <5FBD0E1A-ACCE-36DB-B11C-622F26C85132>  /usr/lib/system/libdyld.dylib

Model: MacBookPro11,1, BootROM 433.120.6.0.0, 2 processors, Dual-Core Intel Core i5, 2,4 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-1680.9)

Bluetooth: Version 8.0.5d7, 3 services, 19 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.2


Posted on Jun 13, 2022 4:18 AM

Reply
Question marked as Top-ranking reply

Posted on Jun 22, 2022 9:35 PM

How about starting your Mac in Safe Mode:


Start up your Mac in safe mode - Apple Support (Safe Mode)


The computer will take a fairly long time to boot, possibly 10-15 minutes. You should see "Safe Boot" in red letters after it boots on the screen. The computer may seem a bit sluggish, but this is to test whether the problem is present in safe mode. If the problem is gone, that means something you have installed is causing the problem, as safe mode disables most user installed extensions. If that is the case, I suggest that you download Etrecheck and post the output here using the Additional Text button below. People may see the culprit.


If the problem persists even in Safe Mode, then there may be a hardware issue. For instance, the reason the pmset command sometimes works is that some third party NVMe drives wake up slower from standby than the machine, and so for a split second, the machine thinks there's no drive, and crashes. That's why it happens when the machine sleeps, but generally not on start up. So the pmset parameter prevents that type of deep sleep and the hardware problem never occurs. Your problem could be hardware but a different type of hardware issue. A 2013 laptop may be nearing end of life and some of the electronics may be wearing out. Or it might be related to the SSD you are using. Can you run the Apple hardware test on your Mac, hold down the D key when starting up:

Mac startup key combinations - Apple Support


Similar questions

9 replies
Question marked as Top-ranking reply

Jun 22, 2022 9:35 PM in response to BramsP

How about starting your Mac in Safe Mode:


Start up your Mac in safe mode - Apple Support (Safe Mode)


The computer will take a fairly long time to boot, possibly 10-15 minutes. You should see "Safe Boot" in red letters after it boots on the screen. The computer may seem a bit sluggish, but this is to test whether the problem is present in safe mode. If the problem is gone, that means something you have installed is causing the problem, as safe mode disables most user installed extensions. If that is the case, I suggest that you download Etrecheck and post the output here using the Additional Text button below. People may see the culprit.


If the problem persists even in Safe Mode, then there may be a hardware issue. For instance, the reason the pmset command sometimes works is that some third party NVMe drives wake up slower from standby than the machine, and so for a split second, the machine thinks there's no drive, and crashes. That's why it happens when the machine sleeps, but generally not on start up. So the pmset parameter prevents that type of deep sleep and the hardware problem never occurs. Your problem could be hardware but a different type of hardware issue. A 2013 laptop may be nearing end of life and some of the electronics may be wearing out. Or it might be related to the SSD you are using. Can you run the Apple hardware test on your Mac, hold down the D key when starting up:

Mac startup key combinations - Apple Support


Jun 14, 2022 7:02 PM in response to BramsP

Are you using the original internal drive that came with the laptop? Or are you using a replacement internal drive?


If you are using a replacement (third party non-Apple) drive, the following may help.


Open Terminal and enter this on the command line:


sudo pmset -a standby 0


Report back whether it fixes the issue.


To restore it back to the default


sudo pmset -a standby 1

Jun 14, 2022 8:10 AM in response to BramsP

Hi BramsP,


Thank you for posting in Apple Support Communities! Do you have any shut down schedules set up when you go to the Apple menu (  ) > System Preferences > Energy Saver?


You can find some more information about those settings here: Get help with your Mac notebook battery - Apple Support.


If this continues, you may want to reach out to Apple Support for further assistance. Depending on your region, you may be able to reach them here: Get Support.


Take Care!

Jun 22, 2022 1:22 PM in response to steve626

Hi @Steve626,


Thanks for your reply.


About 2 years ago i replaced the standard SSD to a samsung SSD. Until a few weeks without any problems. I tried the sudo pmset -a standby 0 part. Sleep wake issue is till present. Every time i'm sending an error report, hope it helps.


After the sudo thing i did a reset of the SMC and PRAM.



Jun 23, 2022 11:25 PM in response to BramsP

There are several questionable softwares installed. I suggest that you uninstall them completely, which typically requires an uninstaller from the manufacturer.


ccleaner -- "cleaning" software can damage your Mac by removing things that are needed for the MacOS to function properly.


CleanMyMac -- it is installed but wasn't loaded at the time Etrecheck was run. Like the previous item, this is another "cleaning" app that is famous in the Apple Discussions for the number of computers that have been misconfigured with it. This needs to be completely uninstalled (with an uninstaller).


It is possible that something else is causing the problem. But we know, in Safe Mode, your Mac worked properly. That means with no third party extensions allowed to operate, the Mac did not crash when sleeping or waking up. Removing these two apps first is a good start to try to get back to that stable state.


If you have removed these two items and the Mac still is misbehaving, you could look for other things to uninstall; things that permeate the system would be the most suspect. I think you have Disk Drill (Cleverfiles) and/or other associated utilities. I have Disk Drill installed on several Macs and never had a problem with it, but you could temporarily uninstall it as a test (you can always reinstall). Cleverfiles (Disk Drill) seems to have installed multiple kexts, those Kernel Extensions can cause problems like you are seeing. It could also be that Disk Drill and the Cleverfiles utilities are ok but somehow were conflicting with CleanMyMac or ccleaner when those apps were installed.



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.

Laptop keeps shutting down - Error: Sleep Wake failure in EFI

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