Currently Being ModeratedMay 10, 2011 2:50 PM (in response to PIT56)
Kernel panics are more usually caused by hardware issues.
What screensaver left over from Tiger are you using?
What is a Kernel Panic?
More details here:
Useful article on how to avoid and eliminate kernel panics here:20" 2.1GHz iSight iMac G5,, Mac OS X (10.5.8), iLife 9 but iMovie 6, QTPro 7.6.9, Safari 5.0.5
Currently Being ModeratedMay 11, 2011 2:25 AM (in response to Klaus1)
Thanks for the suggestions Klaus1, but the chances that this is a hardware problem are almost zero. The Mac was fine pre-Leopard and not after installation. However, just to be sure I checked memory with Rember and did all the other suggested hardware tests - all results came back fine.
As for the screensaver, it's not a leftover from Tiger, it's a standard Leopard one. And it's not just one of the savers that causes the KPs, it's all of them. So I assume the problem must have something to do with the screensaver engine. (In the old days we'd put this down to a simple conflict).
In the past few months I have read countless internet articles and threads on Kernel Panics but I've yet to see one ascribed to a screensaver. That said, the evidence is compelling. Screensaver on, Kernel Panics. Screensaver off, no Kernel Panics. You don't need to be Sherlock Holmes to see the link.
The whole experience has been a pain, but luckily being without a screensaver isn't the end of the world and I will happily live without one if it means avoiding multiple daily crashes.
Currently Being ModeratedMay 11, 2011 4:10 AM (in response to roam)
The screensaver isn't a downloaded one. As I mentioned before, the KPs aren't choosy - they'll happen whichever of the Leopard screensavers is running. Which is why I suspect the problem is something to do with the screensaver engine. This would also explain why I sometimes get KPs when I'm away from my desk. The screensaver must be kicking in and initiating a crash.
As for the crash log, there's no mention of screensavers in any of them.
Currently Being ModeratedMay 11, 2011 6:19 AM (in response to roam)
Odd indeed. I've owned many Macs over the years and have never experienced anything like this.
The good news is I've just dug out my original install disks, so I shall try running the Hardware Test to see if anything's amiss with the video card.
Thanks for the suggestion. Much appreciated.
Currently Being ModeratedMay 11, 2011 8:59 AM (in response to roam)
As you suggested, I ran Hardware Test, but it all came up clean. The problem HAS to be with the screensaver engine. I think I'll trash the screensaver plist and see what happens.
Currently Being ModeratedSep 23, 2011 5:50 AM (in response to PIT56)
I just saw your post while trying to track down kernel panic on my Power Mac G4 OS 10.5.8 (recently updated). The computer would run fine until I walked away and it went to sleep. I had screen saver set to never. I would get the KP when I woke the computer. I set the screensaver to come on now before sleep and no more KP's I also went through the various hardware tests and found nothing. Although when I did get a KP the log seemed to indicate that it was Logitech control center that may be the culprit. I also set the computer to no sleep, no saver and there are no panics. I would have to agree that something about the sleep/saver interface is causing the problem and it only affects 10.5.8 on my machine. Other OS X's don't seem to have the problem. Any luck tracking this down? plist, etc
Currently Being ModeratedFeb 4, 2013 2:08 PM (in response to sruben)
I have the same problem on my PPC running 10.5.8.
Have had two KPs in the last week, both times when I left the computer running for a while without using it, about 30 minutes each time.
I have screensaver on but sleep was set to never.
Any advice gratefully received.
Mon Feb 4 21:53:11 2013
Unresolved kernel trap(cpu 1): 0x400 - Inst access DAR=0x000000001C823000 PC=0x000000001C823000
Latest crash info for cpu 1:
Exception state (sv=0x76c95000)
PC=0x1C823000; MSR=0x40009030; DAR=0x1C823000; DSISR=0x40000000; LR=0x1C823000; R1=0x68E6BE80; XCP=0x00000010 (0x400 - Inst access)
backtrace terminated - unaligned frame address: 0x68E6BDFC
Proceeding back via exception chain:
Exception state (sv=0x76c95000)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x68fcac80)
PC=0x00098444; MSR=0x0000F030; DAR=0x1C823000; DSISR=0x40000000; LR=0x00091DF0; R1=0xF007FAA0; XCP=0x0000000C (0x300 - Data access)
BSD process name corresponding to current thread: ReportCrash
Mac OS version:
Darwin Kernel Version 9.8.0: Wed Jul 15 16:57:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_PPC
System model name: PowerMac11,2
System uptime in nanoseconds: 37752540910764
com.apple.driver.Apple02DBDMAAudio 2.5.8f1 - last unloaded 3554503227
com.apple.driver.AppleBluetoothMultitouch 32.7 - last loaded 1171820437
Currently Being ModeratedFeb 11, 2013 10:01 AM (in response to zombi3g)
Thanks for your advice, I tried that, or at least I unstalled logmein, but I got another one yesterday (KP), a few infact.
In the end the machine refused to boot again, so I replaced the HD, still nothing.
So I removed the RAM, some of which was recently added. One pair made it crash on startup, while the others worked fine.
Strange thing is though, the orginal HD will not now work, tried hooking it up to an external reader, and while it was spinning it wouldn't show up on the desktop.
To be honest, I'm hoping it was one or the either but find it a bit strange that both were a problem.
I got the RAM from 'Mr Memory', firstly ordered 8gb (2x2) but only 4gb would show.
Sent them back, got the new set to work but started getting the panics shortly after.
Probably gonna just stick with the RAM I have in it now and look for my money back for the others.
Also ordered a new HD and will do a fresh install when it arrives.
Again I'd be grateful for any advice.
Currently Being ModeratedFeb 11, 2013 10:18 AM (in response to Klaus1)
Thanks, appreciate the reply.
The RAM I bought does have a lifetime warranty but I cannot vouch for its quality.
Reason I went for this is simply because it's what was in the machine, just wanted to add to it.
What do you think about the HD failing too then? Just chance?