MacBook Pro repeated kernal panic before start up

[unittwentytwo]

My macbook keeps coming up with the following kernal panic which shows as an error before you can even log in and starts a loop of restarts. Usually 2 or 3 before it allows you to log in past the encryption. I replaced one of the SSD's which seemed to fix the issue for several weeks and now it has returned with exactly the same issue. Can anyone shed any light on this issue? Help is very appreciated.

Image below of error showing up before startup.

MBP INFO:
17-inch, Early 2009 - MacBookPro5,2
Software OS X 10.8.2
2 processors, Intel Core 2 Duo, 2.93 GHz
Memory 8 GB 1067 MHz DDR3
Graphics NVIDIA GeForce 9400M 256 MB
2 x SSD
Serial ATA Device: INTEL SSDSC2CT120A3, 120.03 GB
Serial ATA Device: OCZ-VERTEX3, 120.03 GB

Error report:
Interval Since Last Panic Report: 728695 sec
Panics Since Last Report: 2
Anonymous UUID: ADCF976D-4951-2B6A-FBD7-C10D20A7A574

Wed Jan 9 09:08:17 2013
panic(cpu 1 caller 0xffffff801fcb7bd5): Kernel trap at 0xffffff801fc2da10, type 13=general protection, registers:
CR0: 0x000000008001003b, CR2: 0x0000000000000000, CR3: 0x00000000228e5000, CR4: 0x0000000000000660
RAX: 0x0000000000000001, RBX: 0xffffff8032882000, RCX: 0x0000000009000000, RDX: 0xffffff8101cc5078
RSP: 0xffffff8107483e50, RBP: 0xffffff8107483e80, RSI: 0xffffff8101cc5068, RDI: 0x0000000000000000
R8: 0xffffff80fbc65078, R9: 0xffffffffffffffff, R10: 0x00000000ffffffff, R11: 0x00000000ffffff80
R12: 0xffffff80fbc65000, R13: 0xffffff8032882580, R14: 0x01ffff8032882550, R15: 0x0000000000000000
RFL: 0x0000000000010002, RIP: 0xffffff801fc2da10, CS: 0x0000000000000008, SS: 0x0000000000000000
Fault CR2: 0x0000000000000000, Error code: 0x0000000000000000, Fault CPU: 0x1

Backtrace (CPU 1), Frame : Return Address
0xffffff8107483af0 : 0xffffff801fc1d626
0xffffff8107483b60 : 0xffffff801fcb7bd5
0xffffff8107483d30 : 0xffffff801fcce4ed
0xffffff8107483d50 : 0xffffff801fc2da10
0xffffff8107483e80 : 0xffffff802002e1e9
0xffffff8107483ec0 : 0xffffff802002ca47
0xffffff8107483f30 : 0xffffff802002d3a2
0xffffff8107483f70 : 0xffffff8020031e99
0xffffff8107483fb0 : 0xffffff801fcb26b7

BSD process name corresponding to current thread: kernel_task

Mac OS version:
Not yet set

Kernel version:
Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64
Kernel UUID: 69A5853F-375A-3EF4-9247-478FD0247333
Kernel slide: 0x000000001fa00000
Kernel text base: 0xffffff801fc00000
System model name: MacBookPro5,2 (Mac-F2268EC8)

System uptime in nanoseconds: 1424457346
last loaded kext at 1110147748: com.apple.driver.AppleSmartBatteryManager 161.0.0 (addr 0xffffff7fa1a2b000, size 53248)
loaded kexts:
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleFWOHCI 4.9.6
com.apple.driver.AppleAHCIPort 2.4.1
com.apple.driver.AirPort.Brcm4331 602.15.22
com.apple.driver.AppleUSBEHCI 5.4.0
com.apple.nvenet 2.0.19
com.apple.driver.AppleUSBOHCI 5.2.5
com.apple.driver.AppleIntelCPUPowerManagementClient 196.0.0
com.apple.driver.AppleEFINVRAM 1.6.1
com.apple.driver.AppleRTC 1.5
com.apple.driver.AppleHPET 1.7
com.apple.driver.AppleACPIButtons 1.6
com.apple.driver.AppleSMBIOS 1.9
com.apple.driver.AppleACPIEC 1.6
com.apple.driver.AppleAPIC 1.6
com.apple.nke.applicationfirewall 4.0.39
com.apple.security.quarantine 2
com.apple.driver.AppleIntelCPUPowerManagement 196.0.0
com.apple.iokit.IOFireWireFamily 4.5.5
com.apple.iokit.IOAHCIFamily 2.2.1
com.apple.iokit.IO80211Family 500.15
com.apple.iokit.IONetworkingFamily 3.0
com.apple.driver.NVSMU 2.2.9
com.apple.iokit.IOUSBFamily 5.4.0
com.apple.driver.AppleEFIRuntime 1.6.1
com.apple.iokit.IOHIDFamily 1.8.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 220
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 7
com.apple.driver.DiskImages 344
com.apple.iokit.IOStorageFamily 1.8
com.apple.driver.AppleKeyStore 28.21
com.apple.driver.AppleACPIPlatform 1.6
com.apple.iokit.IOPCIFamily 2.7.2
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.corecrypto 1.0
Model: MacBookPro5,2, BootROM MBP52.008E.B05, 2 processors, Intel Core 2 Duo, 2.93 GHz, 8 GB, SMC 1.42f4
Graphics: NVIDIA GeForce 9400M, NVIDIA GeForce 9400M, PCI, 256 MB
Graphics: NVIDIA GeForce 9600M GT, NVIDIA GeForce 9600M GT, PCIe, 512 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1067 MHz, 0x0198, 0x393930353432382D3030352E4130324C4620
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1067 MHz, 0x0198, 0x393930353432382D3030352E4130324C4620
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (5.106.98.81.22)
Bluetooth: Version 4.0.9f33 10885, 2 service, 11 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: INTEL SSDSC2CT120A3, 120.03 GB
Serial ATA Device: OCZ-VERTEX3, 120.03 GB
USB Device: Built-in iSight, apple_vendor_id, 0x8507, 0x24400000 / 3
USB Device: USB 2.0 Hub [MTT], 0x050d (Belkin Corporation), 0x0307, 0x24100000 / 2
USB Device: hub_device, 0x0424 (SMSC), 0x2512, 0x24110000 / 5
USB Device: hub_device, 0x0424 (SMSC), 0x2602, 0x24111000 / 6
USB Device: USB Laser Mouse, 0x046d (Logitech Inc.), 0xc062, 0x24111200 / 8
USB Device: Flash Card Reader, 0x0424 (SMSC), 0x2228, 0x24111100 / 7
USB Device: External, 0x13fd (Initio Corporation), 0x0840, 0x24120000 / 4
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x06100000 / 2
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8217, 0x06110000 / 5
USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0237, 0x04600000 / 3
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x04500000 / 2

 

[Macman45]

Looks like bad RAM, but the SSD insatll could be an issue too. Try removing one stick, boot, then the other, boot again...I think a visit to Crucial might be in order.

 

[justperry]

Run Apple Hardware Test to see if there are any Hardware issues, if no errors show up you are likely OK, then the problem is the OS.

Many times it points towards hardware but I don't see anything here in this report.

Run AHT first by holding D at startup.

Intel-based Macs: Using Apple Hardware Test

 

[unittwentytwo]

I have tried with the RAM before and its not an issue. Also have swapped SSD's to different brand before which didn't fix it.

But, what I have done now is switch off the filevault. Which appears to be working... I shall keep you posted.

 

[justperry]

I have tried with the RAM before and its not an issue. Also have swapped SSD's to different brand before which didn't fix it.

But, what I have done now is switch off the filevault. Which appears to be working... I shall keep you posted.

Ah yeah, filevault which seems to have problems with certain SSD's, should have known.