User profile for user: Lex_alur
Lex_alur Author
User level: Level 1
8 points

Instead of sleep mode MacBook always shutdown

My MacBook Pro on m1 pro always shutdown completely instead of going to sleep.

I've already tried everything I can. Nothing helps.


I tried changing the pmset parameters, but that didn't give any results.

Here are the current pmset settings:

  • SleepDisabled 0
  • powernap 1
  • networkoversleep 0
  • hibernatemode 3


When hibernatemode = 25 is set, switching to hibernation works, but after that macos takes a long time to boot, and compared to this, a shutdown no longer seems so long.

When hibernatemode = 1 or 3, the macbook shutdown, and the subsequent startup is always accompanied by a power-on melody and the gradual restoration of closed windows.


The same in safe mode, when switching from it to sleep, the macbook turns off, and the subsequent startup takes place in normal, not safe mode.


Since SMC works differently in apple silicon, you need to shutdown to reset SMC, and even after turning off manually, rather than going to sleep, the behavior does not change.


I tried disabling filevault, it didn't help. Upgrading to macOS Sequoia also didn't help.


The only thing I haven't done yet is a reinstallation of the system, but I don't want to lose all the data for the sake of a method that is unlikely to work.

MacBook Pro 14″, macOS 15.3

Posted on Feb 28, 2025 11:02 AM

Reply
8 replies
Sort By: 
User profile for user: HWTech
HWTech
User level: Level 9
64,088 points

Feb 28, 2025 7:25 PM in response to Lex_alur

You can try to reset the NVRAM (aka PRAM) by using the following Terminal command (safe for M-series Macs):

sudo  nvram  -c


This command will prompt you for your admin password. Nothing will appear on the screen as you type the password so press the "Return" key to submit the password. After issuing the command, reboot the computer so the system can pull the default values. You may see some settings such as Computer Name cannot be deleted which is normal, as long as the command over all doesn't fail.


You can try a DFU Firmware Revive which resets the security enclave chip & system firmware. Unfortunately you will need access to another Mac running macOS 15.x Sequoia.


FYI, if you have at least 80GB+ of Free storage space, then you can try installing another copy of macOS next to itself by creating a new APFS volume. 80GB should be sufficient for testing a temporary barebones installation of macOS. Test the new install before installing any third party apps or restoring from a backup. Ignore the "Available" storage value which is shown everywhere in macOS since it is very misleading and is not the same thing as the actual Free space value which is shown in Disk Utility.

Use more than one version of macOS on Mac - Apple Support


Or you could install macOS onto an external USB3 SSD, just make sure not to use the DFU USB-C port during the installation to an external drive.

Install macOS on an external storage device and use it as a startup disk - Apple Support




Reply
User profile for user: Zorba_le_grec
Zorba_le_grec
User level: Level 3
576 points

Mar 23, 2025 10:41 AM in response to Lex_alur 

The NVRAM doesn't manage any of the power managment settings.

You can easily check this technical fact with the command line:

    /usr/bin/sudo nvram -p | grep -i power

which will ask you for your account password and won't display it,
and next will display everything talking of power inside your NVRAM settings.

And there is none!

So please forget all the advice which suggest you to tinker with the NVRAM for power management.
Reply
User profile for user: Lex_alur
Lex_alur Author
User level: Level 1
8 points

Mar 1, 2025 1:14 AM in response to HWTech

Thanks for the information about resetting the DFU and installing another copy of macOS, I'll try these methods later.


Unfortunately, reset the NVRAM did not help. I remembered that I had done it before, but it didn't help either then or now.

It seems that the reset is being performed, but such errors appear:

  • nvram: Error clearing firmware variable fmm-mobileme-token-FMM: (iokit/common) not permitted
  • nvram: Error clearing firmware variable fmm-mobileme-token-FMM-BridgeHasAccount: (iokit/common) not permitted
  • nvram: Error clearing firmware variable fmm-computer-name: (iokit/common) not permitted

I assume that's what you were talking about:

You may see some settings such as Computer Name cannot be deleted which is normal
Reply
User profile for user: HWTech
HWTech
User level: Level 9
64,088 points

Mar 1, 2025 10:32 PM in response to Lex_alur

Lex_alur wrote:

Unfortunately, reset the NVRAM did not help. I remembered that I had done it before, but it didn't help either then or now.
It seems that the reset is being performed, but such errors appear:
nvram: Error clearing firmware variable fmm-mobileme-token-FMM: (iokit/common) not permitted
• nvram: Error clearing firmware variable fmm-mobileme-token-FMM-BridgeHasAccount: (iokit/common) not permitted
• nvram: Error clearing firmware variable fmm-computer-name: (iokit/common) not permitted

I assume that's what you were talking about:
You may see some settings such as Computer Name cannot be deleted which is normal

Yes.


Reply
User profile for user: Zorba_le_grec
Zorba_le_grec
User level: Level 3
576 points

Mar 23, 2025 10:30 AM in response to Lex_alur 

Check if your MacBook is in autopoweroff mode (in command line mode, Terminal or xterm):

    /usr/bin/sudo pmset -g | grep autopoweroff

this command will ask you for your account password and won't display it (which is usual on
any command line interface).

If it returns one, then this means your MacBook is in autopoweroff mode,
which fully explains it is forced to a reboot when powered on.
Then turn it off with:

    /usr/bin/sudo pmset autopoweroff 0

and check this is OK by letting your MacBook reach its sleep timeout.
Reply
User profile for user: Lex_alur
Lex_alur Author
User level: Level 1
8 points

Mar 25, 2025 9:59 AM in response to Zorba_le_grec

Unfortunately, using this command does not output anything as there is no such parameter.


Here is my pmset -g:

System-wide power settings:
 SleepDisabled		0
 DestroyFVKeyOnStandby		0
Currently in use:
 standby              1
 Sleep On Power Button 1
 SleepServices        1
 hibernatefile        /var/vm/sleepimage
 powernap             1
 networkoversleep     0
 disksleep            5
 sleep                1 (sleep prevented by sharingd, powerd)
 hibernatemode        3
 ttyskeepawake        1
 displaysleep         10
 tcpkeepalive         1
 lowpowermode         0
 womp                 0


Thank you for trying to help!

Reply
User profile for user: TheDenFire
TheDenFire
User level: Level 1
12 points

Apr 4, 2025 4:14 AM in response to Lex_alur

Hi !


I have the same problem when, during any attempt to enter sleep mode, the macbook turns off.


I created a new volume in my Macintosh and installed the current macOS Sequoia on it, and lo and behold, the sleep mode works flawlessly on the new macOS.


I've tried to try many ways that I've read here on other threads, but so far I've only really succeeded by installing macOS on a new volume (accordingly, a complete rearrangement of macOS should also help)


If you're interested, here's my pmset -g after the rearrangement, but I'm more than sure that no matter what settings are in it, nothing will help in this situation. (Only if you turn off sleep mode and always keep your MacBook on):


System-wide power settings:
Currently in use:
 standby              1
 Sleep On Power Button 1
 hibernatefile        /var/vm/sleepimage
 powernap             1
 networkoversleep     0
 disksleep            10
 sleep                1 (sleep prevented by powerd, powerd)
 hibernatemode        3
 ttyskeepawake        1
 displaysleep         10
 tcpkeepalive         1
 lowpowermode         1
 womp                 1
Reply
User profile for user: Lex_alur
Lex_alur Author
User level: Level 1
8 points

Apr 4, 2025 1:10 PM in response to TheDenFire

Hi thanks for the info, I tried a clean install on an external ssd, it was advised above, I think it's equivalent to installing on a new volume.


In my case it didn't work :(


But, I noticed that a diagnostic report is generated after every such reboot:

{"os_version":"macOS 15.3.2 (24D81)","bug_type":"115","timestamp":"2025-04-04 20:14:29.00 +0300","name":"Reset count","roots_installed":0,"incident_id":"8E9399D4-FB2B-4F07-AE51-09EF7E9CDB36"}
Incident Identifier: 8E9399D4-FB2B-4F07-AE51-09EF7E9CDB36
CrashReporter Key:   86ADC412-E99A-58FC-3F19-1EB88566A53E
Date: 2025-04-04 20:14:29.66 +0300
Reset count: 0
Boot failure count: 1
Boot faults: rst crash,crash_n
Boot stage: 0x50
Boot app: 0
socId: 6000
socRevision: 21

Based on it, we can understand that the error occurs during sleep exit and system boot.


But what's strange is that no pop-up windows about the error appear, and a search for the code "bug_type": "115" leads only to strange errors on the iPhone.


I can add that outwardly such reboots look like this: while going to sleep, USB-connected devices continue to have power, but after trying to wake up the Mac - all USB are abruptly turned off, and then the power comes back on and the system starts booting.


In the end, I was never able to figure it out.

Reply

Instead of sleep mode MacBook always shutdown

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