Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Kernel Panic GPU-related after 10.8.4 update

Hello,


I would appreciate some help. Since I updated to Mac Os X 10.8.4, I'm experimenting kernel panics on my Macbook Air (2011). I think it's a GPU-related issue.


Here comes the log:


Interval Since Last Panic Report: 39659 sec

Panics Since Last Report: 1

Anonymous UUID: 559D34B8-244D-46C7-D287-FF3864895C80

Thu Jun 6 15:37:08 2013

panic(cpu 0 caller 0xffffff80004b8655): Kernel trap at 0xffffff7f81ae0bb7, type 13=general protection, registers:

CR0: 0x000000008001003b, CR2: 0x0000000016f30000, CR3: 0x0000000023678000, CR4: 0x0000000000000660

RAX: 0x0000000000000001, RBX: 0x000000000b983000, RCX: 0x0000000000000001, RDX: 0x0000000000000000

RSP: 0xffffff80405037b0, RBP: 0xffffff80405037f0, RSI: 0x000000000b983000, RDI: 0xffffff8030f8e000

R8: 0x736870796c476b63, R9: 0x0000000000000000, R10: 0x0000000000000001, R11: 0x0000000000001000

R12: 0x0000000000000000, R13: 0x0000000000000000, R14: 0xffffff8030f8e000, R15: 0xffffff80356acfa4

RFL: 0x0000000000010246, RIP: 0xffffff7f81ae0bb7, CS: 0x0000000000000008, SS: 0x0000000000000010

Fault CR2: 0x0000000016f30000, Error code: 0x0000000000000000, Fault CPU: 0x0

Backtrace (CPU 0), Frame : Return Address

0xffffff8040503450 : 0xffffff800041d626

0xffffff80405034c0 : 0xffffff80004b8655

0xffffff8040503690 : 0xffffff80004ce17d

0xffffff80405036b0 : 0xffffff7f81ae0bb7

0xffffff80405037f0 : 0xffffff7f81ae1214

0xffffff8040503860 : 0xffffff7f81ae19d3

0xffffff80405038a0 : 0xffffff7f81aace2f

0xffffff8040503a20 : 0xffffff7f81addf0f

0xffffff8040503ae0 : 0xffffff7f81aab8c8

0xffffff8040503b30 : 0xffffff8000866e69

0xffffff8040503b50 : 0xffffff8000868410

0xffffff8040503bb0 : 0xffffff8000865e2f

0xffffff8040503d00 : 0xffffff8000498c01

0xffffff8040503e10 : 0xffffff8000420b3d

0xffffff8040503e40 : 0xffffff8000410448

0xffffff8040503e90 : 0xffffff800041961b

0xffffff8040503f00 : 0xffffff80004a63de

0xffffff8040503fb0 : 0xffffff80004ce78e

Kernel Extensions in backtrace:

com.apple.GeForce(8.1.2)[7EC545A4-4B57-32F1-8DC3-C31023AFBDCB]@0xffffff7f81a990 00->0xffffff7f81b66fff

dependency: com.apple.NVDAResman(8.1.2)[96AE69DE-8A37-39D0-B2D3-D8446A6AA670]@0xffffff7f80a ec000

dependency: com.apple.iokit.IONDRVSupport(2.3.7)[6C8CFC18-75F0-3DEF-86C7-CEB2C1FD6BB1]@0xff ffff7f80ad8000

dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f80a46000

dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[990D1A42-DF16-3AB9-ABC1-6A88AC142244]@0 xffffff7f80a95000

BSD process name corresponding to current thread: iPhoto

Mac OS version:

12E55

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: 0x0000000000200000

Kernel text base: 0xffffff8000400000

System model name: MacBookAir3,2 (Mac-942C5DF58193131B)

System uptime in nanoseconds: 329675227984

last loaded kext at 246154389059: com.apple.filesystems.msdosfs 1.8.1 (addr 0xffffff7f82584000, size 65536)

last unloaded kext at 306396863193: com.apple.filesystems.msdosfs 1.8.1 (addr 0xffffff7f82584000, size 57344)

loaded kexts:

com.apple.driver.AudioAUUC 1.60

com.apple.filesystems.autofs 3.0

com.apple.driver.AppleHWSensor 1.9.5d0

com.apple.iokit.IOBluetoothSerialManager 4.1.4f2

com.apple.driver.AGPM 100.12.87

com.apple.driver.ApplePlatformEnabler 2.0.6d1

com.apple.driver.AppleMikeyHIDDriver 122

com.apple.driver.AppleHDA 2.3.7fc4

com.apple.iokit.IOUserEthernet 1.0.0d1

com.apple.driver.AppleMikeyDriver 2.3.7fc4

com.apple.Dont_Steal_Mac_OS_X 7.0.0

com.apple.driver.ApplePolicyControl 3.4.5

com.apple.driver.AppleLPC 1.6.0

com.apple.driver.AppleBacklight 170.2.5

com.apple.driver.AppleUpstreamUserClient 3.5.10

com.apple.driver.AppleMCCSControl 1.1.11

com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0

com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport 4.1.4f2

com.apple.GeForce 8.1.2

com.apple.driver.AppleUSBTCButtons 237.1

com.apple.driver.AppleUSBTCKeyboard 237.1

com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1

com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1

com.apple.BootCache 34

com.apple.driver.AppleUSBCardReader 3.1.7

com.apple.driver.XsanFilter 404

com.apple.iokit.IOAHCIBlockStorage 2.3.1

com.apple.driver.AirPort.Brcm4331 615.20.17

com.apple.driver.AppleUSBHub 5.5.5

com.apple.driver.AppleAHCIPort 2.5.2

com.apple.driver.AppleUSBEHCI 5.5.0

com.apple.driver.AppleUSBOHCI 5.2.5

com.apple.driver.AppleSmartBatteryManager 161.0.0

com.apple.driver.AppleEFINVRAM 1.7

com.apple.driver.AppleRTC 1.5

com.apple.driver.AppleHPET 1.8

com.apple.driver.AppleACPIButtons 1.7

com.apple.driver.AppleSMBIOS 1.9

com.apple.driver.AppleACPIEC 1.7

com.apple.driver.AppleAPIC 1.6

com.apple.driver.AppleIntelCPUPowerManagementClient 196.0.0

com.apple.nke.applicationfirewall 4.0.39

com.apple.security.quarantine 2.1

com.apple.driver.AppleIntelCPUPowerManagement 196.0.0

com.apple.kext.triggers 1.0

com.apple.iokit.IOSerialFamily 10.0.6

com.apple.driver.DspFuncLib 2.3.7fc4

com.apple.iokit.IOAudioFamily 1.8.9fc11

com.apple.kext.OSvKernDSPLib 1.6

com.apple.iokit.IOSurface 86.0.4

com.apple.iokit.IOBluetoothFamily 4.1.4f2

com.apple.driver.AppleSMBusPCI 1.0.11d0

com.apple.driver.AppleHDAController 2.3.7fc4

com.apple.iokit.IOHDAFamily 2.3.7fc4

com.apple.driver.AppleGraphicsControl 3.4.5

com.apple.driver.AppleBacklightExpert 1.0.4

com.apple.driver.AppleSMBusController 1.0.11d0

com.apple.driver.IOPlatformPluginLegacy 1.0.0

com.apple.driver.IOPlatformPluginFamily 5.3.0d51

com.apple.iokit.AppleBluetoothHCIControllerUSBTransport 4.1.4f2

com.apple.driver.AppleSMC 3.1.4d2

com.apple.nvidia.nv50hal 8.1.2

com.apple.NVDAResman 8.1.2

com.apple.iokit.IONDRVSupport 2.3.7

com.apple.iokit.IOGraphicsFamily 2.3.7

com.apple.driver.AppleUSBMultitouch 237.3

com.apple.iokit.IOUSBHIDDriver 5.2.5

com.apple.iokit.IOSCSIBlockCommandsDevice 3.5.5

com.apple.iokit.IOUSBMassStorageClass 3.5.1

com.apple.iokit.IOSCSIArchitectureModelFamily 3.5.5

com.apple.driver.AppleUSBMergeNub 5.5.5

com.apple.driver.AppleUSBComposite 5.2.5

com.apple.iokit.IO80211Family 530.4

com.apple.iokit.IONetworkingFamily 3.0

com.apple.driver.AppleMCP89RootPortPM 1.11

com.apple.iokit.IOUSBUserClient 5.5.5

com.apple.iokit.IOAHCIFamily 2.3.1

com.apple.iokit.IOUSBFamily 5.6.0

com.apple.driver.NVSMU 2.2.9

com.apple.driver.AppleEFIRuntime 1.7

com.apple.iokit.IOHIDFamily 1.8.1

com.apple.iokit.IOSMBusFamily 1.1

com.apple.security.sandbox 220.3

com.apple.kext.AppleMatch 1.0.0d1

com.apple.security.TMSafetyNet 7

com.apple.driver.DiskImages 345

com.apple.iokit.IOStorageFamily 1.8

com.apple.driver.AppleKeyStore 28.21

com.apple.driver.AppleACPIPlatform 1.7

com.apple.iokit.IOPCIFamily 2.7.3

com.apple.iokit.IOACPIFamily 1.4

com.apple.kec.corecrypto 1.0

Model: MacBookAir3,2, BootROM MBA31.0061.B07, 2 processors, Intel Core 2 Duo, 1.86 GHz, 2 GB, SMC 1.66f61

Graphics: NVIDIA GeForce 320M, NVIDIA GeForce 320M, PCI, 256 MB

Memory Module: BANK 0/DIMM0, 1 GB, DDR3, 1067 MHz, 0x02FE, 0x45424A3130554538454655302D41452D4620

Memory Module: BANK 1/DIMM0, 1 GB, DDR3, 1067 MHz, 0x02FE, 0x45424A3130554538454655302D41452D4620

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD1), Broadcom BCM43xx 1.0 (5.106.98.100.17)

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

Network Service: AirPort, AirPort, en0

Serial ATA Device: APPLE SSD SM256C, 251 GB

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

USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8403, 0x26100000 / 2

USB Device: BRCM2070 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x04500000 / 3

USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x821b, 0x04530000 / 5

USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0240, 0x04300000 / 2



The kexts don't seem to referenciate any third party software. It looks like I've problems with the GPU and/or iPhoto, but I don't understand this kind of things properly. I must point here that, before the update, I don't have any problemas at all. Also, I've seen in the support forums that there are bugs on Nvidia graphic cards in Mountain Lion. So... my questions are: a) Is this some kind of bug? b) Can I do something to solve this issue (I've already checked Activity Monitor, reset PRAM, repaired permissions, erased Macintosh HD and restored my hard drive... without results)? c) Could you help me?


Thanks!

MacBook Air, OS X Mountain Lion (10.8.4)

Posted on Jun 6, 2013 7:40 AM

Reply
Question marked as Best reply

Posted on Jun 6, 2013 8:18 AM

I don't see anything either - if you didn't download the combo updater and install the 10.8.4 update that way, do so now and apply it. Sometimes a delta updater leaves behind something it shouldn't which applying the combo updater will fix. Beisdes saving bandwidth to update the various machines I'm responsible for, I've found it to be less problmatic than delta releases. (A delta release updates the most recent version minus 1 to the newest while the combo will update any version to the newest.)

36 replies
Question marked as Best reply

Jun 6, 2013 8:18 AM in response to JoseTA

I don't see anything either - if you didn't download the combo updater and install the 10.8.4 update that way, do so now and apply it. Sometimes a delta updater leaves behind something it shouldn't which applying the combo updater will fix. Beisdes saving bandwidth to update the various machines I'm responsible for, I've found it to be less problmatic than delta releases. (A delta release updates the most recent version minus 1 to the newest while the combo will update any version to the newest.)

Jun 6, 2013 9:02 AM in response to JoseTA

That panic was not caused by third-party software. If the problem is recurrent, the possibilities are:


  1. A stale or corrupt kernel cache
  2. A damaged OS X installation
  3. A fault in a peripheral device, if any
  4. Corrupt non-volatile memory (NVRAM)
  5. An internal hardware fault (including incompatible memory)
  6. An obscure bug in OS X


You may already have ruled out some of these.

Rule out #1 by booting in safe mode and then rebooting as usual. Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Post for further instructions.

You can rule out #2 and #3 by reinstalling the OS and testing with non-essential peripherals disconnected and aftermarket expansion cards removed, if applicable. Sometimes a clean reinstallation (after erasing the startup volume) may solve a problem that isn't solved by reinstalling in place, without erasing.


Corrupt NVRAM, which rarely causes panics, can be ruled out by resetting it.


If your model has user-replaceable memory, and you've upgraded the memory modules, reinstall the original memory and see whether there's any improvement. Be careful not to touch the gold contacts. Clean them with a mild solvent such as rubbing alcohol. Aftermarket memory must exactly match the technical specifications for your model. Memory that is either slower or faster than specified may be incompatible.


The Apple Hardware Test, though generally unreliable, will sometimes detect a fault. A negative test can't be depended on. Run the extended version of the test.


In the category of obscure bugs, reports suggest that FileVault may trigger kernel traps under some unknown conditions. Most, though not all, of these reports seem to involve booting from an aftermarket SSD. If those conditions apply to you, try deactivating FileVault.

Connecting more than one display is another reported trigger for OS X bugs.


In rare cases, a malformed network packet from a defective router or other network device can cause panics. Such packets could also be sent deliberately by a skillful attacker. This possibility is something to consider if you run a public server that might be the target of such an attack.


If none of the above applies, make a "Genius" appointment at an Apple Store to have the machine tested. You may have to leave it there for several days. There isn't much point in doing this unless you can reproduce the panic, or if you can't, it happens often enough that it's likely to be repeated at the store. Otherwise you may be told that nothing is wrong.


Print the first page of the panic report and bring it with you.


Back up all data on the internal drive(s) before you hand over your computer to anyone. If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you know how to restore, and you have at least two independent backups.) Don’t erase the recovery partition, if present.


Keeping your confidential data secure during hardware repair


*An SSD doesn't need to be zeroed.

Jun 6, 2013 11:11 AM in response to dwb

Hello! Thanks for answering..


Linc Davis, I don't have FileVault enabled, and before writing here I had already performed a boot in safe mode (ruled out #1), a reset of the NVRAM (ruled out #4) and an Apple Hardware Test (extended version in loop). Also reinstalled Mac Os X (but, after that, I used a Time Machine backup to recover my data), which ruled out #2. I don't have peripherals (only a wi-fi printer), which ruled out #3. My model doesn't have user-replaceable memory.


dwb, I am downloading the combo update right now. Thanks for the advice.


Nevertheless, this always seems to happen while iPhoto is open. And I've got a lot of high resolution photos in there. I will try to rebuild my library and use my Mac without open it. Can iPhoto cause GPU-related kernel panics?

Jun 6, 2013 2:55 PM in response to Linc Davis

Right now, after a clean install of Mountain Lion, a backup of my user's files (Pictures, Documents, etc. not the system, as Linc Davis said), the installation of the combo update suggested by dwb and the restoration of the iPhoto library indicated by Old Toad, the system seems estabilized. No kernel panics in 4 hours, non even after using iPhoto (which more or less was triggering the panics, at least indirectly). I'll work on my mac for the next few days and, if all is ok, I'll close the issue and mark the proper "This solved my question", although I don't know if it's possible to recognise each of you. Thank you very much. I'm deeply grateful.

Jun 24, 2013 8:33 AM in response to JoseTA

I've been getting the SAME GPU related KP's on two different MBP 15's - common thread is same model logic board (I'm an ACMT) with the nVidia GF GT 330M ... I'm wondering if there's a GPU HW problem and/or something wrong with the nVidia kernel extensions - kexts - (aka drivers):


  • com.apple.NVDAResman(8.1.2)
  • com.apple.nvidia.nv50hal(8.1.2)
  • com.apple.GeForce(8.1.2)
  • com.apple.driver.AppleMuxControl(3.4.5)


That last one is new today! Previous KP's have only included the 1st 3 kexts.


I have completely wiped my current machine & re-installed 10.8 from scratch - not restored from TM backup. Updated it via software updates. Installed my apps from scratch - not restored from TM backup. All from a "localadmin" - (e.g. user 501, administrator, not used for everyday work, kept 'clean' for trouble-shooting). Restored *MY* account from a TM backup.


How likely is it that an individual account's preference file(s) are causing KP's?


Below is my /Library/Logs/DiagnosticReports/Kernel-date-etc.panic:

=================================================

Mon Jun 24 11:03:36 2013

panic(cpu 2 caller 0xffffff7f9bc42f1a): "GPU Panic: [<None>] 5 3 7f 0 0 0 0 3 : NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xd2000000 0xffffff810a944000 0x0a5480a2, D0, P3/4\n"@/SourceCache/AppleGraphicsControl/AppleGraphicsControl-3.4.5/src/AppleM uxControl/kext/GPUPanic.cpp:127

Backtrace (CPU 2), Frame : Return Address


<long list of addresses SNIPPED>


Kernel Extensions in backtrace:

com.apple.NVDAResman(8.1.2)[96AE69DE-8A37-39D0-B2D3-D8446A6AA670]@0xffffff7f9a2 d6000->0xffffff7f9a57bfff

dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f99ffd000

dependency: com.apple.iokit.IONDRVSupport(2.3.7)[6C8CFC18-75F0-3DEF-86C7-CEB2C1FD6BB1]@0xff ffff7f9a2c2000

dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[990D1A42-DF16-3AB9-ABC1-6A88AC142244]@0 xffffff7f9a27f000

com.apple.nvidia.nv50hal(8.1.2)[988EAF3A-3318-3787-8A5A-844830FA1522]@0xffffff7 f9a587000->0xffffff7f9a85bfff

dependency: com.apple.NVDAResman(8.1.2)[96AE69DE-8A37-39D0-B2D3-D8446A6AA670]@0xffffff7f9a2 d6000

dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f99ffd000

com.apple.GeForce(8.1.2)[7EC545A4-4B57-32F1-8DC3-C31023AFBDCB]@0xffffff7f9b16d0 00->0xffffff7f9b23afff

dependency: com.apple.NVDAResman(8.1.2)[96AE69DE-8A37-39D0-B2D3-D8446A6AA670]@0xffffff7f9a2 d6000

dependency: com.apple.iokit.IONDRVSupport(2.3.7)[6C8CFC18-75F0-3DEF-86C7-CEB2C1FD6BB1]@0xff ffff7f9a2c2000

dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f99ffd000

dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[990D1A42-DF16-3AB9-ABC1-6A88AC142244]@0 xffffff7f9a27f000

com.apple.driver.AppleMuxControl(3.4.5)[49FEF732-D7A3-327B-A7AA-6AC5A6E3DCFF]@0 xffffff7f9bc35000->0xffffff7f9bc47fff

dependency: com.apple.driver.AppleBacklightExpert(1.0.4)[1D0BB11E-7D71-34CF-ACC3-57DF01CADA 08]@0xffffff7f9bc30000

dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f99ffd000

dependency: com.apple.driver.AppleGraphicsControl(3.4.5)[4A2C8548-7EF1-38A9-8817-E8CB34B8DC A6]@0xffffff7f9bc1c000

dependency: com.apple.iokit.IOACPIFamily(1.4)[A35915E8-C1B0-3C0F-81DF-5515BC9002FC]@0xfffff f7f9a1e9000

dependency: com.apple.iokit.IONDRVSupport(2.3.7)[6C8CFC18-75F0-3DEF-86C7-CEB2C1FD6BB1]@0xff ffff7f9a2c2000

dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[990D1A42-DF16-3AB9-ABC1-6A88AC142244]@0 xffffff7f9a27f000

Jun 28, 2013 5:23 AM in response to andyBall_uk

My MacBook Pro turned out to have the issue mentioned in: TS4088

Luckily I'm also an Apple Cert. Mac Techician and followed the steps mention in a corresponding Service document - (insert non-disclosure) - *IF* your panic logs closely resemble my post above, your MBP 15" (mid-2010) *MIGHT* have the same issue and an Apple Store or Auth. Apple Service Provider can run a special diagnostic test - you will want to provide the link posted by "andyBall_uk" as the service folks may not be aware of the issue, I know I wasn't! THANKS to "andyBall_uk" !!!

Aug 22, 2013 12:25 AM in response to Joe.Kazura

What's the service document you are referring to? I've been getting the same GPU-related kernel panics on my 15" mid-2010 MBP recently. At first I thought it was a third party app but even after removal of said app I'm getting random crashes.


EDIT: Just to be clear, I'm not referring to the TS4088 bulletin, but the corresponding service bulleting you are referring to. Thanks!

Aug 22, 2013 6:14 AM in response to debaire

Unless you have access to GSX, you won't be able to view the service bulletin, as it's not "public". If you do have access to GSX, then search on this: "MacBook Pro (15-inch, Mid 2010): Intermittent black screen" and you will find the cdocument you seek. :-) As I am now the Apple Service Manager for a University, I won't jeopardize my position by posting internal documents and/or numbers, sorry, thats the way Apple wants it.

Sep 11, 2013 11:26 AM in response to JoseTA

Just an update. mine just came back from apple store and they denied my claim. it's MBP 6,2 and it failed the video test however they are telling me that my video card is the upgraded version (due to hires screen option?) so it's not part of the same issue.... at least that's what Apple told me. is there any other way this can be resolved? i can't believe they are covering this as part of the rest of the 6,2 GPU issue. Needless to say I'm very disappointed with this. Been a mac user for a long time and this news totally blew me away in a negative way. 😮


mine's passed the 3 yrs warranty by 2 months but that wasn't the issue.

Sep 11, 2013 12:07 PM in response to peachy MBP

Peachy - That does NOT sound right!!! My MacBook Pro HAS the hi-res "upgrade" that you mentioned and my logic board was replaced no problem. It *sounds like* someone couldn't be bothered ... Apple's service criteria for replacement is that it fails that 'special' video test, which yours apparently meets. MAYBE the service person that worked on your MBP, didn't READ or comprehend the content of the service bulletin. Was it an Apple Retail store or the local Apple re-seller/service center (e.g. not an Apple Retail Store). The special video test is ONLY supposed to "show up" or be available to computers that qualify for the program. If it didn't qualify, then they wouldn't have been able to run the test in the first place.


I would try again and be a bit more forceful and/or take it to a different Service Center ... I would ask to speak with the owner/manager about the tech that worked on your computer. Good Luck!!!

Sep 11, 2013 1:56 PM in response to Joe.Kazura

it's an official apple store here in vancouver, CA. she said that she called apple and that's what apple informed her. they did the MRI test.... then the video test that showed it failed. she said that the "order the part option" wasn't coming out as an option that's why she had to call it in to order the part and to double check if it was really part of the extended service warranty. i'll go there again as well as go to another apple store. i hope this gets sorted out. i'm a bit confused myself.

Kernel Panic GPU-related after 10.8.4 update

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.