Random Kernel Panics, but same caller address

[oticon6]

I've had a lot of kernel panics over the last few months, and apart from a few known issues (vmware beta, AD2P driver), all the rest seem really random apart from one thing: The caller address was ALWAYS 0x001A8CD4 for OSX v9E17, and ALWAYS 0x001A8CEC for OSX v9F33

Where should I be looking? I've tried AHT and simple RAM testing utility (but from within the OS). Yesterday I tried swapping the RAM modules around and retested using the utility (since that should put any dead addresses within the testable memory range) but no luck so far... and no new KPs (yet) so I can't compare a change in address.

Where should I be looking? What is the "caller" and does this consistency imply software or hardware? How can I work out what this is? >_< Everything is impeccably stable other than this...

 

[Sun Baked]

Any USB hubs?

If not it may be a bluetooth device.

---

This is if you see some ....

com.apple.iokit.IOAudioFamily
com.apple.iokit.IOUSBFamily

further down the KP page.

 

[oticon6]

Any USB hubs?

If not it may be a bluetooth device.

---

This is if you see some ....

com.apple.iokit.IOAudioFamily
com.apple.iokit.IOUSBFamily

further down the KP page.

No USB hubs or anything funky connected... and it's definitely NOT a driver issue. There are no "kernel loadable modules" listed. I have had that type of kernel panic, but it's quite obvious when that happens.

Here are a few example panics for what I'm talking about:

Fri Jul 11 07:33:20 2008
panic(cpu 0 caller 0x001A8CD4): Kernel trap at 0x0017e175, type 14=page fault, registers:
CR0: 0x8001003b, CR2: 0x00000010, CR3: 0x010d0000, CR4: 0x00000660
EAX: 0x00000000, EBX: 0x020add38, ECX: 0x00519120, EDX: 0x00000010
CR2: 0x00000010, EBP: 0x6c4f3e48, ESI: 0x0261a0fc, EDI: 0x0821cec4
EFL: 0x00010206, EIP: 0x0017e175, CS: 0x00000008, DS: 0xffff0010
Error code: 0x00000000

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x6c4f3c58 : 0x12b0fa (0x4592a4 0x6c4f3c8c 0x133243 0x0)
0x6c4f3ca8 : 0x1a8cd4 (0x46280c 0x17e175 0xe 0x461fbc)
0x6c4f3d88 : 0x19ede5 (0x6c4f3da0 0x0 0x6c4f3e48 0x17e175)
0x6c4f3d98 : 0x17e175 (0xe 0x4f60048 0x6c4f0010 0x190010)
0x6c4f3e48 : 0x17f626 (0x261a0fc 0x60 0x6c4f3eb8 0x82143d4)
0x6c4f3e68 : 0x172c60 (0x261a0fc 0x6b47048 0x6c4f3ed8 0x719dbc0)
0x6c4f3ea8 : 0x18704d (0x821cec4 0x719a6b0 0x6c4f3f18 0x136853)
0x6c4f3ef8 : 0x17b91a (0x53d418 0x23ac6252 0x16 0x53b0e0)
0x6c4f3f98 : 0x17c67c (0x0 0x0 0x6c4f3fc8 0x719a6b0)
0x6c4f3fc8 : 0x19ebdc (0x0 0x0 0x1a20b5 0x8624f20)
Backtrace terminated-invalid frame pointer 0

BSD process name corresponding to current thread: kernel_task

Mac OS version:
9E17

Kernel version:
Darwin Kernel Version 9.4.0: Mon Jun 9 19:30:53 PDT 2008; root:xnu-1228.5.20~1/RELEASE_I386
System model name: iMac7,1 (Mac-F42386C8)

Tue Sep 2 03:27:46 2008
panic(cpu 0 caller 0x001A8CD4): Kernel trap at 0x0017f745, type 14=page fault, registers:
CR0: 0x80010033, CR2: 0x00010004, CR3: 0x010ea000, CR4: 0x00000660
EAX: 0x00000004, EBX: 0x02a37004, ECX: 0x0053d618, EDX: 0x00010000
CR2: 0x00010004, EBP: 0x5b4cfcb8, ESI: 0x0a296834, EDI: 0x02a1a108
EFL: 0x00010287, EIP: 0x0017f745, CS: 0x00000008, DS: 0x00000010
Error code: 0x00000003

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x5b4cfac8 : 0x12b0fa (0x4592a4 0x5b4cfafc 0x133243 0x0)
0x5b4cfb18 : 0x1a8cd4 (0x46280c 0x17f745 0xe 0x461fbc)
0x5b4cfbf8 : 0x19ede5 (0x5b4cfc10 0x0 0x5b4cfcb8 0x17f745)
0x5b4cfc08 : 0x17f745 (0xe 0x48 0x7e40010 0x10)
0x5b4cfcb8 : 0x17476f (0x2a37004 0x33493 0x5b4cfcd8 0x1a236f)
0x5b4cfcf8 : 0x174dad (0x1 0x23ac6252 0x64 0x0)
0x5b4cfd38 : 0x17514a (0xa29683c 0x0 0x24208000 0x0)
0x5b4cfd78 : 0x16a235 (0xa296834 0xb5e6318 0x0 0x24208000)
0x5b4cfe98 : 0x16a437 (0x24788000 0x0 0x0 0x0)
0x5b4cfed8 : 0x18249d (0x7760870 0x23788000 0x0 0x24788000)
0x5b4cff38 : 0x375025 (0x7760870 0x23788000 0x0 0x1000000)
0x5b4cff78 : 0x3ddde2 (0x72ed970 0x7f91260 0x7f912a4 0xbfffee20)
0x5b4cffc8 : 0x19f2c3 (0x7c86f80 0x0 0x1a20b5 0xb7fc5e0)
No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbfffe7b8

BSD process name corresponding to current thread: Safari

Mac OS version:
9E17

Kernel version:
Darwin Kernel Version 9.4.0: Mon Jun 9 19:30:53 PDT 2008; root:xnu-1228.5.20~1/RELEASE_I386
System model name: iMac7,1 (Mac-F42386C8)

Sat Sep 20 13:45:08 2008
panic(cpu 1 caller 0x001A8CEC): Kernel trap at 0x0017f6e8, type 14=page fault, registers:
CR0: 0x8001003b, CR2: 0x00420004, CR3: 0x010d2000, CR4: 0x00000660
EAX: 0x00800034, EBX: 0x04c450c0, ECX: 0x00000000, EDX: 0x00420000
CR2: 0x00420004, EBP: 0x5b997568, ESI: 0x095e1f50, EDI: 0x03922108
EFL: 0x00010287, EIP: 0x0017f6e8, CS: 0x00000008, DS: 0x00000010
Error code: 0x00000003

Backtrace (CPU 1), Frame : Return Address (4 potential args on stack)
0x5b997378 : 0x12b0fa (0x459234 0x5b9973ac 0x133243 0x0)
0x5b9973c8 : 0x1a8cec (0x4627a0 0x17f6e8 0xe 0x461f50)
0x5b9974a8 : 0x19eed5 (0x5b9974c0 0x218c870 0x5b997568 0x17f6e8)
0x5b9974b8 : 0x17f6e8 (0xe 0x48 0x70 0x190010)
0x5b997568 : 0x174770 (0x4c450c0 0x9336de0 0x5b997588 0x1a236f)
0x5b9975a8 : 0x174dae (0x93c7be0 0x0 0x5b9975d8 0x1f17468)
0x5b9975e8 : 0x17514b (0x95e1f58 0x93b585c 0x5b997628 0x174673)
0x5b997628 : 0x177a6a (0x95e1f50 0x0 0x0 0xf5830000)
0x5b997668 : 0x39a326 (0x95e1f50 0x0 0x0 0x0)
0x5b997688 : 0x1db5de (0x9570120 0x8 0x0 0x2)
0x5b9976d8 : 0x1db806 (0x9570120 0x1 0x5b997708 0x19d6a0)
0x5b997728 : 0x1dd3b8 (0x0 0x4f63c0 0x4601ca0a 0x0)
0x5b997798 : 0x31ea94 (0x0 0x34 0x5b9977ec 0x974b9ec)
0x5b997838 : 0x327009 (0x6c4a804 0xcd67440 0x5b997f08 0x5b997968)
0x5b997998 : 0x1f2c9c (0x5b9979b8 0x2 0x5b9979e8 0x44fe1e)
0x5b9979e8 : 0x1d47aa (0xcd67440 0x5b997df4 0x5b997f08 0xd7dc104)
Backtrace continues...

BSD process name corresponding to current thread: find

Mac OS version:
9F33

Kernel version:
Darwin Kernel Version 9.5.0: Wed Sep 3 11:29:43 PDT 2008; root:xnu-1228.7.58~1/RELEASE_I386
System model name: iMac7,1 (Mac-F42386C8)

 

[oticon6]

I can now confirm that swapping the RAM sticks does not affect the caller address.

 

[TuffLuffJimmy]

This does not belong in the basics! I went cross eyed trying to read that.

 

[oticon6]

This does not belong in the basics! I went cross eyed trying to read that.

Sorry, first post in this particular forum. I thought it would fall under the "and Help" part of the title