Help needed in interpreting panic log from kernel panic error

Question

My G4 iBook has started giving me kernel panic errors, often immediately after starting up. I haven't installed any new software or RAM recently. I've done a clean system install (completely clean - not an archive and install) then downloaded the combo update for 10.4.11. But the kernel panics are still happening from time to time. I've looked at the panic log, but it means nothing to me, so I'm hoping someone can help:
Tue Dec 7 21:53:11 2010
Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x000000005901F81E PC=0x000000000003FFD4
Latest crash info for cpu 0:
Exception state (sv=0x3CFE1280)
PC=0x0003FFD4; MSR=0x00009030; DAR=0x5901F81E; DSISR=0x40000000; LR=0x0003FFBC; R1=0x22073970; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x000E99BC 0x0002BDCC 0x00304E60 0x00304FDC 0x0030309C 0x0030167C
0x003009AC 0x002FCF6C 0x003009AC 0x002B7464 0x002EB314 0x0008B6E8 0x00029234 0x000233F8
0x000ABEAC 0x3D266C74
Proceeding back via exception chain:
Exception state (sv=0x3CFE1280)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x3CF81C80)
PC=0x9000B348; MSR=0x0200F030; DAR=0xE0064000; DSISR=0x42000000; LR=0x9000B29C; R1=0xBFFF9EA0; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x000954F8 0x00095A10 0x00026898 0x000A8204 0x000ABB80
Proceeding back via exception chain:
Exception state (sv=0x3CFE1280)
PC=0x0003FFD4; MSR=0x00009030; DAR=0x5901F81E; DSISR=0x40000000; LR=0x0003FFBC; R1=0x22073970; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x000E99BC 0x0002BDCC 0x00304E60 0x00304FDC 0x0030309C 0x0030167C
0x003009AC 0x002FCF6C 0x003009AC 0x002B7464 0x002EB314 0x0008B6E8 0x00029234 0x000233F8
0x000ABEAC 0x3D266C74
Exception state (sv=0x3CF81C80)
PC=0x9000B348; MSR=0x0200F030; DAR=0xE0064000; DSISR=0x42000000; LR=0x9000B29C; R1=0xBFFF9EA0; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
Message was edited by: Lynn Stephenson

Answer 1

I didn't see anything that would indicate a specific problem. Understanding crash logs isn’t easy and it’s hard (sometimes impossible) to decipher the cause of the problem. Take a look at Apple’s Crash Reporter document at http://developer.apple.com/technotes/tn2004/tn2123.html
Also look at Tutorial: An introduction to reading Mac OS X crash reports
http://www.macfixit.com/article.php?story=20060309075929717
Kernel panics are usually caused by a hardware problem – frequently RAM, a USB device or a Firewire device. What external devices do you have connected?
To eliminate RAM being the problem, Look at this link: *Testing RAM* @ http://guides.macrumors.com/Testing_RAM Then download & use Memtest & Ramber.
Running the Apple Hardware Test in Loop Mode is an excellent troubleshooting step for finding intermittent hardware problems. It is especially useful when troubleshooting intermittent kernel panics. If Loop Mode is supported by the version of the Apple Hardware Test you are using, you run the Extended Test in Loop Mode by pressing Control-L before starting the test. Looping On should appear in the right window. Then click the Extended Test button.The test will run continuously until a problem is found. If a problem is found, the test will cease to loop, indicating the problem it found. If the test fails, be sure to write down the exact message associated with the failure.In some cases, RAM problems did not show up until nearly 40 loops, so give it a good run.
May be a solution on one of these links.
Mac OS X Kernel Panic FAQ
Mac OS X Kernel Panic FAQ
Resolving Kernel Panics
Avoiding and eliminating Kernel panics
12-Step Program to Isolate Freezes and/or Kernel Panics
 Cheers, Tom