Previous 1 30 31 32 33 34 Next 501 Replies Latest reply: Aug 1, 2014 5:22 PM by wickeninc Go to original post Branched to a new discussion.
  • kdixon6 Level 1 (0 points)

    I'm just under the 3-year purchase window for this and of my applecare, but I'm wondering- if I went to the Genius Bar a year+ ago with a kernel panic problem (caused by external HD software), would that somehow invalidate my eligibility with this round of kernel panics caused by my graphics card? Also, if a computer has sustained past water damage, would that possibly affect their decision/ability to replace the logic board?

  • BocaBoy Level 1 (25 points)

    I don't work for Apple so my response falls under the category of opinion, not fact, but if the test they have to identify this specific problem with the mid-2010 MBP is positive, and you're still under Applecare, I would have to think they'd cover it.


    I think the only way you'll find out is to take it in. Apple monitors these discussion boards but never responds, so your best bet is to take it in and verify the problem with the appropriate test.

  • Juri Munkki Level 1 (0 points)

    I bought this used 2010 MacBook about 18 months ago specifically because I could run Snow Leopard on it. With Mavericks coming soon, I felt it was finally time to move on (although I kept Snow Leopard on one partition) and upgraded to Moutain Lion.


    I'm getting the exact same kernel panics that people in this thread are getting. Seems odd that the machine was 100% stable with Snow Leopard and will fail with later operating systems. I'll probably try Mavericks before I start calling the machine broken (shouldn't be long now?) and try to get it fixed.


    However, I find it unfair that Apple has a 3 year limit on this failure if it doesn't affect all operating system versions. There's no way to find out you have a problem than until it is too late if you were reliant on running Snow Leopard (Rosetta/software compatibility reasons). I'm sure that it doesn't help that the machine is also second hand...

  • BocaBoy Level 1 (25 points)

    Don't lose your temper with Apple until they actually tell you, "No." Most people on this thread, regardless of the time frame, have been able to get Apple to fix the problem on their dime. This is especially true since many of us have only seen this problem with the latest versions of OS X, in my case starting with 10.8.5. Until then, for over 3 years, my machine was perfect.


    My experience is if you go into an Apple Store, along with a printout of TS4088, you'll get your MBP repaired for free, assuming it's failing due to the graphics problem outlined in the TS. Just be sure you don't come in with an attitude where they can't wait to get you out of the store, and I'll bet you report back to this forum that your computer was repaired on the house.


    Good luck!

  • Juri Munkki Level 1 (0 points)

    Good point. It turns out that although CoconutBattery says the MacBook is 3.6 years old, this MacBook was actually originally purchased in December (and I might even be able to get the original receipts for this, if needed). This means that as long as Apple agrees that the machine was bought within 3 years and that it is indeed the GPU failing, it should be a clear case where I don't even have to try to stetch any rules.


    The Apple repair shop is right next door from where I work, so I've already been there and they'll probably test the machine tomorrow. (I needed it for work today and I'm running it with Snow Leopard again for now.) I'm hoping I'll have a working machine back in my hands on Thursday or possibly even as early as Wednesday. They were very well aware of the issue - all I had to say was that I'm getting GPU-related kernel panics after upgrading to Mountain Lion...

  • Juri Munkki Level 1 (0 points)

    Turns out I was the third owner already and the machine is well over 3 years old, so I'm down to a least plea with Apple Support on this. I'm also trying Mavericks to see if it might somehow be able to work around the issue. No crashes with Mavericks so far, but I only installed it 15 minutes ago, so it's far too early to say if it behaves any differently - doesn't seem worse than Mountain Lion so far.

  • Juri Munkki Level 1 (0 points)

    Still getting panics with Mavericks. Feels like it's less often, but I just got one a few moments ago.

  • Juri Munkki Level 1 (0 points)

    I found that nVidia has posted a new CUDA driver yesterday, so I installed that and also gfxCardStatus (to be able to see the switching) and did an SMC reset. I haven't had a panic after that. I used the MacBook for "normal web surfing" while watching TV tonight. For the past hour, I have been doing stress testing with the MBP connected to a projector (both mirrored and separate display modes). I have used VLC, Photoshop, Lightroom, iTunes (movie playback), QuickTime Player.


    Too early to be certain, but I'm getting my hopes up again. That CUDA driver is certainly worth trying and SMC resets are never a bad idea. Work tomorrow will be the acid test...


    You can find the CUDA driver here:


  • BocaBoy Level 1 (25 points)

    Juri, what IS a CUDA driver? What does CUDA stand for? I'm reluctant to play with success as Apple already replaced my motherboard and screen on their dime and I'm afraid of tinkering with it.

  • Juri Munkki Level 1 (0 points)

    CUDA is a technology that allows applications to use nVidia graphics chips for computing. Photoshop is a good example. If you read this topic from the first page, you'll find it mentioned a few times.


    Some background information:



    I don't know if CUDA comes standard with MacOS and I don't know what the odds are that an application would install it, if it doesn't. However, the component comes directly from nVidia and it interfaces extremely intimately with the GPU. If you read nVidia's documentation and release notes on it, you'll find that they have had some issues with it and the resulting kernel panics sound a lot like the ones that people here are getting.


    If your MacBook is still crashing, it's worth trying. If you have no problems, I wouldn't touch a thing and just keep my fingers crossed.


    It's quite often possible to use software engineering to work around hardware problems. That's pretty much the only option you have when something breaks on a space probe or satellite, for example. If the hardware repair is too difficult or expensive, writing a bit of code to work around a hardware malfunction makes a lot of sense.

  • BocaBoy Level 1 (25 points)

    Thanks, Juri. Since I've got my MacBook Pro working perfectly, I think I'll take a pass on it. I do use Photoshop a lot, but the only "problems" I've noticed is that it runs a bit more hesitantly under Mavericks than it did under Mountain Lion, but hardly noticeable.


    Thanks again for the answer. Any idea what CUDA stands for??

  • Juri Munkki Level 1 (0 points)

    Unfortunately I have bad news: my MacBook just had a panic attack again. I'm still waiting for some final answer from Apple (haven't heard a peep since Wednesday).


    The Wikipedia article that I linked above has your answer: Compute Unified Device Architecture

  • Jan Anderson Level 1 (30 points)

    Perhaps not entirely helpfu but here it goes:

    I had this problem for a long time and decided to upgrade to 10.9 and see if it fixed it, as it has some new code reg. displays and graphics. And touch wood, the problem appears to be gone for us...


  • hymai Level 1 (0 points)

    Hi. Can anyone help me to find out what is the cause of this kernel panic?


    Sun Dec 22 14:26:02 2013

    panic(cpu 2 caller 0xffffff7f9ac3b300): "Potential Fifo Overflow in GFX\n"@/SourceCache/GraphicsDrivers/GraphicsDrivers-8.16.74/Common/IONDRV/Intel /HSW/AppleIntelFramebuffer/AppleIntelController.cpp:306

    Backtrace (CPU 2), Frame : Return Address

    0xffffff80985cb550 : 0xffffff8018a1d636

    0xffffff80985cb5c0 : 0xffffff7f9ac3b300

    0xffffff80985cb600 : 0xffffff7f9abdd7d7

    0xffffff80985cb630 : 0xffffff7f9abdd604

    0xffffff80985cb660 : 0xffffff7f9abb832e

    0xffffff80985cb690 : 0xffffff7f9ab45e75

    0xffffff80985cb6b0 : 0xffffff7f9ab469e8

    0xffffff80985cb6d0 : 0xffffff7f9abe5bcf

    0xffffff80985cb730 : 0xffffff7f9abbce8f

    0xffffff80985cb9e0 : 0xffffff7f9ab490c5

    0xffffff80985cba10 : 0xffffff7f9ab49391

    0xffffff80985cba40 : 0xffffff7f9ab54df5

    0xffffff80985cba80 : 0xffffff7f9abc39f1

    0xffffff80985cbaa0 : 0xffffff7f9ab474d3

    0xffffff80985cbb30 : 0xffffff8018e70173

    0xffffff80985cbb50 : 0xffffff8018e70d4d

    0xffffff80985cbbb0 : 0xffffff8018e6e74f

    0xffffff80985cbd00 : 0xffffff8018a98c21

    0xffffff80985cbe10 : 0xffffff8018a20b4d

    0xffffff80985cbe40 : 0xffffff8018a10448

    0xffffff80985cbe90 : 0xffffff8018a1961b

    0xffffff80985cbf00 : 0xffffff8018aa63ee

    0xffffff80985cbfb0 : 0xffffff8018acf221

          Kernel Extensions in backtrace:

   [8F074659-F84D-3303-8E40-F7726 C5A2B10]@0xffffff7f9ac27000->0xffffff7f9ac7cfff

                dependency:[A35915E8-C1B0-3C0F-81DF-5515BC9002FC]@0xfffff f7f99512000

                dependency:[6C1D646D-7E5E-3D7F-A557-2CBA398FF878]@0xffffff 7f99051000

                dependency:[9928306E-3508-3DBC-80A4-D8F1D87650D7]@0 xffffff7f99577000

   [CC44ABAB-C39F-34EF-853D-50DA40B6D45 F]@0xffffff7f9ab41000->0xffffff7f9aba4fff

                dependency:[6C1D646D-7E5E-3D7F-A557-2CBA398FF878]@0xffffff 7f99051000

                dependency:[9928306E-3508-3DBC-80A4-D8F1D87650D7]@0 xffffff7f99577000

   [E5B86F86-1654-369D-B939-C309BF D3BFAD]@0xffffff7f9abb2000->0xffffff7f9ac01fff

                dependency:[6C1D646D-7E5E-3D7F-A557-2CBA398FF878]@0xffffff 7f99051000

                dependency:[F16E015E-1ABE-3C40-AC71-BC54F4BE442E]@0xff ffff7f995ba000

                dependency:[9928306E-3508-3DBC-80A4-D8F1D87650D7]@0 xffffff7f99577000

                dependency:[CC44ABAB-C39F-34EF-853D-50DA40B6D45 F]@0xffffff7f9ab41000



    BSD process name corresponding to current thread: hl2_osx



    Mac OS version:




    Kernel version:

    Darwin Kernel Version 12.5.0: Sun Sep 29 13:33:47 PDT 2013; root:xnu-2050.48.12~1/RELEASE_X86_64

    Kernel UUID: EA38B02E-2B88-309F-BA68-1DE29F605DD8

    Kernel slide:     0x0000000018800000

    Kernel text base: 0xffffff8018a00000

    System model name: MacBookAir6,2 (Mac-7DF21CB3ED6977E5)



    System uptime in nanoseconds: 9661923706937

    last loaded kext at 244460294289:          1.8.1 (addr 0xffffff7f9b03a000, size 65536)

    last unloaded kext at 304566861903:          1.8.1 (addr 0xffffff7f9b03a000, size 57344)

    loaded kexts:          124          4.1.7f4          3.0          1.60          100.13.12          1.0.0          2.0.7d2          3.5.12          2.4.7fc4          1.0.0d1          2.0.3d0          7.0.0          4.1.7f4          3.4.5          1.6.3          4.08.1          170.3.5          1.1.11          8.1.6          8.1.6          3.3.1          10.20          404          2.3.5          1.0.0d1          1.0.0d1          34          635.4.0          2.6.6          641.15.1          635.4.0          161.0.0          1.8          1.5          1.8          1.9          1.8          1.7          4.0.39          2.1          10.0.6          1.0          2.4.7fc4          1.9.2fc7          1.12          86.0.4          4.1.7f4          4.1.7f4          2.4.7fc4          2.4.7fc4          1.0.0          3.1.5d4          5.4.1d13          3.4.5          1.0.4          1.0.11d1          74.15          2.3.7          2.3.7          623.4.0          2.5.0          2.5.0          1.3.2          3.5.6          3.5.2          3.5.6          621.4.6          621.4.0          170.2.4          23          237.4          630.4.4          2.5.1          1.9.2          2.7.7          530.5          3.0          23          2.0.34          635.4.0          2.0.34          2.0.34          2.0          2.0          1.8.1          1.1          220.3          1.0.0d1          7          345          1.8          28.21          1.8          2.8          1.4          1.0


    Running OS X 10.8.5

    Mid June 2013 MBA

    Processor: 1.3 GHz Intel Core i5

    Memory: 4GB 1600 MHz DDR3

    Intel HD Graphics 5000


    Thanks for the help.


    P.S. just realised this is in the Macbook Pro section because i found this through google search. Hope you guys would still help me out thanks.


    Message was edited by: hymai

  • BocaBoy Level 1 (25 points)

    On the surface, it looks like a graphics driver issue. From the model, it looks like you're running a mid-2010 MBP. If it is the graphics subsystem that's causing the problem, you need to take it to an Apple Genius or call Apple and reference TS4088. They have a test they can perform to verify it. It is then at their option whether they will fix it for free or not, but in almost every case I've heard of, they will replace the motherboard on the house.


    My advice is to take it to Apple, and if the problem is related to this TS, nicely work with the Genius to get Apple to replace this at their expense.


    Good luck.