MX500gb SSD installed onto mid 2012 unibody macbook pro, kernel panic ensues

Bit Baby

MX500gb SSD installed onto mid 2012 unibody macbook pro, kernel panic ensues

I bought a 500gb crucial ssd to install onto my Macbook pro (mid 2012) and installation went fine. But now, I sometimes get kernel panics? The macbook just slows down and then shuts off. When I restart it says it can not see any startup disk, then i wait a bit and try again and it works fine. What should I do? When I first installed I had messed up. I did not change my startup disk to the newly installed ssd and when I removed the usb i used to install Mojave obviously my computer didnt start up. So i tried again and this time i did change the startup disk to the ssd, but then it wouldnt work once again. So I just installed OS lion from the internet, and then updated to mojave, all on the SSd, then everything was fine. But a few days later, as I was working on word and had some tabs open, my computer just slowed down, and it froze, i shut it off, restarted, and saw the icon indicating no starup disk found, then the icon indicating no OS was found and then th eaple logo, and it cycled through these three logos for a bit. I shut it off and waited an hour, and then it ws fine, and in the console i saw kernel panic had casued the crash. This same thing happened a little while later, same exact thing, just had to wait a bit for it to work again, This time it happened when I had multiple tabs of chrome open, a word doc and i was charging some stuff via the USB ports, I noticed my mac had gotten really hot so maybe that had something to do with it? Anyways any help would be appreciated.


4 Replies

Re: MX500gb SSD installed onto mid 2012 unibody macbook pro, kernel panic ensues

Is this a 13" model?  If so you may need to replace the Hard Drive Cable.   First you can try reseating the cable to the Logic Board.  Also check the memory modules are locked into place.  Use a wooden toothpick to press on the edge of the "lower" memory module to see if it is locked in place (make sure not to press against any of the small components on the memory module or they will become damaged.  Then press down on the upper module.  Sometimes the levers locking the memory in place can unlatch.


Post one of the Kernel Panic logs here.  You can use the Console app to locate it.  Within the Console app, the log name will begin with "Kernel" and and with ".panic" and will include the timestamp within the name.  I believe in Mojave you need to click on one of the Diagnostic folders (probably the one in /Library folder) the System Reports folder in the left pane within the Console app and this panic file will show up in the 2nd pane.


You can try running the Apple Hardware Test by holding the D key immediately after powering on.  See if it fails any of the tests.

Bit Baby

Re: MX500gb SSD installed onto mid 2012 unibody macbook pro, kernel panic ensues

Hi, thanks for the reply. It is a 13" model, and the hard drive cable has been replaced once before, about a year ago. I'll try and check under the hood. The kernel panic is as follows, also i found some "shutdown stalls" reports? I'm not sure if any of that is relevant. Anyways, Thank you!

Mon Jan 14 23:10:09 2019

*** Panic Report ***
panic(cpu 1 caller 0xffffff80012da1ed): Kernel trap at 0xffffff7f8262c570, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x000000164f524080, CR3: 0x000000000504e000, CR4: 0x00000000001626e0
RAX: 0xffffff8018c0c000, RBX: 0xffffff8102833db0, RCX: 0xffffff80ec7f8100, RDX: 0x0000000000000001
RSP: 0xffffff8102833db0, RBP: 0xffffff8102833de0, RSI: 0xffffff80142b6420, RDI: 0xffffff8102833db0
R8: 0x0000000000000019, R9: 0xffffff8001a9de80, R10: 0xffffff8001a9dc60, R11: 0x0000000000000040
R12: 0x0000000100000509, R13: 0xffffff80018292b0, R14: 0xffffff80142b6380, R15: 0x00000001000003ca
RFL: 0x0000000000010286, RIP: 0xffffff7f8262c570, CS: 0x0000000000000008, SS: 0x0000000000000000
Fault CR2: 0xffffff80ec7f8118, Error code: 0x0000000000000002, Fault CPU: 0x1, PL: 0, VF: 10

Backtrace (CPU 1), Frame : Return Address
0xffffff8102833880 : 0xffffff80011aeafd
0xffffff81028338d0 : 0xffffff80012e85a3
0xffffff8102833910 : 0xffffff80012d9fca
0xffffff8102833980 : 0xffffff800115bca0
0xffffff81028339a0 : 0xffffff80011ae517
0xffffff8102833ac0 : 0xffffff80011ae363
0xffffff8102833b30 : 0xffffff80012da1ed
0xffffff8102833ca0 : 0xffffff800115bca0
0xffffff8102833cc0 : 0xffffff7f8262c570
0xffffff8102833de0 : 0xffffff7f82646b35
0xffffff8102833e20 : 0xffffff7f8264671b
0xffffff8102833e40 : 0xffffff7f82646801
0xffffff8102833e60 : 0xffffff80018293bd
0xffffff8102833ea0 : 0xffffff800185546e
0xffffff8102833ee0 : 0xffffff8001828479
0xffffff8102833f60 : 0xffffff8001832e67
0xffffff8102833fa0 : 0xffffff800115b0ce
Kernel Extensions in backtrace:[FA92A03C-F113-384A-9B1F-B2C52DE7F4D2]@0xffffff7f82610000->0xffffff7f826b4fff

BSD process name corresponding to current thread: kernel_task

Mac OS version:

Kernel version:
Darwin Kernel Version 18.2.0: Mon Nov 12 20:24:46 PST 2018; root:xnu-4903.231.4~2/RELEASE_X86_64
Kernel UUID: 56B30885-F9BA-30E8-AD1C-5D59EC243BA9
Kernel slide: 0x0000000000e00000
Kernel text base: 0xffffff8001000000
__HIB text base: 0xffffff8000f00000
System model name: MacBookPro9,2 (Mac-6F01561E16C75D06)

System uptime in nanoseconds: 72632945199106
last loaded kext at 61510476280158: 5.0.0 (addr 0xffffff7f84706000, size 32768)
last unloaded kext at 63179909419677: 5.0.0 (addr 0xffffff7f846dc000, size 28672)
loaded kexts: 2.0.0 3.3.1 1.70 18.306.12 3.0 110.23.46 1.0.0 131 3.28.4 3.28.4 282.10 282.10 3.6.5 1 1.0.1 6.0.9f2 1 3.0.4d1 7.0.0 12.0.4 3.1.2 1 1.0.0 3.1 1 212 4.0.0 12.0.4 170.12.11 1.5.6 254 254 354 945.230.6 2.1.2 407.200.4 1.0.0d1 40 1.0.0 1.0 408.200.1 1.7.6 1.0 5.6.0 1400.1.1 10.3.3 329.200.2 161.0.0 2.0 6.1 1.8 2.1 6.1 1.7 220.0.0 190 8 220.0.0 1.0 282.10 527 710.1 700.7 1.0 3.28.4 282.10 282.10 3.28.4 1.0.14d1 2.3.0 1.0.0 6.0.0d8 1.0.0 404.2.2 255.1 3.28.4 1.1.0 530 1.0.18d1 530.14 6.0.9f2 6.0.9f2 6.0.9f2 6.0.9f2 263 1.2 206.5 1.2.0 5.0.0 1.2 1.2 11 1 408.200.1 1.8 1.8 1.8 5.5.8 5.5.8 2.1.4 301.200.2 267.50.1 4.7.3 4.7.6 6.8.1 1200.12.2 1.0.4 1.1.0 1.0.1b8 288 1.2 1.2 1.2 1.2 1.0 900.4.2 1.2 2.1 2.1 1.1 2.0.0 3 300.0 1.0.0d1 493.0.0 28.30 1.0 2 456.230.1 1.0.5 1 145.200.2 408.200.1 408.200.1 2.1 1.0 1 1.2 1.0 1.0 1.0.1 1 47 700.7 3.4 6.1 3.1.9 2.9 1.4 1 1 1.0


System Profile:
Network Service: Wi-Fi, AirPort, en1
Thunderbolt Bus: MacBook Pro, Apple Inc., 25.1
Boot Volume File System Type: apfs
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343531533641465238412D50422020
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343531533641465238412D50422020
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: FaceTime HD Camera (Built-in)
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: Hub
USB Device: Apple Internal Keyboard / Trackpad
USB Device: IR Receiver
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: USB 3.0 Bus
Serial ATA Device: CT500MX500SSD1, 500.11 GB
Serial ATA Device: HL-DT-ST DVDRW GS41N
Model: MacBookPro9,2, BootROM, 2 processors, Intel Core i5, 2.5 GHz, 8 GB, SMC 2.2f44
Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xF5), Broadcom BCM43xx 1.0 ( AirPortDriverBrcm4360-1315.1)
Bluetooth: Version 6.0.9f2, 3 services, 18 devices, 1 incoming serial ports


Re: MX500gb SSD installed onto mid 2012 unibody macbook pro, kernel panic ensues

Thanks for posting the Panic log, but unfortunately nothing too useful there.  As for the "stalls" you mentioned, I have seen those too on otherwise working systems so I guess they are not really significant.  Apple has seriously ruined the usefulness of reviewing logs as they now put all manner of worthless junk in them.  Much of it appears to be left over debugging messages.  Even the legitimate messages have been watered down to next to useless.


Definitely try my previous suggestions.  You can also try using a USB to SATA Adapter/dock/enclosure and connect the SSD externally in order to test it.  This would help determine whether the Hard Drive Cable is at fault.   I've never knowingly seen a HD cable fail that quickly, but I'm sure it would be possible.  If you end up replacing it again, you may want to put some electrical tape underneath it to help protect it from rubbing against the Top Case.  I'm sure a lot of the cables being sold are not really the updated version.   


I've also seen where the memory slot nearest the Bottom Case can become "damaged" or defective.  This can be determined by having the laptop powered on at the Option Boot screen and then pressing on the black plastic base of the memory slot or sometimes even on the Bottom Case in that general area.  If there is a problem you will see graphical glitches on the display and the cursor may stop moving.

Crucial Employee

Re: MX500gb SSD installed onto mid 2012 unibody macbook pro, kernel panic ensues

Mirroring what @HWTech has suggested, get a USB to SATA cable and test the drive externally. Your problems sound like a potential ribbon cable issue.

This troubleshooting and further discussion about the cables is outlined in this TKB we have below.

Crucial_Benny, Micron CPG Support, US

How do I know what memory to buy?
Shop for your region: US | UK | EU | France |
I think my memory is bad. What do I do now?
FAQs and Top Forum Solutions
Did a user help you? Say thanks by giving Kudos!
Still need help? Contact Customer Service
Want to be a Super User?