Kernel Panics

[1ambulletproof]

Thanks for any help, this is my first post of this kind so please be kind if I am missing some obvious information and don't hesitate to request it!



The Problem:

I started experienceing intermittent KERNEL PANICS on a late 2011 15" Macbook Pro.



Questions & Requests:

1. I cannot interpret the kernel panic logs and therefore am hoping for help doing so.

2. I also have yet to identify the cause of the kernel panics so please suggest any causes as well!

3. Is there any doubt to the Apple Hardware Test program? Memtest did not detect a ram error (though I'm not sure it could test all of my ram).

4. Can I install OS X 10.10 on another partition of my internal 1TB SSD if I already have it installed on the same drive (but not same partition)? Could I then boot into the clean installed partition to effectively test the effect 3rd party software is having? (I believe I could do all of this on an external drive, but would prefer internal)

5. How can I clean a Macbook Pro memory slot ( eraser? Isopropyl alcohol? Compressed air? etc.)



Notes on the Kernel Panics:

1. They occur at random, lengthy, intervals, usually about once per day or two, sometimes longer.

2. When the kernel panic occurs, the system restarts, offers an error report and reloads all software to it's last state.

3. I installed everything using migration assistant from a 2012 13" Macbook Pro

4. Will crash while asleep or while running. Will crash with and without any peripheral devices attached.

5. I will list the occurrences recorded in /library/logs/DiagnosticReports and at least one sample at the end of my post.



What I've Tried & the Effect (in chronological order)

1. Delete things from spotlight - no effect

2. OS X reinstall (but not an erase & install) - seemed to reduce frequency of crashes but not solve problem

3. Deleted PRAM/NVRAM - no effect

4. Reset SMC - no effect

5. Repair disk (said repair unneeded) - no effect

6. Apple Hardware Test w/ Ram in 6 different configurations:

2x8gb Original Configuration - Failed Apple Hardware Test (error 4MEM/9/40000000 0x846e7218) but Passed Memtest & Rember

2x8gb Swapped slots - Failed Apple Hardware Test ( error 4MEM/9/40000000 0x846e8398)

Module A in Slot 0, Module B out - Failed Apple Hardware Test ( error 4MEM/9/40000000 0x846e7218)

Module A in Slot 1, Module B out - Passed at least 1 loop ( Went 1.5-2 hours looped no problems vs failed tests take 10 minutes or less)

Module B in Slot 0, Module A out - Failed Apple Hardware Test ( 4MEM/9/40000000 0x846e7498)

Module B in Slot 1, Module A out -Passed at least 1 loop ( Went 1 hours looped no problems vs failed tests take 10 minutes or less)


What I Plan To Do

1. Operate with 1x8gb memory in slot 1 to examine the possibility slot 0 is the problem. (This is the current state of my machine & testing)

2. Test another set of ram against the Apple Hardware Test

3. Reinstall 2x8GB ram and do a full erase and reinstall with limited third-party software, hoping that may fix the problem.


About my Mac:

Late 2011 15" Macbook Pro (version 8,2)

OS: OSX Yosemite 10.10

CPU: 2.4Ghz Intel Core i7

GPU: MD 6770M 1024MB / Intel HD 3000 512MB

RAM: 1x8GB DDR3 1600MHz (brand = PNY) .............(previously 2x8GB DDR 1600MHz PNY memory but removed 1 stick to test ram slots)

HD: 1x 1TB SSD Samsung 840 EVO

Screen: Default 15" screen / #HELPME 27 xi 27" 1080p external monitor

Peripheral Devices: Logitech Track Pad T651 / Logitech Solar-Powered Bluetooth Keyboard K760 / Logitech Gaming Mouse G100s / Seagate 1TB external Hard drive / WD 500GB external Hard drive



Date/Time of logged kernel panics: (MM/DD/2014 EST )

11/09 2:33PM 11/05 9:17PM 10/29 10:32PM 10/26 8:32PM 10/25 11:30PM 10/24 9:58PM 10/24 9:30PM 10/21 12:30AM


Kernel Panic Details:

 

[honestone]

Hi 1ambulletproof,

Welcome to the forums. Hopefully, you can get the help that you need.

Your first post above is fantastic! You certainly provided quite a bit of useful, pertinent information. And, you have certainly tried a number of trouble shooting things. From a google search I just did on "How to resolve Kernel Panics with Yosemite", it looks like there is one other thing you could try, and that is to boot into Safe Mode. This link has a good explanation about it:

http://support.apple.com/en-us/HT201262

As for installing Yosemite on another partition of your internal drive, it would seem theoretically possible, but I have never tried it myself.

The possible "issues" you are having with the RAM installed in your machine is somewhat bothersome. If you had the more robust Disk Repair program Tech Tool Pro, you could use its' superior Memory Modules Test feature to see if there are any issues. One of it's memory tests is SPD (Serial Presence Detect) Data, useful for isolating each memory module separately for potential issues.

 

[1ambulletproof]

Thanks for the advice. I am currently running the computer on just 1 stick of ram. Unfortunately, that has been going quite well, seemingly indicting the ram slot as the guilty party. I will certainly bring an update by this coming weekend!

Part of me is concerned given the age of the machine that more things will go wrong and I am tempted to sell it. I wouldn't mind your opinion on the matter!

UPDATE:

Based on some advice I got on the forums, I took a look at all of the kernel panic logs and you can see there are a few KEXTS which keep popping up as the last loaded or unloaded:
Logitech KEXTS & AppleUSB something....in fact at least one of those KEXTS is the last unloaded or loaded in every single panic log I have! Is this significant?!

do you think these could be a potential cause and what can I do about them? I assume I can simply uninstall the logitech software although I'm not sure how well my logitech devices will work then...as for the Apple stuff, I'm clueless.


11/9
System uptime in nanoseconds: 121895193199883
last loaded kext at 66958143499949: com.apple.driver.AppleUSBCDC 4.2.2b5 (addr 0xffffff7f8c99f000, size 20480)
last unloaded kext at 121240555710350: com.logitech.driver.LogiGamingMouseFilter 1 (addr 0xffffff7f8c99b000, size 16384)

11/5
System uptime in nanoseconds: 16432253968964
last loaded kext at 16388467454921: com.logitech.driver.LogiGamingMouseFilter 1 (addr 0xffffff7f93544000, size 40960)
last unloaded kext at 6923418831333: com.logitech.driver.LogiGamingMouseFilter 1 (addr 0xffffff7f93544000, size 16384)

10/29
System uptime in nanoseconds: 58488352878479
last loaded kext at 51593552162610: com.apple.iokit.IOSCSIBlockCommandsDevice 3.7.0 (addr 0xffffff7fada24000, size 81920)
last unloaded kext at 51657253699073: com.apple.driver.AppleUSBCDC 4.2.2b5 (addr 0xffffff7fada0f000, size 16384)

10/26
System uptime in nanoseconds: 2043764451404
last loaded kext at 1834323264648: com.apple.filesystems.afpfs 11.0 (addr 0xffffff7f8e1b6000, size 364544)
last unloaded kext at 730073576325: com.apple.driver.AppleUSBCDC 4.2.2b5 (addr 0xffffff7f8e18f000, size 16384)

10/25
System uptime in nanoseconds: 9370783650975
last loaded kext at 9357865422649: com.logitech.driver.LogiGamingMouseFilter 1 (addr 0xffffff7fb2c19000, size 40960)
last unloaded kext at 366625627883: com.apple.driver.AppleUSBUHCI 656.4.1 (addr 0xffffff7fb0842000, size 65536)

10/24
System uptime in nanoseconds: 1591406329428
last loaded kext at 1388887581639: com.apple.filesystems.afpfs 11.0 (addr 0xffffff7f8edc6000, size 364544)
last unloaded kext at 203104128335: com.apple.driver.AppleUSBUHCI 656.4.1 (addr 0xffffff7f8ca42000, size 65536)

10/24
System uptime in nanoseconds: 9287320888067
last loaded kext at 672758242689: com.apple.filesystems.afpfs 11.0 (addr 0xffffff7f85dca000, size 364544)
last unloaded kext at 893891531064: com.logitech.driver.LogiGamingMouseFilter 1 (addr 0xffffff7f85da7000, size 16384)

10/21
System uptime in nanoseconds: 6077713560322
last loaded kext at 925741973337: com.logitech.driver.LogiGamingMouseFilter 1 (addr 0xffffff7f87872000, size 40960)
last unloaded kext at 996517082480: com.logitech.driver.LogiGamingMouseFilter 1 (addr 0xffffff7f87872000, size 16384)

 

[honestone]

Man, I really wish I could help you. But, from a google search I did yesterday regarding your issue, a number of the associated discussions pointed to a defective/bad Ram slot inside your machine.

I guess you could try and "clean" it with a can of compressed air, but that might not do anything, especially based on your Ram slot testing with each of your good, 8 GB Ram sticks. (By the way, are you still able to use the machine no matter which 8 GB Ram stick is in the "good" slot?)

Sorry I can't offer anything better.