Skip to main content

Fix Your Stuff

Right to Repair

Parts & Tools

Released April 2010 / 2.4, 2.53 GHz Core i5 or 2.66, 2.8 GHz Core i7 Processors

608 Questions View all

Kernel panic and HDD format questions

I did another replacement of capacitor C9560 on a 820-2850 board (2010 MBP 15” ), and it ran fine after with a fresh install with a High Sierra HDD. I used the cap I bought from Louis Rossman’s store, the oversized unit, and also had replaced the trackpad, which had been the only error showing in ASD after the surgery.

I was ready to give it to a new owner, but upon inserting the new owner's old SSHD (which had previously been in one of those infamous 2011 MBP with a 820- 2915), the 2850 did a panic again, even with the new cap.

Are there other reasons to panic on these 2850 boards beside the cap? I’m currently running Disc Warrior on the new owner's SSHD (which had previously been in the infamous 2011 MBP with a 820- 2915), and it showed 7 out of 10 in the optimization index. Could it be that the machine did the kernel panic just because I installed his SSHD which was subjected to kernel panics in the owner previous 2915?

Another factor which MIGHT play into the crash of my freshly re-capped 2850 has come to light: The SSHD I had tried to implant into my freshly re capped machine had a " Logical Volume Group" Type, and a "Logical partition" format. Being the rookie I still am (for the time being) , I am drawing blanks as to what that means, other than that when I put my own "GUID Partition Table " formatted HDDs into the machine, it crashes no more… Can anyone shed some light please?

Answer this question I have this problem too

Is this a good question?

Score 0


What did the panic report tell you? The answer is there!


Not sure how to insert an attachment for a pdf file here : So I copy and paste the first part only to stay below the 1000 symbol limit:*** Panic Report ***

panic(cpu 3 caller 0xffffff7f841a4bc9): "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 0xffffff911ea8a000 0x0a5480a2,

D0, P2/4\n"@/Library/Caches/


Backtrace (CPU 3), Frame : Return Address

0xffffff910dacaee0 : 0xffffff80016dab52

0xffffff910dacaf60 : 0xffffff7f841a4bc9

0xffffff910dacb040 : 0xffffff7f85168a6a

0xffffff910dacb100 : 0xffffff7f852359e8

0xffffff910dacb140 : 0xffffff7f85235a53

0xffffff910dacb1c0 : 0xffffff7f854a9a85

0xffffff910dacb330 : 0xffffff7f85257711


Add a comment

1 Answer

With the users SSHD installed re-run the Mojave OS Installer from a bootable OS installer USB thumb drive How to create a bootable macOS Mojave installer drive if I remember correctly this is how @mayer fixed his problems with SSHD’s.

Also make sure you have the correct version of SSHD! The newest 2.5” version only runs at SATA III (6.0 Gb/s) unlike the older one which also ran at SATA II (3.0 Gb/s) had Auto sense technology the new one doesn’t!

Was this answer helpful?

Score 0


Hmm, thank you Dan. If that SSHD drive had Mojave on it, then it is no surprise that it crashed in my 2010 15” MBP, I suppose. Unless I am misinformed, the 820-2850 board in the 2010 can only go up as high as High Sierra, right?

The SSHD came out of a 2011 machine, which packed it in due to the GPU. Do the 2011 MBPs support Mojave? And is that the reason the SSHD was formatted as a Logical volume group?


@jurgenkoppen - Sorry I jumped to a higher version on you. I don't use High Sierra I either stick with Sierra or jump to Mojave.

Frankly, I would go with Sierra here but as you updated to High Sierra you are caught on a rough version ;-{ Mojave is better but not so good for SATA based systems.

Then you have the Apple supported issue: Technically Apple won't support issues under Mojave with the older Mac's, but you can install it on the older Mac systems using DosDude1. Even still I would stick with Sierra unless you are playing around and don't have a newer system to run it on.

As for your 'Logical Volume group' I think you're just seeing Disc Warrior's jargon for the volume type. I would just stick with Apples Disk Utility. Unless You have an updated version of Disc Warrior I would recommend you throw it into a dusty drawer and just stick with the Apple tools. There is just too much canes over the last few years to trust any 3rd party tools, more so on older ones.


Thank you Dan for shedding some light and your take on Sierra, High Sierra and Mojave.

I’m not that interested in Mojave, because I like the " older" 2010 MBP’s since they do not shed keyboards and fry GPUs as the post 2010 machines do.

Well, I must check and see what OS is actually on the original SSHD which came in my buddy's fried 2011. But what ever OS is on there, since I am putting him onto a 2010 MBP, I will transfer his data then to a Sierra OS SSD. Does that sound right to you? Also, the info : " Type: Logical Volume Group" and "Format: Logical Partition" I read on the Disc Utility which I used to prep SSDs , and this Disc Utility is just the standard Yosemite program came with the OS.

I just did not know what to make of it....Before that I had put my friends original SSHD on Disc Utility in a Snow Leopard machine, it just said " unsupported format".


So I checked the SSHD OS which I am trying to transfer to a2010 machine, and it is El Capitan. So all should be well, as I am migrating its data now onto a fresh install El Capitan SSD, to keep his sytem the same, only on a more reliable 2010 machine.


OK I think I'm getting it ;-} You have three different file systems at play! The oldest being what Leopard supported the older HFS, the newer HFS+ and now we have APFS! My brain is hurting going so far back. The unsupported file system was because you had HFS on the drive not HFS+

It been awhile since I've installed a SSHD so I'm rusty on how it looks I think you're just seeing the logical partition as the onboard SSD is involved.

The best thing here is to make a backup and reformat the drive with HFS+ and then install Sierra or older OS onto the drive.

Don't go with High Sierra it has too many issues!

As far as your reasons the 2011 models do have an issue with the GPU's, but the 2012 are very sable and don't have the same sensitivity with their GPU's. It still comes downs to what you run on the system. It's not a gamers box or one that can handle heavy graphical stuff. So you do need to be mindful of that.

The late 2013 retinas to 2015 are all OK, but the 2016 onward (2018) are just not reliable! Between the keyboard and the display cables.


Show 1 more comment

Add a comment

Add your answer

Jurgen will be eternally grateful.
View Statistics:

Past 24 Hours: 0

Past 7 Days: 1

Past 30 Days: 2

All Time: 59