Jump to content

Lots of failed discs, getting fed up!


Tides

Recommended Posts

I seem to get this a hell of a lot and I am making coasters like no ones business. I used to have a fairly old drive in my desktop and I never made a coaster and now I have my laptop and it burns coasters like no ones business. It seems to be pretty crazy and unpredictable, but i think I this is right. If the L0 load zone fails to set it will fail about 20-30 percent into the burn and if I go cancel when it fails and go to burn it again it will not fail the load zone, but will still fail. If the load zone does not fail the first time I am pretty sure the disc will burn just fine. Why do some burn and others fail? Here are my 2 logs:

 

Log 1:

 

I 09:05:02 ImgBurn Version 2.5.0.0 started!

I 09:05:02 Microsoft Windows Vista Home Premium x64 Edition (6.0, Build 6002 : Service Pack 2)

I 09:05:02 Total Physical Memory: 4,192,556 KB - Available: 2,683,996 KB

W 09:05:02 SPTD can have a detrimental effect on drive performance.

I 09:05:02 Initialising SPTI...

I 09:05:02 Searching for SCSI / ATAPI devices...

I 09:05:03 Found 1 DVD

Link to comment
Share on other sites

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

I 09:05:39 Write Speed: 2.4x

Try burning at 4x to see if you get better results. You might also want to try a lens cleaning disc on your burner, but laptop burners in general are rubbish, especially for burning dual-layer media.

Link to comment
Share on other sites

Thanks for the fast replies! I am going to try writing at 4x now and I am also looking at this external burner. What do you guys think?

 

Samsung SE-S084C 8x Slim External DVD-Writer, USB 2.0, Black I can grab it for 70 bucks CAD.

 

EDIT: The 4x burning seems to be working much better! I just burned that image fine. I will go out and buy some more discs now and try burning some others that failed.

 

Also why would this occur: E 09:06:30 Set L0 Data Zone Capacity Failed! - Reason: Program Memory Area Update Failure

Edited by Tides
Link to comment
Share on other sites

So if this ends up being an anomaly and games still fail here and there even at 4x you think I should get an enclosure and but a desktop drive? I guess I could do it, but thats just more and more cash :(

 

Although wasting all these discs is the biggest waste of cash so...

Link to comment
Share on other sites

I found a cheap option and it seems to be working out so far; I got an LG GE20LU10 external for half price. I do have a question however, I noticed that when I burn everything goes fine, but I get this every time which I have never seen before:

 

W 05:46:38 L0 Data Zone Capacity Miscompare!

W 05:46:38 Wanted: 1913760, Got: 2086912

 

The images burn successfully and work just fine I just want to know what it means and should I be worried about the discs not being a 1:1 copy? Here is the full log of a disc just burned now:

 

I 05:46:06 ImgBurn Version 2.5.0.0 started!

I 05:46:06 Microsoft Windows Vista Home Premium x64 Edition (6.0, Build 6002 : Service Pack 2)

I 05:46:06 Total Physical Memory: 4,192,556 KB - Available: 2,690,264 KB

W 05:46:06 SPTD can have a detrimental effect on drive performance.

I 05:46:06 Initialising SPTI...

I 05:46:06 Searching for SCSI / ATAPI devices...

I 05:46:06 Found 2 DVD

Edited by Tides
Link to comment
Share on other sites

Some LG drives don't work how every other drive on the planet does.

 

If I set the LB to a certain position and query the drive for the LB position, I expect the drive to report the value I just told it to use.... some LG's don't and just report the default one.

 

The reason for this is that most drives will write whatever needs to be written to the disc to move the LB there and then... so you get a pause between me setting it and me then being able to query its current position. If you look at the times in the log you can see that all the LB stuff has exactly the same timestamp - meaning the drive hasn't done anything (and therefore probably wants to do it later on!).

 

So anyway, that's why you get the mismatch entry in the log but the disc info AFTER the burn should show the LB in the correct place.

 

To sum up, it's nothing to worry about :)

Link to comment
Share on other sites

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.