I have a late 2013 Macbook Pro (MacBookPro11,3) running OS 10.9.3 that I want to keep as locked down as possible since I have sensitive company data on it. To that end, I have turned on FileVault, set DestroyFVKeyOnStandby 1 hibernatemode 25, and set a firmware password. I have turned off Wake for WiFi access, Power Nap, and graphics card switching.

This set up works most of the time. However, I have found that it always crashes under the following sequence:

  • Sleep by closing the lid and then Hibernate while connected to power
  • Remove power. The display backlight comes on; wait for it to go out.

Boom, no more waking, now I have to hit the power button to reboot the machine. (If I remove power but immediately open the lid, then fully wake the machine by entering the firmware password and then the FileValut password, I'm fine.)

Of course I'd like a solution that maintains the protection of the data while the computer is sleeping/hibernating, but I'd settle for theories about what the computer is trying and failing to do when power is removed while hibernating so that maybe I can figure out a solution from there.

  • To find out what is it trying to do, you need to open the Console in Utility and publish related time stamps here.
    – Ruskes
    Jun 6 '14 at 8:47
  • 1
    @Buscar웃 If the laptop never gets as far as mounting the disk, what makes you think it will be able to write anything to the Console log?
    – Old Pro
    Jun 6 '14 at 21:37
  • I wanted to know what is it doing during hibernate if anything, since some processes can overwrite the PMSET
    – Ruskes
    Jun 6 '14 at 21:55
  • If you have a reproducible crasher, why not also file a bug with Apple so it gets fixed? If you submit it to open radar, others can dupe it ;)
    – bmike
    Jun 17 '14 at 13:35
  • @bmike Filing bug reports with Apple when you're not a developer seems like a waste of time in general, and especially when you are using a feature like hibernate 25 that is explicitly "not supported".
    – Old Pro
    Jun 18 '14 at 16:54

I ran into a similar issue with my own late 2013 Macbook Pro running 10.9.3. In the end, I had to run the following commands with root privileges:

pmset -a darkwakes 0
pmset -a standby 0
pmset -a standbydelay 0
pmset -a lidwake 0
pmset -a acwake 0
pmset -a destroyfvkeyonstandby 1 hibernatemode 25

Once I did that, I found that I needed to wake the laptop by touching the power button (pmset -a lidwake 0 disables the automatic wake-up when you open the lid) but my MacBook Pro now hibernates properly and does not crash.

I have a post on the issues I had with 10.9.2 available here:


  • My understanding of standby 0 is that it would prevent the laptop from hibernating, but I want the laptop to hibernate. Reading your post I see you solved this by leaving autopoweroff set to 1, but then I'm thinking that (a) that will suck too much battery before kicking in and (b) my computer will be vulnerable longer. With your configuration do you still get the grey screen password prompt every time you wake?
    – Old Pro
    Jun 14 '14 at 1:22
  • Yes, I get the FileVault 2 password prompt every time when I wake it from sleep. Jun 14 '14 at 2:59
  • Since you're setting the laptop to hibernate automatically rather than sleep by setting pmset to use hibernate mode 25, having standby set to 0 will not increase power drain nor will your laptop have any increased vulnerability. Jun 14 '14 at 3:06
  • Setting hibernate mode 25 does not set the laptop to hibernate automatically, it just sets the behavior when SafeSleep is called for, which is normally triggered by going into standby. I can't shake the feeling that you solved the problem by turning off standby and preventing your laptop from ever hibernating as well as preventing it from ever waking automatically.
    – Old Pro
    Jun 16 '14 at 5:02
  • There may be some misunderstanding about how these settings apply to hibernation. Here's the relevant sections of the pmset man page: developer.apple.com/library/mac/documentation/Darwin/Reference/… ----- hibernatemode = 25 (binary 0001 1001) is only settable via pmset. The system will store a copy of memory to persistent storage (the disk), and will remove power to memory. The system will restore from disk image. If you want "hibernation" - slower sleeps, slower wakes, and better battery life, you should use this setting. Jun 16 '14 at 12:43

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .