Kernel Panic GPU-related after 10.8.4 update

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.)

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.

As a test launch iPhoto with the Option key held down and create a new, test library. Import some photos and test for a while to see if the same problem persists. Does it?

OT

iPhoto is not capable of causing a kernel panic directly, no matter how corrupt its data.

Restoring from a backup doesn't rule out system corruption. The backed-up system could also be corrupt.

The AHT doesn't rule out a hardware fault. It's not reliable.

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

http://support.apple.com/kb/ts4088

Linc thanks for all the helpful info,

I keep having these panics in Mountain Lion on my 15-in Mid 2010 Macbook Pro and I do have FileVault set up (I have to for work). What do you recommend in that case? I have already done a clean reinstall, reset the NVRAM, and am using the native memory, but I keep having the panics.

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" !!!

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!

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.

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.

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!!!

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.