MBP SR Kernel Trap

[pingouin]

I just had 2 kernel panic yesterday... any clues? 1st time I was away, and the default screen saver was running... and just panic...

Tue Sep 18 16:17:39 2007
panic(cpu 1 caller 0x003BEE20): OSObject::refcount: Attempting to retain a freed object
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x258dbbb8 : 0x128d08 (0x3cc0a4 0x258dbbdc 0x131de5 0x0)
0x258dbbf8 : 0x3bee20 (0x3f262c 0x3f2608 0x4408624 0x42e5080)
0x258dbc18 : 0x3c1cab (0x3f433c0 0x4b0958 0x28 0x3c1934)
0x258dbc48 : 0x3c1e04 (0x522dbc0 0x42e5080 0x0 0x3c205f)
0x258dbc68 : 0x3c27fa (0x42e5080 0x0 0x0 0x0)
0x258dbca8 : 0x3c2867 (0x42e5080 0x5160540 0x423b180 0x1628d8)
0x258dbce8 : 0x38759c (0x42dc280 0x0 0x258dbd28 0x3c1f72)
0x258dbd08 : 0x38adbb (0x474f900 0x438dac0 0x0 0x474f900)
0x258dbd28 : 0x3b23a8 (0x474f900 0x438dac0 0x258dbd58 0x3bef49)
0x258dbd78 : 0x188511 (0x474f900 0x528a7b4 0x528a7c8 0x11cc32)
0x258dbdb8 : 0x12b4c3 (0x528a5b4 0x528a798 0x0 0x0)
0x258dbdf8 : 0x124b17 (0x528a500 0x0 0x18 0x258dbedc)
0x258dbf08 : 0x195a42 (0x258dbf44 0x0 0x0 0x0)
0x258dbfc8 : 0x19b32e (0x4966260 0x0 0x19e0b5 0x4966260) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb011e3c8

Kernel version:
Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386


*********

Tue Sep 18 23:24:23 2007
panic(cpu 1 caller 0x001A4A55): Unresolved kernel trap (CPU 1, Type 14=page fault), registers:
CR0: 0x80010033, CR2: 0x00000000, CR3: 0x01352000, CR4: 0x000006e0
EAX: 0x04404b20, EBX: 0x00000018, ECX: 0x004b0958, EDX: 0x0440a660
CR2: 0x00000000, EBP: 0x2593bc48, ESI: 0x00000003, EDI: 0x054b9200
EFL: 0x00010202, EIP: 0x00000000, CS: 0x00000008, DS: 0x00000010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x2593ba18 : 0x128d08 (0x3cc0a4 0x2593ba3c 0x131de5 0x0)
0x2593ba58 : 0x1a4a55 (0x3d24b8 0x1 0xe 0x3d1cdc)
0x2593bb68 : 0x19aeb4 (0x2593bb80 0x206 0x2593bbd8 0x1416ad)
0x2593bc48 : 0x3c1e04 (0x54b9200 0x4176f40 0x0 0x3c205f)
0x2593bc68 : 0x3c27fa (0x4176f40 0x0 0x0 0x0)
0x2593bca8 : 0x3c2867 (0x4176f40 0x52c7e80 0x53a7e00 0x1628d8)
0x2593bce8 : 0x38759c (0x4148180 0x0 0x2593bd28 0x3c1f72)
0x2593bd08 : 0x38adbb (0x412c680 0x53b1540 0x0 0x412c680)
0x2593bd28 : 0x3b23a8 (0x412c680 0x53b1540 0x2593bd58 0x3bef49)
0x2593bd78 : 0x188511 (0x412c680 0x3f839b4 0x3f839c8 0x11cc32)
0x2593bdb8 : 0x12b4c3 (0x4e00cb4 0x3f83998 0x0 0x0)
0x2593bdf8 : 0x124b17 (0x4e00c00 0x0 0x18 0x2593bedc)
0x2593bf08 : 0x195a42 (0x2593bf44 0x0 0x0 0x0)
0x2593bfc8 : 0x19b32e (0x4a08ee0 0x0 0x19e0b5 0x48cede0) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb011e3b8

Kernel version:
Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386

 

[mad jew]

My first guess is RAM. Take a chip out at a time to test if it could be causing the panics. While you're at it, you may as well run the Apple Hardware Test from the discs that came with the machine. They may not necessarily find anything wrong with your MacBook Pro, but they could point you in the right direction.