Ga door naar hoofdinhoud

Released June 2012 / Core i7 processor with Turbo Boost / Up to 1 GB DDR5 Video RAM

464 Vragen Bekijk alle

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.

Panic Report

Update (06/16/2018)

For what it's worth... the EtreCheck report.

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

Beantwoord deze vraag Dit probleem heb ik ook

Is dit een goede vraag?

Score 0

Commentaar:

How do you have your SSD drives setup? Independent or RAID'ed?

door

Independent.

door

Een opmerking toevoegen

PC Laptop batterijen

An easy fix for a big power boost.

Nu winkelen

PC Laptop batterijen

An easy fix for a big power boost.

Nu winkelen

2 Antwoorden

Het nuttigste antwoord

I experienced this on several machines in the last couple of months. It is my personal belief the Apple has caused it in their system upgrade with High Sierra on machines that have ANY third party upgrades (RAM or hard drives. So far I have been able to get all of them running again by booting from an external drive with El Capitan installed. Next I removed the internal drive and wiped it on another machine then installed El Capitan. One 2009 I had to take back to Mavericks.

Was dit antwoord nuttig?

Score 2

Commentaar:

Interesting theory. I'm running Sierra on my current machine. I also experienced issues with El Capitan on the older machine. If your theory is true, looks like I'll be waiting for that next MBP to drop.

door

@mayer - I don't think Apple is doing anything deliberately here.

I had a system a few weeks ago that had a similar problem with memory errors. In that case the systems RAM was to low for what the person was trying to run (Photoshop). In that case the graphics chip was using the main RAM and with such a tight system (RAM-wise) it was shuttling active RAM to drive (Paging) so much it was falling on top of its self. In addition the system was overheating.

Cleaned the system and replaced the heatsink and thermal paste added more RAM and wiped the drive and re-installed the OS & Apps (HDD) came back to life!

door

@danj You did what I'm having to do. Wipe the drive and reinstall a clean system.

door

@mayer - True! I think this gets into the age of these systems needing a bit more TLC and not expect more out of them than what they were designed to run.

Basically, people are expecting more than what some of these systems can support.

door

@danj I just find it extremely suspicious that this has only happened to machines with either RAM or Hard drive upgrades and all right after a High Sierra update. It appears to me that since 2010 (the heat sensor on non-Apple hard drives, that Apple has directly targeted any third party upgrades and now service (especially on iPhones). The use of proprietary storage in all Retina machines. My business is down 70% in the last year. How are you doing?

BTW have you noticed you can't find parts and iFixit lists them but almost none are in stock.

door

1 commentaar meer tonen

Een opmerking toevoegen

There are a few things I would do here. Make sure the HD bay drive is your faster drive and you likely need to replace the HD SATA cable as they tend to breakdown.

Remember your system will leverage the drive for virtual RAM which can mis-lead you into thinking you have a RAM error when in fact the virtual RAM (page file) is corrupted. This is where you’ll need to fully wipe the drive and re-install the OS & apps!

You may need to look at the SSD using the vendors tools to see what its health looks like you might have some bad blocks that need to be mapped out.

I often find artist which use Mac’s have more of a problem with bad blocks on SSD’s as the way they use their systems tends to cause a lot of data churn while a HD can handle that quite well SSD’s not so much! This is due to their design. Don’t get me wrong! I love SSD’s, its how we abuse them thats the issue!

In your case I’m thinking you maybe hitting a wear issue on the primary SSD (your boot drive). You might want to look at getting a new SSD and maybe one thats better suited for heavy data churning I/O like the Samsung Pro series. You don’t need something huge but you want something that can support all your OS, Apps and the virtual RAM (paging). I have a 500 GB drive in my iMac.

Lastly, you may want to clean your heat sink and apply a fresh coat of thermal paste so your chips run cooler.

Was dit antwoord nuttig?

Score 1

Commentaar:

Fantastic info. I'll respond at length when I have more time. Thank you.

door

I'm finally getting back around to this post... Yes, the HD bay is the faster of the 2 SSDs (Samsung EVO). This would make sense since this was the HD in both machines.

Samsung's Magician Software is only available for Windows. Any rec's for decent software to check the SSD?

I've always been curious: When wiping the HD and reinstalling OS & Apps, is reinstalling from a time machine backup or restoring from a disk image of my current setup the same as re-installing the apps 1by1? Or, does restoring copy the "corrupt" portions of my system back onto the freshly wiped drive?

Noted on heat sink and thermal paste. Will do some research. For what it's worth, I run iStat Menus which contains fan control features and I always keep an eye on my temps and up the default fan speeds when doing heavy work.

Thanks again for the info!

door

For what it's worth, Samsung has amazing customer support.

door

@globalksp - Yes they do! I only use Samsung SSD drives. Did they tell you how to make a bootable Magician software using Linux?

Thats what I have here's a link to the Samsung download page which has the info and tools (in case you don't have the CD disk) Samsung Tools

door

Thanks @Dan. But, I don't have an optical drive in the MBP anymore. I've tried creating a bootable ISO on an external, firewire drive, but no luck.

door

10 commentaren meer tonen

Een opmerking toevoegen

Voeg je antwoord toe

Kyle Petrozza zal eeuwig dankbaar zijn.
Weergavestatistieken:

Afgelopen 24 Uren: 0

Afgelopen 7 Dagen: 2

Afgelopen 30 Dagen: 21

Altijd: 466