Mid 2012 13" MacBook Pro kernel panic issue

[luthier42]

I picked up a used MacBook Pro a while ago and immediately replaced the HDD with a 1TB SSD and maxed the RAM. I only turned it on once before hand to run a hardware test which came back okay. It often (almost all the time) crashes whenever I wake it up from sleep either immediately or within a few minutes. Hardware test still says it's okay. Thoughts?

panic(cpu 0 caller 0xffffff8029e17cc2): Kernel trap at 0xffffff802aa47f33, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0xffffff802aa47f33, CR3: 0x000000041c5820a9, CR4: 0x00000000001626e0
RAX: 0x0000000000000000, RBX: 0x0000000000000001, RCX: 0xc6e0e3549a680097, RDX: 0x0000000000000000
RSP: 0xffffff82288bb9b0, RBP: 0xffffff82288bba00, RSI: 0xffffff806a489800, RDI: 0xffffff8052f9da50
R8: 0x0000000000000001, R9: 0x0000000000000000, R10: 0xffffff806a489800, R11: 0x0000110fe1b734b1
R12: 0x0000000000040000, R13: 0x0000000407980000, R14: 0x0000000007980000, R15: 0xffffff8052f9da50
RFL: 0x0000000000010286, RIP: 0xffffff802aa47f33, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0xffffff802aa47f33, Error code: 0x0000000000000010, Fault CPU: 0x0

Backtrace (CPU 0), Frame : Return Address
0xffffff82288bb660 : 0xffffff8029d2bda1
0xffffff82288bb6e0 : 0xffffff8029e17cc2
0xffffff82288bb8a0 : 0xffffff8029e34b73
0xffffff82288bb8c0 : 0xffffff802aa47f33
0xffffff82288bba00 : 0xffffff8029cfdb6b
0xffffff82288bba40 : 0xffffff8029d8dd79
0xffffff82288bba80 : 0xffffff8029d8f464
0xffffff82288bbaf0 : 0xffffff8029d8dff5
0xffffff82288bbb20 : 0xffffff8029d90591
0xffffff82288bbb60 : 0xffffff8029d952bf
0xffffff82288bbd10 : 0xffffff8029d99aa3
0xffffff82288bbf20 : 0xffffff8029e18224
0xffffff82288bbfb0 : 0xffffff8029e34a85

BSD process name corresponding to current thread: com.apple.photom

Mac OS version:
14D136

Kernel version:
Darwin Kernel Version 14.3.0: Mon Mar 23 11:59:05 PDT 2015; root:xnu-2782.20.48~5/RELEASE_X86_64
Kernel UUID: 4B3A11F4-77AA-3D27-A22D-81A1BC5B504D
Kernel slide: 0x0000000029a00000
Kernel text base: 0xffffff8029c00000
__HIB text base: 0xffffff8029b00000
System model name: MacBookPro9,2 (Mac-6F01561E16C75D06)

 

[thekev]

The hardware test isn't that helpful. Does it have any third party ram installed? Failing memory is a frequent cause of panics, and many people fail to test their memory upgrades. Failing logic boards are a much worse one.

 

[yukari]

The hardware test isn't that helpful. Does it have any third party ram installed? Failing memory is a frequent cause of panics, and many people fail to test their memory upgrades. Failing logic boards are a much worse one.

+1. That is exactly what happen to my late 2011 MBP 15". At first I tested all the hardwares and found no issues. But when the MBP started chiming on the start up, it indicated it was the RAM. I forget how many times it chimed. I think there is a code for the number of chimes to the problem.

 

[thekev]

+1. That is exactly what happen to my late 2011 MBP 15". At first I tested all the hardwares and found no issues. But when the MBP started chiming on the start up, it indicated it was the RAM. I forget how many times it chimed. I think there is a code for the number of chimes to the problem.

It doesn't always chime. Sometimes a chip still works but doesn't work that well. In those cases you have to really test them. Most third party ram is carries a long warranty, so it's one of the cheaper fixes. It's a lot worse if the issue is a failing logic board.