Retina MacBook Pro wont wake from sleep

The same problem with reboot here. To me is is obvious that it started to happen after the latest (November) update via AppStore. I would point out to Nvidia engine/drivers update as it was described. After this when I close the lid and open it again immediately it is ok but if the lid is closed for some time mbp will not wake up and I need to hold the power button for 10 seconds to reboot. The Apple HW test says everything is fine, but I have the rmbp for 2 months already and before if was ok.

Apple, please, fix this. It is very annoying to loose all work while travelling from one meeting to another :-(

Follow-up: VLC Player also causes the hanging/vanishing/unresponsive cursor upon quitting.

Electronista has also picked up on this issue:

http://www.electronista.com/articles/12/11/14/sporadic.reports.of.lower.thermal. thresholds.gpu.underclocking/

Is there a way how to downgrade EFI? In case of BIOS it is hard sometimes even impossible to downgrade but I do not have that experience with Apple machines...

The problem with freezing during the sleep is IMHO related to the new nVidia drivers (November release - v305). Before it was ok. If you do not experience issues when running Adobe stuff (Premiere Pro etc.) as this update was released to fix those I recommend do not update. The new version is buggy for some RMBP versions (sadly, my case).

Just to Confirm same problem

after sleep - display is blinknig

this start after november updates

For me the display is not blinking but after more than 1 hour sleep it will not wake up. iIn the kernel trace I see problems with nvidia drivers. To me it seems almost for sure that the nvidia drivers v305 (november update) are corrupted for ML 10.8.2 and RMBP.

Very annoying to loose all work everytime I travel...yet I did not find a proper way to downgrade back 😟

my problems starts AFTER install

MacBook Air and MacBook Pro Update 2.0

Mine has gotten so bad at waking up from sleep that I shut it down completely instead of letting it sleep. It boots up so quickly that it's not horrible, but I do wish they'd fix this!

I identified that what cousing the problem is when the machine is trying to hibernate (deep sleep). After closing the lid it falls asleep, but the memmory is still powered. After specified amount of time it wakes up and writes the content of the RAM to the HDD and falls to a deep sleep. When this happens with the new nv drivers from the September update it hangs up requiring the hard reset as I described.

But there is a workaround to this. By default there is a 70 minutes delay before sleeping and a deep sleep mode. This delay is adjustable. Set it to something higher and the machine will never go to a deep sleep, thus will behave normally and wakes up instantly. Of course this workaround costs some power as the RAM is powered, but to me it is a fix till Apple/nVidia fix the drivers.

I routinely let my MBPr sleep and left it in my backpack when not in use. Twice it overheated to the point where it was too hot to hold. Someone at Apple Care said the aluminum body is part of the heat sink and even when asleep it needs cooling, which doesn't work inside a padded laptop bag with no air circulation. I was advised to turn it off anytime it is stored in the laptop bag.

Firstly I hesitate to provide this information because...

IN NO WAY DO I ADVOCATE OR SUPPORT INSTALLING the NVIDIA CUDA drivers here because it apparently will not resolve the problem, and in fact would probably make things worse.

http://www.nvidia.com/object/cuda-mac-driver.html

What I do find interesting is the information at the bottom:

Known Issues

• There is a known issue in this release where forcing or allowing the system to go to sleep while running CUDA applications on 2012 MacBook Pro models with automatic graphics switching will cause a system crash (kernel panic). You can prevent the computer from automatically going to sleep by setting the Computer Sleep option slider to Never in the Energy Saver pane of the System Preferences.

• There is a known issue in this release where CUDA applications will not automatically engage the discrete GPU on 2012 MacBook Pro models with automatic graphics switching. To run CUDA applications, it is necessary to uncheck the Automatic Graphics Switching checkbox in the Energy Saver pane of the System Preferences.

This GPU/Intel "hand-off", manifesting itself upon sleep/wake-up, almost suggests that this problem is so deeply rooted, perhaps at a hardware level, that only a half-baked solution is workable at best.

I know if this is the case, this MBPr is going back to Apple with extreme prejudice.

My problem was solved through work iwth Apple support

My wake up from sleep issue, which occurred only when connected to a monitor relates to a problem which apparently Apple is studying

USB and Thunderbolt monitors do not mix.

Apple engineers noticed, from my logs whaad forgotten.On the back of my new thunderbolt monitor i had plugged in a Logitech USB receiver for a Logitech wireless mouse.I also had a Belkin USB hub plugged into another port on the back of the monitor.

I don't see the back of my monitor so I forgot about those USB things

Apple suggested I remove the USB items and test.Voila, my problem has gone away!!

I did more research on line and saw that USB and Thunderbolt is an issue raised months ago.

Apple engineers believe the Logitech USB nano receiver was disrupting the Monitor's recognition when I reconnected my sleeping Mac.

I can easily use the USB ports on my monitor and do when connecting a back up drive. I just no longer leave USB plugged in "permanently"

Using Bluetooth trackpad and mouse (apple Magic Mouse)now , happily

Hope this helps some of you

Yes, it helped me definitevely. I had the same problem with a new MacBook Pro Retina with Mountain Lion preinstalled and an Apple Cinema Display (not Thunderbolt, but connected via DVI adaptor to a Thunderbolt port). The computer was apparently noisy and hot, after each long sleep, but refused to awake, with both screens totally black. Removing usb devices previously connected to the monitor seems to have worked. Thank you.

Ciao, Maurizio

I'm guessing it's merged with mine as I'm still live with them.