Tracing Possible Causes of RAM Kernel Panics: 2 Machines, Same Problem
I've been thinking about and dealing with this issue for over six months now and I'm stuck.
TLDR: x2 2012 era MBP's with aftermarket RAM & SSDs started experiencing kernel panics. Computer A started first. Then bought computer B as replacement. 6 months later, Computer B displays same behavior. Physical pressure/movement of RAM brings computer back from not starting up. How am I killing my MBPs?
Purchased a used 2012 MBP back in 2015 when my MBP was stolen. Machine was in good shape. I added 16GB DDR3 from Crucial, swapped out optical and HDD for SSDs. About a year and a half later, I start seeing kernel panics (crashes... machine will freeze up - or sometimes restart itself). Researched and found out it was a RAM issue. Bought new RAM (Crucial or OWC), installed, same issues.
So, I bought another used 2012 MBP, performed the same mods to it, ran like a top for about 6 months and then boom, kernel panic. Same. Exact. Thing.
So I started treating this like an investigation or an epidemiological study. Something I’m doing must be causing this to happen. For what it’s worth, I have many sticks of RAM, and I’ve swapped them around and still the same thing occurs. Since I tried new RAM sticks for the last MBP and it didn’t work, I’m hesitant to do it again.
When the machine does “panic”, it won’t restart and gives the black screen with the 3 peeps. ( Like it did, just now. ) The only thing that gets it to boot again is a physical pushing on the bottom of the case where the RAM lives. It’s as if the RAM module has a loose connection to the logic board (I’ve tightened the screws to the RAM module and no change).
Same with the other computer. The only thing I can think of is that the way the laptop has been carried, in my camera bag, has caused the logic board to flex over time and caused damage to the RAM module. Does this sound asinine? Possible? Or, is it possible that all these RAM sticks are bad? I’ve run Rember tests on it and comes back as A OK.
Hoping some of you out there have had this issue or can have fun thinking it through with me. I’m really not looking forward to buying a new MBP at the moment for a number of reasons.
Current Machine Specs:
15" MBP Mid-2012
Sierra 10.12.6 (previous machine was running El Capitan)
2.6 GHz Intel Core i7
16GB 1600 MHz DDR3
Nvidia GeForce GT 650M 1024MB
Intel HD Graphics 4000 1536MB
Everything is up to date, well taken care of.
Update (06/16/2018)
For what it's worth... the EtreCheck report.
Update (06/29/2018)
Adding another update as I'm still stumped.
I've been using the problem machine for a few days now with little issue. That said, the laptop has been sitting stationary, on a desk, and plugged into an iMac (as secondary display) and hasn't moved.
Then, yesterday, I take it with me into town to do some work (no panics) and this morning was using it to read the news over breakfast (again, no panics). I then set it back down to hook it up to the iMac and boom... panic.
It will not reboot until I physically press down on the keyboard (or the underside) with some force. Enough force to move the logic board. This leads me to believe that it's a physical connection issue. Is this a ludicrous idea? How could physically pressing on the machine otherwise effect it?
I can only continue like this for so long before needing to purchase another MBP at which time I'll be stuck with the debate: buy this year & model again (it's really powerful enough and thousands of dollars cheaper) or buy the latest MBP and spend all the money to future proof it as much as possible?
Latest Panic Report:
Fri Jun 29 2018 10-48-15 Panic Report
Adding another update as I'm still stumped.
I've been using the problem machine for a few days now with little issue. That said, the laptop has been sitting stationary, on a desk, and plugged into an iMac (as secondary display) and hasn't moved.
Then, yesterday, I take it with me into town to do some work (no panics) and this morning was using it to read the news over breakfast (again, no panics). I then set it back down to hook it up to the iMac and boom... panic.
It will not reboot until I physically press down on the keyboard (or the underside) with some force. Enough force to move the logic board. This leads me to believe that it's a physical connection issue. Is this a ludicrous idea? How could physically pressing on the machine otherwise effect it?
I can only continue like this for so long before needing to purchase another MBP at which time I'll be stuck with the debate: buy this year & model again (it's really powerful enough and thousands of dollars cheaper) or buy the latest MBP and spend all the money to future proof it as much as possible?
Latest Panic Report:
Fri Jun 29 2018 10-48-15 Panic Report
Update (06/29/2018)
Adding another update as I'm still stumped.
I've been using the problem machine for a few days now with little issue. That said, the laptop has been sitting stationary, on a desk, and plugged into an iMac (as secondary display) and hasn't moved.
Then, yesterday, I take it with me into town to do some work (no panics) and this morning was using it to read the news over breakfast (again, no panics). I then set it back down to hook it up to the iMac and boom... panic.
It will not reboot until I physically press down on the keyboard (or the underside) with some force. Enough force to move the logic board. This leads me to believe that it's a physical connection issue. Is this a ludicrous idea? How could physically pressing on the machine otherwise effect it?
I can only continue like this for so long before needing to purchase another MBP at which time I'll be stuck with the debate: buy this year & model again (it's really powerful enough and thousands of dollars cheaper) or buy the latest MBP and spend all the money to future proof it as much as possible?
Latest Panic Report:
Anonymous UUID: 79A4449D-6B81-B4CC-4355-7ECA6F19880B
Fri Jun 29 10:48:15 2018
- Panic Report ***
panic(cpu 0 caller 0xffffff80251fe085): Kernel trap at 0xffffff7fa59358da, type 13=general protection, registers:
CR0: 0x000000008001003b, CR2: 0x00007fac5f8ed530, CR3: 0x000000002919b000, CR4: 0x00000000001626e0
RAX: 0xe9884400000001bf, RBX: 0x0000000000000001, RCX: 0xffffff8025808e80, RDX: 0x0000000000000001
RSP: 0xffffff920f733d60, RBP: 0xffffff920ff33ec0, RSI: 0x0000000000000001, RDI: 0xffffff8044e273c0
R8: 0x000000231153405d, R9: 0xffffff8025808ed8, R10: 0x0000000000000000, R11: 0xffffff80259d1a50
R12: 0x0000002310badff5, R13: 0xffffff8044e273c0, R14: 0xffffff80453f5800, R15: 0xffffff7fa5934d42
RFL: 0x0000000000010286, RIP: 0xffffff7fa59358da, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x00007fac5f8ed530, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 0
Backtrace (CPU 0), Frame : Return Address
0xffffff8024f4b450 : 0xffffff80250e850c
0xffffff8024f4b4d0 : 0xffffff80251fe085
0xffffff8024f4b6b0 : 0xffffff8025099543
0xffffff8024f4b6d0 : 0xffffff7fa59358da
0xffffff920ff33ec0 : 0xffffff7fa5934d67
0xffffff920ff33ee0 : 0xffffff80256bc68f
0xffffff920ff33f30 : 0xffffff80256baef1
0xffffff920ff33f80 : 0xffffff80256ba4d6
0xffffff920ff33fb0 : 0xffffff80250988f7
Kernel Extensions in backtrace:
com.apple.kec.corecrypto(1.0)[E3701C61-A548-3181-9F3E-C90DF8327185]@0xffffff7fa5c70000->0xffffff7fa5d18fff
com.apple.kec.pthread(1.0)[225C22A5-813D-3651-9C40-FDEEAB0D78E1]@0xffffff7fa5d5f000->0xffffff7fa5d6dfff
com.apple.kec.Libm(1.0)[968CBFF1-925D-321E-A5E0-0C5C563BF08C]@0xffffff7fa62b8000->0xffffff7fa62c2fff
com.apple.iokit.IOACPIFamily(1.4)[4F7FB6AD-2498-3F71-827C-ED7AA4BF2511]@0xffffff7fa5c05000->0xffffff7fa5c0dfff
kmod dependency scan stopped due to missing kmod page: 0x400000001
com.apple.iokit.IOPCIFamily(2.9)[A2EC4168-207E-3423-B948-EEB22E66F9C7]@0xffffff7fa5931000->0xffffff7fa5965fff
com.apple.driver.AppleACPIPlatform(5.0)[65E05472-6AE7-3308-8CC8-FA6CB0DB2AEE]@0xffffff7fa8703000->0xffffff7fa8762fff
dependency: com.apple.iokit.IOACPIFamily()[4F7FB6AD-2498-3F71-827C-ED7AA4BF2511]@0xffffff7fa5c05000
dependency: com.apple.iokit.IOPCIFamily(@9c%Model: MacBookPro9,1, BootROM MBP91.00DA.B00, 4 processors, Intel Core i7, 2.6 GHz, 16 GB, SMC 2.1f175
Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In
Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x0D9B, -
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x0D9B, -
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xF5), Broadcom BCM43xx 1.0 (7.21.171.133.1a2)
Bluetooth: Version 5.0.5f2, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: Samsung SSD 850 EVO 250GB, 250.06 GB
Serial ATA Device: Crucial_CT750MX300SSD1, 750.16 GB
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
Thunderbolt Bus: MacBook Pro, Apple Inc., 25.1
Update (06/29/2018)
Adding another update as I'm still stumped.
I've been using the problem machine for a few days now with little issue. That said, the laptop has been sitting stationary, on a desk, and plugged into an iMac (as secondary display) and hasn't moved.
Then, yesterday, I take it with me into town to do some work (no panics) and this morning was using it to read the news over breakfast (again, no panics). I then set it back down to hook it up to the iMac and boom... panic.
It will not reboot until I physically press down on the keyboard (or the underside) with some force. Enough force to move the logic board. This leads me to believe that it's a physical connection issue. Is this a ludicrous idea? How could physically pressing on the machine otherwise effect it?
I can only continue like this for so long before needing to purchase another MBP at which time I'll be stuck with the debate: buy this year & model again (it's really powerful enough and thousands of dollars cheaper) or buy the latest MBP and spend all the money to future proof it as much as possible?
Latest Panic Report:
Anonymous UUID: 79A4449D-6B81-B4CC-4355-7ECA6F19880B
Fri Jun 29 10:48:15 2018
- Panic Report ***
panic(cpu 0 caller 0xffffff80251fe085): Kernel trap at 0xffffff7fa59358da, type 13=general protection, registers:
CR0: 0x000000008001003b, CR2: 0x00007fac5f8ed530, CR3: 0x000000002919b000, CR4: 0x00000000001626e0
RAX: 0xe9884400000001bf, RBX: 0x0000000000000001, RCX: 0xffffff8025808e80, RDX: 0x0000000000000001
RSP: 0xffffff920f733d60, RBP: 0xffffff920ff33ec0, RSI: 0x0000000000000001, RDI: 0xffffff8044e273c0
R8: 0x000000231153405d, R9: 0xffffff8025808ed8, R10: 0x0000000000000000, R11: 0xffffff80259d1a50
R12: 0x0000002310badff5, R13: 0xffffff8044e273c0, R14: 0xffffff80453f5800, R15: 0xffffff7fa5934d42
RFL: 0x0000000000010286, RIP: 0xffffff7fa59358da, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x00007fac5f8ed530, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 0
Backtrace (CPU 0), Frame : Return Address
0xffffff8024f4b450 : 0xffffff80250e850c
0xffffff8024f4b4d0 : 0xffffff80251fe085
0xffffff8024f4b6b0 : 0xffffff8025099543
0xffffff8024f4b6d0 : 0xffffff7fa59358da
0xffffff920ff33ec0 : 0xffffff7fa5934d67
0xffffff920ff33ee0 : 0xffffff80256bc68f
0xffffff920ff33f30 : 0xffffff80256baef1
0xffffff920ff33f80 : 0xffffff80256ba4d6
0xffffff920ff33fb0 : 0xffffff80250988f7
Kernel Extensions in backtrace:
com.apple.kec.corecrypto(1.0)[E3701C61-A548-3181-9F3E-C90DF8327185]@0xffffff7fa5c70000->0xffffff7fa5d18fff
com.apple.kec.pthread(1.0)[225C22A5-813D-3651-9C40-FDEEAB0D78E1]@0xffffff7fa5d5f000->0xffffff7fa5d6dfff
com.apple.kec.Libm(1.0)[968CBFF1-925D-321E-A5E0-0C5C563BF08C]@0xffffff7fa62b8000->0xffffff7fa62c2fff
com.apple.iokit.IOACPIFamily(1.4)[4F7FB6AD-2498-3F71-827C-ED7AA4BF2511]@0xffffff7fa5c05000->0xffffff7fa5c0dfff
kmod dependency scan stopped due to missing kmod page: 0x400000001
com.apple.iokit.IOPCIFamily(2.9)[A2EC4168-207E-3423-B948-EEB22E66F9C7]@0xffffff7fa5931000->0xffffff7fa5965fff
com.apple.driver.AppleACPIPlatform(5.0)[65E05472-6AE7-3308-8CC8-FA6CB0DB2AEE]@0xffffff7fa8703000->0xffffff7fa8762fff
dependency: com.apple.iokit.IOACPIFamily()[4F7FB6AD-2498-3F71-827C-ED7AA4BF2511]@0xffffff7fa5c05000
dependency: com.apple.iokit.IOPCIFamily(@9c%Model: MacBookPro9,1, BootROM MBP91.00DA.B00, 4 processors, Intel Core i7, 2.6 GHz, 16 GB, SMC 2.1f175
Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In
Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x0D9B, -
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x0D9B, -
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xF5), Broadcom BCM43xx 1.0 (7.21.171.133.1a2)
Bluetooth: Version 5.0.5f2, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: Samsung SSD 850 EVO 250GB, 250.06 GB
Serial ATA Device: Crucial_CT750MX300SSD1, 750.16 GB
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
Thunderbolt Bus: MacBook Pro, Apple Inc., 25.1
Questa è una buona domanda?
2 Commenti
How do you have your SSD drives setup? Independent or RAID'ed?
da Dan
Independent.
da Kyle Petrozza