Random restarts (Kernel Panic)

[NiclasFacius]

Hi!

I'm starting to get frustrated with these random restarts my MBP 15" (mid 2010) does. I am on Yosemite, have installed an SSD a few years back, and upgraded my rams from 4 to 8 about a year ago. I've had these random restarts for some months now.

As I've read it could be a software that is outdated and causing this? I can't seem to figure out which app this is. This also happens with only native Apple Apps open (ex. Safari and mail). Sometimes it doesn't happen for a day or two, and then other days it happens like 5-7 times on one day. Any ideas?


Here is the crash report I get, when my computer is on again after a crash:

*** Panic Report ***

panic(cpu 0 caller 0xffffff7f8e251c1b): "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 0xffffff8128275000 0x0a5480a2, D0, P2/4\n"@/SourceCache/AppleGraphicsControl/AppleGraphicsControl-3.10.25/src/AppleMuxControl/kext/GPUPanic.cpp:127

Backtrace (CPU 0), Frame : Return Address

0xffffff8114d12800 : 0xffffff800b52ad21

0xffffff8114d12880 : 0xffffff7f8e251c1b

0xffffff8114d12960 : 0xffffff7f8c0c2b9f

0xffffff8114d12a20 : 0xffffff7f8c18c18e

0xffffff8114d12a60 : 0xffffff7f8c18c1fe

0xffffff8114d12ad0 : 0xffffff7f8c40b056

0xffffff8114d12c00 : 0xffffff7f8c1af82d

0xffffff8114d12c20 : 0xffffff7f8c0c95f1

0xffffff8114d12cd0 : 0xffffff7f8c0c70fc

0xffffff8114d12ed0 : 0xffffff7f8c0c8a4b

0xffffff8114d12fa0 : 0xffffff7f8d783b37

0xffffff8114d13070 : 0xffffff7f8d78116a

0xffffff8114d13090 : 0xffffff7f8d7828a6

0xffffff8114d131c0 : 0xffffff7f8d78100a

0xffffff8114d13220 : 0xffffff7f8d780bad

0xffffff8114d132d0 : 0xffffff7f8d7b4b77

0xffffff8114d13510 : 0xffffff7f8d7ae330

0xffffff8114d13670 : 0xffffff7f8d7afee4

0xffffff8114d136b0 : 0xffffff7f8d7af88c

0xffffff8114d13740 : 0xffffff7f8d797547

0xffffff8114d137a0 : 0xffffff7f8d797e53

0xffffff8114d137f0 : 0xffffff7f8d79827f

0xffffff8114d13860 : 0xffffff7f8d798a11

0xffffff8114d138a0 : 0xffffff7f8d7640f5

0xffffff8114d13a20 : 0xffffff7f8d7953c1

0xffffff8114d13ae0 : 0xffffff7f8d762c15

0xffffff8114d13b30 : 0xffffff800bafff36

0xffffff8114d13b60 : 0xffffff800bb0165b

0xffffff8114d13bc0 : 0xffffff800bafede3

0xffffff8114d13d00 : 0xffffff800b5e1307

0xffffff8114d13e10 : 0xffffff800b52ef8c

0xffffff8114d13e40 : 0xffffff800b5139f3

0xffffff8114d13e90 : 0xffffff800b52429d

0xffffff8114d13f10 : 0xffffff800b60231a

0xffffff8114d13fb0 : 0xffffff800b6344c6

Kernel Extensions in backtrace:

com.apple.driver.AppleMuxControl(3.10.25)[752C63EA-73E8-39BC-8225-3A97D0C403BF]@0xffffff7f8e243000->0xffffff7f8e256fff

dependency: com.apple.driver.AppleGraphicsControl(3.10.25)[3DC2F93F-5197-3B16-8975-0142E7A0474B]@0xffffff7f8e23b000

dependency: com.apple.iokit.IOACPIFamily(1.4)[70E2B65E-A91A-3522-A1A0-79FD63EABB4C]@0xffffff7f8bfa9000

dependency: com.apple.iokit.IOPCIFamily(2.9)[05578B0B-C99C-3A87-9F3E-B4746D19CEF4]@0xffffff7f8bd24000

dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[8922721D-5517-3883-BD3A-57422D0244A0]@0xffffff7f8c01b000

dependency: com.apple.driver.AppleBacklightExpert(1.1.0)[65E3187E-949B-36E9-BA33-1B13ABB0581A]@0xffffff7f8e23e000

com.apple.nvidia.classic.NVDAResmanTesla(10.0)[796AE430-39FB-3255-8161-D52AFA28EE2B]@0xffffff7f8c072000->0xffffff7f8c2dbfff

dependency: com.apple.iokit.IOPCIFamily(2.9)[05578B0B-C99C-3A87-9F3E-B4746D19CEF4]@0xffffff7f8bd24000

dependency: com.apple.iokit.IONDRVSupport(2.4.1)[7372D580-6DDE-3457-B043-49B8447FC9D2]@0xffffff7f8c062000

dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[8922721D-5517-3883-BD3A-57422D0244A0]@0xffffff7f8c01b000

com.apple.nvidia.classic.NVDANV50HalTesla(10.0)[7FE40648-F15F-3E18-91E2-FDDDF4CDA355]@0xffffff7f8c2e6000->0xffffff7f8c58ffff

dependency: com.apple.nvidia.classic.NVDAResmanTesla(10.0.0)[796AE430-39FB-3255-8161-D52AFA28EE2B]@0xffffff7f8c072000

dependency: com.apple.iokit.IOPCIFamily(2.9)[05578B0B-C99C-3A87-9F3E-B4746D19CEF4]@0xffffff7f8bd24000

com.apple.GeForceTesla(10.0)[6CC57746-0012-3634-8CA3-6A75C2BC32D7]@0xffffff7f8d750000->0xffffff7f8d81dfff

dependency: com.apple.iokit.IOPCIFamily(2.9)[05578B0B-C99C-3A87-9F3E-B4746D19CEF4]@0xffffff7f8bd24000

dependency: com.apple.iokit.IONDRVSupport(2.4.1)[7372D580-6DDE-3457-B043-49B8447FC9D2]@0xffffff7f8c062000

dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[8922721D-5517-3883-BD3A-57422D0244A0]@0xffffff7f8c01b000

dependency: com.apple.nvidia.classic.NVDAResmanTesla(10.0.0)[796AE430-39FB-3255-8161-D52AFA28EE2B]@0xffffff7f8c072000



BSD process name corresponding to current thread: WindowServer



Mac OS version:

14F1605



Kernel version:

Darwin Kernel Version 14.5.0: Tue Sep 1 21:23:09 PDT 2015; root:xnu-2782.50.1~1/RELEASE_X86_64

Kernel UUID: 06D286E3-A8A1-3BE7-A7EB-EAC6E0C69758

Kernel slide: 0x000000000b200000

Kernel text base: 0xffffff800b400000

__HIB text base: 0xffffff800b300000

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



System uptime in nanoseconds: 35628249681534

last loaded kext at 1084108434597: com.apple.filesystems.smbfs 3.0.2 (addr 0xffffff7f8e357000, size 389120)

last unloaded kext at 209856355505: com.apple.driver.AppleUSBUHCI 656.4.1 (addr 0xffffff7f8c91d000, size 65536)

loaded kexts:

com.squirrels.airparrot.framebuffer 5

com.squirrels.driver.AirParrotSpeakers 1.8

com.apple.filesystems.smbfs 3.0.2

com.apple.filesystems.msdosfs 1.10

com.apple.driver.AppleHWSensor 1.9.5d0

com.apple.driver.AGPM 110.19.6

com.apple.driver.AudioAUUC 1.70

com.apple.iokit.IOUserEthernet 1.0.1

com.apple.iokit.IOBluetoothSerialManager 4.3.6f3

com.apple.Dont_Steal_Mac_OS_X 7.0.0

com.apple.driver.AppleHWAccess 1

com.apple.driver.AppleHV 1

com.apple.filesystems.autofs 3.0

com.apple.driver.AppleOSXWatchdog 1

com.apple.driver.AppleMikeyHIDDriver 124

com.apple.driver.AppleMikeyDriver 272.18.3

com.apple.driver.AppleHDA 272.18.3

com.apple.driver.AppleUpstreamUserClient 3.6.1

com.apple.driver.AppleIntelHDGraphics 10.0.0

com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.3.6f3

com.apple.driver.AppleSMCLMU 2.0.7d0

com.apple.driver.AppleLPC 1.7.3

com.apple.driver.AppleIntelHDGraphicsFB 10.0.0

com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0

com.apple.driver.SMCMotionSensor





Model: MacBookPro6,2, BootROM MBP61.0057.B11, 2 processors, Intel Core i5, 2.4 GHz, 8 GB, SMC 1.58f17

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

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

Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1067 MHz, 0x859B, 0x435434473353313036374D2E433136464B00

Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1067 MHz, 0x859B, 0x435434473353313036374D2E433136464B00

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

Bluetooth: Version 4.3.6f3 16238, 3 services, 18 devices, 1 incoming serial ports

Network Service: Wi-Fi, AirPort, en1

Serial ATA Device: Samsung SSD 840 PRO Series, 256,06 GB

Serial ATA Device: MATSHITADVD-R UJ-898

USB Device: Hub

USB Device: Apple Internal Keyboard / Trackpad

USB Device: Internal Memory Card Reader

USB Device: BRCM2070 Hub

USB Device: Bluetooth USB Host Controller

USB Device: Hub

USB Device: IR Receiver

USB Device: Built-in iSight

Thunderbolt Bus:

 

[Samuelsan2001]

Looks like a graphics card death to me.

Not a lot you can do apart from replace the logic board (not worth it on a 6 year old machine) or get a new computer.

There are guides for baking logic boards that may give you a few more months but it's not looking good.

 

[JohnDS]

The last loaded Kext is AirParrot. Often the kernel panic is caused by the last loaded Kext. Make sure your version of AirParrot is up-to-date.

The current version is Version 2.3.2. If updating AirParrot does not solve the problem, as a test, try uninstalling it: http://help.airsquirrels.com/suppor...9-how-do-i-uninstall-airparrot-2-from-my-mac-

 

[NiclasFacius]

Looks like a graphics card death to me.

Not a lot you can do apart from replace the logic board (not worth it on a 6 year old machine) or get a new computer.

There are guides for baking logic boards that may give you a few more months but it's not looking good.

Shiiiit.. Thats bad.. Any second opinion on this, before I rule my computer out?
[doublepost=1455295764][/doublepost]

The last loaded Kext is AirParrot. Often the kernel panic is caused by the last loaded Kext. Make sure your version of AirParrot is up-to-date.

The current version is Version 2.3.2. If updating AirParrot does not solve the problem, as a test, try uninstalling it: http://help.airsquirrels.com/suppor...9-how-do-i-uninstall-airparrot-2-from-my-mac-

I have uninstalled AirParrot awhile ago. I also gave it a though, but I can't seem to find any related files leftover from AirParrot.. At least not when I search in Finder..

 

[JohnDS]

Well, the kernel panic report showed:

com.squirrels.airparrot.framebuffer 5

com.squirrels.driver.AirParrotSpeakers 1.8

as the last two loaded Kexts, so obviously they are still on your computer.

Follow the instructions on the link in my last post to remove them.

 

[NiclasFacius]

Well, the kernel panic report showed:

com.squirrels.airparrot.framebuffer 5

com.squirrels.driver.AirParrotSpeakers 1.8

as the last two loaded Kexts, so obviously they are still on your computer.

Follow the instructions on the link in my last post to remove them.

My bad! Gotcha!

Tried deleting those two kexts.. I'll see if that fixes the issue. Thanks!!!

 

[treekram]

There was someone else who had a similar issue to yours just a few days ago.

https://forums.macrumors.com/threads/kernel-panic-mac-book-pro-2010.1955455/

If you don't use graphics-intensive programs, the gfxCardStatus program suggested may work for you.

 

[l.a.rossmann]

You have an 820-2850 motherboard with a common issue. Change C9560 with a polymer film capacitor. The issue is the 330 uF tantalum capacitor on PP1V8R1V55_S0GPU_ISNS rail. It is too small and goes out with time and causes the kernel panics.

The same issue is present on 2008-2009 machines with C7771, on 820-2330 and 820-2610 motherboards. On this board C7771 is a 330 uF tantalum capacitor on PP1V05_S5_MCP. When it dies PP1V05_S5_MCP will be stuck at 0.316v instead of 1.05v and the machine won't turn on.

This design flaw was carried into the 2010 MBP where this same capacitor was used on the PP1V8R1V55_S0GPU rail that powers the GPU and VRAM. It takes longer for the problem to manifest itself in the 2010 MBP because the cap is present on an S0 rail - S0 power rails are only on when the computer is on. On the 2008 MBP, that cap is on an S5 rail, which is present all the time - S5 rails are rails that are powered up so long as the laptop has the battery or a charger plugged in.

You'll have to be creative with how you fit the new capacitor in there - the proper capacitor for the job is larger than what there is space on the board for. You can either fit a wire in there to extend the ground pad, or scrape the coating off the groundplane of the board a little.

I explain a little bit of how this works with this video. This is about the older 820-2330 board, but it is the same general principle - same capacitor, same buck converter circuit, same failure.

[doublepost=1455467455][/doublepost]Also, don't replace the logic board. Any board you buy that is this old will have the same failing cap on it. Just change it on your board and you'll be good to go.

Good luck!
[doublepost=1455467553][/doublepost]Oh, and lastly, don't tell Apple - this'll be our little secret. For the duration of the extended warranty period Apple announced they were giving out the same motherboard with the same problem, so I am confident Apple themselves don't even understand what was causing these failures. I don't feel like giving them ALL the answers for free.

 

[NiclasFacius]

You have an 820-2850 motherboard with a common issue. Change C9560 with a polymer film capacitor. The issue is the 330 uF tantalum capacitor on PP1V8R1V55_S0GPU_ISNS rail. It is too small and goes out with time and causes the kernel panics.

The same issue is present on 2008-2009 machines with C7771, on 820-2330 and 820-2610 motherboards. On this board C7771 is a 330 uF tantalum capacitor on PP1V05_S5_MCP. When it dies PP1V05_S5_MCP will be stuck at 0.316v instead of 1.05v and the machine won't turn on.

This design flaw was carried into the 2010 MBP where this same capacitor was used on the PP1V8R1V55_S0GPU rail that powers the GPU and VRAM. It takes longer for the problem to manifest itself in the 2010 MBP because the cap is present on an S0 rail - S0 power rails are only on when the computer is on. On the 2008 MBP, that cap is on an S5 rail, which is present all the time - S5 rails are rails that are powered up so long as the laptop has the battery or a charger plugged in.

You'll have to be creative with how you fit the new capacitor in there - the proper capacitor for the job is larger than what there is space on the board for. You can either fit a wire in there to extend the ground pad, or scrape the coating off the groundplane of the board a little.

I explain a little bit of how this works with this video. This is about the older 820-2330 board, but it is the same general principle - same capacitor, same buck converter circuit, same failure.

[doublepost=1455467455][/doublepost]Also, don't replace the logic board. Any board you buy that is this old will have the same failing cap on it. Just change it on your board and you'll be good to go.

Good luck!
[doublepost=1455467553][/doublepost]Oh, and lastly, don't tell Apple - this'll be our little secret. For the duration of the extended warranty period Apple announced they were giving out the same motherboard with the same problem, so I am confident Apple themselves don't even understand what was causing these failures. I don't feel like giving them ALL the answers for free.

Thanks! I will give this a shot! The previous suggestions didn't fix the issue, even though i suspect that they lowered the frequency of the restarts. But again. That is hard to say when they seem to be random.


Thanks for the help. I will try to give this a go within the next few weeks, and update you on how it goes!