What do you see in the file /Library/Logs/panic.log? Especially if you find anything labeled "kernel loadable modules in backtrace...", the following lines can show you what part of the system caused the panic. The suggestion of bad RAM is possible (see the rant in my previous message today), though I've also seen bad hard drives cause panics, though it's quite rare, compared to other causes. So, let us know if you find anything helpful in there - or post some of the log to the list. The most important lines are anything starting "com." in the kernel loadable modules section, and the first line which will list a rather vague cause (usually "data access", in my experience). You can cut out all the register values (anything 0x...), because those aren't usually useful for finding the root cause. alexandre <mac.k at a2k.ch> writes: > last month, my hard drive crashed. i replaced the original 80gb/4'800 > with a 100gb/7200. symptoms prior to the death of the drive (AND > prior to smart-reporter reporting anything) were strange noises > coming from the drive, the whole computer would lock up and the hd > would spin into overdrive. force-quit was not possible and re-booting > was the only option. > > > so i switched the drive and everything has been well until > last > week. everyday now (4 days in a row) i get a kernel panic. > > when i open console, i read this: "SuperLunchTray crashdump[233]: > wrapper crashed"