MacBook Pro (Retina, Mid 2012) freeze with Yosemite

This article from november sums up the issue we're encounting (and rightfully links to this thread): http://www.macnn.com/articles/14/11/04/several.support.threads.discussing.issue. related.to.gpu.switching/

They say that Apple is aware of this problem and that GPU-related bugs in Yosemite are on the rise. Let's hope they'll find out what it is, and fix it, be it software or hardware.

I'm guessing that Apple is being very careful how to handle this trying to figure out whether this is a software/Yosemite issue, a failing hardware issue, or worse yet for them, a defective hardware issue caused by new software.

Following the replies in this thread, my issues on my mid-2012 rMBP has been fairly intermittent, I only began experiencing it when I started editing video on the MBP which I normally do on my iMac. So to me it seems there GPU switching is causing the crashes and the handling of the nVidia chip while under a heavy graphical ram load causes the artifacts. I've experienced both fairly often during my video editing project; none since.

I'm seeing a lot of people taking their machines to Apple and switching out the logic board which seems to fix the issue though I haven't seen an clear "yes, logic board replacement fixes the issue. This is the solution to the problem" unless I overlooked it. If the final solution is a logic board replacement, this would be a very costly fix for Apple as this means the logic boards were defective when they were made and this would signal a full recall on sold units as opposed to relying on those with Apple Care to fix theirs. Similar to a vehicle recall, it requires enough of a failed sample size that's consistently reproducible to which they would have to replace all rMBP's with new logic boards. Apple does not want to do that.

It's one thing to have a conversation in a forum on Apple's site discussing the problem; they can somewhat choose to ignore it. However, it's entirely different when the press has taken notice and writing articles which can sway public opinion. This should get Apple to make a public response as to how to fix the issue of defective hardware and not just hacking it to play nicely with their new software. I'm hoping we hear something soon.

cc SychiO;

Hi, Thanks for the info guys.. but can I just add that it isn't *just* Retina MBP. I have a 15" matte screen, Mid2012 MBP with intel HD Graphics 4000 and NVidia GeForce GT 650M cards. And it used to crash all the time. At present I have a fault where (even after the graphic switching has been locked to the internal graphics card) a constant error saying: "A graphics problem has been detected". If I Report it, if just Ignore it (the two options given) the box reappears within 10 seconds, often immediately. So I have to leave the box up all the time! [none of this ever happened before Yosemite].

fyi: The Matte screens are/were actually higher res than the standard 'Gloss' screens, so it could be a graphics call related to the higher res?

Obviously if there was a recall on the logic boards I'd hope it would be for all affected machines, not just a version of them!

@Tara21c

Your case is more severe than others sadly and you should take your MBP to an Apple Store. And I highly doubt there will be a logic board replacement program.

Any update anyone? Success or failure stories?

My MBPr, just a few months old, is being sent out of the Apple Store for repair (see my previous post about this last week.) It was odd, after they agreed to order a new mother board I got a call the next day. They said that after further testing, there were several "bad ports" and they couldn't do the repair in the store, it had to be done at the service center. I don't understand this...does anyone have any light to shed on it? Bad ports? What does that mean, exactly? And what repair would be so complex they couldn't do it right there? Replacing the mother board would certainly fix a "bad port." I'm wondering if they decided they needed to send this to someone working on the problem we're discussing right here. Thoughts? I should have my MBPr back by Friday.

So far so good. As I said before, I decided to update / deactivate every plugin or program that works in the background, and no freeze since.

Interesting... this is kind of what they said about mine.

As my past posts state, took my MBPr in about 3 weeks ago after having issue with Yosemite. When I got it back they said they "replaced the Logic Board and went ahead and replaced the hard-drive cable, but it's not on the repair sheet".

I thought it was odd they wouldn't put the hard-drive cable on the repair sheet...and I didn't know there was a cable, I just assumed it plugged into the board directly.

I still haven't had any issues since I got it back.

I spoke too soon: it tried the link again (http://douglatornell.ca/blog/category/sublime-text/) and when refreshing the page, it crashed. The logs displayed the usual info: GPU reset, "trying restart GPU" ...

I have had the same crashing and artifacts issues as everyone, but I have yet to be able to generate a crash using that link. I just tried with three different browsers (FF, Chrome and Safari), with multiple refreshes back-to-back-to-back after the page finishes loading. I see that it does switch the GPU to nVidia, but doesn't ever crash. Mine crashes when I'm doing intense video editing using Premiere Pro or After Effects.

My specs:

15" Mid-2012 MacBook Pro Retina

2.3 ghz Intel i7

8gb DDR3 ram (1600)

250gb SS drive

Anyone with those specs able to generate a crash with that link? iStat widget shows I have 1.2gb free RAM available when I tried testing, if memory is an issue.

One last effort: I just tried opening Premiere Pro and After Effects, loaded large timelines on both, playing the timelines on both and tried refreshing the link over 10 times and still can't get it to crash. Down to 41mb of available ram. This all seems really inconsistent.

Same problem here. mid 2012 rMBP after installing Yosemite upgrade nothing but crashes. They all seem to be related to the GPU I have tried everything mentioned to no avail. It has been becoming more frequent and more difficult to keep the screen on. At least apple is getting 20-30 error reports a day from me. I suspect a conflict the the GPU on logic board and Yosemite. I would bet apple is desperately trying to solve the problem with a software update otherwise they are looking at a logic board upgrade. As of right now they aren't standing behind the laptop that was the most expensive one they sold at the time. It makes it real hard to consider buying another high end product from them. Maybe all the surface mounted peripherals and integrated GPU wasn't such a good idea.

I have "MacBook Pro (Retina, 15-inch, Early 2013)" and it freezes with Yosemite. Mavericks was fine; worked brilliantly, but as soon as Yosemite was on, boom, it froze.

I also get blocks of corrupt graphics when running Safari, my choice of browser on the MBP. Safari, however, over time starts to gobble up lots of memory. Impressively it's still responsive.

What I have done, and what has made the system useable, is removed FLASH. You know Adobe software is bad when you're getting more updates for their products than Microsoft give out for Windows! Having removed Flash there's some sites I don't get the neat animations, but I've discovered that YouTube still works; perhaps even better now. So I'd certainly recommend deleting Flash.

I've read how people are getting logic boards replaced because of Yosemite problems. I'm not entirely convinced it's a hardware problem. Or if it is hardware, then one which the software should be smart enough to avoid. Reason for my belief is fairly simple; Mavericks worked!

Apple Developer Relations: Duplicate of 18323051

Engineering has determined that your bug report is a duplicate of another issue and will be closed.

So my bug report at bugreport.apple.com is closed as of now and I have no access to the original issue. I guess they are aware of the problem.

Bit worrying if Apple start closing down reports; how are they going to measure the scale of this problem?

They didn't close the report, the consolidated it into another one. It is unfortunate though that mostruash does not have access to the other duplicate.