El Capitan Frozen After Sleep

Monday morning the track pad simply stopped working. USB interface would move the mouse, but trackpad was non responsive. After a call to Apple Tech Support I was off to the store. The store confiscated the machine, ashamed of the failure and sent it out for repair.

I've had one DOA Strawberry Imac about 16 years ago. And outside the sound issue on my IIsi, my hardware has always worked. While this has been frustrating for sure, my hardware failures - now across a family - have been extremely rare.

This actually worked for me. It seems it was a hibernation issue i am guessing... anyway its been several days and this seems to have helped...

gmd2283's fix above works really well. Easy to do, has almost completely sorted the problem (just remember to re-do it after OS updates or SMC resets).

Thanks gmd!

re-posting gmd's fix link for ease - http://www.macissues.com/2015/05/08/how-to-fix-your-mac-not-waking-from-sleep/

Got bored of waiting for either Apple to release a patch for the issue or for VMWare to update Fusion 7 so bit the bullet and swallowed the upgrade fee to update to Fusion 8.

So far, it seems to be OK again. Will report back if the issue re-occurs.

Not happy with either Apple or VMWare for this.

I haven't experienced the freezing after waking from sleep since I did the following:

• Upgraded to 10.11.2 (from 10.11.1)
• Disabled the screen saver

The screen saver was really pointless anyway, since the power saving feature turned off the screen before it even kicked in. I have an external 4K Dell display operating in max resolution and it's nearly always connected. I still get 3-4 weird flashes when waking from sleep where it looks like the OS is trying to recognize the attached display — that was usually the point where the freeze would occur. So far, so good.

Guys, do you think this is a hardware problem ?

No, I do not think it a hardware problem.

First off, my main encounter of this problem has been on a Mac Pro (i.e. not a MacBook Pro).

Secondly, since 10.11.2 came out, it is happening much less frequently on my Mac Pro (around four times total since 10.11.2 as opposed to daily before). Also, my MacBook Pro (2015) is not having the problem at all (which might imply a hardware (or better put, firmware (e.g. BIOS)) problem for others).

From watching this case, I can only assume that there are no Apple 3rd party debs in this litany, else, someone would have opened a bug report against 10.11 telling Apple that it is "affecting their product's development" or some such wording. I am a member of the Mac dev program but am not any help as I said it's occurring far less frequently (e.g. Apple will always ask a dev if they have the most recent OS/code installed and if not, put it on before they will address the case).

If it becomes repeatable enough though, I will open a case and see if I can get some attention to this egregiously quality-poor problem.

"From watching this case, I can only assume that there are no Apple 3rd party debs in this litany, else, someone would have opened a bug report against 10.11 telling Apple that it is "affecting their product's development" or some such wording. I am a member of the Mac dev program but am not any help as I said it's occurring far less frequently (e.g. Apple will always ask a dev if they have the most recent OS/code installed and if not, put it on before they will address the case)."

THats total bull **** on Apples part. So you mean to tell me that I have to be a developer (I am in the iOS developers program) in order to get any help or kicking it up to higher support? As I have stated before, one good thing about Microsoft's support forums is that they have actual members of their team moderate the forums and provide timely feedback. I've been on this thread over a month and have yet heard an Apple employee weigh in. And yes I am also an Apple shareholder with several hundreds shares (not in mutual funds).

Its true my prob has since been gone since I down graded my virtual box to an earlier version.

Yes, you are right, Apple should be monitoring forums for serious problems such as this. But, they obviously aren't.

So, all I suggested is a way to directly get their attention on the problem. Having said that, there are no known ways of getting them to watch forums and thus monitor serious bugs (as this is). When someone finds a way to do so, perhaps they will post it here.

Mine presented as a software problem but eventually was conclusively hardware. I've had my laptop back a week plus and its rock solid.

I most certainly hope not. As this is the most expensive piece of hardware I have ever purchased. I have Mac OS X 10.11.2 running on my MacBook Pro 15" Retina with 2,8 GHz Intel Core i7, 16GB of 1600MHz RAM, 1TB SSD and AMD Radeon R9 M370X 2048 MB, AKA MacBookPro11,5 or MJLU2LL/A. I too use VMware Fusion 8 - Version 8.1.0 (3272237), and the Sleep Wake Error still happens often after long sleeps, with or without VMware running. This is really annoying for the supposedly top performance macbook pro this far.

I throw my thread support in, I have tried several of the suggestions within this thread along with many of my own failed attempts and nothing worked. I have the same problem, close the lid on my MacBook Pro and no keyboard or mouse blah blah the same... My system is:

OX X El Capitan

Version 10.11.2

MacBook Pro (Retina, 15-inch, Mid 2014)

Processor 2.8 GHz Intel Core i7

Memory 16 GB 1600 MHz DDR3

Graphics Intel Iris Pro 1536 MB

Seems this problem has gone on for a long time for as many people that are complaining about it. I just shut down the VM and have to wait for stupid windows to boot when I need it.... ***** wasting my time... That is what I always liked about MAC.... they don't typically waste your time on stupid stuff like hanging and booting.. till this upgrade.

I have had this problem for a while. I believe it predates El Capitan. I am on 13" Macbook Pro early 2015, and I am not using any VMware. I also have an office full of mac minis (mid 2012) all of which are running El Cap and one iMac running El Cap and Parallels with Window 10. NONE crash when the screen saver comes on overnight or over the weekend. So the issue is either with the laptop hardware to something to do with how the laptops go to sleep when closed.

I think it is time call/visit apple.

Although you may be correct that it's a hardware issue. However given that people with different macs are having the same issue its hard for me to see why it is hardware. if this issue was with a single line of MacBooks then one can argue it's a hardware problem. but especially when there are also different model years assuming there are interim hardware updates too.

mac pro

macbook pro retina 2014 & 2015

ive seen some Mac airs as well.

I have this same issue. First thought was to reset the SMC. Also on my second custom iMac that the USB ports dont work, Apple is really starting to make ****** products.