Sign up ×
Ask Different is a question and answer site for power users of Apple hardware and software. It's 100% free, no registration required.

My mid-2010 MacBook Pro keeps rebooting after upgrade to Mountain Lion.

The crashes are happening in different applications but seems to happen most often when scrolling inside of an email or Safari, opening iPhoto, or opening a video from Youtube.

Not sure who can review the panic report and offer assistance.

Thu Sep 13 12:30:25 2012 panic(cpu 3 caller 0xffffff7f9bf61c85): NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xd2000000 0xffffff80baab7000 0x0a5480a2, D0, P3/4 Backtrace (CPU 3), Frame : Return Address 0xffffff80973ab040 : 0xffffff801b81d5f6 0xffffff80973ab0b0 : 0xffffff7f9bf61c85 0xffffff80973ab140 : 0xffffff7f9c05b5b7 0xffffff80973ab1a0 : 0xffffff7f9c05b62b 0xffffff80973ab210 : 0xffffff7f9c370883 0xffffff80973ab350 : 0xffffff7f9c08175d 0xffffff80973ab380 : 0xffffff7f9bf6b9e6 0xffffff80973ab430 : 0xffffff7f9bf670b8 0xffffff80973ab620 : 0xffffff7f9bf67b3a 0xffffff80973ab710 : 0xffffff7f9cfd2c51 0xffffff80973ab760 : 0xffffff7f9cfcffad 0xffffff80973ab7a0 : 0xffffff7f9cfce1a5 0xffffff80973ab7d0 : 0xffffff7f9cf7efef 0xffffff80973ab7f0 : 0xffffff7f9cf9a94c 0xffffff80973ab820 : 0xffffff7f9cf9a6f3 0xffffff80973ab870 : 0xffffff7f9cf990f1 0xffffff80973ab890 : 0xffffff7f9cf87e98 0xffffff80973ab8c0 : 0xffffff7f9cfcbd54 0xffffff80973ab900 : 0xffffff7f9cf86f31 0xffffff80973aba80 : 0xffffff7f9cfc82ee 0xffffff80973abb40 : 0xffffff7f9cf85a3a 0xffffff80973abba0 : 0xffffff801bc64929 0xffffff80973abbc0 : 0xffffff801bc65ed0 0xffffff80973abc20 : 0xffffff801bc638ef 0xffffff80973abd70 : 0xffffff801b8981a1 0xffffff80973abe80 : 0xffffff801b820abd 0xffffff80973abeb0 : 0xffffff801b810448 0xffffff80973abf00 : 0xffffff801b8195fb 0xffffff80973abf70 : 0xffffff801b8a5ad6 0xffffff80973abfb0 : 0xffffff801b8ced13 Kernel Extensions in backtrace:[6A699209-FB98-316B-A3C0-DCA82AA8C86B]@0xffffff7f9befa000->0xffffff7f9c1fcfff dependency:[8C9E06A4-13D0-33F5-A377-9E36F0ECC229]@0xffffff7f9be6f000 dependency:[E37F420A-B5CD-38ED-9441-5247583B6ACE]@0xffffff7f9bee6000 dependency:[5D671681-D21B-3CCA-9810-B15E648C1B27]@0xffffff7f9bea3000[9CD95A4A-FD94-349E-A4B6-FC3B74E197F5]@0xffffff7f9c20a000->0xffffff7f9c52cfff dependency:[6A699209-FB98-316B-A3C0-DCA82AA8C86B]@0xffffff7f9befa000 dependency:[8C9E06A4-13D0-33F5-A377-9E36F0ECC229]@0xffffff7f9be6f000[91C40470-82BA-329A-A9D7-4C70F28275FD]@0xffffff7f9cf79000->0xffffff7f9d03bfff dependency:[6A699209-FB98-316B-A3C0-DCA82AA8C86B]@0xffffff7f9befa000 dependency:[E37F420A-B5CD-38ED-9441-5247583B6ACE]@0xffffff7f9bee6000 dependency:[8C9E06A4-13D0-33F5-A377-9E36F0ECC229]@0xffffff7f9be6f000 dependency:[5D671681-D21B-3CCA-9810-B15E648C1B27]@0xffffff7f9bea3000

BSD process name corresponding to current thread: WebProcess

Mac OS version: 12B19

Kernel version: Darwin Kernel Version 12.1.0: Tue Aug 14 13:29:55 PDT 2012; root:xnu-2050.9.2~1/RELEASE_X86_64 Kernel UUID: 3005059E-270B-3B9F-940D-7A66C05DDC9D Kernel slide:
0x000000001b600000 Kernel text base: 0xffffff801b800000 System model name: MacBookPro6,2 (Mac-F22586C8)

System uptime in nanoseconds: 2564255630731 last loaded kext at 32532016903: 97 (addr 0xffffff7f9db99000, size 16384) last unloaded kext at 155001924757: 5.1.5 (addr 0xffffff7f9c7dc000, size 65536) loaded kexts: 97 1.9.5d0 1.60 3.0 4.0.9f8 100.12.69 122 2.3.0f2 2.3.0f2 3.5.10 4.0.9f8 1.0.0 1.6.0 1.0.33 1.0.0d1 7.0.0 3.2.6 8.0.0 3.2.6 8.0.0 2.0.2d0 1.0.0 8.0.0 3.0.2d6 235.4 3.1.0 320.15 235.4 1.0.0d1 1.0.0d1 34 3.5.1 404 5.1.6 2.2.1 601.15.21 3.2.5b3 4.9.5 2.4.0 5.1.5 1.6.1 161.0.0 1.6 1.5 1.7 1.9 1.6 1.6 196.0.0 4.0.39 2 196.0.0 97 97 97 97 97 97 97 1.0 10.0.6 2.3.0f2 1.8.9fc9 1.6 4.0.9f8 1.0.10d0 1.0.10d0 86.0.2 4.0.9f8 2.2.5 2.3.0f2 2.3.0f2 1.0.4 3.2.6 8.0.0 8.0.0 2.3.4 1.0.0 5.2.0d16 2.3.4 3.1.3d11 3.5.1 3.5.0 235.7 5.0.0 5.1.5 5.0.0 3.5.1 1.7 1.7.1 1.7.1 2.5.0 3.5.1 5.0.0 500.15 1.0.2b1 3.0 4.5.5 2.2.0 5.1.6 1.6.1 1.8.0 1.1 220 1.0.0d1 7 344 1.8 28.18 1.6 2.7 1.4 1.0

share|improve this question
You are not alone. I am in the same boat. –  The Who Sep 14 '12 at 2:16
I have the same issue! I found your thread on google by searching by "91C40470-82BA-329A-A9D7-4C70F28275FD", wonder what it is. Have you discovered anything else regarding our problem? please keep the question thread up to date! :) –  Fernando Sep 18 '12 at 23:43
Does the problem still occur after you install the 10.8.2 Mountain Lion update? –  root Sep 24 '12 at 9:29
If you have 5 to 10 instanced of this happening - it would be pretty easy to look over the logs and see what might be causing the panic. Are you looking for a canonical article on how to debug kernel panics? Apple is the holder of the source code to the browser and the OS - so the "canonical" solution is to file a bug report with them and/or isolate the issue by reinstalling the OS and not installing plug in / third party software if that is contributing to the issue. The big question, is can you reproduce the panic and make it happen within 5 minutes of trying to cause a crash? –  bmike Sep 25 '12 at 18:03
I'm also experiencing the same kernel panic on my mid-2010 MBP. It took me a few months to get around to upgrading to Mountain Lion but now this is driving me crazy. I'm on 10.8.2. Has anybody found a fix for this? –  Mike Dec 3 '12 at 0:36

2 Answers 2

From the log above, it seems like it's graphics related. There is also a thread on Apple's community forums confirming that suspicion.

It looks like the graphics chip is not functioning as intended. They suggested looking into getting it replaced. I know this is not an immediate solution, but I hope it narrows down the issue further.

share|improve this answer
As a kernel developer, I would agree with that assessment. :-) It makes sense that this happens in Safari and iPhoto, as those are known to use GPU acceleration. I assume all firmware and OSX updates have been installed; if so, the hardware is likely defective. –  pmdj Sep 21 '12 at 15:26

I'm inclined to agree with @Melwan; however, I know how Apple Techs work and they're going to push you to attempt a clean install before diagnosing your hardware. So go ahead and do a clean install (Back up your files of course) then boot your mac holding down the alt key, you should see your HD show up and a restore partition show up. Select the restore partition and make sure you wipe the harddrive and do a clean install. This may help if something that handles your graphics installed wrong. It's worth a shot, especially if you don't have AppleCare any longer.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.