Q: El Capitan Frozen After Sleep

I've never had this option checked, and I still have the problem.

Update on upgrading to VMware Fusion  8, I had my computer "power napping" over the whole weekend and upon wakeup nothing was frozen.  If you have vmware fusion, then upgrading to 8 seems to have corrected the problem or at least made it substantially better .

Well this is odd. Other than updating to 7.1.3 I've not made any other changes to my system. I left VMWare running etc. when I closed the lid on Friday, and opened it a few times over the weekend. And again this morning.

Not frozen.

So either Apple have slid an update in, or VMware has, or it's something else. But for now at least, it's back to normal. Bizarre.

I get the same problem when I leave VMware Fusion 7 OPEN before putting it to sleep. The problem only began after I upgraded from Yosemite to El Capitan.

However, since I updated to VMware Fusion 7.1.3 (as of November 23,2015 from 7.1.2), nothing to report.

Cheers,

I too am having this problem. Mine occurs on a 2013 Mac Pro 6 core 32GB 1TB SSD. I thought it was related to putting my MP to sleep each night (I also had discs set to sleep when possible) I have since left it running all night (i.e. no sleep at all) and each morning when I try to start my work day, the display is frozen black with a SBBOD when I touch return on the keyboard or press a mouse button. Due to what's been said herin, I've now shut off the discs to sleep when possible setting just to see where this goes.

This problem is as repeatable as one can be. I've yet to peruse the system log to look for an error that might indicate what it might be (or at least a related symptom). I've done OS level work (Tandem NonStop) but would rather just use my MP as a photography tool.

This is really quite a damning quality issue on Apple. The folks in Cupertino need to be putting more effort into quality than this problem bears out.

I'll report back any results I get from today's settings or if I see anything useful in the system logs.

I've upgraded to VMWare 7.1.3 and unfortunately, the problem is still occurring.

After opening your lid, try pressing "Command+Control" to unlock your mouse pointer.

Let me know if it works.

First off, I have a Mac Pro (the bigcyclinder) NOT a MacBook Pro; so there is no "lid".

Secondly, this did not work. The SBBOD is still there and I had to reboot (as I now have to EVERY MORNING).

But thanks for the suggestion...

Folks: note that in my case (Mac Pro 2013 (NOT a MacBook Pro)), that turning off the "put disks to sleep" option had no effect.

I still have to reboot EVERY MORNING because either the screen is completely locked up or I get a SBBOD upon pressing a key on my keyboard or pressing a mouse button.

As a Mac Developer, I will be opening a case with Apple; this is absolute crap of an OS performance!

Will advise ...

Are you a VMware Fusion user?

Yes, but I only run it when I need to: about once every two weeks. I also use Parallels VM around once a day. I use no other VM env and never leave one running (as some have I have noted in this email trail).

I DON'T HAVE A MACBOOK PRO, IT IS A Mac PRO (NO LID)!

Please don't yell mdturnerinoz.  We're trying to keep this forum productive.  Posting three times the same thing is not helpful.  ALL CAPS psts are not helpful.

I'm not sure you have the same problem as the rest of us.  The problem discussed on this forum is Mac laptops freezing up after deep sleep and it's relation to VMWare Fusion. 

You mentioned you have VMWare but only run it periodically.  Have you noticed your problem as it relates to when you are (or are not) running VMWare?

I don't know why you're shouting. 'northamerigan-jack' wasn't even replying to you, and you're in a forum for the Macbook Pro on a thread started by someone with a Macbook Pro.

It may well be that there's a wider OS level issue here that is nothing to do with MBP or indeed VMWare Fusion... but you may as well remain civil.

In the inimitable words of the late Don Adams ("Get Smart"): "sorry about that, chief..."

My situation may be related to what you all are seeing, but I'm not sure how I can verify that other than my config. I have no need to run either of my VMs (Parallels or VMWare Fusion) unless I'm using the underlying VM at that time (I run Windows 8.1 under Parallels and Bugzilla under Turnkey Linux under VMWare); I use both VMs because I'm too lazy to consolidate the underlying OSes under one or the other.

Has anyone found any syslog entries that might key us in on what's hanging? I know that a MBP and MP are different hardware envs, but this sure smells like some sort of process loop with interrupts disabled or the like. If there is a way to have Activity Monitor log (or some other equally useful tool), we might be able to "catch" the process (or maybe it's even an errant driver) causing the lockup. Perusing thousands of log entries can be a real pain.