Previous 1 45 46 47 48 49 Next 760 Replies Latest reply: Feb 13, 2016 3:38 PM by BobHarris Go to original post Branched to a new discussion.
  • nathan262 Level 1 Level 1

    mhvrr wrote:


    If I were in Nathan's place, I would first inquire the issue with Apple and if Apple says it is covered in warranty,

    Good advice and that was my plan-B. I took the laptop with good grace and a polite thank you, then called  Apple this morning. The support engineer reviewed my case and said Apple will cover this at their expense and he''s updated my case file to reflect that. I'm taking the Macbook back to the store tomorrow and fingers crossed it all works out.


    This is one of the (many) reasons I buy Apple laptops. Even when I got the rejection initially the staff were  polite and professional. Apple knows how to keep it customers happy and that's why we keep coming back. I'll get this laptop fixed and hand it down to my brother. Then it's about time I bought myself a new Macbook before the EOFY.

  • grimnotions Level 1 Level 1

    Mr Sparkle75,

    Thanks for the great summary. I took my Macbook, which is out of warranty and no Applecare, to the genius bar and they confirmed it had this problem. I drop it off this evening for a free repair.


  • Yobym Level 1 Level 1

    Im having the same problem as all of you people. Random Kernel panics. 15 inch 2010 macbook pro. This never happened to me on 10.6 but I jumped to 10.8 recently and since then it has been nothing but restarts and crashes. It is VERY frustrating. Maybe 10.8 just brought a hardware problem to light that has always been there? I thought apple laptops were supposed to be reliable and if not... I would expect a company like apple to FIX any standing issues with their products. Boy was I wrong!

  • Grant Bennet-Alder Level 9 Level 9

    10.8 just brought a hardware problem to light that has always been there?

    Yes, that appears to be what happened.


    There are many stories here of readers who were polite but persistent and got their MacBooks fixed after going through the steps described.


    If you cannot get that to happen, you might consider going back to an older Mac OS X that does not show the problem.

  • Kathy Martin1 Level 1 Level 1

    Thanks so much. These forums are great, and helped me diagnose the same problem I had with my mid-2010 MacBook Pro. I had just updated to Mtn Lion around Feb or March and started having problems. Had kept all copies of the panic logs, went to Apple Store on May 2, told them about the problem. At that point thought it was due to iPhoto, b/c I had uploaded over 1000 photos and scrolling through them caused panics (makes sense now if due to graphics!). I rebuilt my iPhoto Library, still had problem. Apple store did not perform any tests, and told me to come back if more problems.


    Went back in early July, told them about "mid 2010 problem", but did not know yet about the special test. They only did the overnight test, and re-installed 10.8.x.


    Two days later, had the same problem.


    Finally, printed out TS4088, and info about running the extra test, and took the MacBook Pro to another Boston-area store. Specified that I wanted the video test done. It FAILED. The Apple Genius was great and did know about this.


    My 3-year warranty had expired four days after I FIRST brought it in in May. But, I'm so glad I did that, as they did honor the warranty specifically for this problem. However, the MB availabiltiy is "constrained" and may not come in for weeks.


    I thank everyone on this forum, especially those (like MrSparkle) who described exactly what I, and the Apple Store, needed to know.

  • bishibashi Level 1 Level 1

    I had my Macbook Pro (mid-2010) logic board replaced with Apple about 2 months ago due to the TS4088 after it it was tested and failed the Special Hardware Test.


    All seemed fine after it. but recently my macbook started crashing again. However it is not the same as previous when it displays the kernel panic; but instead the screen starts getting fuzzy and then it crashes.


    Attached are 2 photo's i took, at different times it has happened.

    And a recorded video of it at : - where you can see the screen is pixelated and moving statically, but the macbook is unresponsive.


    Is this the same problem?




  • Dious Level 1 Level 1

    You can see this problem on my video : With this problem Apple change my motherboard for free. I hope this video will help you.

    The problem happens when your macbook pro 15 core i7 mid-2010 passes the intel graphics card to nvidia 330M graphics card with iPhoto for example.


    Sorry for my bad english.

  • androok Level 1 Level 1

    I've been on mountain lion with my macbook air since it was released, yet I just started having this problem a couple weeks ago when I enabled time machine backups to point to my SMB share media server (which included adding a "mount" task on login, and enabling TM backup on unsupported network drives). The only other change is that I updated my java JDK and removed two old ones. Since this occurs when my computer is supposed to be asleep, I believe it has something to do with waking while asleep for either wifi access or for the 'power nap' functionality. It could also be a problem with the kext (1.8.4) ?


    Also - my machine ONLY has intel HD 3000 graphics... so it's not an nvidia or AMD problem.

    As another note - when plugged in to an external display - if this panic happens - I usually 'wake' the machine to find graphics anomolies and weird pixelation everywhere as if the GPU has gone bad.


    Either way, it stinks trading one problem for another: I no longer worry about my previously irregular backup schedule, but now I get these wonderful Kernel Panics.


    Going to disable wake for wifi and power nap to see if this solves the problem.


    In case anyone was wondering - here's my most recent panic report where all 'Apps' were quit and I simply shut my lid to engage sleep:

    Thu Aug 15 04:07:39 2013

    panic(cpu 0 caller 0xffffff8027ab8655): Kernel trap at 0xffffff7fa85973ed, type 14=page fault, registers:

    CR0: 0x000000008001003b, CR2: 0xffffff80d8f9c000, CR3: 0x0000000029cbc000, CR4: 0x00000000000606e0

    RAX: 0x0000000000000000, RBX: 0x0000000000000780, RCX: 0xffffff80d8f9b000, RDX: 0x0000000000000200

    RSP: 0xffffff80a09bbcc0, RBP: 0xffffff80a09bbcc0, RSI: 0x00000000000003c0, RDI: 0x0000000000000000

    R8:  0x0000000000001e00, R9:  0x0000000000000000, R10: 0xffffff80a09bbc00, R11: 0x00000000ffffffff

    R12: 0xffffff80cf08c454, R13: 0x0000000000000780, R14: 0x0000000000000000, R15: 0xffffff80d8f9b000

    RFL: 0x0000000000010283, RIP: 0xffffff7fa85973ed, CS:  0x0000000000000008, SS:  0x0000000000000010

    Fault CR2: 0xffffff80d8f9c000, Error code: 0x0000000000000002, Fault CPU: 0x0



    Backtrace (CPU 0), Frame : Return Address

    0xffffff80a09bb960 : 0xffffff8027a1d626

    0xffffff80a09bb9d0 : 0xffffff8027ab8655

    0xffffff80a09bbba0 : 0xffffff8027ace17d

    0xffffff80a09bbbc0 : 0xffffff7fa85973ed

    0xffffff80a09bbcc0 : 0xffffff7fa85972dd

    0xffffff80a09bbd00 : 0xffffff7fa858cca2

    0xffffff80a09bbd80 : 0xffffff7fa858ce32

    0xffffff80a09bbdb0 : 0xffffff7fa918e515

    0xffffff80a09bbe10 : 0xffffff7fa858ec78

    0xffffff80a09bbe50 : 0xffffff7fa858df63

    0xffffff80a09bbe80 : 0xffffff7fa858d31e

    0xffffff80a09bbef0 : 0xffffff8027e48588

    0xffffff80a09bbf30 : 0xffffff8027e4708a

    0xffffff80a09bbf80 : 0xffffff8027e471b9

    0xffffff80a09bbfb0 : 0xffffff8027ab3137

          Kernel Extensions in backtrace:

   [990D1A42-DF16-3AB9-ABC1-6A88AC142244]@0 xffffff7fa8580000->0xffffff7fa85b7fff

                dependency:[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7fa8083000

   [34C96C82-1E3B-3165-B6AD-85A9EC3 376CE]@0xffffff7fa9188000->0xffffff7fa91b5fff

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

                dependency:[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7fa8083000

                dependency:[990D1A42-DF16-3AB9-ABC1-6A88AC142244]@0 xffffff7fa8580000



    BSD process name corresponding to current thread: kernel_task



    Mac OS version:




    Kernel version:

    Darwin Kernel Version 12.4.0: Wed May  1 17:57:12 PDT 2013; root:xnu-2050.24.15~1/RELEASE_X86_64

    Kernel UUID: 896CB1E3-AB79-3DF1-B595-549DFFDF3D36

    Kernel slide:     0x0000000027800000

    Kernel text base: 0xffffff8027a00000

    System model name: MacBookAir4,2 (Mac-742912EFDBEE19B3)

  • Grant Bennet-Alder Level 9 Level 9



    You need to post the entire panic report, not just the beginning of it. Use this artcile to find them in the logs and include all the information please. The beginning is interesting, but not enough to draw any conclusions without the rest of the report.


    Mac OS X: How to log a kernel panic

  • androok Level 1 Level 1

    Interval Since Last Panic Report:  17089 sec

    Panics Since Last Report:          1

    Anonymous UUID:                    99DE944E-A717-281F-D0D8-639A47952755



    Sat Aug 17 07:39:25 2013

    panic(cpu 2 caller 0xffffff8024eb8655): Kernel trap at 0xffffff8024ea7856, type 14=page fault, registers:

    CR0: 0x000000008001003b, CR2: 0xffffff80d6c4f000, CR3: 0x00000000270bc000, CR4: 0x00000000000606e0

    RAX: 0x0000000003a5312c, RBX: 0x0000000000000050, RCX: 0x0000000000000028, RDX: 0x0000000000000140

    RSP: 0xffffff80a3fcbcc8, RBP: 0xffffff80a3fcbd00, RSI: 0xffffff80d31fbed4, RDI: 0xffffff80d6c4f000

    R8:  0x0000000000000010, R9:  0x00000000ff091006, R10: 0xffffff80a3fcbc00, R11: 0x00000000ffffffff

    R12: 0xffffff80d31fbed0, R13: 0x0000000000000000, R14: 0x0000000000000050, R15: 0xffffff80d6c4f000

    RFL: 0x0000000000010206, RIP: 0xffffff8024ea7856, CS:  0x0000000000000008, SS:  0x0000000000000010

    Fault CR2: 0xffffff80d6c4f000, Error code: 0x0000000000000002, Fault CPU: 0x2



    Backtrace (CPU 2), Frame : Return Address

    0xffffff80a3fcb960 : 0xffffff8024e1d626

    0xffffff80a3fcb9d0 : 0xffffff8024eb8655

    0xffffff80a3fcbba0 : 0xffffff8024ece17d

    0xffffff80a3fcbbc0 : 0xffffff8024ea7856

    0xffffff80a3fcbd00 : 0xffffff7fa598cca2

    0xffffff80a3fcbd80 : 0xffffff7fa598ce32

    0xffffff80a3fcbdb0 : 0xffffff7fa658e515

    0xffffff80a3fcbe10 : 0xffffff7fa598ec78

    0xffffff80a3fcbe50 : 0xffffff7fa598df63

    0xffffff80a3fcbe80 : 0xffffff7fa598d31e

    0xffffff80a3fcbef0 : 0xffffff8025248588

    0xffffff80a3fcbf30 : 0xffffff802524708a

    0xffffff80a3fcbf80 : 0xffffff80252471b9

    0xffffff80a3fcbfb0 : 0xffffff8024eb3137

          Kernel Extensions in backtrace:

   [990D1A42-DF16-3AB9-ABC1-6A88AC142244]@0 xffffff7fa5980000->0xffffff7fa59b7fff

                dependency:[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7fa5483000

   [34C96C82-1E3B-3165-B6AD-85A9EC3 376CE]@0xffffff7fa6588000->0xffffff7fa65b5fff

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

                dependency:[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7fa5483000

                dependency:[990D1A42-DF16-3AB9-ABC1-6A88AC142244]@0 xffffff7fa5980000



    BSD process name corresponding to current thread: kernel_task



    Mac OS version:




    Kernel version:

    Darwin Kernel Version 12.4.0: Wed May  1 17:57:12 PDT 2013; root:xnu-2050.24.15~1/RELEASE_X86_64

    Kernel UUID: 896CB1E3-AB79-3DF1-B595-549DFFDF3D36

    Kernel slide:     0x0000000024c00000

    Kernel text base: 0xffffff8024e00000

    System model name: MacBookAir4,2 (Mac-742912EFDBEE19B3)



    System uptime in nanoseconds: 34792863307907

    last loaded kext at 7022871773458:          1.8.1 (addr 0xffffff7fa69fa000, size 65536)

    last unloaded kext at 110538297327:          5.2.5 (addr 0xffffff7fa5761000, size 65536)

    loaded kexts:          1.8.1          1.8.4          1.60          1.9.5d0          3.0          100.12.87          2.0.6d1          4.1.4f2          122          2.3.7fc4          3.5.10          1.6.0          170.2.5          2.3.7fc4          1.1.11          1.0.0          4.1.4f2          1.0.0d1          7.0.0          3.4.5          1.0.0          2.0.3d0          8.1.2          8.1.2          3.1.7          237.1          237.1          1.0.0d1          1.0.0d1          34          404          2.3.1          5.5.5          615.20.17          2.5.2          5.5.0          161.0.0          1.7          1.7          1.5          1.8          1.9          1.7          1.6          196.0.0          4.0.39          2.1          196.0.0          1.0          10.0.6          2.3.7fc4          1.8.9fc11          1.6          1.0.4          2.3.7fc4          2.3.7fc4          4.1.4f2          86.0.4          4.1.4f2          3.4.5          1.0.0          5.3.0d51          1.0.11d0          3.1.4d2          1.0.11d0          2.3.7          2.3.7          3.5.5          3.5.1          3.5.5          1.8.9          1.8.9          1.2.6          237.3          5.2.5          5.5.5          5.2.5          530.4          3.0          5.5.5          2.3.1          1.7.8          2.4.0          5.6.0          1.7          1.8.1          1.1          220.3          1.0.0d1          7          345          1.8          28.21          1.7          2.7.3          1.4          1.0

    System Profile:

    Model: MacBookAir4,2, BootROM MBA41.0077.B0F, 2 processors, Intel Core i5, 1.7 GHz, 4 GB, SMC 1.73f66

    Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 384 MB

    Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1333 MHz, 0x02FE, 0x45424A3230554638424353302D444A2D4620

    Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1333 MHz, 0x02FE, 0x45424A3230554638424353302D444A2D4620

    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xE9), Broadcom BCM43xx 1.0 (

    Bluetooth: Version 4.1.4f2 12041, 2 service, 11 devices, 1 incoming serial ports

    Network Service: Wi-Fi, AirPort, en0

    Serial ATA Device: APPLE SSD SM128C, 121.33 GB

    USB Device: hub_device, 0x0424  (SMSC), 0x2513, 0xfa100000 / 3

    USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x024c, 0xfa120000 / 5

    USB Device: BRCM20702 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0xfa110000 / 4

    USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x821f, 0xfa113000 / 6

    USB Device: FaceTime Camera (Built-in), apple_vendor_id, 0x850a, 0xfa200000 / 2

    USB Device: hub_device, 0x0424  (SMSC), 0x2513, 0xfd100000 / 2

    USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8404, 0xfd110000 / 3

  • androok Level 1 Level 1

    I didn't realize this - but it's actually happened every single day since I enabled Time Machine.


    I'm now disabling both wake for wifi and power nap to see if this fixes it - next stop is the apple store.


    Fun fact - sometimes when I wake my macbook air, it looks like the picture I've posted here.


    This is quite terrible - as it's not happening to the other macbook air we have (same year/model & OS version).


    Pretty sure neither of our 2011 Macbook Airs are under applecare anymore either...

  • debaire Level 1 Level 1

    For those of you with this issue, how often was it crashing?


    At one point it seemed to be crashing every couple of minutes.


    I read somewhere else to first try the 10.8.4 combo update and to disable automatic graphics switching.


    I've tried both and for now it seems to be stable. Still, I made an appointment to see the Genius Bar on Monday. I guess I'm looking into plan B's just in case it doesn't work out. I'm currently in Beijing and I'm not sure how up to date the staff is there, although this particular store is in an area with a lot of ex-pats.

  • J A Bohrer Level 1 Level 1

    I have just had my logic board replaced, and the VST test shows a PASSED result with the work done. (Thank you MrSparkle75!)


    Will the newly replaced logic board now continue to function properly into the future?


    That is to say, can any of you speak to whether once the logic board and GPU replacement is accomplished that the problem is 'fixed' and will not return?

  • Grant Bennet-Alder Level 9 Level 9

    The problem that caused the recall is a latent defect that was always there in a certain revision of graphics chips. When the software is updated to 10.8, the problem becomes much more obvious, and the diagnostic was written to catch that specific defect. Once those defective chips are replaced with ones that do not contain the defect, that exact problem will not recur.


    But it is possible for your graphics card to fail in some other way -- that is the nature of these electronic systems.

  • J A Bohrer Level 1 Level 1

    Ha ha ha, well put, Grant.


    I really didn't find anywhere in these articles that the defect had been corrected. I simply had the impression some chips were defective, some not, and the logic boards containing defective chips were replaced with other boards with GPU's that were simply defect free. No one had mentioned that later GPU's have a corrected chip on the replacement boards.


    I will hope that the (most likely refurbished) board that has been placed into my machine contains a chip without said defect and simply allow me to continue working...


    Thanks for the reply.

Previous 1 45 46 47 48 49 Next