Is anyone else having a problem with a complete system freeze after Mac wakes from sleep mode? Post OS X Yosemite install.

Following a suggestion I tried unplugging my external speakers from the headphone socket. Bingo, no more freeing!

But I have now a mute Mac mini...

I find out however that if I plug in my iphone earphone the freezing problem does not happen. But this is not a solution, I have been using the speakers for years which are unbranded but not so bad. I wouldn't mind buying new ones, but what if I cannot find ones that work well with Yosemite?

Look at the plugs on the headphones vs the speakers (count the number of "rings".) If they aren't the same the problem might be an incompatible cable.

Unplugging my Logitech speakers works for me. No more freezing. And the hassle of plugging and unplugging that cord is way less than the hassle of having to shut down the computer every time I don't want it to keep using power.

But I still hope for a software fix, since these speakers never caused this problem before. Maybe this discovery can point the developers toward the audio input/output software.

Same problem with Mac (27-inch, Late 2012). This has been an issue for some time and seemingly ignored by Apple. What about "it just works" this does not! Having to hard reboot every morning is worse than my corporate Windows laptop. Suggestions about unplugging stuff every night are dark ages solutions. Get a grip Apple.

I found that when I went into energy saver, my computer was NOT set to sleep. After I set it to sleep in 3 hours, I've now had three straight days with NO ISSUES after waking from real sleep. I don't know whether this setting was changed as a result of the changeover to Yosemite Sam - as in it defaulted to never sleep, so check your settings.

I had this problem and bypassed it by connecting my speaker output to my monitor instead of my mac mini and losing the controls built in to Yosemite. It cured the problem, though. I adjust volume on the speakers or by using the volume slide in iTunes. I came across this temporary fix in another thread which I can't locate now. Hope this helps

Yosemite 10.10.1 update seems to have solved the problem. I have it installed and since then, I have no problem waking up my MBA.

It solved my problem as well. Thanks Apple!

And mine. Whoopee!

this started happening to me 2 days ago after the latest update to Yosemite im starting to go crazy not only does it freeze after sleep but also when I force to power down leaving pressed down the power button (on my MacBook pro 2011 17 in ) it will not boot, all I see is my log in after password it then restars and repeat this lots of times I have to turn off for a while and pray every time that it works it's one every 10 attempts to turn on and react out of it ....very very frustrated since I know next update will take a while to come out and this is my work computer

I'm sure you've seen the fix in the App Store and that your computer, like the rest of us in this thread, is working fine now

I have been having this problem for months...Tried a fresh install of Yosemite and continued to have this problem almost daily when waking computer from sleep. Same thing...system completely freezes and requires a hard boot. I had this with a clean install, and am having it with the recent upgrade to 10.10.1. I thought it was related to parallels, but seems to happen whether parallels is running, installed, or not installed. I thought it might be pathfinder related, but alas it happens regardless of whether pathfinder is installed, running or not installed. Starting to think it is a result of icloud or Google Chrome now as I have recently seen these logs crop up prior to a hard reset, with error noted at suhelperd[217] and excessive wakeups

...

11/23/14 11:10:46.041 AM ntpd[136]: wake time set +1.062175 s

11/23/14 11:10:46.000 AM kernel[0]: BUG in process suhelperd[217]: over-released legacy external boost assertions (1 total, 1 external, 0 legacy-external)

11/23/14 11:10:46.269 AM cloudd[298]: <CKDGlobalConfigurationURLRequest: 0x7fa758f735a0> sent request UUID D5A92191-865D-4BC3-942A-D13420900D16, received (null)

11/23/14 11:10:46.668 AM CalendarAgent[275]: [com.apple.calendar.store.log.caldav.coredav] [Refusing to parse response to PROPPATCH because of content-type: [text/html; charset=UTF-8].]

11/23/14 11:10:46.720 AM CalendarAgent[275]: [com.apple.calendar.store.log.caldav.coredav] [Refusing to parse response to PROPPATCH because of content-type: [text/html; charset=UTF-8].]

11/23/14 11:10:47.440 AM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.

11/23/14 11:10:47.717 AM discoveryd[49]: AwdlD2d AwdlD2dStartBrowsingForKey: '_airplay' Browsing service started

11/23/14 11:10:47.718 AM discoveryd[49]: AwdlD2d AwdlD2dStartBrowsingForKey: '_raop' Browsing service started

11/23/14 11:10:53.000 AM kernel[0]: BUG in process suhelperd[217]: over-released legacy external boost assertions (1 total, 1 external, 0 legacy-external)

...MULTIPLE

11/23/14 11:10:53.000 AM kernel[0]: bird[254] Unable to quarantine: 93

11/23/14 11:10:53.000 AM kernel[0]: BUG in process suhelperd[217]: over-released legacy external boost assertions (1 total, 1 external, 0 legacy-external)

...MULTIPLE

11/23/14 11:10:55.625 AM CalendarAgent[275]: [com.apple.calendar.store.log.caldav.coredav] [Refusing to parse response to PROPPATCH because of content-type: [text/html; charset=UTF-8].]

11/23/14 11:10:55.675 AM CalendarAgent[275]: [com.apple.calendar.store.log.caldav.coredav] [Refusing to parse response to PROPPATCH because of content-type: [text/html; charset=UTF-8].]

11/23/14 11:11:21.000 AM kernel[0]: pci pause: SDXC

11/23/14 11:12:05.000 AM bootlog[0]: BOOT_TIME 1416769925 0

11/23/14 11:12:09.000 AM syslogd[17]: Configuration Notice:

ASL Module "com.apple.AccountPolicyHelper" claims selected messages.

Those messages may not appear in standard system log files or in the ASL database.

11/23/14 11:14:57.000 AM kernel[0]: process Google Chrome He[326] caught causing excessive wakeups. Observed wakeups rate (per sec): 299; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 45412

11/23/14 11:15:01.446 AM spindump[461]: Saved wakeups_resource.diag report for Google Chrome Helper version 38.0.2125.122 (2125.122) to /Library/Logs/DiagnosticReports/Google Chrome Helper_2014-11-23-111501_shenpa.wakeups_resource.diag

Any help would be much appreciated. Tired of using the hard reset button. Starting to feel like I own a window's machine again.

Dothan08...I bought new Mac few months ago and having this problem. I have Apple Support. But instead of wasting time with them, I thought to ask you if they found a solution for your issue? If yes, what was the root cause?

Hello dothan08,

did Apple support for you resolve your/our issue ?

If so, how ?

On May of 15th 2016 I have the same issue.😕 So many months after installing Yosemite release.

I remember this issue appeared on September last year for the first time. I hope the upgrade to El Capitan resolves it, but not.

Today I reseted SMC, but since issue appears randomly, I do not have the result of my action.

I have a MacBook Pro (Retina, 13-inch, Late 2013) with OS X El Capitan Version 10.11.4.