Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Machine shuts down instead of sleeping

My MacBook Air is the 11" mid-2011 model, and I'm running OS X 10.10.3.


Recently, the machine shuts itself down instead of going to sleep. That is, if I leave the machine for a while, or if I shut the lid, when I return to use it, it does not wake from sleep. I have to press the power button, and it starts up quickly. But it's definitely starting up rather than faux wake-from-sleep, because applications are restarting.


As far as I can tell, this only happens when it's not plugged in, and it happens at least 50% of the time it supposedly sleeps.


What is the likely cause here?


(I've tried googling to see if others have reported this issue, but I haven't found anything; perhaps my search terms are too general.)


Other information that may be of use, or may be unrelated:

(1) I replaced the original battery with a Lizone battery last week. Prior to the replacement, the uninvited shutdown was happening about once every week or two; I had hoped it would go away when the battery was replaced. Instead, it seems to be happening more frequently. (I replaced the original battery because it was showing signs of imminent failure.)

(2) The Lizone battery appeared to fit the Air in every way except that the central screw hole didn't align, so I had to leave that screw out.

(3) I've done Repair Disk Permissions and Verify Disk and both showed no issues.

(4) The machine was serviced just before the AppleCare ran out, about 10 months ago; the trackpad and hard drive were replaced.

(5) I looked in the Console logs to see if there were any telltale messages just prior to boot... and there's nothing there, just the usual chatter of the machine.

MacBook Air, OS X Yosemite (10.10.3)

Posted on May 31, 2015 6:04 PM

Reply
6 replies

May 31, 2015 11:04 PM in response to smbelcas

With the Power Nap feature enabled, the computer enters a so-called standby mode after it has been in sleep on battery power for more than a certain time (one hour, by default.) In that mode, the contents of memory are saved to a file, and then the power is turned off. When the computer wakes up, the contents of memory are restored from the file. As a result, waking from sleep takes longer than it otherwise would. The benefit is that sleep can be prolonged indefinitely without draining the battery or having to restart the computer.

Late-model Macs are configured to enter standby after four hours in sleep while on AC power, in order to comply with a directive of the European Union. That behavior doesn't depend on the status of Power Nap.

If waking from standby is slower than usual, follow the instructions in this support article. Otherwise, see below.

You have three choices. One is to do nothing. Use the machine as designed. That's what I recommend.

The second choice is to disable Power Nap in the Energy Saver pane of System Preferences. Uncheck the box marked Enable Power Nap... in each of the tabs. You won't get the wake delay anymore, but you won't get any of the features of Power Nap either. The wake delay while on AC power won't be affected.

The third choice is to increase the delay before standby mode is triggered, or to disable standby mode completely. This is an unsupported option and you're on your own as to the consequences. If you choose to go this route, proceed as below. These instructions are for advanced users only.

Back up all data before making any changes.

These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.

Drag across the line below to select it, then copy it to the Clipboard by pressing the key combination command-C:

sudo pmset –a standbydelay

Don't copy the blank space at the end of the line.

Launch the Terminal application.

Paste into the Terminal window by pressing command-V. Press the space bar, then type the delay you want, in seconds. For example, if you want to change the standby delay from the default one hour to eight hours, enter 28800. Don't put commas or other punctuation marks in the number. To disable standby, enter 0 (zero.)

When the command is complete, press return. You'll be prompted for your login password. Nothing will be displayed when you type it. Type carefully and then press return. You may get a one-time warning to be careful. If you don’t have a login password, you’ll need to set one before you can run the command. After running it, quit Terminal. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.

To disable standby on AC power, enter this command:

sudo pmset autopoweroff 0

and to revert to the default state,

sudo pmset autopoweroff 1

Jun 1, 2015 5:20 AM in response to Linc Davis

Thank you for your response, but it does not address the issue. The machine is not behaving as designed; its behavior has changed dramatically in the last week.


(1) The machine is shutting down, not entering Power Nap.

(2) This happens when it has been left unattended for 5--15 minutes. As in, I close the laptop and 3 minutes later when I open it, discover it has shut itself down.

Jun 1, 2015 7:05 AM in response to smbelcas

Step 1

Take all the applicable steps in this support article. That's the starting point for any further efforts to solve the problem. Please read the whole article carefully and don't skip any of the steps, including the ones under the heading Additional troubleshooting. If you don't understand any of the steps, ask for guidance.

Also note that if you replaced the internal hard drive with an SSD, or if you're starting up from an external SSD, then that device may be causing the problem. Check the SSD manufacturer's website for a firmware update. The only solution may be to reinstall the original drive or avoid sleep altogether.

Step 2

If you're running OS X 10.8.5 or earlier, from the menu bar select

 ▹ System Preferences... ▹ Accessibility

If the checkbox at the bottom marked

Enable access for assistive devices

is checked, uncheck it and test.

If you're running OS X 10.9 or later, select

 ▹ System Preferences... ▹ Security & Privacy ▹ Privacy ▹ Accessibility

If any applications are listed on the right and have a checked box next to them, uncheck all the boxes and test. You may first have to click the padlock icon in the lower left corner of the window and authenticate as an administrator to unlock the settings.

Step 3

In the Energy Saver pane of System Preferences, uncheck the box marked

Put hard disks to sleep when possible

Step 4

If you don't already have a current backup, back up all data, then reinstall the OS.* You don't need to erase the startup volume, and you won't need the backup unless something goes wrong. If the system was upgraded from an older version of OS X, you may need the Apple ID and password you used.

If you installed the Java runtime distributed by Apple and still need it, you'll have to reinstall it. The same goes for Xcode. All other data will be preserved.

*The linked support article refers to OS X 10.10 ("Yosemite"), but the procedure is the same for OS X 10.7 ("Lion") and later.

Step 5

This and the next step must be taken as an administrator. If you have only one user account, you are the administrator.

Launch the Console application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ Open LaunchPad and start typing the name.

In the Console window, select

DIAGNOSTIC AND USAGE INFORMATION Diagnostic and Usage Messages

In the search box in the window's toolbar, enter "powerd" (without the quotes.)

You may see one or more lines like this:

com.apple.message.signature: Platform Failure

If you do see that, and you did everything in the preceeding steps, then you're dealing with an internal hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.

Step 6

In the Console window, select

DIAGNOSTIC AND USAGE INFORMATION System Diagnostic Reports

(not Diagnostic and Usage Messages) from the log list on the left. If you don't see that heading, select

View Show Log List

from the menu bar.

There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down.

You may see one or more reports with a name that begins with "Sleep Wake Failure" followed by a date. Select the most recent one. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.

I know the report is long, maybe several hundred lines. Please post all of it anyway.

Jun 1, 2015 8:32 AM in response to Linc Davis

Thank you for taking the time to respond, but it does look to me like this is a canned response rather than specifically addressing my machine's behavior. I say this because I've seen you give this response to others in my searches of the support forums for similar issues.


(1) I had already read the support article you cite in Step 1. Yes, I read it carefully. It doesn't have an "Additional Troubleshooting" section. Also, it's not applicable because it's about computers not sleeping when they should. Mine is simply shutting down some of the time instead of sleeping. That is not a power management issue, correct?


(2) There have been no software changes to the machine in the last few months. The behavior change occurred with, or increased with, the battery change.


(3) I forgot to mention this earlier: Sometimes (again, only when battery powered) the machine boots itself when I try to wake it. That is, I open the lid, and without touching any keys the machine chimes and boots. The system logs reflected that this is a boot, not a wake.


(4) I had done Steps 5 and 6 already, and there is nothing applicable showing up in the logs by the rubric suggested above. I do have some JavaApplicationStub and SystemUIServer logs.

In the system messages log, I get things like


5.30.15 3:42:03.532 PM watchdogd[213]: [watchdog_daemon] @( pm_callback) - ref=0x0 msg_type=0xe0000280 msg=0x42000d
5.30.15 3:42:03.532 PM watchdogd[213]: [watchdog_daemon] @(wd_daemon_thread) - events buffer: 14r1744 1323s1744 1350r15831 2459s15831 2486r21898 2877s21898

5.30.15 3:42:03.533 PM discoveryd[72]: Basic DNSResolver UDNSServer:: PowerState is DarkWake

5.30.15 3:42:03.535 PM coreaudiod[287]: 2015-05-30 03:42:03.534944 PM [AirPlay] Power: SystemWillSleep

5.30.15 3:42:03.536 PM coreaudiod[287]: 2015-05-30 03:42:03.535503 PM [AirPlay] BTLE client stopping to browse for AirPlay Solo Target Presence.

5.30.15 3:42:03.536 PM coreaudiod[287]: 2015-05-30 03:42:03.535757 PM [AirPlay] BTLE discovery removing all devices

5.30.15 3:42:03.537 PM coreaudiod[287]: 2015-05-30 03:42:03.537286 PM [AirPlay] BTLE client stopped to browse for AirPlay Solo Target Presence.

5.30.15 3:42:03.653 PM identityservicesd[318]: <IMMacNotificationCenterManager: 0x7fd7d8e253e0>: notification observer: com.apple.iChat notification: __CFNotification 0x7fd7d8f8ff80 {name = _NSDoNotDisturbEnabledNotification}

5.30.15 3:42:03.673 PM identityservicesd[318]: <IMMacNotificationCenterManager: 0x7fd7d8e253e0>:NC Disabled: YES

5.30.15 3:42:03.680 PM identityservicesd[318]: <IMMacNotificationCenterManager: 0x7fd7d8e253e0>: DND Enabled: YES

5.30.15 3:42:03.680 PM identityservicesd[318]: <IMMacNotificationCenterManager: 0x7fd7d8e253e0>: Updating enabled: NO (Topics: (

))

5.30.15 3:42:03.000 PM kernel[0]: PM response took 280 ms (82, blued)

5.30.15 3:42:03.000 PM kernel[0]: PM response took 282 ms (82, blued)

5.30.15 3:42:04.634 PM WindowServer[139]: device_generate_desktop_screenshot: authw 0x7f9cf56138a0(2000), shield 0x7f9cf543c620(2001)

5.30.15 3:42:04.937 PM WindowServer[139]: device_generate_lock_screen_screenshot: authw 0x7f9cf56138a0(2000)[0, 0, 1366, 768] shield 0x7f9cf543c620(2001), dev [1366,768]

5.30.15 3:42:07.235 PM com.apple.xpc.launchd[1]: (com.apple.mdworker.lsb.02000000-0000-0000-0000-000000000000) Service only ran for 4 seconds. Pushing respawn out by 6 seconds.

5.30.15 3:42:14.668 PM com.apple.xpc.launchd[1]: (com.apple.mdworker.lsb.02000000-0000-0000-0000-000000000000) Service only ran for 1 seconds. Pushing respawn out by 9 seconds.

5.30.15 3:42:18.547 PM discoveryd[72]: Basic BTMMServer Sleep offload failed. Start deregistering

5.30.15 3:42:19.450 PM loginwindow[88]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.

5.30.15 3:42:23.000 PM kernel[0]: PM response took 4779 ms (50, powerd)

5.30.15 3:42:23.000 PM kernel[0]: [0x26cfa38000, 0x40000000]

5.30.15 3:42:23.000 PM kernel[0]: [0x0, 0x0]

5.30.15 3:42:23.000 PM kernel[0]: AirPort_Brcm43xx::powerChange: System Sleep

5.30.15 7:44:45.000 PM bootlog[0]: BOOT_TIME 1433029485 0


And that's why it's so mysterious to me: The system said it went to sleep, and then when I opened it hours later, all it did was boot.

Jun 1, 2015 9:07 PM in response to Linc Davis

I read it carefully.

Including the first line ("OS X: When your Mac doesn't sleep or wake")?

Yes; nothing in the main body of the article was applicable.


Thanks for the clarification about the change of "Additional Troubleshooting" to "Learn More." I'm now working my way through those recommendations. Resetting the SMC has reduced the frequency of shutdown-on-sleep. So the machine's behavior is less annoying (yay!) but it takes longer to determine whether a fix has taken (boo).

Machine shuts down instead of sleeping

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