Burn Error on Data DVD

[Bluefusionx]

I am getting a burn error and I have no idea why. Here is the output when I push advanced:

 

Sense: 02  ASC: 04  ASCQ: 07 (Command 51)
-------------------------------------------------------
Px.dll: 2.7.27.500
pxdrv.dll: 1.1.67.0
PxMas.dll: 2.7.27.500
PxSFS.DLL: 2.7.27.500
PxWave.dll: 2.7.27.500
PXWMA.dll: 1.0.0.3

 

It happens when I attempt to burn a project with 4 AVI files, 2 inf files, 1 exe file, and 1 folder with 2 images.

 

The AVI files are ranging from 1200-1600 MB, resulting in 4.1GB. I burned successfully 4 DVDs of the same type of DVD with just different AVI files. Any help is appreciated.

[Bluefusionx]

I think I focused to problem further.

 

It says I have I/O errors when I try to copy it anywhere on the hard drive. How can I fix an I/O error?

[gi7omy]

That sounds very like a faulty file when it won't copy. I'm afraid it may be fubar

[gi7omy]

Do you get the same result if you make an image file first and open that with Disc Copier?

[Bluefusionx]

How do make an image file? I can't find it. . .

[gi7omy]

When you go to burn, select the hard drive and burn to file as the target

[Bluefusionx]

It says the same thing when I do that. I am very suprised, I did not think it would do that. Here is the output:

 

Sense: 00  ASC: 00  ASCQ: 00 (Command 00)
-------------------------------------------------------
Px.dll: 2.7.27.500
pxdrv.dll: 1.1.67.0
PxMas.dll: 2.7.27.500
PxSFS.DLL: 2.7.27.500
PxWave.dll: 2.7.27.500
PXWMA.dll: 1.0.0.3

[Bluefusionx]

I believe I have pinpointed the problem.

 

The second AVI file will not burn but all of the others will. I did a test by removing one by one each file and burning an image until one worked.

 

What can cause one file not to burn correctly? It's not being used currently, and it plays perfectly.

 

Please help!

[gi7omy]

Welcome to the whacky world of computing

 

Strange things do happen for no apparent reason but I suspect in your case there is a glitch somewhere in the offending file that is causing the program to spit it out with an error message.

 

It could be something as simple as a bad frame or two, data corruption or anything and is probably so small that you visually don't notice it on playback. You could check maybe on how long into the sequence before it happens - and then check at the same time point, but blink and you'd miss it. Computers aren't as forgiving as the human eye in small glitches