Jump to content
Sign in to follow this  
Piras

Disc freezes at layer-break point.

Recommended Posts

Hi there,

 

Used ImgBurn for the first time today and ended up with a DL DVD that freezes at the layer-break point.

Any thoughts?

 

Here's my log:

 

I 13:06:56 ImgBurn Version 2.3.2.0 started!

I 13:06:56 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 2)

I 13:06:56 Total Physical Memory: 1.047.852 KB - Available: 652.636 KB

I 13:06:56 Initialising SPTI...

I 13:06:56 Searching for SCSI / ATAPI devices...

I 13:06:56 Found 1 DVD-ROM and 1 DVD±RW!

I 13:07:26 Operation Started!

I 13:07:26 Building Image Tree...

I 13:07:28 Checking Directory Depth...

I 13:07:28 Calculating Totals...

I 13:07:28 Preparing Image...

E 13:08:38 Operation Aborted! - Duration: 00:01:11

I 13:12:36 Operation Started!

I 13:12:36 Building Image Tree...

I 13:12:38 Checking Directory Depth...

I 13:12:38 Calculating Totals...

I 13:12:38 Preparing Image...

I 13:13:35 Using Layer Break LBA: 1445536 -> 2078320 (VTS_01, PGC: 1, Chapter: 10, Cell: 10, Vob/Cell ID: 1/10, Time: 00:40:35, SPLIP: Yes -> No)

I 13:13:35 Checking Path Length...

I 13:13:35 Image Size: 8.512.798.720 bytes

I 13:13:35 Image Sectors: 4.156.640

I 13:13:42 Operation Successfully Completed! - Duration: 00:01:05

I 13:13:42 Operation Started!

I 13:13:42 Source File: -==/\/[bUILD IMAGE]\/\==-

I 13:13:42 Source File Sectors: 4.156.640 (MODE1/2048)

I 13:13:42 Source File Size: 8.512.798.720 bytes

I 13:13:42 Source File Volume Identifier: David Bowie - Paris 2002-07-01 Proshot DVD (PAL)

I 13:13:42 Source File Application Identifier: IMGBURN V2.3.2.0 - THE ULTIMATE IMAGE BURNER!

I 13:13:42 Source File Implementation Identifier: ImgBurn

I 13:13:42 Source File File System(s): ISO9660; UDF (1.02)

I 13:13:42 Destination Device: [0:1:0] AOPEN DUW1608/ARR A080 (F:) (ATA)

I 13:13:42 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2,4x)

I 13:13:42 Destination Media Sectors: 4.173.824

I 13:13:42 Write Mode: DVD

I 13:13:42 Write Type: DAO

I 13:13:42 Write Speed: 2,4x

I 13:13:42 Link Size: Auto

I 13:13:42 Test Mode: No

I 13:13:42 BURN-Proof: Enabled

I 13:13:42 Optimal L0 Data Zone Capacity: 2.078.320

I 13:13:42 Optimal L0 Data Zone Method: IFO Cell Boundary

I 13:13:56 Filling Buffer... (40 MB)

I 13:13:57 Writing LeadIn...

I 13:13:59 Writing Image... (LBA: 0 - 4156639)

I 13:13:59 Writing Layer 0... (LBA: 0 - 2078319)

I 13:35:04 Writing Layer 1... (LBA: 2078320 - 4156639)

I 13:56:15 Synchronising Cache...

I 13:56:19 Closing Track...

I 13:56:20 Finalising Disc...

I 13:57:33 Image MD5: 0ba6440e1374dca7cf917329492d5534

I 13:57:35 Operation Successfully Completed! - Duration: 00:43:51

I 13:57:35 Average Write Rate: 3.278 KB/s (2.4x) - Maximum Write Rate: 3.492 KB/s (2.5x)

I 13:57:35 Cycling Tray before Verify...

W 13:57:43 Waiting for device to become ready...

I 13:58:03 Device Ready!

I 13:58:03 Operation Started!

I 13:58:03 Source Device: [0:1:0] AOPEN DUW1608/ARR A080 (F:) (ATA)

I 13:58:03 Source Media Type: DVD-ROM (Book Type: DVD-ROM) (Speeds: 16x)

I 13:58:03 Image File: -==/\/[bUILD IMAGE]\/\==-

I 13:58:03 Image File Sectors: 4.156.640 (MODE1/2048)

I 13:58:03 Image File Size: 8.512.798.720 bytes

I 13:58:03 Image File Volume Identifier: David Bowie - Paris 2002-07-01 Proshot DVD (PAL)

I 13:58:03 Image File Application Identifier: IMGBURN V2.3.2.0 - THE ULTIMATE IMAGE BURNER!

I 13:58:03 Image File Implementation Identifier: ImgBurn

I 13:58:03 Image File File System(s): ISO9660; UDF (1.02)

I 13:58:04 Verifying Sectors... (LBA: 0 - 4156639)

I 13:58:04 Verifying Layer 0... (LBA: 0 - 2078319)

I 14:03:46 Verifying Layer 1... (LBA: 2078320 - 4156639)

W 14:04:02 Miscompare at LBA: 2078320, Offset: 2, File: VIDEO_TS\VTS_01_3.VOB

W 14:04:02 Device: 0x00

W 14:04:02 Image File: 0x01

W 14:04:02 Total Errors in Sector: 222

I 14:04:02 Verifying Sectors...

W 14:04:05 Miscompare at LBA: 2078321, Offset: 2, File: VIDEO_TS\VTS_01_3.VOB

W 14:04:05 Device: 0x00

W 14:04:05 Image File: 0x01

W 14:04:05 Total Errors in Sector: 1.955

I 14:04:05 Verifying Sectors...

W 14:04:06 Miscompare at LBA: 2078322, Offset: 2, File: VIDEO_TS\VTS_01_3.VOB

W 14:04:06 Device: 0x00

W 14:04:06 Image File: 0x01

W 14:04:06 Total Errors in Sector: 1.982

I 14:04:06 Verifying Sectors...

W 14:04:08 Miscompare at LBA: 2078323, Offset: 2, File: VIDEO_TS\VTS_01_3.VOB

W 14:04:08 Device: 0x00

W 14:04:08 Image File: 0x01

W 14:04:08 Total Errors in Sector: 2.005

I 14:04:08 Verifying Sectors...

W 14:04:08 Miscompare at LBA: 2078324, Offset: 2, File: VIDEO_TS\VTS_01_3.VOB

W 14:04:08 Device: 0x00

W 14:04:08 Image File: 0x01

W 14:04:08 Total Errors in Sector: 1.965

I 14:04:08 Verifying Sectors...

W 14:04:09 Miscompare at LBA: 2078325, Offset: 2, File: VIDEO_TS\VTS_01_3.VOB

W 14:04:09 Device: 0x00

W 14:04:09 Image File: 0x01

W 14:04:09 Total Errors in Sector: 2.040

I 14:04:09 Verifying Sectors...

W 14:04:10 Miscompare at LBA: 2078326, Offset: 2, File: VIDEO_TS\VTS_01_3.VOB

W 14:04:10 Device: 0x00

W 14:04:10 Image File: 0x01

W 14:04:10 Total Errors in Sector: 2.018

I 14:04:10 Verifying Sectors...

W 14:04:10 Miscompare at LBA: 2078327, Offset: 2, File: VIDEO_TS\VTS_01_3.VOB

W 14:04:10 Device: 0x00

W 14:04:10 Image File: 0x01

W 14:04:10 Total Errors in Sector: 1.963

I 14:04:10 Verifying Sectors...

W 14:04:11 Miscompare at LBA: 2078328, Offset: 2, File: VIDEO_TS\VTS_01_3.VOB

W 14:04:11 Device: 0x00

W 14:04:11 Image File: 0x01

W 14:04:11 Total Errors in Sector: 2.015

I 14:04:11 Verifying Sectors...

E 14:04:22 Miscompare at LBA: 2078329, Offset: 2, File: VIDEO_TS\VTS_01_3.VOB

E 14:04:22 Device: 0x00

E 14:04:22 Image File: 0x01

E 14:04:22 Total Errors in Sector: 1.992

E 14:04:22 Failed to Verify Sectors!

E 14:04:22 Operation Failed! - Duration: 00:06:18

I 14:04:22 Average Verify Rate: 11.295 KB/s (8.2x) - Maximum Verify Rate: 18.953 KB/s (13.7x)

I 14:05:37 Close Request Acknowledged

I 14:05:37 Closing Down...

I 14:05:37 Shutting down SPTI...

I 14:05:37 ImgBurn closed!

Share this post


Link to post
Share on other sites

Thanks,just execute that file and let it do it's thing?

 

Sorry if I sound daft but: What are duff burns?

Share this post


Link to post
Share on other sites

Can you verify the disc in the 'DVD-ROM' you appear to have rather than the writer? (hopefully it's not a virtual drive!)

 

To be honest I'd just replace the AOPEN with something else and hopefully that'll work ok.

Share this post


Link to post
Share on other sites
Can you verify the disc in the 'DVD-ROM' you appear to have rather than the writer? (hopefully it's not a virtual drive!)

 

To be honest I'd just replace the AOPEN with something else and hopefully that'll work ok.

 

It's not a virtual drive so yes:I could. How exactly do I do that?

 

Replacing and hoping it will work doesn't sound very cool to me...

Share this post


Link to post
Share on other sites

You switch to Verify mode, select the dvdrom (after putting the burnt disc in it), select the image you just burnt and then click the big 'Verify' button.

 

It's impossible to say for sure (100%) that replacing the drive will fix all your problems, all you can do is try. Borrow a drive from someone if you can... put yours in another pc or try your discs in another drive. Only by trial and error will you get to the bottom of it.

Share this post


Link to post
Share on other sites

That can happen if you ever click a link to the forum in google. It seems to index in that way and when you click it, that setting gets stored in your cookie.

Share this post


Link to post
Share on other sites

I am going to blame it on Donta, I am pretty sure he's cursed my mouse trying to get me to do a clean install of the OS

Share this post


Link to post
Share on other sites

I hate it when your fave mouse breaks and you cannot buy them anymore.

 

Happened to me a few years ago bought some very cheap PS2 standard mice and they were fantastic for Team fortress and got some use then the micro switch went dodgy and i replaced the middle micro switch with left as I never use middle and all was well then it broke used the next one and so on. I bought 4 of them and 4 of them lasted 4 years.

 

Never found one that worked that well again even after spending lots of money on so called quality mice.

Share this post


Link to post
Share on other sites

Update: I had another go at this using NERO.

Guess what? It burned me a perfect disc!

 

More thoughts? I'm lost...

Share this post


Link to post
Share on other sites

Go into the settings and look on the 'Write' tab.

 

Change the 'Write Type' to 'Incremental' instead of 'DAO'.

 

Some drives are buggy and prefer one over the other.

 

Did you try to verify the disc in another drive as mentioned earlier in the thread?

Share this post


Link to post
Share on other sites
Go into the settings and look on the 'Write' tab.

 

Change the 'Write Type' to 'Incremental' instead of 'DAO'.

 

Some drives are buggy and prefer one over the other.

 

Ok,thanks. I will try that.

 

Did you try to verify the disc in another drive as mentioned earlier in the thread?

 

No,I can't really figure out how to do that..

Is there a guide for that?

Share this post


Link to post
Share on other sites
You switch to Verify mode, select the dvdrom (after putting the burnt disc in it), select the image you just burnt and then click the big 'Verify' button.

 

Ok so the only thing that's different is that you'd need to build an image first - which is exactly the same as how you're using Build mode right now, except you change the 'Output' to 'Image File' (in the menu at the top). There are guides for that in the guides forum too. You'd need 8GB of hdd space for the image though.

 

Once you've got the image on your hdd you can write it to the disc using 'Write' mode. Then you can compare the image to the disc (when it's in your DVDROM) using 'Verify' mode.

Share this post


Link to post
Share on other sites

If you build an image now from the existing data, there will be some verify errors connected with time and date issues in the filesystem (first 500 or so sectors). Generally, these can be ignored. But the data verifcation - especially where you have issues round sector 2,000,000 - should be non-existent

 

Regards

Share this post


Link to post
Share on other sites
Sign in to follow this  

×

Important Information

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