El Capitan Frozen After Sleep

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?

I saw somewhere in this thread a suggestion to delete any unused Bluetooth devices. I had the same issue as a lot of people; if I put my macbook pro 15" to sleep, it would have crashed and I would have to push the power button to reboot, with a "wake from sleep error" report waiting for me. Funny thing was it didn't happen when I was on the road, only when I was home. Deleting all unused bluetooth devices fixed the issue for me

same problem, here is a solution which worked for me:

1. download sleepwatcher

2. edit a file, for example pause.sh with following content (replace Ubuntu\ 64-bit\ 14.04.3.vmwarevm/Ubuntu\ 64-bit\ 14.04.3.vmx with your own VM path)

/Applications/VMware\ Fusion.app/Contents/Library/vmrun stop Documents/Virtual\ Machines.localized/Ubuntu\ 64-bit\ 14.04.3.vmwarevm/Ubuntu\ 64-bit\ 14.04.3.vmx

3. open a terminal and run:

Downloads/sleepwatcher_2.2/sleepwatcher -s ./pause.sh

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

OS X El Capitan 10.11.4 (15E65)

I, too, started encountering this problem suddenly. Occasionally, opening the lid to wake the Mac would leave it in a state where the keyboard and trackpad did not respond. The cursor would not respond to the trackpad and I could not enter my password to login - the Mac is set to require login on wake. After a while the screen would blank out, but as noted in another post, the system was not hung because pressing the power button would cause the screen to come back again. That was the only button on the keyword that appeared to work, however an external USB mouse would move the cursor. I don't have a USB keyboard to test if that would have worked, I suspect it would have.

The fix that appears to work for me (again thanks to another post I believe here), is to UNCHECK the following:

System Presences -> Bluetooth -> Advanced:

• Open Bluetooth Setup Assistant at startup if no keyboard is detected;
• Open Bluetooth Setup Assistant at startup if no mouse or trackpad is detected; and
• Allow Bluetooth devices to wake this computer.

I think I don't need to uncheck the last one for this fix but I have no need for that capability.

I suspect the reason this problem appears occasionally is that at home I have a bluetooth speaker (Sony SRS-BTX500) which my Mac connects to when it wakes us and this pairing is causing the problem. In places where no paring occurs the problem does not manifest itself. I have not tested this theory and I don't know if the problem is with OS X or incorrect capabilities advertised by the BT speaker or some combination of the two. It has only been a week so I may yet find that this wasn't the problem after all and I will post if that turns out to be the case, but for now, this fix appears to be working for me.

HTH

/nitin

Update on my resolution: it was the hardware. I took it to the Apple store, and they replaced the top case (keyboard+trackpad). Disappointing in terms of hardware quality (my Macbook is just over 1 year old), and not over trilled to be laying out more cash for an already very expensive computer, but happy to have the laptop back.

Tip for whoever is facing this issue: check the errors in Console. This tipped me off that it wasn't a software issue. I noticed errors with the AppleUSBLegacyRoot and AppleUSBMultitouchDriver. Essentially, waking from sleep wasn't inherently an issue. It just happened to be that on waking from sleep, the computer was trying to locate/load the trackpad and keyboard. Over time, the hardware was failing more and more, leading to more freeze-ups.

Same problem. Updated to El Capitan because the App Store app forced me too and now the MacBook does not respond to keyboard and trackpad after a long sleep. It is a shame, I never had issues with my Windows computers.

Apple cannot even test their own hardware! You probably have like 7 models to test a new OS against and you cannot even do that? And you say Apple just works!!!

The only reason I use this pice of crap is because I have to write apps for the app store. Steve Jobs would be turning in his grave seeing Apple go down the toilet!

System Version: OS X 10.11.5 (15F34)

Kernel Version: Darwin 15.5.0

Boot Volume: Macintosh HD

Boot Mode: Normal

Secure Virtual Memory: Enabled

System Integrity Protection: Enabled

Model Name: MacBook Pro

Model Identifier: MacBookPro11,2

Processor Name: Intel Core i7

Processor Speed: 2.2 GHz

Number of Processors: 1

Total Number of Cores: 4

L2 Cache (per Core): 256 KB

L3 Cache: 6 MB

Memory: 16 GB

Boot ROM Version: MBP112.0138.B17

SMC Version (system): 2.18f15

This just started happening to my rebuilt MacBook Pro that I got in February. After reading this long thread I see that it is actually a hardware problem. What I want to know is why has Apple not done a recall on this? It is a horrible thing to have to do a hard reboot every time you step away from the computer for an hour! I am really angry about this, and will demand a repair!

I'm not 100% convinced it's a hardware issue because when I upgraded my virtual box build I started having the issue. Once I downgraded the version it was fine again. The issue went away. Which leads me to believe it's more of an OS or software issue. ive since updated my virtual box build to the latest and have not witness any issues. As a matter of fact the new vb build is even better than the old version.

ANother issue I noticed was that when I had avira antivirus installed I was having a hard time uploading my build using Xcode to the App Store. When I turn avira off everything works fine. Since I have deleted avira as I was having issues with my wifi (on another thread) with the last El Capitan upgrade.

THats at my five cents worth.

DOnt one get me wrong. I'm no fanboy. I own a Mac to develop apps. But have since gone on to embrace my Mac. I still run things in Windows because there are certain programs I still need plus with virtual box i can sandbox one system from another.

Bye virtual box is an awesome tool for running Windows in a Mac environment.

I have always loved Macs and have owned them since the old green screen days and in the old days even did a bit of code in Basic, but I am really off the grid when it comes to the new stuff. I hate to admit it but I have no idea what half the things you have said mean. I don't know what a "vertual box" is or "Xcode" or "avira". And having had some experience having to use Windows for work years ago, I cannot imagine wanting in on my Mac. It's a POS as far as I am concerned. I just want my Mac to work right. If it isn't hardware, I have no idea what it is. It didn't do this when I first bought it. It just started a few days ago and I don't remember what updates I may have done. I always do OS updates when I get a notice because it has always worked for me.

I am running El Capitan 10.11.5

This is my machine specks:

Model Identifier: MacBookPro11,4

Processor Name: Intel Core i7

Processor Speed: 2.2 GHz

Number of Processors: 1

Total Number of Cores: 4

L2 Cache (per Core): 256 KB

L3 Cache: 6 MB

Memory: 16 GB

Boot ROM Version: MBP114.0172.B09

SMC Version (system): 2.29f24

If it is a software issue or a hardware issue, I hope someone can help me!

Lol, sorry about that. I'm kind of new to all this Mac stuff as well.

Virtual box is like VM Ware where it allows you to run another "virtual machine" inside the Mac environment. Think of it like having another window open where it runs MS Windows 7/8/10/XP where you can easily switch, say, between Safari and whatever windows program you are using. However, by being a virtual machine, whatever happens on that machine stays on it and won't, like if the windows gets a virus and rather than trying to use an antivirus, you can destroy the machine and restart a new one without affecting your Mac. You can also set up Linux to run within your Mac if you are incline to do so. But from what I know, Mac OS is a variant of Linux/Unix anyway. Its a way of "dual booting" but having to be able to run both OS at the same time.

Xcode is a software development kit that Apple provides to allow you to make apps for iPhone, watch, Apple TV, and Macs.

Avira is an anti-virus program just like Norton's, McAfee, etc.

Its possible that you may have programs that run in the background like an antivirus that is causing this issue and its conflicting with the new El Capitan update. I'm running the same 10.11.5 version and have not have to issue recur.

I remember when I had the issue, what I did was wipe my drive clean and reinstall (be very careful not to wipe out the recovery partition, which I did once.) and slowly reinstall each program to find the culprit and it was a new version of virtual box. I then went back to an older version and didn't have any issues. I am currently running a newer new version of virtual box and have not had any issues.

With that said, there was someone that mentioned it was a hardware issue when they brought it back to the Apple store.

I am really bummed now, because I had my older macbook pro die a bad hardware death and kill my Time Capsule backup at the same time and I lost all my data. I am just now finally getting back to something close to normal and I really don't want to risk wipe. That's how I lost my data before. I went to the mac store and they thought it was the software, asked if they could wipe it and I said "sure, I have total backup". Only I didn't because it got fried too. So now I have the new computer and a new time capsule and I back up a lot of stuff on the iCloud and I do not need to go through all this again. I have never used anything but the mac anti-virus that comes with the computer. It works fine for me. So I have no idea. I am not going to mess with this. I will call Mac Help tomorrow and possible end up in the genius bar again. Ugh.

Update on my system.

The bluetooth config changes did not help and the machine exhibited the same behavior 3 days later.

I then started shutting down all my VMWare Fusion 7.1.1 virtual machines and quitting VMWare before closing the lid and putting the machine to sleep. That appeared to work so I upgraded to VMWare Fusion 8.1.1 as suggested by an earlier post on this thread. That was on on 5/17 and I have not experienced the problem since then (~ 13 days and counting) so I am cautiously optimistic that the VMWare upgrade has fixed the problem. Not other changes made to the machine.

HTH

/nitin