Jump to content
Sign in to follow this  
Groundrush

Corrupt Image

Recommended Posts

Hey guys, have any ideas as to what has happened.

 

I've burned four discs today without incident, all logs and graphs are identical to every good burn from the past. The problem is when I play each and every disc in my stand alone i get is a corrupt image.....badburn9ec.png

 

The four burns are two different files which is why I'm confused :ermm: Firmware is uptodate and i use TY media . I burned one file then checked on my stand alone only to discover the problem, so i then re-burned the same file and again found the same problem. I then changed the file, burned another disc and when viewed had the same problem. Me being me, I've then burned a fourth.......same problem..... I now give up :suicide:

Share this post


Link to post
Share on other sites

So do they look ok on your PC or are they messed up on that too?

 

Do you verify your burns too? That all go ok?

Share this post


Link to post
Share on other sites

Hey Lightning, the image was snapped of my PC and it's identical to the one on my TV. All my burns are verified and each one went without incident, I'll include a log if that helps? and a DVDinfo screen shot.:thumbup:

 

I 10:00:05 ImgBurn Version 1.3.0.0 started!

I 10:00:05 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 2)

I 10:00:05 Initialising SPTI...

I 10:00:05 Searching for SCSI / ATAPI devices...

I 10:00:05 Found 1 DVD+RW and 1 DVD?RW!

I 10:00:33 Operation Started!

I 10:00:33 Source File: C:\Compressed\DVD.ISO

I 10:00:33 Source File Sectors: 2,285,847 (MODE1/2048)

I 10:00:33 Source File Size: 4,681,414,656 bytes

I 10:00:33 Source File Volume Identifier: DVD

I 10:00:33 Source File Implementation Identifier: DVD Shrink

I 10:00:33 Source File UDF Revision: 1.02

I 10:00:33 Destination Device: [0:0:0] LITE-ON DVDRW SHW-1635S YS0Y (G:) (USB)

I 10:00:33 Destination Media Type: DVD+R (Disc ID: YUDEN000-T02-00) (Speeds: 6x, 8x)

I 10:00:33 Destination Media Sectors: 2,295,104

I 10:00:33 Write Mode: DVD

I 10:00:33 Write Type: DAO

I 10:00:33 Write Speed: 8x

I 10:00:33 Link Size: Auto

I 10:00:33 Test Mode: No

I 10:00:33 BURN-Proof: Enabled

I 10:00:33 Filling Buffer...

I 10:00:36 Writing LeadIn...

I 10:01:15 Writing Image...

I 10:08:39 Synchronising Cache...

I 10:08:44 Closing Track...

I 10:08:45 Finalising Disc...

I 10:09:07 Exporting Graph Data...

I 10:09:07 Graph Data File: C:\Documents and Settings\Owner\My Documents\ImgBurn Export Data\LITE-ON_DVDRW_SHW-1635S_YS0Y_03-JUNE-2006_10-00_YUDEN000-T02-00_8x.ibg

I 10:09:07 Export Successfully Completed!

I 10:09:07 Operation Successfully Completed! - Duration: 00:08:34

I 10:09:07 Average Write Rate: 10,319 KB/s (7.5x) - Maximum Write Rate: 11,159 KB/s (8.1x)

I 10:09:07 Cycling Tray before Verify...

W 10:09:17 Waiting for device to become ready...

I 10:09:24 Device Ready!

I 10:09:24 Operation Started!

I 10:09:24 Source Device: [0:0:0] LITE-ON DVDRW SHW-1635S YS0Y (G:) (USB)

I 10:09:24 Source Media Type: DVD+R (Book Type: DVD+R) (Disc ID: YUDEN000-T02-00) (Speeds: 6x, 8x)

I 10:09:25 Image File: C:\Compressed\DVD.ISO

I 10:09:25 Image File Sectors: 2,285,847 (MODE1/2048)

I 10:09:25 Image File Size: 4,681,414,656 bytes

I 10:09:25 Image File Volume Identifier: DVD

I 10:09:25 Image File Implementation Identifier: DVD Shrink

I 10:09:25 Image File UDF Revision: 1.02

I 10:09:25 Verifying Sectors...

I 10:15:59 Exporting Graph Data...

I 10:15:59 Graph Data File: C:\Documents and Settings\Owner\My Documents\ImgBurn Export Data\LITE-ON_DVDRW_SHW-1635S_YS0Y_03-JUNE-2006_10-00_YUDEN000-T02-00_8x.ibg

I 10:15:59 Export Successfully Completed!

I 10:15:59 Operation Successfully Completed! - Duration: 00:06:34

I 10:15:59 Average Verify Rate: 11,632 KB/s (8.4x) - Maximum Verify Rate: 16,996 KB/s (12.3x)

I 10:16:54 Close Request Acknowledged

I 10:16:54 Closing Down...

I 10:16:54 Shutting down SPTI...

I 10:16:54 ImgBurn closed!

 

badburn7rt.png

Share this post


Link to post
Share on other sites

does the same thing happen if you mount the iso in daemon tools and watch it with power dvd?

Share this post


Link to post
Share on other sites

I'm unable to do that corny, i got rather :swear: off i deleted the files thinking they were no good.

 

Out of curiosity what would that tell us?

 

Could it have been a problem when creating the origional files?

Edited by Groundrush

Share this post


Link to post
Share on other sites

if it did the same in power dvd from the hdd iso then it would have probably meant the image was corrupt

Share this post


Link to post
Share on other sites

and if the image was corrupt, you'd go back to the video_ts folder/files (if they ever existed).

 

After that you'd go back to whatever created the files...etc etc.

 

Somewhere along the line you'd find the problem!

Share this post


Link to post
Share on other sites
and if the image was corrupt, you'd go back to the video_ts folder/files (if they ever existed).

 

After that you'd go back to whatever created the files...etc etc .

 

Somewhere along the line you'd find the problem!

 

Hey guys, I've burned the files again, this time successful. :D I've tried to recover the original file(unsuccessfully) so i can't tell if they were corrupt or not. This time i used an alternative method to create the .ISO file for burning, hence the success i presume. :whistling: I'll use the original app' for the next couple of burns and see what happens, but can i ask if there is any way to check the integrity of the file before burning...?

Share this post


Link to post
Share on other sites
but can i ask if there is any way to check the integrity of the file before burning...?
Yup, as per corny's quote below.

 

 

mount the iso in daemon tools and watch it with power dvd?

Share this post


Link to post
Share on other sites

@ corny/ken, thanks guys, consider it done :thumbup:

 

Although I can't belive I didn't figure that out from corny's post......... :blush:

Share this post


Link to post
Share on other sites

That appears to be the Paramount home video logo... :wink:

 

 

Anyway, have you tried making an image of this disc and burning it to a rewritable DVD for testing? If you get it on both the PC and a standalone, then, there are only 2 possibilities, within reason:

 

1.) really lousy compression codec/error during processing so that the file itself was created that way

 

2.) there is a problem with the physical disc, either during the burning process, the dye itself, or the reflectivity of the surface. All of which could be either a dying burner or a bad disc, even in a batch of good ones.

Share this post


Link to post
Share on other sites

Hi guys,

I don?t know if it is relevant or not, but I had a problem generating an ISO image a while back using PGCEdit and MKISOFS. The generation of the ISO went OK, see the attached log:

 

mkisofs log for DVD "#############################_DISK1"

From: "H:\Blanked\##################################"

DVD-TEXT General Name: "###############################"

Provider ID: "#######################"

Number of VTS: 2

Output file: "Q:\ISO\################################.ISO"

Volume label: "################################"

Running under windows (OS type: Windows NT)

 

mkisofs 2.01 X (i686-pc-cygwin)

Layer break is at absolute sector 1886992. (Offset in L0 is 465032.)

Layer break cell:

1421960: VTST 1 , 1 TTN 1 (1:54:46) Title 1 Cell 16 (00:01:16.24), V/CID: 7/1

 

The pad was 465048 for file VIDEO_TS.IFO

Total translation table size: 0

Total rockridge attributes bytes: 0

Total directory bytes: 4248

Path table size(bytes): 42

Max brk space used 5000

3773976 extents written (7371 MB)

 

ISO created OK. :)

 

I will attempt to attach a png of the ImgBurn screen captures, but I haven?t had much success with this in the past. Just in case the text in the error window was as follows:

 

The burn failed during ImgBurn with the following message: ?Failed to read from the file: #########################_Disk1.ISO?

Reason: Data error (cyclic redundancy check).?

 

I 00:47:57 ImgBurn Version 1.2.0.0 started!

I 00:47:57 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2)

I 00:47:57 Initialising SPTI...

I 00:47:57 Searching for SCSI / ATAPI devices...

I 00:47:57 Found 1 CD-ROM, 1 CD-RW, 1 DVD-ROM and 2 DVD?RWs!

I 00:48:14 Operation Started!

I 00:48:14 Source File: Q:\ISO\########################_DISK1.ISO

I 00:48:14 Source File Sectors: 3,773,976 (MODE1/2048)

I 00:48:14 Source File Size: 7,729,102,848 bytes

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

I 00:48:14 Source File Implementation Identifier: mkisofs

I 00:48:14 Destination Device: [3:0:0] PLEXTOR DVDR PX-716A 1.09 (W:) (SCSI)

I 00:48:14 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2.4x, 4x, 6x)

I 00:48:14 Destination Media Sectors: 4,173,824

I 00:48:14 Write Mode: DVD

I 00:48:14 Write Type: DAO

I 00:48:14 Write Speed: 6x

I 00:48:14 Link Size: Auto

I 00:48:14 Test Mode: No

I 00:48:14 BURN-Proof: Enabled

I 00:48:14 User Specified L0 Data Zone Capacity: 1,886,992

I 00:48:14 Filling Buffer...

I 00:48:15 Writing LeadIn...

I 00:48:58 Writing Image...

I 00:48:58 Writing Layer 0... (LBA: 0 - 1886991)

E 00:56:19 Failed to read from file: ###########################.ISO

E 00:56:19 Reason: Data error (cyclic redundancy check).

I 01:17:21 Synchronising Cache...

I 01:17:24 Closing Track...

I 01:17:26 Finalising Disc... >_<

 

I mounted the ISO file using DAEMON tools and then tried ripping the ISO file back to the HD using DVDDecripter.

 

I 01:27:34 DVD Decrypter Version 3.5.4.0 started!

I 01:27:34 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2)

W 01:27:34 Drive C:\ (FAT) does not support single files > 4 GB

I 01:27:34 Initialising SPTI...

I 01:27:34 Searching for SCSI / ATAPI devices...

I 01:27:35 Found 1 CD-ROM, 1 CD-RW, 1 DVD-ROM and 2 DVD?RWs!

I 01:28:06 Operation Started!

I 01:28:06 Source Device: [5:0:0] MY5642L OAL694C 1.0 (U:) (SCSI)

I 01:28:06 Source Media Type: DVD-ROM

I 01:28:06 Source Media Region Code: 1, 2, 3, 4, 5, 6, 7, 8

I 01:28:06 Source Media Copyright Protection System Type: None

I 01:28:06 Source Media Implementation Identifier: mkisofs

I 01:28:06 Destination Folder: S:\###########################_DISK1\VIDEO_TS\

I 01:28:06 File Splitting: By File

I 01:28:06 Detect Mastering Errors: No

I 01:28:06 Multi Angle Processing: No

I 01:28:06 Remove Macrovision Protection: Yes

I 01:28:06 Stream Processing: No

I 01:28:06 Copying VIDEO_TS.IFO... (LBA: 287 - 291) - KEY: N/A

I 01:28:07 Copying VIDEO_TS.BUP... (LBA: 465340 - 465344) - KEY: N/A

I 01:28:07 Copying VTS_01_0.IFO... (LBA: 465345 - 465388) - KEY: N/A

I 01:28:07 Copying VTS_01_0.VOB... (LBA: 465389 - 558315) - KEY: N/A

I 01:28:20 Copying VTS_01_1.VOB... (LBA: 558316 - 1082602) - KEY: N/A

I 01:29:42 Copying VTS_01_2.VOB... (LBA: 1082603 - 1606889) - KEY: N/A

I 01:31:02 Copying VTS_01_3.VOB... (LBA: 1606890 - 2131176) - KEY: N/A

W 01:31:39 Sector 1778984 - Pack Header Not Found (0x52494646)

W 01:31:39 Sector 1778985 - Pack Header Not Found (0x00000000)

I 01:32:32 Copying VTS_01_4.VOB... (LBA: 2131177 - 2655463) - KEY: N/A

I 01:33:45 Copying VTS_01_5.VOB... (LBA: 2655464 - 3179750) - KEY: N/A

I 01:34:57 Copying VTS_01_6.VOB... (LBA: 3179751 - 3704037) - KEY: N/A

I 01:36:08 Copying VTS_01_7.VOB... (LBA: 3704038 - 3732310) - KEY: N/A

I 01:36:12 Copying VTS_01_0.BUP... (LBA: 3732311 - 3732354) - KEY: N/A

I 01:36:12 Copying VTS_02_0.IFO... (LBA: 3732355 - 3732361) - KEY: N/A

I 01:36:12 Copying VTS_02_1.VOB... (LBA: 3732362 - 3773967) - KEY: N/A

I 01:36:18 Copying VTS_02_0.BUP... (LBA: 3773968 - 3773974) - KEY: N/A

I 01:36:18 Operation Successfully Completed! - Duration: 00:08:12

I 01:36:18 Average Read Rate: 13,449 KB/s (9.7x) - Maximum Read Rate: 33,359 KB/s (24.1x) :(

 

I went back and repeated the generation of the ISO file a second time from the same VIDEO_TS folder and the resulting file was ok and burned without any errors. :) . A scan of the HD that contained the ISO file with the reported error did not show any errors, nor were there any error in the system log files.

 

Note I have edited out certain items in the log and screen capture with ?#####?s? to protect the innocent.

 

I haven?t seen a reoccurrence of this problem. :)

 

Don?t know if this helps but??. Note UK I probably should have posted this data back when the error happened, but since it only happened one time as far as I can tell, I decided not to bother you at the time. I hope this adds something to the discussion. :blush:

 

Rcubed

post-120-1149485740_thumb.png

Share this post


Link to post
Share on other sites

There shouldn't be any reason for Windows to throw that error unless there really is/was a problem reading from the hdd.

 

Maybe all it needed was to have those sectors written to again and that fixed them.

Share this post


Link to post
Share on other sites
If you get it on both the PC and a standalone, then, there are only 2 possibilities, within reason:

 

1.) really lousy compression codec/error during processing so that the file itself was created that way

Hey db, I'm inclined to go with option 1 in that the app' i used to create the file was the cause of the problem. I switched to an alternative method to create the files for the burns that were sucsessful.

 

As for using RW media for testing purposes, It never crossed my mind but something i shall implement forth with.:thumbup: That said re-writable media is something i do not posses and really know nothing about as I've never used it.:unsure:

 

What would you recommend in that department.

Share this post


Link to post
Share on other sites

DB really is the RW king, To the best of my knowledge he's by far the biggest RW user within the beta team.

He should be able to put you on the right tram with that question. :)

Share this post


Link to post
Share on other sites

Hey Ken, It's pretty obvious when you think about it, using RW do make sure everything is ok. I'm never pushed for time when burning so another 10 minutes or so is nothing, the other bonus is that you don't end up wasting you good media :)

Edited by Groundrush

Share this post


Link to post
Share on other sites

Yeah, that's right, good when you're trying track down problems without wasting good media.

I use them for that, and storing temp data, like backups.

Share this post


Link to post
Share on other sites
There shouldn't be any reason for Windows to throw that error unless there really is/was a problem reading from the hdd.

 

Maybe all it needed was to have those sectors written to again and that fixed them.

 

UK,

I was unsure at the time, but from your reply I take it that was an error from XP not an internally detected error with the data on the part of ImgBurn. I guess I'm puzzled about several things. Were the W 01:31:39 Sector 1778984 - Pack Header Not Found (0x52494646) and W 01:31:39 Sector 1778985 - Pack Header Not Found (0x00000000) messages in DVDDecriptor equivalent to the same error (In this case with the image mounted as a vitrual drive via Daemon tools)? that is, does Daemon tools pass the error on to the using program?

 

I realize you may not be able to answer it but why didn't XP report the same error when the hdd file was read by Daemon tools? It was a repeatable error in light of the fact the rip of the iso image also failed. I'm not familiar as to how hardware errors are reported to the application by the operating system and the applications responsibility to report the error to the user (or end application). In the same light would one expect an error be posted in the Computer Management/Event Viewer/Application or System logs, or is that a function of how the application handles the error? When I had another hdd going south before this incident (the drive had been replaced long before this error) there were errors posted in the Event Viewer logs indicating tha hdd errors had been occuring. Neither log showed any hdd related read errors for this case :unsure:

 

Also I believe that I went back and did a full scan of that logical drive using Computer Manager/Properties/Tools/Error Checking to scan the disk prior to generating the file the second time, there were no reported errors?

 

Not to beat a dead horse, but any additional light you could shed on the topic would be appreciated.

 

BTW again my contgrats on a great tool, I'm using ImgBurn exclusively to burn DVDs now and have had minimal problems. I'm a great supporter of your efforts and greatly appreciate them :):):):)

 

Thanks again for your patience and help,

 

Rcubed

Share this post


Link to post
Share on other sites
Hey Ken, It's pretty obvious when you think about it, using RW do make sure everything is ok. I'm never pushed for time when burning so another 10 minutes or so is nothing, the other bonus is that you don't end up wasting you good media :)

It'll be a bit longer than 10 minutes. :) The last time I checked, 4x was the max speed for RW media but I never use them except for transferring stuff from a DVD recorder to PC.

 

<Shamus *loves* The Iron Chef> =))

Share this post


Link to post
Share on other sites
BTW again my congrats on a great tool, I'm using ImgBurn exclusively to burn DVDs now and have had minimal problems. I'm a great supporter of your efforts and greatly appreciate them :):):):)

You'll probably enjoy the things that Lightning_UK! is adding to ImgBurn that we're still testing (i.e. playing with and attempting to break) for ISO creation. It's very slick indeed.

Share this post


Link to post
Share on other sites

Agreed. Still, it doesn't matter who it is, they can all cook up some pretty disgusting stuff. :&

Share this post


Link to post
Share on other sites

As for what I would recommend, well, just don't get any CMC. =)) Other than that, what I've found that works well for me because I can get it easily here in town as the ones from Office Depot, which are Riteks with their badge on them. However, picky players like the Playstation 2 have had some random skipping problems on playback, but, the kind that are truly random. Meaning, you can rewind back over the brief pause and resume play and not get it again.

 

 

Unfortunately, there's no real recommendation to make. You have to just find what works for the hardware you have. One of the real problems, IMO, with writable DVD's of any kind. Despite there being a book standard, very few hardware manufactures and some disc manufacturers just choose to ignore them :rolleyes: and slap anything together.

 

 

On the DVD+RW side, though I normally prefer - to + in general across the board, I've found Maxell and HP DVD+RW discs played without problems in all the test hardware I currently have.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×

Important Information

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