Skip navigation

Your computer restarted because of a problem - Mountain Lion, Xbench

2399 Views 4 Replies Latest reply: Apr 28, 2013 4:51 AM by grzmucin RSS
grzmucin Calculating status...
Currently Being Moderated
Apr 21, 2013 6:03 AM

Hi. I have a MacBook Pro 15 inch (mid 2010) and until october 2012 I had been successfully using OS X 10.6.8 when i upgraded to Mountain Lion. And after I did that strange things started to happen: my MBP occassionally started to restart without any warning. At first it was like twice a week, then started to occur several times a day. I've read plenty of threads here and on other mac forums but to be honest, there were as many solutions as threads describing the problem. So I decided to clean my whole MBP and make a fresh install of 10.6.8 from a CD that came together with the computer. And for some 3 months when I've been using 10.6.8 nothing happened. No kernel panics, no fails. So a week ago I upgraded again to Mountain Lion. Everything was OK until I noticed that Mission Control lags and is not working smoothly as it should. So I ran the Xbench test and... Here is my log from so well known crash:


Interval Since Last Panic Report:  36308 sec

Panics Since Last Report:          1

Anonymous UUID:                    277E2404-C90E-64B7-044E-36F51A9F686A


Sun Apr 21 14:06:24 2013

panic(cpu 2 caller 0xffffff7f96f587f2): NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0x0a2910de 0x00100000 0x00000000, BAR0 0xd2000000 0xffffff80935c5000 0x0a5480a2, D0, P3/4

Backtrace (CPU 2), Frame : Return Address

0xffffff8092b737a0 : 0xffffff801681d626

0xffffff8092b73810 : 0xffffff7f96f587f2

0xffffff8092b738d0 : 0xffffff7f970553b9

0xffffff8092b73930 : 0xffffff7f9705542e

0xffffff8092b739a0 : 0xffffff7f9737bc82

0xffffff8092b73ad0 : 0xffffff7f9707bfe8

0xffffff8092b73b10 : 0xffffff7f96f60567

0xffffff8092b73bc0 : 0xffffff7f96f5e05a

0xffffff8092b73dc0 : 0xffffff7f96f5f0c5

0xffffff8092b73ea0 : 0xffffff7f96efdaba

0xffffff8092b73ef0 : 0xffffff7f98a660df

0xffffff8092b73f40 : 0xffffff7f98a651e7

0xffffff8092b73f60 : 0xffffff801683dcfe

0xffffff8092b73fb0 : 0xffffff80168b2977

      Kernel Extensions in backtrace:
[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7f96efb 000->0xffffff7f97208fff

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

            dependency:[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xff ffff7f96ee7000

            dependency:[74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7f96ea4000
[5F021999-8B18-3BD5-9B98-90617E638A63]@0xffffff7f9 7216000->0xffffff7f97537fff

            dependency:[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7f96e fb000

            dependency:[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f96e66000
[A7004F02-7D39-3398-8BD3-729DCC404E5F]@0xffffff 7f98a64000->0xffffff7f98a73fff

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

            dependency:[2C131EAF-F74C-39D1-A702-A499B 39C293C]@0xffffff7f979ce000

            dependency:[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xff ffff7f96ee7000

            dependency:[74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7f96ea4000


BSD process name corresponding to current thread: kernel_task


Mac OS version:



Kernel version:

Darwin Kernel Version 12.3.0: Sun Jan  6 22:37:10 PST 2013; root:xnu-2050.22.13~1/RELEASE_X86_64

Kernel UUID: 3EB7D8A7-C2D3-32EC-80F4-AB37D61492C6

Kernel slide:     0x0000000016600000

Kernel text base: 0xffffff8016800000

System model name: MacBookPro6,2 (Mac-F22586C8)


System uptime in nanoseconds: 16212173313717

last loaded kext at 1848206582371:          1.8 (addr 0xffffff7f98be7000, size 65536)

last unloaded kext at 2204497783350:          1.8 (addr 0xffffff7f98be7000, size 57344)

loaded kexts:          1.8          1.9.5d0          1.60          100.12.87          3.0          122          2.3.7fc4          1.0.0d1          4.1.3f3          2.3.7fc4          7.0.0          8.1.0          3.5.10          4.1.3f3          3.3.0          1.0.0          1.6.0          1.0.0          8.1.0          8.1.0          2.0.3d0          3.3.0          1.1.11          3.0.3d1          237.1          320.15          3.1.7          1.0.0d1          1.0.0d1          34          237.1          3.5.5          404          2.3.1          5.5.5          614.20.16          4.9.6          2.5.1          3.6.0b1          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          196.0.0          1.0          2.3.7fc4          1.8.9fc11          1.6          86.0.4          10.0.6          4.1.3f3          2.2.5          8.1.0          8.1.0          4.1.3f3          1.0.11d0          1.0.0          5.3.0d51          2.3.7fc4          2.3.7fc4          3.3.0          1.0.4          2.3.7          1.0.11d0          2.3.7          3.1.4d2          3.5.5          3.5.1          237.3          5.2.5          5.5.5          5.2.5          3.5.5          1.7          1.7.1          1.7.1          2.5.1          3.5.5          5.5.5          522.4          4.5.5          2.3.1          1.0.2b1          3.0          5.5.5          1.7          1.8.1          1.1          220.2          1.0.0d1          7          345          1.8          28.21          1.7          2.7.3          1.4          1.0

Model: MacBookPro6,2, BootROM MBP61.0057.B0F, 2 processors, Intel Core i5, 2.53 GHz, 4 GB, SMC 1.58f17

Graphics: Intel HD Graphics, Intel HD Graphics, Built-In, 288 MB

Graphics: NVIDIA GeForce GT 330M, NVIDIA GeForce GT 330M, PCIe, 256 MB

Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1067 MHz, 0x802C, 0x31364A53463235363634485A2D3147314631

Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1067 MHz, 0x802C, 0x31364A53463235363634485A2D3147314631

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

Bluetooth: Version 4.1.3f3 11349, 2 service, 18 devices, 1 incoming serial ports

Network Service: AirPort, AirPort, en1

Serial ATA Device: Hitachi HTS545050B9SA02, 500,11 GB

Serial ATA Device: MATSHITADVD-R   UJ-898

USB Device: hub_device, 0x0424  (SMSC), 0x2514, 0xfa100000 / 2

USB Device: BRCM2070 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0xfa110000 / 5

USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8218, 0xfa113000 / 8

USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8403, 0xfa130000 / 4

USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0237, 0xfa120000 / 3

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

USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd120000 / 4

USB Device: Built-in iSight, apple_vendor_id, 0x8507, 0xfd110000 / 3



Any helpful ideas? Thanks.

MacBook Pro, OS X Mountain Lion (10.8.3)
  • clintonfrombirmingham Level 7 Level 7 (26,655 points)


    Mid-2010 15" MacBook Pros - the bad NVIDIA GPU


    If you're having frequent kernel panics with your 15" mid-2010, or intermittent screen problems, the problem is, more than likely, the faulty NVIDIA GPU found in a number of those machines.


    Here's just a sample of a kernel panic log that points to the faulty NVIDIA card:


    Kernel Extensions in backtrace (with dependencies):>0x82b7afff             dependency:             dependency:             dependency:             dependency:>0x84019fff             dependency:>0x8378dfff             dependency:             dependency:             dependency:


    Here's the "official" Apple take on the issue - but the very real kernel panics need not be preceded by 'Intermittent black screen or loss of video'... in fact, you might not experience any video problems at all. Although video problems can certainly be a portent of things to come…


    So what can you do? Print out a copy of your kernel panic and a copy of the Knowledge Base article and take them, along with your machine, to your local Apple Store or an Apple Authorized Service Provider. They should be more than willing to install a new logic board at no cost. I have no idea why this faulty GPU is making the headline here on the MacBook Pro forum so often now - could it be because Mountain Lion is just bringing the issue to a head more readily? I don't know - I only know that we're seeing more and more of these kernel panics of late.


    Good luck,




More Like This

  • Retrieving data ...

Bookmarked By (0)


  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.