Sleep/wake crash OSX Mavericks, Macbook Air 2013

Hi EagleTree, I completely agree, and more, although there may indeed be an issue with that rapport tool, I don't use it, don't have it and don't need it, still my system hangs every now and then completey when coming out of sleep. I've already changed the anti-virus, stopped the time-machine backup to a NAS disk and God knows what but still, no luck.

Did anybody with an Apple support contract made Apple aware? Because the problem is old, very annoying and was not solved in 10.9.2 so it makes me wonder..... Furthermore, it seems there are quite a few people having this issue so a solution would be nice.

Did you go through your browser extensions? There are some tools like Glitch that used to crash my computer which I removed.

Just try and think back to all the 3rd party apps that you have put on your Mac and hopefully it will become apparent to you before long, which is what I did when I remembered I had put Rapport on my new MBP for the first time, however with this being a new issue with Mavericks which is a new OS, hence lack of discovered/known fixes in this forum, it took me almost 4 months of tiresome testing and Console log analysis to twig!! 😮

Alternatively you could partition your hard drive and install a fresh copy of Mavericks on the partition. In this fresh install of Mavericks you will obviously only have stock Mac apps on it, so from there you can start rebuilding up your fresh install so that it has the same apps that your original install has on it. The process of installing your required 3rd party apps would be a good way of jogging your mind as to what you have on your Mac and may well reveal the culprit.

If you are worried about the possibility of it being a hardware issue then call up Apple and tell them about the sleep problem, they will ask you to either take your laptop in to the Genius bar for a thorough hardware diagnostics test (which I would predict won't show any faults), or they will guide you through doing the aforementioned partition of your hard drive with a fresh install of Mavericks. However, they will ask you to leave the partitioned fresh install of Mavericks 'as is' (i.e. don't install any additional software/apps) so that when you have finished using your Mac for the day in your 'original install' of Mavericks, you will shut-down out of your 'original install' then boot-up to your newly created Mavericks install and put your Mac to sleep for the night. Chances are you won't have the sleep problem occur on the fresh partitioned install of Mavericks thus proving to Apple that it's not a hardware issue but rather an issue with some software you have put on your Mac, at which stage Apple will be very pleased (no repair/replacement required) and leave you back at 'square one' again trying to pinpoint which piece of additional software is causing the sleep problem.

This links to "third party software" are... Why all of sudden everyone is getting issues with third party software after update to Maveric? Yes, let's blame third party software!

ViktorKh wrote:

This links to "third party software" are... Why all of sudden everyone is getting issues with third party software after update to Maveric? Yes, let's blame third party software!

It's not really a case of who's to blame. Operating systems change all the time and 3rd party software changes all the time, so conflicts occur, and yes in mine and other peoples cases, the conflict causing this hibernation crash was between Mavericks and some 3rd party security software.

However an operating system can't change to suit each of the hundreds of different 3rd party security apps available, that would be impossible as they all work differently. What happens if I decide to write a new 3rd party anti-virus application and upon release it conflicts with Mavericks, should Apple have to release an update solely to suit my security software? No. I should change my software to suit Mavericks as I'm trying to build a piece of software that is compatible with an operating system so I can give away/sell lots of copies of it to those people using that operating system, just like every other software company.

So it's not a matter of blame, an updated operating system naturally requires updated 3rd party applications, which in-turn requires time.

It appears to happen only when I put my computer to sleep using a keyboard shortcut, like command-option-power/eject.

After some discussion with someone from Apple Support, I deleted the file /Library/Preferences/SystemConfiguration/com.Apple.PowerManagement.plist and then removed it from Trash so it was completely gone, then I rebooted and since then the system has been up and running without crashes for three nights now. Time machine makes the backup every night so it wakes up only once. So far so good, fingers crossed.

Hope this helps anyone.

brand new 1-week old MBA 13 - same issues persist & I brought it to Apple Store for a logic board replacement (waste of time) - same issue persist!!!! YIKES!!!! no doubt now that it is a softare issue - but why do my other MBA machines have no issues (same 10.9.2)??? Is this sleep/crash issue isolated to new machine manufactured in recent months? crazy - never had this much trouble w/ a Mac laptop -

tried your method

1. removed the file

2. rebooted

3. closed the lid

4. next day opened the lid - hung on login screen and failed the system

doesn not work for my MBP2013

OK, well I must admit, in the same action I removed the anti-virus software

1. to exlude it as a possible cause

2. the guy from support convinced me that on Mavericks it was not necessary to have this software installed

I am still researching if it is indeed harmless to run without virusscanners or not.

All security is a risk/benefit tradeoff. The main advantage I have seen from running AV on OS X (or linux) is to find PC viruses in mail/documents before they get to a PC near you. In my experience, many viruses go indetected in PC email archives until the user tries to transfer the archives to OS X.

ClamAV is reasonably good, free, and can be used in on-demand mode that is less likely to interfere with sleep/wake so might be worth using while you wait for Mavericks sleep issues to be sorted out.

douwevt wrote:

I am still researching if it is indeed harmless to run without virusscanners or not.

I don't think anybody can determine that it's harmless unless they are not hooked up to a network and have 100% control to prevent physical access. There are multiple opportunities to be infected, but OS X has a rasonably robust system to keep malware from gaining a foothold. Your research should start with: OS X: About the "Are you sure you want to open it?" alert (File Quarantine / Known Malware Detection)and OS X: About Gatekeeper. There is also a Malware Removal Tool that runs once with each Apple Security or Java update to remove "commonly found malware" that might have been installed in the past. That should cover all currently known malware that can impact OS X or it's applications as long as you make use of those capabilities and heed any warnings they give you. If you choose to disable any of them, ignore their warnings or give up your admin password without fully understanding what is asking for it and why, then you may need additional protection.

The second place I recommend you browse is the Mac Malware Guide to gain a thorough understanding of the threat, potential A-V software solutions as well as safe computing skills.

I have a mid-2009 MacBookPro with 8GB RAM and a new 512GB Samsung SSD. I am running Mavericks 10.9.2, currently as of March 25, 2014 the latest version.

The following fix from @abjoc appears to have eliminated the close lid / sleep-wake issue. I am able to now close my lid (sleep) and then awake the system by holding down the power button for about 1.5 - 2 seconds. The system appears to restore itself from a power failure type of scenario (although this may a new or standard wake, I am not sure). The computer then allows me to continue to login and access my open programs and windows. Note this works when closing the lid. I did run into the system failure / crash when I left the screen lid open for too long yesterday; it hung on what appears to be the default iCloud screensaver (got stuck on the fish) and I had to hard boot my Mac.

So this is NOT a fail safe, however it appears to limit the straight up crash everytime my computer went to sleep.

From @abjoc - Thank you!

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.

I am no expert on this but from reading believe the default setting is 3.

This can be checked by using pmset -g which will list the current settings.

I took a chance that changing to hibernatemode = 25 might help. It takes a little longer to resume from sleep when opening the lid - maybe an additional two seconds, and enough that you can open the lid and still see a black screen for a second or so - but over the past few days, and going in and out of sleep lots of times no reoccurance.

I changed it using the command - sudo pmset -a hibernatemode 25

As has been suggested a number of times, if you are having this issue PLEASE report it! Feedback site: http://www.apple.com/feedback/

Thank buddah for Communities board!

just FYI

I downgraded my MBP to the 10.8 Mountain Lion and now I have NO issues with the same set of "third party applications". Finally I resolved this annoying problem.

I liked new feature from Mavericks with multi display work, but normal sleep/wake process worth this downgrade.

Keep monitoring all theses discussion with a hope that Apple is going to fix Mavericks some day.

I'm on a separate forum and had a user suggest typing kextstat | grep -v apple into terminal to see what non-Apple kernels were running. I had AirParrot which I no longer use anyway and thought I had deleted.

After following some simple terminal commands detailed on AirParrot's website, I removed all Mavericks-conflicting issues and seem to have my sleep/wake issue on my 2013 MBA fixed. It's only been a few hours, granted...However, having literally tried everything with absolutely nothing working and being able to 100% reproduce the issue on demand...This is very promising.

I might be back on here shortly saying it's reappeared, but wanted to let everyone know ASAP just in case...wish I had known this months ago!