DL Burning problem

[MrBurns]

I have burned quite a few DL backups of DVD-9, but the last three discs have all failed repeatedly - right at the start of the burn, creating about 15 coasters in the process.

This happens with good ISO reads from DVDDecrypter and also images created in PgcEdit, but both work fine with single layer media. I am using datawrite DVD+R DL media, and although I note the comments in other postings, I have made many successful back ups with these discs.

 

The last Log was typical and looks like this;

 

I 18:28:17 ImgBurn Version 1.3.0.0 started!

I 18:28:17 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 2)

I 18:28:17 Initialising SPTI...

I 18:28:17 Searching for SCSI / ATAPI devices...

I 18:28:17 Found 1 DVD?RW!

I 18:31:14 Operation Started!

I 18:31:14 Source File: C:\MONTY_PYTHON_THE_HOLY_GRAIL.MDS

I 18:31:14 Source File Sectors: 2,553,536 (MODE1/2048)

I 18:31:14 Source File Size: 5,229,641,728 bytes

I 18:31:14 Source File Volume Identifier: MONTY_PYTHON_THE_HOLY_GRAIL

I 18:31:14 Source File Implementation Identifier: SONY DVD Video

I 18:31:14 Source File UDF Revision: 1.02

I 18:31:14 Destination Device: [1:0:0] HL-DT-ST DVD-RW GCA-4080N 0C35 (D:) (ATA)

I 18:31:14 Destination Media Type: DVD+R DL (Disc ID: CMC MAG-D01-00) (Speeds: 2.4x)

I 18:31:14 Destination Media Sectors: 4,173,824

I 18:31:14 Write Mode: DVD

I 18:31:14 Write Type: DAO

I 18:31:14 Write Speed: MAX

I 18:31:14 Link Size: Auto

I 18:31:14 Test Mode: No

I 18:31:14 BURN-Proof: Enabled

I 18:31:14 Optimal L1 Data Zone Start LBA: 1717632 (VTS_01, PGC: 1, Cell: 62)

I 18:31:14 Optimal L0 Data Zone Capacity: 1,717,632

I 18:31:14 Optimal L0 Data Zone Method: IFO Cell Boundary, 'SPLIP' Flag Not Set

I 18:31:25 Filling Buffer...

I 18:31:25 Writing LeadIn...

W 18:31:25 Failed to Write Sectors 32 - 63 - Write Error

W 18:31:25 Retrying (1 of 20)...

W 18:31:25 Retry Failed - Invalid Address For Write

W 18:31:25 Retrying (2 of 20)...

W 18:31:25 Retry Failed - Invalid Address For Write

W 18:31:25 Retrying (3 of 20)...

W 18:31:25 Retry Failed - Invalid Address For Write

W 18:31:25 Retrying (4 of 20)...

W 18:31:25 Retry Failed - Invalid Address For Write

W 18:31:25 Retrying (5 of 20)...

W 18:31:25 Retry Failed - Invalid Address For Write

W 18:31:25 Retrying (6 of 20)...

W 18:31:25 Retry Failed - Invalid Address For Write

W 18:31:25 Retrying (7 of 20)...

W 18:31:25 Retry Failed - Invalid Address For Write

W 18:31:25 Retrying (8 of 20)...

W 18:31:25 Retry Failed - Invalid Address For Write

W 18:31:25 Retrying (9 of 20)...

W 18:31:25 Retry Failed - Invalid Address For Write

W 18:31:25 Retrying (10 of 20)...

W 18:31:25 Retry Failed - Invalid Address For Write

W 18:31:25 Retrying (11 of 20)...

W 18:31:25 Retry Failed - Invalid Address For Write

W 18:31:25 Retrying (12 of 20)...

W 18:31:25 Retry Failed - Invalid Address For Write

W 18:31:25 Retrying (13 of 20)...

W 18:31:25 Retry Failed - Invalid Address For Write

W 18:31:25 Retrying (14 of 20)...

W 18:31:25 Retry Failed - Invalid Address For Write

W 18:31:25 Retrying (15 of 20)...

W 18:31:25 Retry Failed - Invalid Address For Write

W 18:31:25 Retrying (16 of 20)...

W 18:31:25 Retry Failed - Invalid Address For Write

W 18:31:25 Retrying (17 of 20)...

W 18:31:25 Retry Failed - Invalid Address For Write

W 18:31:25 Retrying (18 of 20)...

W 18:31:25 Retry Failed - Invalid Address For Write

W 18:31:25 Retrying (19 of 20)...

W 18:31:25 Retry Failed - Invalid Address For Write

W 18:31:25 Retrying (20 of 20)...

W 18:31:25 Retry Failed - Invalid Address For Write

W 18:31:27 Retrying (21)...

W 18:31:27 Retry Failed - Invalid Address For Write

E 18:31:29 Failed to Write Sectors 32 - 63 - Write Error

I 18:31:29 Synchronising Cache...

W 18:31:30 Potential 'WaitImmediateIO' Deferred Error - Write Error

W 18:31:33 Potential 'WaitImmediateIO' Deferred Error - Write Error

E 18:31:35 Synchronise Cache Failed! - Reason: No Additional Sense Information

I 18:31:35 Closing Track...

I 18:31:45 Finalising Disc...

W 18:31:46 Potential 'WaitImmediateIO' Deferred Error - Write Error

W 18:31:50 Potential 'WaitImmediateIO' Deferred Error - Write Error

E 18:31:52 Finalise Disc Failed! - Reason: No Additional Sense Information

 

Would appreciate some clues as to whats going on here. Cheers

[cornholio7]

try and get some verbatim discs, CMC are a load of rubbish unfortunately.

you may want to see if theres a newer firmware for your drive too

[polopony]

I am using datawrite DVD+R DL media, and although I note the comments in other postings, I have made many successful back ups with these discs.

 

 

I 18:31:14 Destination Media Type: DVD+R DL (Disc ID: CMC MAG-D01-00) (Speeds: 2.4x)

 

 

Would appreciate some clues as to whats going on here. Cheers

 

like Corn said those discs are the kiss of death,really anything with CMC MAG dye is second or third rate .The ones that were successful try to read them 6 months down the line .Memorex has some marketing genius working for them otherwise how could they sell so much crap media

[Movie Junkie]

I am using datawrite DVD+R DL media, and although I note the comments in other postings, I have made many successful back ups with these discs.

 

I 18:31:14 Destination Media Type: DVD+R DL (Disc ID: CMC MAG-D01-00) (Speeds: 2.4x)

While you may think the backups have been successful you are in for a rude awakening. If you're lucky you may get a few months with those discs. If you're not lucky they may not play right the next time you try to watch them.

[Kenadjian]

It is most definitely media problems my frend.

[Shamus_McFartfinger]

As I?m feeling left out, I thought I?d also say that it?s a media problem.

[lfcrule1972]

I think it could be a media problem too Shamus.....

[spinningwheel]

OK I guess it's a medium problem also.....

[lfcrule1972]

You know what I miss ? Suggesting that people

[Movie Junkie]

You know what I miss ? Suggesting that people

Then I'll say it for you...

[volvofl10]

just thought I'd mention, it could well be a media problem

[Movie Junkie]

On the other had it might be...

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

never mind, it's a media problem.

Edited August 4, 2006 by Movie Junkie

[peirick]

FWIW, I've had this problem with several kinds of media, Verbatim included. The consistent symptom remains that I can always count on getting a successful copy by uninstalling and reinstalling Nero from scratch, which takes about an hour. The first copy after this ceremony is consistently good, as are an indeterminate number of sucessive copies, somtimes zero successive copies. I'm inclined to suspect Nero, but have no solid evidence to suppor that suspicion. On the other hand Nero successfully burns CDs even after it stops being able to burn DVDs.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

never mind, it's a media problem.

[spinningwheel]

FWIW, I've had this problem with several kinds of media, Verbatim included. The consistent symptom remains that I can always count on getting a successful copy by uninstalling and reinstalling Nero from scratch, which takes about an hour. The first copy after this ceremony is consistently good, as are an indeterminate number of sucessive copies, somtimes zero successive copies. I'm inclined to suspect Nero, but have no solid evidence to suppor that suspicion. On the other hand Nero successfully burns CDs even after it stops being able to burn DVDs.

 

 

Sindce your problem in this thread is with NERO, the best way to handle it is to contact their customer service since you paid for their help whan you bought the program.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

never mind, it's a media problem.

[MrBurns]

Thanks to all who took the trouble to post a reply.

Finally gave in, in spite of exteme doubts, and bought a pack of Verbatim discs.

Guess what......perfect burn first time!

 

Cheers

[Movie Junkie]

Thanks to all who took the trouble to post a reply.

Finally gave in, in spite of exteme doubts, and bought a pack of Verbatim discs.

Guess what......perfect burn first time!

 

Cheers

I'm glad to know that your problem has been solved. Using top of the line media is the only way to go.

[volvofl10]

Thanks to all who took the trouble to post a reply.

Finally gave in, in spite of exteme doubts, and bought a pack of Verbatim discs.

Guess what......perfect burn first time!

 

Cheers

 

Glad you got there in the end , try and stick to verbatim media for any Dual layer stuff, and avoid -R DL media as well

 

it was more a case of being lucky with the datawrite ones you used previously. sadly they haven't got the hang of consistency yet

[Kenadjian]

Thanks to all who took the trouble to post a reply.

Finally gave in, in spite of exteme doubts, and bought a pack of Verbatim discs.

Guess what......perfect burn first time!

 

Cheers

There should have been no doubts at all, just about every member said the same thing, well done on taking the advice, unlike some others that keep insisting that it's not a media problem.

[blutach]

@kenadjian

 

You mean blokes that say "I know my media, setup and burner are perfect"? I saw that somewhere before. Hmmmmmm....lemme see if I can remember.

 

Regards

[Kenadjian]

[Mohawk3]

Hello. I have been reading several posts on these forums and I have not really been able to find my dual layer burning issue solution yet. I have attempted to backup the film Brick about 6 times on DL media (3 times on MKM 001 and 3 times on Ritek D01) . There have been horrible issues at the layer break with each burn. I never had a problem until I upgraded to ImgBurn 2.0.

 

I believe it is Blutach's guide on burning DL media that I follow normally. Before 2.0, I would rip the disk with DVDFABDecrypter, then create the ISO with PGC edit. Often times I would not directly burn from PGC edit because my burns appeared to be better after restarting the computer and then burning the created ISO with ImgBurn. My burns were pretty good this way, even at 8x.

 

My system is Windows XP Pro machine with a Benq 1640 (firmware BSQB, which has been good for me), Athlon64 socket 754 3700, 1 gig of ram, and a Benq 1620 (used for ripping). I am running the newest PGC edit as well.

 

I also turned off the 32k padding after three coasters when reading that from a post.

 

With this film , I tried a couple ways to burn the iso.

I tried creating it from the build portion of ImgBurn and then burning the ISO by selecting the MDS file (burn was at 2.4X) - This turned out horrific.

 

I also tried having PGC edit call up ImgBurn and have the burn (2.4X) go that way. The first scan is that bad burn and the log before it goes with that bad burn.

 

The other scan is of a DL burn that went well at 8x before the upgrade to 2.0 (it was still an ImgBurn creation)

 

Other than the upgrade to the newest PGCedit and ImgBurn, I can't think of anything different in my computer setup. Please let me know what other info I need to provide to see if my problem can be solved. I have never used six discs and had them all be failures.

 

Thank you for any help that you can provide.

 

 

I 09:11:06 ImgBurn Version 2.0.0.0 started!

I 09:11:06 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2)

I 09:11:07 Initialising SPTI...

I 09:11:07 Searching for SCSI / ATAPI devices...

I 09:11:07 Found 2 DVD?RWs!

I 09:11:07 Operation Started!

I 09:11:07 Source File: F:\Video TS\Brick.iso

I 09:11:07 Source File Sectors: 3,916,460 (MODE1/2048)

I 09:11:07 Source File Size: 8,020,910,080 bytes

I 09:11:07 Source File Volume Identifier: BRICK

I 09:11:07 Source File Application Identifier: MKISOFS ISO 9660/HFS FILESYSTEM BUILDER & CDRECORD CD-R/DVD CREATOR © 1993 E.YOUNGDALE © 1997 J.PEARSON/J.SCHILLING

I 09:11:07 Source File Implementation Identifier: mkisofs

I 09:11:07 Source File File System(s): ISO9660, UDF (1.02)

I 09:11:07 Destination Device: [1:0:0] BENQ DVD DD DW1640 BSQB (H:) (ATA)

I 09:11:07 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2.4x, 4x, 8x)

I 09:11:07 Destination Media Sectors: 4,173,824

I 09:11:07 Write Mode: DVD

I 09:11:07 Write Type: DAO

I 09:11:07 Write Speed: 2.4x

I 09:11:07 Link Size: Auto

I 09:11:07 Test Mode: No

I 09:11:07 BURN-Proof: Enabled

I 09:11:08 User Specified L0 Data Zone Capacity: 1,979,472

I 09:11:08 Filling Buffer...

I 09:11:08 Writing LeadIn...

I 09:11:21 Writing Image...

I 09:11:21 Writing Layer 0... (LBA: 0 - 1979471)

I 09:32:28 Writing Layer 1... (LBA: 1979472 - 3916459)

I 09:53:19 Synchronising Cache...

I 09:53:20 Closing Track...

I 09:53:26 Finalising Disc...

I 09:55:23 Image MD5: 85b73f5c80b200c368a1f9e9233c60da

I 09:55:29 Operation Successfully Completed! - Duration: 00:44:16

I 09:55:29 Average Write Rate: 3,112 KB/s (2.2x) - Maximum Write Rate: 3,360 KB/s (2.4x)

 

 

[cornholio7]

have you tried building direct to disc from the files?

i have burned lots this way and had no coasters as yet , i never did try using pgc edit for dual layer so maybe blutach will be along to help you with that bit

[Mohawk3]

have you tried building direct to disc from the files?

i have burned lots this way and had no coasters as yet , i never did try using pgc edit for dual layer so maybe blutach will be along to help you with that bit

 

 

The burn before that last fail was made using the build feature. I think both of these scans may have been from the build feature.

 

I know that Ritek sucks, but I got them for a dollar a disc, so I figured I could live with a few fails. It is just strange to me that I am having fails on Verbatim discs when most of my burns in the past have been pretty good.

 

 

[cornholio7]

i am using BSRB and BSOB before that, both gave great results with verbatim.

i know you mentioned you used build mode to make an iso but did you use build direct to disc?

[Mohawk3]

i am using BSRB and BSOB before that, both gave great results with verbatim.

i know you mentioned you used build mode to make an iso but did you use build direct to disc?

 

I am sorry that I did not understand. I don't really know what that mode is. Is there a guide to that in the forums? If that worked for you, it is something that I should check out.