CRASH WHEN WAKING FROM HIBERNATION / DEEP SLEEP

Question

Level 1

4 points

CRASH WHEN WAKING FROM HIBERNATION / DEEP SLEEP

Hi All,

2011 Macbook Pro 15", OS 10.6.8, 750GB Western Digital Black 7200rpm, 16GB RAM

I have searched and found several different discussions regarding this issue. When the battery gets low the OS forces a system hibernation / deep sleep. Once you connect the macbook pro into a charger and try to wake, it gets about 1/2 way through the grey bars and then crashes, and then keeps beeping indefinitely. The only thing you can do is to force a hard reset. Everyone seems to think it is related to an SSD Hard drive, but I have a traditional 7200rpm HDD and it still happens to me. The answer from Apple is "dont run your battery down that far". I am sorry but that is NOT a solution. I am on the road ALL day and sometimes I simply do NOT have access to recharging my macbook pro. The Hibernation / Deep Sleep feature should function correctly as it has done since TIGER 10.4. Can someone please chime in on how to ACTUALLY REPAIR this feature.

MacBook Pro, Mac OS X (10.6.8), 15" / 750GB HDD / 16GB RAM

Posted on Feb 2, 2012 5:31 AM

Reply

Answer 1

Feb 4, 2012 8:50 PM in response to praxiscor1

I am so glad I read this! I have the exact same freaking problem, same model, only I have the 500GB 7200RPM stock HD (Hitachi I believe) and 8GB OWC RAM. I have this happen EVERY TIME now when the computer tries to wake from hibernation. I already got replacement RAM, which I thought was the culprit, since I had my logic board already replaced under warranty for the weird black screen with loud fan and solid power light on startup issue. But to my dismay this hibernation 3-beep of bad RAM garbage is still happening! I have no solution but I can add that I constantly use Parallels and it is open everytime I try to wake from hibernation so maybe it is related since that hogs a lot of RAM for me. I am upset though that it makes me force restart and wastes hours of work unless I can make sure to save before I run low on battery. Please help release a firmware or whatever update to fix this!!!! I did not spend almost $3000 on a computer to have it screw up like this... Apple-hello?

Reply

Answer 2

yPhone

Level 1

0 points

Feb 5, 2012 6:15 AM in response to praxiscor1

Same here. I have installed 16 GB as well, and use VMware to run a 4 GB Windows VM.

Reply

Answer 3

praxiscor1 Author

Level 1

4 points

Feb 5, 2012 9:30 AM in response to praxiscor1

Thanks for chiming in guys! I am also running Parallels and allocating 1952MB of RAM. I am curious is that is the common denominator . . . I will try to force the hibernation mode without parallels running and see how it goes . . . if you guys get the chance see if you can do the same and reply with your findings . . . might be helpful for Apple when they are trying to fix this (if they ever fix this). Thanks, Colin

Reply

Answer 4

praxiscor1 Author

Level 1

4 points

Feb 5, 2012 2:31 PM in response to praxiscor1

UPDATE . . . Ok I quit out of Parallels and let the battery rundown. The macbook entered hibernation . . . I plugged it an and VWALA! it started up no problems . . . so this definitely has something to do with the RAM and the way the new MACBOOK Pro and Parallels are assigning it . . . can anyone else comfirm that they are havign the same results?

Reply

Answer 5

Feb 26, 2012 9:48 PM in response to praxiscor1

Yes I can confirm that this is what I was suspecting. When my Macbook Pro hibernates with Parallels running, it freezes with the RAM problem. When Parallels is off, if wakes normally, no problem at all. I am also getting constant bad RAM "access violation", "runtime", and "exception" errors when running RAM-intensive programs that crash whatever I was working on. This is really making Windows unuseable for me but I am struggling with it considering there is no alternative expect using an actual crappy PC.

I found an article on Parallels forum that describes this issue among others: http://forum.parallels.com/showthread.php?t=108735

Unfortunately, it's been an issue for almost a year now and no solution. Really bad support from Parallels if you ask me. Can't say anything about VMWare though, because I do not use that.

Reply

Answer 6

GWitek

Level 1

4 points

Apr 14, 2012 4:47 AM in response to praxiscor1

Yup. Me too! Same symprom, running Parallels and Win7. My "fix" has been to avoid letting the MPB get exhausted. CLEARLY not a good long term solution. Any further progress on this issue?

Reply