10 Replies Latest reply: Mar 13, 2013 11:36 AM by Aroara
Aroara Level 1 (0 points)

Whenever I close my MacBook, it shuts down instead of going into sleep mode. At first, I thought it was a problem with my MacBook not waking up from sleep at all, but if I use the Sleep function from the drop down menu, it will wake up normally.


I've looked around the community to see if anyone had a similar issue, but most people say they need to reboot it to start it up again, which isn't my case at all. It just does a typical shut down. How do I make it go to sleep instead of shutting down when I close it?

MacBook Air (13-inch Late 2010), OS X Mountain Lion (10.8.2)
  • Aroara Level 1 (0 points)

    I've tried that, and it didn't work.

  • Linc Davis Level 10 (192,265 points)

    Triple-click anywhere in the line below to select it:


    bzgrep 'Previous Shutdown' /var/log/system.log*


    Copy the selected text to the Clipboard (command-C).


    Launch the Terminal 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. Click Utilities, then Terminal in the icon grid.


    Paste into the Terminal window (command-V).


    Post any lines of output that appear below what you entered — the text, please, not a screenshot.

  • Aroara Level 1 (0 points)

    /var/log/system.log:Feb 17 15:29:22<owners>-MacBook-Air kernel[0]: Previous Shutdown Cause: 5

    /var/log/system.log:Feb 18 18:25:05 localhost kernel[0]: Previous Shutdown Cause: 5

    /var/log/system.log:Mar  2 07:46:43 <owners>-MacBook-Air kernel[0]: Previous Shutdown Cause: -60

    /var/log/system.log:Mar  6 05:39:54 localhost kernel[0]: Previous Shutdown Cause: 0

    /var/log/system.log:Mar  6 07:12:11 <owners>-MacBook-Air kernel[0]: Previous Shutdown Cause: 0

    /var/log/system.log:Mar 11 13:36:25 <owners>-MacBook-Air kernel[0]: Previous Shutdown Cause: -2

    /var/log/system.log:Mar 11 16:52:22 localhost kernel[0]: Previous Shutdown Cause: -2

    /var/log/system.log:Mar 12 11:25:16 localhost kernel[0]: Previous Shutdown Cause: -128

    /var/log/system.log:Mar 12 12:18:17 <owners>-MacBook-Air kernel[0]: Previous Shutdown Cause: -128


    I put one of each line that was different, and deleted the duplicates (because the log was pretty long and the only difference between them were the date).

  • Linc Davis Level 10 (192,265 points)

    Make a "Genius" appointment at an Apple Store to have the machine tested.

    Back up all data on the internal drive(s) before you hand over your computer to anyone. If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, independent backups, and you know how to restore to an empty drive from any of them.) Don’t erase the recovery partition, if present.

    Keeping your confidential data secure during hardware repair

    *An SSD doesn't need to be zeroed.

  • Aroara Level 1 (0 points)

    I don't mean to offend or question you, but I just got my computer back Apple after replacing the battery and the logicboard, they tested it in front of me, it was fine.


    I need my laptop on a day-to-day basis. I can't afford to go without for another 5 days, so this solution is not particularly helpful, considering it's just a matter of shutting down when I close it.


    I would much rather wait for the next OS X update, because this did start happening the day I installed the latest one... Coincidentally, the same day I got my computer back. There have been "rumours" on similar threads that the latest update is the problem.


    It's not the end of the world -- it's just incredibly frustrating. Thanks for trying giving your time to this, though.

  • Linc Davis Level 10 (192,265 points)

    When did you get it back?

  • Aroara Level 1 (0 points)

    Monday (March 11)

  • Linc Davis Level 10 (192,265 points)

    Since then you've logged four abnormal shutdowns with unknown causes, and no normal ones. Before the repairs, you had logged one abnormal shutdown with an unknown cause and two apparently due to low power.


    The reason codes are not publicly documented, but a zero or negative number means that the shutdown wasn't initiated by user action. From what I've been able to gather, these events are rarely, if ever, caused by software errors. They may be caused by corrupt SMC data, but you've ruled that out. If you wish, you can reinstall OS X, but I wouldn't expect any change from doing that. You can also reset the NVRAM, but again, I wouldn't expect any change.


    About NVRAM and PRAM


    That leaves hardware. The possibilites are that one of the parts that wasn't replaced is causing the problem, or that one of the replacement parts is faulty (which is not unheard of), or that the installation wasn't done right. I guess it's remotely possible that transients in your electricity supply could be responsible, but that would make sense only if the shutdowns happen exclusively when the AC adapter is connected.


    That's about all I can tell you.

  • Aroara Level 1 (0 points)

    (You're right, PRAM didn't work.)


    Either way, i would need to wait until April to bring it in, since the end (and most stressful point) of the semester is coming up. I guess I'll just have to live with it for now and have it fixed when I can.


    Thanks anyway