MacBook Pro (Retina, Mid 2012) freeze with Yosemite

The issue is still present in 10.10.3 for me. Just had another system freeze and reboot, identical to the issue that I've always had since upgrading to Yosemite.

MacBook Pro Retina mid 2012, as per thread title.

@Jimaroid ... hmm, have you experienced it under Mavericks? If yes, then in your case it may be an actual hardware fault (your model is listed as affected models here: https://www.apple.com/support/macbookpro-videoissues/)

I've been watching this thread with interest, as my mid 2012 MacBook Pro Retina has been driving me mad since I 'upgraded' to Yosemite

MacBook Pro (Retina, Mid 2012)

2.3GHz Intel Core i7

8GB 1600 MHz DDR3

Intel HD Graphics 4000 1024 MB

I've had numerous online sessions with apple, none of which have helped, so I was relieved to see there is a 'recall' for affected models.

Having contacted my local iStore (nearest apple store is 60 miles away) they have told me to repackage it in its original box (otherwise they will charge me £50 for the privilege) and then they will send it away to be looked at. If it's deemed to be 'faulty' then they will repair and apple will pay the bill. If the fault isn't recognised by apple then I have to pay to have it repaired...

What is all that about??

I'm going to send it away regardless, and tell them that if it isn't covered by apple I would like it back as is, as I am not prepared to pay for repairs on a £1800 laptop that is only just over 2 years old!

JWDemon wrote:

NO, YOU ARE MISSING THE POINT! Your NVIDIA GPU with CUDA will allow you to use your machine, would you rather fight with it or do without it and continue posting your complaints or would you rather use your machine??? There are many other applications, including Apple apps that can benefit from the use of CUDA with the NVIDIA GPU. Your waisting your time if you think Apple has any type of priority to try to fix this issue. Oh, and the freezing problem comes from the Automatic Graphics Switching routines so it's software related but I wouldn't hold my breath for a fix.

This is not the case. Apple software uses OpenCL, which is equivalent to CUDA but not based on (nor makes use of) CUDA. OpenCL allows accelerated code to run on any support CPU or GPU without the developer understanding proprietary specifics, whereas CUDA is nVidia only. The reasons for this are pretty clear: Apple ships 3 different types of GPU's: nVidia and AMD on the Mac and PowerVR in the AX chips on iOS devices. OpenCL accelerated code will run on all of them. CUDA does not.

The CUDA driver increasing stability for you is probably purely coincidental.

Just FYI - been watching this thread for a while. Same issue here - MBP Retina Mid 2012 with 650M and Intel HD 4000. Disabling graphics switching (in Energy Saver) solves the problem.

For the record, I have the CUDA driver installed for some legacy acceleration code and stability is not affected by it; only thing that improves the system is to disable use of the integrated HD4000 GPU completely and incur the associated battery life reduction and heat increase.

Pleas stop talking about that CUDA thing again, the software doesn`t do anything, not with this bug.!!! I have been running OS X 10.10.3 beta now for almost 2 weeks, no graphic cars switching problems yet...

Those of you that have this freezing bug, turn off automatic graphic switching in power settings or upgrade to 10.10.3 beta.. Do not bother to download this CUDA thing (1 person at this thread began to refer to it). Ill say it again, and I am going to post this message a couple of times: CUDA = worthless with this bug.

mariusa wrote:

Pleas stop talking about that CUDA thing again, the software doesn`t do anything, not with this bug.!!! I have been running OS X 10.10.3 beta now for almost 2 weeks, no graphic cars switching problems yet...

Those of you that have this freezing bug, turn off automatic graphic switching in power settings or upgrade to 10.10.3 beta.. Do not bother to download this CUDA thing (1 person at this thread began to refer to it). Ill say it again, and I am going to post this message a couple of times: CUDA = worthless with this bug.

... which is what I just said. Please read before replying.

I just suffered my first total freeze under 10.10.3 beta. This is also the first freeze since I installed 'gfxCardStatus', and interestingly, there was no switching in GPUs when the freeze occurred. Moreover, there was nothing in the crash logs about the GPU (granted, I don't always show a crash log after freezing, although I used to see "GPU restart" in some instances).

I just suffered my first total freeze under 10.10.3 beta. This is also the first freeze since I installed 'gfxCardStatus', and interestingly, there was no switching in GPUs when the freeze occurred. Moreover, there was nothing in the crash logs about the GPU (granted, I don't always show a crash log after freezing, although I used to see "GPU restart" in some instances).

That means that your freeze has another source. There are a lot of them in Yosemite. The thing that this thread about always occurs while switching between cards.

By the way. I am about week with 10.10.3 already. And no sign of freeze. All my efforts to make it are vain. Before this, i could freeze 10.10.2 during 10 minutes if i wanted.

I don't want to celebrate too soon, but it looks like very good version of Yosemite for all with this problem.

Update on my situation:

It's been about a week and a half since I got my mid-2012 rMBP back from the Genius Bar with a logic board replacement under Apple's new repair program. Up until this point I had not had any issues with freezing/restarts/or GPU lockups. However, I just had an incident where everything freezed except for the mouse cursor and then came back to life. This happened a few times in succession, but the machine did not restart. I checked the Console, and sure enough, the logs show four GPU Resets on the Intel GPU, about 5 seconds apart. It appears as if this time, the OS was able to restart the GPU successfully after a few tries.

I was browsing a website in Safari, not doing anything abnormal or heavy, and the machine is only very slightly warm to the touch (so I don't think this is a heat issue). The fact that the machine did not restart could still mean that the logic board replacement solved something, but at this point it appears that this issue is indeed not entirely hardware. I am on 10.10.2 and have not tried the 10.10.3 beta (would prefer to gather more data first before I switch over to 10.10.3).

I just insatlled 10.10.3 beta but it still says 10.10.2 in the About window, and launching the new Photos fails saying I'm on 10.10.2 ... however, the update does show as installed in the App Store. DId anyone else experience this?

Repeatedly toggling the GPU switching in Energy Saver preferences no longer freezes my rMBP Late 2013. On 10.10.2 it would freeze almost instantly (at the 2nd toggle). It seems 10.10.3 did fix the issue ... any clues about the reporting of 10.10.2 instead of 10.10.3 though?

I've just dropped my MacBook off with my local iStore.

They didn't test it, just checked it over and asked me what the issues I was having were.

Apparently, it's going to have a new graphics card fitted, as that is what apple have told them to do with all affected machines...

We will see what happens when it comes back in 2 weeks!

I can definitely recommend anyone that had this problem to try out 10.10.3 in the Public beta. I've upgraded just yesterday but my machine has not had any freezes since and I've been doing extensive stress-testing today.

When updating you should expect spotlight re-indexing and if you use the Photo's app a lot of CPU usage for indexing photos, which can take hours depending on the amount of photos you have. Just be patient 🙂

I had to stop myself from throwing my MacBook Pro Retina Early 2013 across the room. Honestly, I had it ready for launch, and only calmed down when I realised I'd then have to buy a new one, and Apple are getting no more money from me until this is fixed.

My MacBook Pro used to be the epitome of reliability and stability. Now it's an embarrassment of instability. It all changed when Yosemite was installed.

It's bad enough that it does crash, and then asks to report GPU panics to Apple (therefore they must surely know of the problem), but since 10.10.2 I can get a brief look at the display as it re-boots before it goes to a black screen. Today was the worst and took several re-starts and then lid-downs before the machine became active again. Once it's back up and running it's usually fine to be put in standby and woken up again, until the next time Yosemite crashes.

Not buying another Apple product until it's fixed, and to be honest, the experience has seriously dented my confidence in buy Apple products at all.

I have a 2012 cMBP with a 512MB GT650m. I didn't take the time to read the entire thread, but I believe that most people are seeing this problem on retina MacBooks and those with cMBPs generally have the 1GB version (not that it is much different).

I've been dealing with this issue (frozen screen except for mouse) since I've upgraded to Mavericks (no issues on Mountain Lion), but today was the first time the console has shown a GPU reset, allowing me to find this thread. Normally, no logs appear so I was never able to determine the issue.

As with everyone else, repeatedly checking the Automatic Graphics Switching box can force the issue quite rapidly. I have registered with the 10.10.3 public beta, but I never got it to show up possibly due to a bug with registration for the Yosemite public beta over the summer. Right now, running dGPU only so far has been working fine. Hopefully when the official 10.10.3 update drops we can see some improvements with this issue.