IDVD 4.0.1 Repeatedly Crashing at Burning Stage--Kern Protection?

Question

Many of us seem to have a similar problem with 4.0.1, and mine has popped up since the latest Apple Tiger update. I go through the entire process of setting up the dvd through iMovie and iDVD, it goes through menus, encoding and multiplexing, but about a minute into the burning stage it crashes. I have done various things to work around this and despite following some of the suggested steps in this forum, I keep crashing, having lost 7 fresh dvds and countless hours waiting for the project to get to this stage.
I'm fairly fluent in iDVD and know to keep other apps turned off, to have enough hard drive space and to basically let it do it's thing overnight. There's obviously messed up in the iDVD software.
How to fix?
Below is some of the crash log stuff; maybe someone has an easy answer. Thanks for your help!
dt
Command: iDVD
Path: /Applications/iDVD.app/Contents/MacOS/iDVD
Parent: WindowServer [65]
Version: 4.0.1 (4.0.1)
Build Version: 1
Project Name: iDVD_App
Source Version: 4920000
PID: 219
Thread: 14
Exception: EXCBADACCESS (0x0001)
Codes: KERNPROTECTIONFAILURE (0x0002) at 0x00000020
Thread 14 crashed with PPC Thread State 64:
srr0: 0x00000000fffeff18 srr1: 0x000000000200f030 vrsave: 0x0000000000000000
cr: 0x44000244 xer: 0x0000000000000006 lr: 0x00000000928b7ea8 ctr: 0x0000000000000010
r0: 0x0000000000000001 r1: 0x00000000f080f6e0 r2: 0x000000000580a630 r3: 0x000000000ace39c0
r4: 0x0000000090a28918 r5: 0x00000000000003e8 r6: 0x00000000ffffffff r7: 0x0000000000000001
r8: 0x000000000acf7541 r9: 0x0000000005809000 r10: 0x0000000000000001 r11: 0x000000006f5c8918
r12: 0x0000000000000000 r13: 0x00000000000000d6 r14: 0x0000000000000000 r15: 0x0000000000000000
r16: 0x00000000273c09e2 r17: 0x0000000000000000 r18: 0x0000000000345fd0 r19: 0x0000000000346390
r20: 0x0000000000346394 r21: 0x0000000000346398 r22: 0x0000000000348048 r23: 0x00000000000003e8
r24: 0x0000000000217ae9 r25: 0x00000000000003e8 r26: 0x0000000000000001 r27: 0x0000000000000040
r28: 0x000000000772f2e0 r29: 0x000000000ace39c0 r30: 0x0000000010620000 r31: 0x00000000928b7ca4

Answer 1

fsck -yf will work for either Panther or Tiger.
FSCK - File System Check
To start up in single-user mode
1. Restart the computer.
2. Immediately after the startup sound, press and hold both the Command (Apple) and "s" keys on your keyboard. The computer will display a series of text messages, at which time you may release these keys.
When the computer has started up, it will display a command line prompt (#). The computer is now in single-user mode.
How to Run the File System Check from the Command Line
Once you have reached a command line, follow these steps to use fsck:
1. At the prompt, type: fsck -fy (NOTE, there is a space between the k and the “-”)
The fsck utility will go through five "phases" and then return information about the disk's utilization and fragmentation. Once the check is finished, if no issue is found, you should see "** The volume <name of volume> appears to be OK."
If fsck alters, repairs, or fixes anything, it will display the message:
**** FILE SYSTEM WAS MODIFIED ***
IMPORTANT: If this message appears, repeat the "fsck -fy" command until this message no longer appears. It is not unusual for your computer to require several "passes" of fsck, because first-pass repairs may uncover additional errors. Run it until you get two consecutive times with an "OK" result.
3. When fsck reports that no problems were found, type: reboot
4. Press Return.