It is DEFINITELY not a hardware problem.

FORCED RESTART to get your computer up and running is like having to get out of your car to hand-crank the engine to get it started.  This is a big problem and I am so surprised that Apple hasn't yet addressed it.

I have a Mac Mini running 10.11.3 and this just started happening about January 2016.  If it sleeps for a short while it's fine. When it sleeps for a few hours the keyboard and mouse no longer work.  The system is not hung because if I press the power button momentarily the screen will come back to life and I can see messages and notifications popping up.

VERY FRUSTRATING !!

Apple - You really need to fix this. The problem has been going on for a long time.

MacBook Air (13-inch, Mid 2011)

OS X El Capitan ver. 10.11.3

I have no VMware or Fusion. After installing El Capitan, I have been experiencing frozen Macbook 2-3 times every day after long sleeps. For example, after closing lid for few hours, Macbook wake up but touchpad is not responsive and seems frozen. Someone discussed about VMware or Fusion issue, but in my case, similar to some other people's report, I DO NOT have these apps, and this problem persist after installing El Capitan. Thus, my guess is that some bugs in the El Capitan in my case.

Exactly the same problem. Same timescale.

Mac Mini 2.6GHz Intel Core i5, 16Gb 1600MHz DDR3

El Capitan 10.11.3

System still running - can see screen and all apps after clicking the power button. Can see cursor. No response from keyboard, mouse or keypad (all Apple)

replugged into another usb - still no response.

I'm doing a forced reboot every morning. Once its up I can make the system go in and out of sleep manually but after an indeterminate amount of time ( at least an hour I think) above input peripherals appear not to function. MacOs puts up a message saying no bluetooth keyboard connected and that dialog box sits there with the wheel spinning.

So assuming the forced reboot is not the healthiest way to restart I decided to shut down the Mac every evening and start up again in the morning.

This morning the cursor failed to appear! It usually starts life in the top left hand corner on my system but no sign and no response from the keyboard so I couldn't use keyboard shortcuts to navigate either. Another forced reboot restored the cursor. I did take the opportunity to zap the PRAM as well.

I've now disabled any energy saving and just set the screen saver to start after 15 mins which suits the way I work.

Feels like a software problem - it only started for me after upgrading to 10.11.3. And it reminds me of the "Mac mini 2014 won't wake monitor via HDMI" which went on for ages with Apple blaming everything but themselves and then fixing it with a software update.

So I guess it's the old waiting game.

Here's another log for the fire. Just clean installed el capitan. Didn't shut my mac for the first week or two it was running while I restored files. But now when I close my mac, when I open it up it's frozen. Sometimes I can still move the mouse, but the clock is always frozen (I have seconds turned on) and the cursor to enter my password doesn't blink.

Have almost nothing on my computer except for chrome and backup software. Do have virtualbox, but problem happens when it isn't running.

Will probably pay apple for support, if I learn anything I'll share.

I don't think it is related to El Capitan specifically.

My laptop:

Macbook Pro Retina SSD mid 2014

Mavericks 10.9.5

It initially all started with the internal trackpad not working on waking about 2 months ago. Now if I close the lid for more that a few minutes the keyboard freezes on opening the lid. My bluetooth mouse works fine but I can't log in because of the keyboard. The caps lock button doesn't light. The only key that will work is the power button. The only way to get the keyboard responsive again is to do a hard reboot. The trackpad very rarely works now and I'm forced to use my bluetooth mouse. So I suspect the keyboard issue is related to hibernation. Heaven only knows why the trackpad will not work.

So every time I finish with the computer I have to shutdown and to reboot to use. I'm certainly glad that this will only take about 20 sec.

I have Parallels loaded and will occasionally use a window 8.1 virtual machine. Interestingly if a close the lid and reopen it with windows 8.1 going the trackpad will occasionally  works fine, but this is very sporadic and most of the time I can't replicate it.

I do not think it is a hardware issue though rebooting in safe mode will not make my trackpad responsive.

I have tried all of the suggestions in this tread but nothing has helped.

Somehow I don't think taking my laptop in and getting the trackpad fixed or replaced will help, especially since the trackpad will work perfectly from time to time.

Paul

I looked tru this thread, and not seeing the solution I decided to experiment a bit: What helped me was to stop animations in the dock, including those for opening and closing applications. In my opinion there may be a memory leak with the animations triggered by the dock as this freeze after long sleep at times shows flashes over the screen, typical for memory issues in my experience. It is short day, but so far I have not been frozen after sleep. keep fingers crossed.

I never had this problem before upgrading to El Capitan. Specifically, I'm on 10.11.3 with a 2011 MBP. The past 2+ weeks, every time the laptop went into deep sleep, the screen remained black upon opening it, even though the keyboard would light up and I could hear notification alert sounds. The laptop was also extraordinarily warm, especially for having been in hibernation for many hours, as if it were stuck in some processing loop despite being "asleep". Pressing any key didn't work. Closing and reopening the cover didn't work. Waiting some period of time for it to wake up didn't work. Only fix was rebooting with power button. Short periods of sleep were fine; only deep sleep caused this problem.

Last night I tried the second part of gmd's solution above (http://www.macissues.com/2015/05/08/how-to-fix-your-mac-not-waking-from-sleep/). Specifically, I deleted the hibernation file, by entering the following in Terminal:

sudo rm /var/vm/sleepimage

This morning was the first morning in about 2 weeks that I haven't had to do a reboot with the power button to wake the laptop up from deep sleep. Assuming this happy situation continues, I'm calling this a complete solution. Will report back if it turns out this isn't a permanent fix.

The Bad News:

Alas, I spoke too soon. Erasing the hibernation file works, but it works exactly once. The second time the computer goes in deep sleep, I'm right back to where I started: dark screen and having to reboot with power button.

The Good News:

If you re-erase the hibernation file, it works again. So now I've got a Terminal window permanently open, and every time I wake the laptop up from deep sleep, I re-erase the file to assure smooth wake-up the next time. Obviously a PITA, but until a better solution presents itself (and I leave it to someone with way more expertise to figure out what's going wrong with the hibernation file every time it's rewritten), it's at least something that's fast/easy to do and keeps me from having to reboot Every. Effing. Time.

Hope that helps others.

I'm having mixed success with this http://www.macissues.com/2015/05/08/how-to-fix-your-mac-not-waking-from-sleep/ as mentioned by multiple others.

Before I tried it, essentially every time I hibernated my system would crash on wake. Since running the commands, I've hibernated 5-10 times, and only crashed on wake once. If I go a week or so without a crash maybe I'll consider it fixed.

Since I installed El Capitan I had this problem regularly with my MBP 13" 2011. Finally I found out that running VMware Fusion caused this problem, even after updating it to VMware 8. The only non-original hardware was a 3rd party 8GB RAM (shortly after purchase iin 2011)  in it and a 500GB Samsung 850 Pro SSD instead of the original 320GB harddisk (early 2014), but never had problems with theis hardware.

Virtual every time after running a VMware session (with Windows 10 or Windows 7) and after shutting down the Windows guest and completely exiting VMware Fusion I closed the lid (or let it 'fall asleep' by leaving my macbook unattended).

When I opened the lid, the screen remained blank and had to reboot by long-pressing the power button. Once this even happened during a long image stacking session under Windows (under VMware) and the screen turned off.

In all cases my Macbook was reachable by SSH from another computer or cellphone with an SSH client, so it is a GUI problem.

So I decided to migrate my VMware images to Virtual Box 5 and the problem disappeared completely. No more blank screens after opening the lid and neither after hibernating after use of 'Deepsleep'.

Anyway, this is a VMware issue, but partially also an OSX issue as OSX should withstand ill-behaving apps.

Oh boy, this problem started for me suddenly about 4 days ago. In my case, the trackpad completely freezes after waking from sleep. The keyboard is fine. Looks like the community is on its own...

My $0.02:

MacBook Pro 13" Early 2015

OS X 10.11.4

- I'm running Parallels, but that doesn't seem to have an effect one way or the other. The same thing happens whether or not Parallels is running.

- It seemed at first that it was only happening after hibernation (not after sleep) because it would only happen when I opened my laptop in the morning. I used pmset to disable hibernation (mode=0). But, the problem persists.

- Still oddly, however, it doesn't happen during the day when I open and close my laptop during the normal course of business. Does anyone else see a correlation to amount of time that the system is sleeping?

- I'm going to try to disable FireVault to see if that is related at all.

And, a naive question from a long time Windows user... why can't I just re-install the trackpad drivers?