Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

rgetter

macrumors member
Original poster
Sep 20, 2008
47
25
Portland, Oregon
I have a really nice mid-2013 Core i7, 1.7GHz MBA running High Sierra. Right after I bought it, I installed an OWC Aura Pro X 480GB SSD and installed High Sierra. Every so often, after I leave it sitting closed for a while (sometimes a few days, this isn't my primary computer), I'll return to it and find it a bit warm to the touch and when I open it, will see the flashing-folder system-not-found icon. I power cycle it and it starts up fairly normally, with the multi-lingual message that it had recovered from a serious crash (the kernel panic grim-aftermath screen). The logs don't show very much, but I did note an entry in the power management log (the last entry before my reboot) the said:

00:11:41.105176 -0800 powerd Entering Sleep state due to 'Maintenance Sleep':

Some extensive Googling (I owe a lot of my IT career to Google search), led to the possibility of it being caused by Power Nap. I turned that off, but it still seems to happen on occasion. It got to the point where the only Energy Saver (Power Adapter) setting I had checked was to wake for WiFi network access. With the problem returning this past week, I just unchecked that.

Has anybody experienced anything like this? Better yet, does anybody know how to fix it??

Thanks,
Ric
 
There is a lot of activity going on in sleep mode (also called Dark mode), however none should warm up your mac.
It would be interesting to know if something else is going on in sleep mode
For that Open the Terminal app in the Utility folder and type

pmset -g assertions

See what assertions do you have running
 
Last edited:
There is a lot of activity going on in sleep mode (also called Dark mode), however none should warm up your mac.
It would be interesting to know if something else is going on in sleep mode
For that Open the Terminal app in the Utility folder and type

pmset -g assertions

See what assertions do you have running

I tried this a few times over a period of a couple of days. The results were consistently the same:
2019-02-09 01:17:52 -0800
Assertion status system-wide:
BackgroundTask 1
ApplePushServiceTask 0
UserIsActive 1
PreventUserIdleDisplaySleep 0
PreventSystemSleep 0
ExternalMedia 0
PreventUserIdleSystemSleep 1
NetworkClientActive 0
InternalPreventSleep 1
Listed by owning process:
pid 112(hidd): [0x00000015000980d3] 00:00:00 UserIsActive named: "com.apple.iohideventsystem.queue.tickle.4294967985.3"
Timeout will fire in 3420 secs Action=TimeoutActionRelease
pid 66(powerd): [0x000028dd000d8b96] 00:00:29 InternalPreventSleep named: "com.apple.powermanagement.acwakelinger"
Timeout will fire in 16 secs Action=TimeoutActionRelease
pid 398(UserEventAgent): [0x000028df000b8bb5] 00:00:27 BackgroundTask named: "com.apple.AddressBook.ScheduledSync"
Created for PID: 2200.
pid 2200(AddressBookSourceSync): [0x000028df00018bb4] 00:00:27 PreventUserIdleSystemSleep named: "Address Book Source Sync"
Timeout will fire in 1773 secs Action=TimeoutActionTurnOff
pid 89(apsd): [0x000028f8000b8bd8] 00:00:01 ApplePushServiceTask named: "com.apple.apsd-lastpowerassertionlinger"
pid 83(backupd-helper): [0x000028dd000b8b9c] 00:00:29 BackgroundTask named: "backupd-helper"
No kernel assertions.
Idle sleep preventers: IODisplayWrangler
[doublepost=1549861539][/doublepost]
The 2013 MacBook with a third party SSD does not support hibernation mode 25. Try mode 0 or 3.

The hibernate mode setting is still at its default: 3
 
I tried this a few times over a period of a couple of days. The results were consistently the same:
2019-02-09 01:17:52 -0800
Assertion status system-wide:
BackgroundTask 1
ApplePushServiceTask 0
UserIsActive 1
PreventUserIdleDisplaySleep 0
PreventSystemSleep 0
ExternalMedia 0
PreventUserIdleSystemSleep 1
NetworkClientActive 0
InternalPreventSleep 1
Listed by owning process:
pid 112(hidd): [0x00000015000980d3] 00:00:00 UserIsActive named: "com.apple.iohideventsystem.queue.tickle.4294967985.3"
Timeout will fire in 3420 secs Action=TimeoutActionRelease
pid 66(powerd): [0x000028dd000d8b96] 00:00:29 InternalPreventSleep named: "com.apple.powermanagement.acwakelinger"
Timeout will fire in 16 secs Action=TimeoutActionRelease
pid 398(UserEventAgent): [0x000028df000b8bb5] 00:00:27 BackgroundTask named: "com.apple.Address Book.ScheduledSync"
Created for PID: 2200.
pid 2200(AddressBookSourceSync): [0x000028df00018bb4] 00:00:27 PreventUserIdleSystemSleep named: "Address Book Source Sync"
Timeout will fire in 1773 secs Action=TimeoutActionTurnOff
pid 89(apsd): [0x000028f8000b8bd8] 00:00:01 ApplePushServiceTask named: "com.apple.apsd-lastpowerassertionlinger"
pid 83(backupd-helper): [0x000028dd000b8b9c] 00:00:29 BackgroundTask named: "backupd-helper"
No kernel assertions.
Idle sleep preventers: IODisplayWrangler
[doublepost=1549861539][/doublepost]

The hibernate mode setting is still at its default: 3

**********
OK,
the Address Book stuff is normal synchronization (very low power consumption) = let it be.
you have some kind of backup going on / is it the time machine ?.
 

Attachments

  • upload_2019-2-10_22-42-37.png
    upload_2019-2-10_22-42-37.png
    226 KB · Views: 222
Try mode 0?

Hmm, I think that may really limit the amount of time on battery when it's closed and off wall power. This has become a very rare occurrence. The fact that it's a kernel panic leads me to believe that it's hardware-related. I'm also considering moving it up to Mohave soon and perhaps that will change things. This particular OWC SSD requires AFS and I've heard that it has matured a bit in Mohave.

Ric
 
Hmm, I think that may really limit the amount of time on battery when it's closed and off wall power. This has become a very rare occurrence. The fact that it's a kernel panic leads me to believe that it's hardware-related. I'm also considering moving it up to Mohave soon and perhaps that will change things. This particular OWC SSD requires AFS and I've heard that it has matured a bit in Mohave.

Ric
Hibernation mode 25 saves the most battery power.

2013 and 2014 Airs and Pros cannot use mode 25 with a non-Apple SSD. This is a common problem as seen in this thread: https://forums.macrumors.com/threads/upgrading-2013-2014-macbook-pro-ssd-to-m-2-nvme.2034976/

People in the above-linked thread had reported that switching to mode 0 was required with a nvme drive to prevent panics.

2015 Airs and Pros can use mode 25 and do not suffer from kernel panics when waking from sleep as their bootrom has updated nvme drivers.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.