-
All replies
-
Helpful answers
-
Jan 5, 2016 5:06 AM in response to zcolbsterby dralison3,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.
-
-
Jan 5, 2016 12:52 PM in response to F4hadby mdturnerinoz,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.
-
Jan 5, 2016 12:59 PM in response to mdturnerinozby arcticmed,"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.
-
Jan 5, 2016 1:11 PM in response to arcticmedby mdturnerinoz,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.
-
Jan 5, 2016 1:45 PM in response to F4hadby eventhedogshaveipods,Mine presented as a software problem but eventually was conclusively hardware. I've had my laptop back a week plus and its rock solid.
-
Jan 6, 2016 2:58 AM in response to F4hadby batspeck,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.
-
Jan 11, 2016 5:25 PM in response to zcolbsterby Herb-K,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.
-
Jan 17, 2016 10:31 AM in response to zcolbsterby Scott996,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.
-
Jan 17, 2016 1:03 PM in response to Scott996by arcticmed,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.
-
Jan 19, 2016 3:43 PM in response to zcolbsterby mpreilly,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.
-
Jan 21, 2016 9:23 AM in response to zcolbsterby miketyhs,Late to the party, but I'm also having the same issue. After deep sleep with VMs running (running VMware Fusion 7.1.3) it hangs (no keyboard/mouse). Didn't have this problem with Yosemite.
OS X El Capitan 10.11.2
MacBook Pro (Retina, 15-inch, Late 2013)
2.3 GHz Intel Core i7
16 GB RAM
Intel Iris Pro 1536 MB
This is my 3rd Macbook Pro and I'm starting to have doubts about Apple's quality.
-
Feb 6, 2016 1:01 AM in response to zcolbsterby fcadili,I can reproduce this issue in my mac book pro with the following step:
1. close the lid
2. wait till the mac go to sleep (some minutes).
When I reopen the lid the mac was not responsive.
I do some searching and I discover "clamshell" mode. The official support describe how to use a mac with lid closed: How to use your Mac notebook computer in closed-clamshell (display closed) mode with an external display - Apple Suppor…
The easy way to disable clamshell mode is to use InsomniaX downloadable at http://semaja2.net/projects/insomniaxinfo/
However other solution can be found starting from this link: http://apple.stackexchange.com/questions/152777/how-to-disable-clamshell-mode-in -yosemite
Regards,
Francesco
-
Feb 15, 2016 8:42 AM in response to zcolbsterby ehmkay,I was having this issue and using VMWare Fusion 7.1.3. I went through the whole of this thread and others trying a whole bunch of different things. It just got to a point where it was crazy as if I walk away from my computer for 10 mins, I have to reboot it once I come back. Not knowing if I had saved stuff on the running Windows VM or on the OSX e.g. open docs etc. It got too much for me and decided to upgrade to Fusion 8.1.0.
After the upgrade I have not had to reboot once and it has been about 5 days now (I would have rebooted at least 30 times by now). It is really frustrating as this almost feels like a gimmick to ensure people pay the $$$ to upgrade to version 8. I am almost sure it is only a handful of files which were updated, but one definitely has the fix and they don't seem to be porting it back to 7.1.3.
What is interesting is through the thread is there are some people with this issue but don't run Fusion at all. I am just happy to have a "working"machine again. Good luck to all and hope this helps someone.
-
Feb 24, 2016 6:35 AM in response to Mike32768by johnebee,Exactly the same thing has happened to me, ever since upgrading to El Capitan. There are so many people with this same problem I don't know why Apple hasn't notified all El Capitan users that they are AT LEAST working on a fix.