flips01

Q: Recurring error: A graphics problem has been detected.

All of a sudden I'm now getting:

 

A graphics problem has been detected. Click "Report" to submit report...

[Ignore]  [Report]

 

And if I click any of the choices it comes right back pretty soon.

(It's less annoying just leaving the error message there.)

 

This is on a MBP 15" Retina late 2013 running latest Yosemite OS X 10.10.

This model switches graphics card/GPU when running on battery.

 

I've tried both safe booting and ran disk check and permissions check from Recovery.

 

It all started when the display server/loginwindow or something froze. I could move the mouse pointer around, but nothing registered with clicking mouse/touchpad or keyboard.

 

It happened after/when I plugged in an external screen with the mini-dp/thunderbolt-to-DVI adapter.

(Which have never been a problem before ...)

 

Any hints as to what may be the problem? Hardware or software?

(I'm aware that Yosemite is still beta, but I assume it's still OK to ask. Couldn't find the dedicated error reporting tool anymore.)

MacBook Pro with Retina display, Other OS, Yosemite 10.10

Posted on Oct 14, 2014 6:22 AM

Close

Q: Recurring error: A graphics problem has been detected.

  • All replies
  • Helpful answers

first Previous Page 7 of 9 last Next
  • by Healz4u,

    Healz4u Healz4u Jan 2, 2015 4:10 PM in response to Flaxion
    Level 1 (4 points)
    Jan 2, 2015 4:10 PM in response to Flaxion

    Yes. Unfortunately, until Apple admits that there is a problem with their software (specifically, Yosemite), the majority of hardware replacements are going to be a waste of time. And, for people living in countries that do not have a local Apple Store, having hardware replaced, when it is most likely not a hardware issue, is a huge undertaking and a big inconvenience. But, not doing anything about it while their product is under warranty, on the outside chance that the problem is due to faulty hardware, is risky. This is a terrible position for people to be in and I hope the smart folks at Apple come to this realization, fast!! And, hopefully, soon, the Apple "geniuses" will quit stating that they "have never heard of anyone having this issue!"

  • by John Readwin1,

    John Readwin1 John Readwin1 Jan 3, 2015 3:00 PM in response to Flaxion
    Level 1 (0 points)
    Jan 3, 2015 3:00 PM in response to Flaxion

    While I know this may not pertain to everyone, I had this happening on my Mac Pro (Early 2014) and none of the "solutions" mentioned in this thread  worked for me. I was able to detemine itw as software not hardware, since booting from another disk with Yosemite did not produce the error.

     

    Aftr exentsive trouble shooting I determined it was an extension I had installed ( left over from Mountain Lion/Mvaericks)  It was called  Kick Start and was desigend to "kickstart" all my widegets, after removeal I have not had the error re-occur

    Hope this might help someone else.

  • by Flaxion,

    Flaxion Flaxion Jan 4, 2015 12:45 PM in response to Flaxion
    Level 1 (4 points)
    Jan 4, 2015 12:45 PM in response to Flaxion

    It happened to me again (this was the third time in total). Didn't do much but browsing - only two tabs open. The power cord was plugged in and there was no change in power consumption (like switching to the battery).

     

    I better follow Apple's instructions to get this thing to an approved Apple reseller, so they can have a look at it..

  • by Schoggiweggli,

    Schoggiweggli Schoggiweggli Jan 6, 2015 7:37 AM in response to Flaxion
    Level 1 (0 points)
    Jan 6, 2015 7:37 AM in response to Flaxion

    Try to check "Reduce transparency" under Accessibility -> Display. I had no crash since two days and a significant improvement in UI performance. I don't believe that this is a fix but maybe it helps to reduce the amount of errors.

  • by Ricc83,

    Ricc83 Ricc83 Jan 6, 2015 10:56 AM in response to John Readwin1
    Level 1 (0 points)
    Jan 6, 2015 10:56 AM in response to John Readwin1

    Hello John. Did it really solve the problem? I always thought software or plugins can not cause a kernel panic error? I was told it could only be yosemite that directly communicates with the hardware?

  • by John Readwin1,

    John Readwin1 John Readwin1 Jan 6, 2015 11:28 AM in response to Ricc83
    Level 1 (0 points)
    Jan 6, 2015 11:28 AM in response to Ricc83

    I don't think the error is really a "kernal panic" error, but rather interaction with the graphics card and OS (this is not to say that it couldn't be a HW graphics card problem for other users) , anyways it's been about 10 days and a half dozen restarts ( to continue testing) and I have not had it re-occur, if it does I will be sure to update my post.

  • by Ricc83,

    Ricc83 Ricc83 Jan 6, 2015 11:32 AM in response to John Readwin1
    Level 1 (0 points)
    Jan 6, 2015 11:32 AM in response to John Readwin1

    I had this error now 3 times. over a period of 1-2 months. Not sure what to think... Apple Helpline told me to bring it in for Diagnostic, and they think it could be a, very likely, be a hardware defect.

     

    Maybe Apple is holding back because it is a hardware problem and trying to figure out how to best solve it instead of recalling all laptops?

     

    I have a mid 2014 Apple Mac Book Pro Retina.

  • by cbetsinger,

    cbetsinger cbetsinger Jan 11, 2015 2:59 AM in response to flips01
    Level 1 (0 points)
    Jan 11, 2015 2:59 AM in response to flips01

    fixed my issue

  • by bcassid,

    bcassid bcassid Jan 11, 2015 7:43 AM in response to cbetsinger
    Level 1 (4 points)
    Mac OS X
    Jan 11, 2015 7:43 AM in response to cbetsinger

    I thought it solved mine also, but then it started happening again after about a week.

  • by mickalford,

    mickalford mickalford Jan 12, 2015 1:10 AM in response to flips01
    Level 1 (4 points)
    Jan 12, 2015 1:10 AM in response to flips01

    Flips01 has it right on.  Constant rebooting from my mid 2011 imac, and report a problem with graphics  Went to computer/library/logs/diagnostic reports and delted all the gpurestart entries.  Immediate response and back to working as normal.

  • by bcassid,

    bcassid bcassid Jan 12, 2015 5:45 AM in response to mickalford
    Level 1 (4 points)
    Mac OS X
    Jan 12, 2015 5:45 AM in response to mickalford

    Wish that had worked for me.

  • by wsdakota,

    wsdakota wsdakota Jan 15, 2015 5:10 PM in response to flips01
    Level 1 (0 points)
    Jan 15, 2015 5:10 PM in response to flips01

    Having the same problem on a refurbished mac pro (late 2013). Exact same error message. Taking it in to genius bar to make sure the video card is ok. Has ANYONE from apple responded to this issue? The phone tech had not heard anything about it.

  • by bcassid,

    bcassid bcassid Jan 15, 2015 5:19 PM in response to wsdakota
    Level 1 (4 points)
    Mac OS X
    Jan 15, 2015 5:19 PM in response to wsdakota

    They always say they haven't heard of the problem before. You might point them to this thread.

  • by Flaxion,

    Flaxion Flaxion Jan 19, 2015 10:25 AM in response to Flaxion
    Level 1 (4 points)
    Jan 19, 2015 10:25 AM in response to Flaxion

    so this error happeneed again last night, so I kept it frozen and turned on and delivered to my local apple authorized service provider (same as first time), so they could see and experience the error themselves. i have never seen a technician looked so blank before. he also said he didn't know what to do. I also called Apple support and asked them to just take my now 1 month macbook pro in. but they won't do that directly because it's over 14 days of age. sigh... I also found a pixel error in the screen, and some days ago when browsing the top of the screen became pink ehen loading a page in the safari browser.

  • by alex.ozr,

    alex.ozr alex.ozr Jan 20, 2015 8:48 AM in response to mickalford
    Level 1 (0 points)
    Jan 20, 2015 8:48 AM in response to mickalford

    Deleting all crash logs didnt help for me (mac mini 2012 as media server, connected to yamaha receiver via HDMI)

    Panic error and reboot happen almost every day at night when I dont use my mac! Such an annoying issue with this Yosemite..

     

    Also I have an error in logs every few seconds:

    Jan 20 19:23:19 al04.local ReportGPURestart[60099]: gpurestart_header:  gpurestart_message
    Jan 20 19:23:19 al04 com.apple.xpc.launchd[1] (com.apple.ReportGPURestart[60099]): Service exited with abnormal code: 1
    Jan 20 19:23:19 al04 com.apple.xpc.launchd[1] (com.apple.ReportGPURestart): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
    

     

    What could it be?

first Previous Page 7 of 9 last Next