Can Anyone help with Kernel Panic!?!?!

Question

I've been having loads of problems with leopard since install. I have updated to 10.5.2 but the same problem persists i.e. whole system crashes: grey screen comes down and i have to restart. there seems to be no logic to it (it sometimes crashes when just itunes/DVDplayer is running).
I'm not very tech-savvy, but it seems to be a kernel problem and/or a problem with conflict of commands.
Does anyone know what i can do about it? This is becoming quite unnerving.
Cheers
Here is the Problem Details:
Sun Mar 9 16:40:48 2008
Unresolved kernel trap(cpu 1): 0x700 - Program DAR=0x0000000000445858 PC=0x000000000008F504
Latest crash info for cpu 1:
Exception state (sv=0x89f61000)
PC=0x0008F504; MSR=0x00089030; DAR=0x00445858; DSISR=0x40000000; LR=0x0002C1B4; R1=0x616CFDC0; XCP=0x0000001C (0x700 - Program)
Backtrace:
0x00000000 0x0002C10C 0x00024C88 0x000B2C4C 0x6145676F
backtrace terminated - frame not mapped or invalid: 0xF0AA87C0
Proceeding back via exception chain:
Exception state (sv=0x89f61000)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x5b661500)
PC=0x923A0978; MSR=0x0200F030; DAR=0x5C82A590; DSISR=0x42000000; LR=0x923A78A0; R1=0xF0AA87C0; XCP=0x00000030 (0xC00 - System call)
BSD process name corresponding to current thread: EyeTV
Mac OS version:
9C31
Kernel version:
Darwin Kernel Version 9.2.0: Tue Feb 5 16:15:19 PST 2008; root:xnu-1228.3.13~1/RELEASE_PPC
System model name: PowerMac11,2
Unresolved kernel trap(cpu 0): 0x400 - Inst access DAR=0x000000001B356000 PC=0x0000000000000810
Latest crash info for cpu 0:
Exception state (sv=0x6bbf6a00)
PC=0x00000810; MSR=0x40009030; DAR=0x1B356000; DSISR=0x40000000; LR=0x0010F00C; R1=0x5B66F400; XCP=0x00000010 (0x400 - Inst access)
Backtrace:
0x0010DAE8 0x00110514 0x0025E2E8 0x00250C60 0x00250E64 0x002621BC
0x00109604 0x00109A54 0x000F1B94 0x000F74F4 0x000F78A0 0x00309C3C 0x000B2AC8 0x5DFF8DF4
backtrace terminated - frame not mapped or invalid: 0xBFFFE3F0
Proceeding back via exception chain:
Exception state (sv=0x6bbf6a00)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x89f5ec80)
PC=0x923A1600; MSR=0x0000F030; DAR=0x1B356000; DSISR=0x42000000; LR=0x923EA388; R1=0xBFFFE3F0; XCP=0x00000030 (0xC00 - System call)
BSD process name corresponding to current thread: Opera
panic(cpu 1 caller 0xFFFF0004): 0x700 - Program
Latest stack backtrace for cpu 1:
Backtrace:
0x0009B2F8 0x0009BC9C 0x00029DC4 0x000AEF10 0x000B28F8
Proceeding back via exception chain:
Exception state (sv=0x89f61000)
PC=0x0008F504; MSR=0x00089030; DAR=0x00445858; DSISR=0x40000000; LR=0x0002C1B4; R1=0x616CFDC0; XCP=0x0000001C (0x700 - Program)
Backtrace:
0x00000000 0x0002C10C 0x00024C88 0x000B2C4C 0x6145676F
backtrace

Answer 1

Kernel panics usually occur as the result of a conflict with external hardware or bad .kext files that are driving those pieces of hardware. EyeTV is implicated in one of the threads. Check for firmware or software updates. Google "EyeTV kernel panic" and you'll find several hits. Didn't look like there was a solution as the company that is making an extension to the OS thinks it is an OS problem.