Anyone Running Yosemite on a mid-2010 15"

Discussion in 'OS X Yosemite (10.10)' started by sevoneone, Jul 14, 2014.

  1. sevoneone macrumors 6502

    May 16, 2010
    As many owners of this model know, there is a latent problem with the nVidia 330M graphics chip that can cause all sorts of issues that only started to appear in 10.7 and got worse in 10.8 and 10.9 as Apple changed the way the system used the GPU to render the UI. Some people get occasional graphics glitches, others Kernel Panics.

    Just curious is anyone running running the DP releases has one of these machines and if they've noticed if the problems are the same/worse/better?

    I wish Apple would extend the logic board replacement program for this, some of us didn't start to have symptoms until well after the 3 year cutoff.
  2. Sowelu macrumors regular


    Aug 15, 2008
    New York City
    I have a mid-2010 15" MBP and have had 10.7, 10.8 and now 10.9 running and I've never noticed any glitches and never had any kernel panics on this machine. What sort of glitches? Maybe I never realized.
  3. c1phr macrumors 6502

    Jan 8, 2011
    I used to have that model and I did get kernel panics after upgrading to 10.7. At first, uninstalling gfxCardStatus fixed the issue. Once that application was updated, I reinstalled it, and from there on out, NOT using it would cause the panics to come back.

    My brother has the machine now, and I believe always uses gfxCardStatus, but he hasn't reported any panics on 10.9 nor did I have any from 10.9 launch up until December of last year.
  4. FrankySavvy macrumors 65816

    Mar 4, 2010
    Long Island, NY
    I am currently using Yosemite Beta 3 on my 2010 Macbook Pro 15" with the 330m and have had a handful of GPU Kernel panics.

    Brought it to Apple and they tested the hardware and found no errors. He offered to keep the computer for 24 hours for a more thorough test but I declined because the issue has only happened a few times. If it continues happening I will be having them do that test.

    I was hoping it was a bug in Yosemite.

Share This Page