abelliveau

Q: 2011 MacBook Pro and Discrete Graphics Card

I have an early 2011 MacBook Pro (2.2 GHz Intel Core i7, 8 GB 1333 MHz DDR3 memory) running OS 10.8.2.  It has two graphics components: an AMD Radeon HD 6750M and a built-in Intel HD Graphics 3000. Since I've had the computer, the screen would get a blue tint when the computer switched between them.

 

However, as of two days ago, the problem has become substantially more severe.  The computer was working fine, when all of a suddent the screen when completely blue.  I had to force restart the computer.  Since then, the screen has gone awry on numerous occassions - each time necessitating a hard reset.

 

I installed gfxCardStatus, and have discovered that the computer runs fine using the integrated card, but as soon as I switch to the discrete card - the screen goes .

 

I am just wondering what my options are (any input on any of these would be appreciated!):

 

1) Replace the logic board.  Would this necessarily fix the issue?

 

2) Is there any way to "fix" the graphics card? 

 

3) Keep using gfxCardStatus and only use the integrated graphics card.  This is definitely the easiest/cheapest option, but to have such a computer and not be able to use the graphics card seems like a real shame.

 

4) Is there any other alternative?

 


MacBook Pro, OS X Mountain Lion (10.8.2), 2.2 GHz Intel Core i7, 8 GB memory

Posted on Feb 1, 2013 4:45 PM

Close

Q: 2011 MacBook Pro and Discrete Graphics Card

  • All replies
  • Helpful answers

first Previous Page 92 of 891 last Next
  • by Taranbeer,

    Taranbeer Taranbeer Nov 16, 2013 9:29 AM in response to apple_power
    Level 1 (0 points)
    Nov 16, 2013 9:29 AM in response to apple_power

    These are the pics from all the squence and what all i got as a result from all the tricks i tried to boot the laptop blue one is from the recovery menu. I don't know how to go into diagnostic mode. If you know how to do that and if its safe tell me will try and post you the pics over here.

    https://www.dropbox.com/sc/gl36se2spp605f5/GhJyFTW702

  • by FredBrazil,

    FredBrazil FredBrazil Nov 16, 2013 9:49 AM in response to apple_power
    Level 1 (0 points)
    Nov 16, 2013 9:49 AM in response to apple_power

    You said only:

     

    "As soon as your Finder comes up (if you have lots of Apps open, close them all)  download gfxCardStatus, start it and select 'Integrated Only' "

     

    as can be observed left a space between the two texts, to leave it understood ...

     

    Yes, Taranbeer, I just copied the post and added more to it,

     

    forgiveness for the misunderstanding

     

     


  • by FredBrazil,

    FredBrazil FredBrazil Nov 16, 2013 9:57 AM in response to apple_power
    Level 1 (0 points)
    Nov 16, 2013 9:57 AM in response to apple_power

    If Apple is not responsible and does not solve my case I have to stay with a MBP expensive does not work? No!!

    What I am suggesting is it has worked in some cases, but if you believe it is not a good option, ok, we're all trying to find a solution to a mess of Apple.

     

     

  • by FredBrazil,

    FredBrazil FredBrazil Nov 16, 2013 10:00 AM in response to abelliveau
    Level 1 (0 points)
    Nov 16, 2013 10:00 AM in response to abelliveau
  • by MJSfoto1956,

    MJSfoto1956 MJSfoto1956 Nov 16, 2013 10:05 AM in response to abelliveau
    Level 1 (0 points)
    Nov 16, 2013 10:05 AM in response to abelliveau

    For those of you who think that GPU overheating is unique to Macbook Pros, you might want to read the following thread which shows that gamers too have "sudden crashes" -- this particular discussion centers around driver issues (i.e. software) causing the overheating. I found it fascinating the parallels to what we are experiencing on our MBPs

     

    http://www.tomshardware.com/forum/315789-33-overheating-huge-temp-increase-crash es#.

     

    Michael

  • by SpaceBacon,

    SpaceBacon SpaceBacon Nov 16, 2013 10:21 AM in response to MJSfoto1956
    Level 1 (5 points)
    Nov 16, 2013 10:21 AM in response to MJSfoto1956

    The 70 degrees Celsius claimed by op in that thread is no where near  overheating. Additionally overheating is not a constant with the particular glitches we are seeing here as glitches can happen immediately on startup from a cool machine. After reading all 90 pages of this thread it seems that reballing and removal of excess thermal paste is the solution. Not firmware, drivers, software or overuse. Overheating could possibly be the catalyst but not the core problem.

  • by FredBrazil,

    FredBrazil FredBrazil Nov 16, 2013 10:24 AM in response to SpaceBacon
    Level 1 (0 points)
    Nov 16, 2013 10:24 AM in response to SpaceBacon

    Just is this...

  • by MJSfoto1956,

    MJSfoto1956 MJSfoto1956 Nov 16, 2013 10:55 AM in response to SpaceBacon
    Level 1 (0 points)
    Nov 16, 2013 10:55 AM in response to SpaceBacon

    I think the key thing is that the OP of the thread made a claim that is very similar to ours: that "suddenly" his machine started acting up. And that everyone is in agreement: 70° C is not the root cause but in his case the discussion explored the concept of drivers being the issue. Additionally mention was made of the video RAM which has been brought up repeated in our own thread.

     

    I think dismissing something out of hand because you have come to your own conclusion is not helpful. A more open mind is what is needed right now as we explore every avenue.

     

    YMMV

     

    Michael

  • by bartfromkortrijk,

    bartfromkortrijk bartfromkortrijk Nov 16, 2013 11:09 AM in response to abelliveau
    Level 1 (0 points)
    Nov 16, 2013 11:09 AM in response to abelliveau

    This is an Apple issue and time to have feedback from Apple?

     

    https://discussions.apple.com/message/23784189#23784189

     

    Had to buy a new MBP today. 15" still in repair ... after 2y5m.

  • by Dricks123,

    Dricks123 Dricks123 Nov 16, 2013 11:30 AM in response to abelliveau
    Level 1 (0 points)
    Nov 16, 2013 11:30 AM in response to abelliveau

    What do u guy think of this post....i found it in a similar thread here -  https://discussions.apple.com/thread/2768351?start=2130&tstart=0

     

     

     

     

     

     

    Update on my situation: my MacBook Pro 17-inch, late 2011, had all the problems everybody else is describing in this thread. And now they seem to be resolved. This is how:

     

    I was desparate because when the machine basically became useless while working in Saudi Arabia and on the clock with a project, since there is no Apple Support in the country. Luckily, in nearby Bahrain there is, and teh good people at iMachines Manama have taken it in for repair. First, they put in a first new logic board, but the problems came back within less than 24 hours. Then, they put in another one. This time, I insisted that I could not afford to loose any more time, and money - and because I brought them the MacBook Pro literally on the last day of Apple's warranty for the machine. So they kept it under observation for 4 days. And ran all possible analyses. Bottom line: the 16GB of RAM I had installed on the machine had created the problem. Now, I am back with 8GB of RAM with only one DIMM socket occupied.

    Yes, to be honest Apple officially does not support 16GB of RAM, and yes, the 8GB DIMM really is faulty. Anyways, for the last 8 days I had no problems whatsoever.

    I have another 80 days of warranty for that repair, so there is virtually no risk I am stuck with this problem and a huge sum to pay for repair. But it seems to me that this time, the "culprit" is not Apple. Will update you in about 80 days or so. In the meantime I recommend that you check your RAM, if you upgraded your machine and if this upgrade is officially supported or not. Cheers!

     

     

     


  • by degger,

    degger degger Nov 16, 2013 11:32 AM in response to MJSfoto1956
    Level 1 (0 points)
    Nov 16, 2013 11:32 AM in response to MJSfoto1956

     

    I think dismissing something out of hand because you have come to your own conclusion is not helpful. A more open mind is what is needed right now as we explore every avenue.

     

    I don't think anyone here is dismissing valuable facts. But we're already at a point where it is very clear that this is a permanent hardware failure not a temporary problem so your post is not really helping anyone already having the problem.

  • by SpaceBacon,

    SpaceBacon SpaceBacon Nov 16, 2013 12:07 PM in response to Dricks123
    Level 1 (5 points)
    Nov 16, 2013 12:07 PM in response to Dricks123

    This is a possibility for me as I do have 16GB of 1600 MHz DDR3 corsair ram. I will swap out and report back here but it will be a couple weeks before I am back home where the old ram is. For now the solution for me is still bypassing discrete with gfxCardStatus.

  • by Wojzo,

    Wojzo Wojzo Nov 16, 2013 12:13 PM in response to SpaceBacon
    Level 1 (0 points)
    Nov 16, 2013 12:13 PM in response to SpaceBacon

    SpaceBacon wrote:

     

    This is a possibility for me as I do have 16GB of 1600 MHz DDR3 corsair ram. I will swap out and report back here but it will be a couple weeks before I am back home where the old ram is. For now the solution for me is still bypassing discrete with gfxCardStatus.

     

    FWIW I upgraded my ram first to 8GB then to 16GB, the original 4GB of ram was in my MBP for maybe 4 weeks. Once the issues started I too suspected RAM and I switched back to Apple's original 4GB.

     

    Sadly the issue persisted.

     

    I ran Apple's daigs on both my 16GB and 4GB, neither failed the tests.

     

    If it was a RAM issue then you'd expect to experience the problems on both the Discrete and Integrated, even more so the Integrated video card as that leverages your system's RAM.

  • by SpaceBacon,

    SpaceBacon SpaceBacon Nov 16, 2013 12:14 PM in response to MJSfoto1956
    Level 1 (5 points)
    Nov 16, 2013 12:14 PM in response to MJSfoto1956

    I havn't come to this conclusion on my own ... it's the others in this thread that had their GPU reballed and the excess thermal paste removed that claimed this fixed the specific issue of the OP.

     

    I have not seen any proof in this thread that changing anything non hardware related has fixed any of the symptoms to date. That's all.

  • by Stevie-B813,

    Stevie-B813 Stevie-B813 Nov 16, 2013 1:03 PM in response to Dricks123
    Level 1 (0 points)
    Nov 16, 2013 1:03 PM in response to Dricks123

    When I first encountered problems with my GPU, after my first logic board replacement I did discover that somehow my 8GB of OWC ram did go bad as well. So I switched it back to the original 4GB of Ram and that held up for awhile but a week later the issues came back

first Previous Page 92 of 891 last Next