PassedPawn Posted July 24, 2011 Share Posted July 24, 2011 I am getting miscompare warnings when verifying after the burn. Example: W 00:41:39 Miscompare at LBA: 833640, Offset: 1102, File: \BDMV\STREAM\00000.m2ts W 00:41:39 Device: 0x4C W 00:41:39 Image File: 0x6C W 00:41:39 Total Errors in Sector: 1 This is from a burn of a BD movie to a Verbatim BD-R. There were 8 of these. And in each one the total errors in sector was 1. Does that mean a total of 8 bytes on the disc are different than the original file? My experience is that if something goes wrong during the burn - bad disc, bad burn, whatever - then the entire sector, and most likely several sectors, become corrupt and unreadable. But in this case the sector is readable but one byte is different. How does this happen? The program tells the drive to burn A and the drive burns B? Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted July 24, 2011 Share Posted July 24, 2011 Post the whole log please. Miscompares can mean lots of things. It might not be an issue with the disc at all, it could be a memory issue. Link to comment Share on other sites More sharing options...
PassedPawn Posted July 25, 2011 Author Share Posted July 25, 2011 Curious that you mentioned memory issue. Come to think of it the only change I made to my system recently was to add additional memory. Before that I had never gotten miscompare when verifying in over 300 burns. Sorry, didn't save the log. Next time it happens I will post the full log. Link to comment Share on other sites More sharing options...
Cynthia Posted July 25, 2011 Share Posted July 25, 2011 Old logs. http://forum.imgburn.com/index.php?showtopic=14632 Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted July 25, 2011 Share Posted July 25, 2011 You should run Memtest86+ for a few passes to check for memory issues. http://www.memtest.org/ Link to comment Share on other sites More sharing options...
PassedPawn Posted August 4, 2011 Author Share Posted August 4, 2011 I ran memtest86 for a couple of passes. No problem was found. After that I burned 7 BD-R discs with no miscompare warnings. But on the lastest burn I again got miscompare. Only one on the whole disc. The log of that session follows. After the burn I calculated md5 for the file in question on both the burned disc and on the local hard drive. They were identical. Should I just ignore miscompares altogether? ----------------------------------------------------------- I 19:06:57 ImgBurn Version 2.5.5.0 started! I 19:06:57 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7601 : Service Pack 1) I 19:06:57 Total Physical Memory: 8,346,704 KB - Available: 6,605,136 KB I 19:06:57 Initialising SPTI... I 19:06:57 Searching for SCSI / ATAPI devices... I 19:06:57 -> Drive 1 - Info: HL-DT-ST DVD+-RW GH50N B101 (F:) (ATAPI) I 19:06:58 -> Drive 2 - Info: PIONEER BD-RW BDR-205 1.11 (G:) (ATAPI) I 19:06:58 -> Drive 3 - Info: ELBY CLONEDRIVE 1.4 (H:) (SCSI) I 19:06:58 -> Drive 4 - Info: ELBY CLONEDRIVE 1.4 (I:) (SCSI) I 19:06:58 Found 1 DVD±RW/RAM, 2 BD-ROM/HD DVD-ROMs and 1 BD-RE! I 19:07:01 Operation Started! I 19:07:01 Building Image Tree... I 19:07:01 Calculating Totals... I 19:07:01 Preparing Image... I 19:07:02 Contents: 12 Files, 14 Folders I 19:07:02 Content Type: BD Video I 19:07:02 Data Type: MODE1/2048 I 19:07:02 File System(s): UDF (2.50) I 19:07:02 Volume Label: [Not Configured] I 19:07:02 Size: 24,885,816,556 bytes I 19:07:02 Sectors: 12,151,286 I 19:07:02 Image Size: 24,886,837,248 bytes I 19:07:02 Image Sectors: 12,151,776 I 19:07:02 Operation Successfully Completed! - Duration: 00:00:00 I 19:07:13 Operation Started! I 19:07:13 Building Image Tree... I 19:07:21 Calculating Totals... I 19:07:21 Preparing Image... I 19:07:21 Contents: 12 Files, 14 Folders I 19:07:21 Content Type: BD Video I 19:07:21 Data Type: MODE1/2048 I 19:07:21 File System(s): UDF (2.50) I 19:07:21 Volume Label: THE_BLUES_BROTHERS I 19:07:21 Size: 24,885,816,556 bytes I 19:07:21 Sectors: 12,151,286 I 19:07:21 Image Size: 24,886,837,248 bytes I 19:07:21 Image Sectors: 12,151,776 I 19:07:28 Operation Successfully Completed! - Duration: 00:00:14 I 19:07:28 Operation Started! I 19:07:28 Source File: -==/\/[bUILD IMAGE]\/\==- I 19:07:28 Source File Sectors: 12,151,776 (MODE1/2048) I 19:07:28 Source File Size: 24,886,837,248 bytes I 19:07:28 Source File Volume Identifier: THE_BLUES_BROTHERS I 19:07:28 Source File Volume Set Identifier: 3F0398E600B96B76 I 19:07:28 Source File Application Identifier: ImgBurn v2.5.5.0 I 19:07:28 Source File Implementation Identifier: ImgBurn I 19:07:28 Source File File System(s): UDF (2.50) I 19:07:28 Destination Device: [0:2:0] PIONEER BD-RW BDR-205 1.11 (G:) (ATAPI) I 19:07:28 Destination Media Type: BD-R (Disc ID: VERBAT-IMe-000) (Speeds: 2x, 4x, 6x, 8x, 10x, 12x) I 19:07:28 Destination Media Sectors: 12,219,392 I 19:07:28 Write Mode: BD I 19:07:28 Write Type: DAO I 19:07:28 Write Speed: 4x I 19:07:28 BD-R Verify Not Required: Yes I 19:07:28 Link Size: Auto I 19:07:28 Lock Volume: Yes I 19:07:28 Test Mode: No I 19:07:28 OPC: Yes I 19:07:28 BURN-Proof: Enabled I 19:07:28 Write Speed Successfully Set! - Effective: 17,980 KB/s (4x) I 19:07:28 Advanced Settings - Optimal Writing Speed: No I 19:07:45 Filling Buffer... (40 MB) I 19:07:46 Writing LeadIn... I 19:07:46 Writing Session 1 of 1... (1 Track, LBA: 0 - 12151775) I 19:07:46 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 12151775) I 19:31:09 Synchronising Cache... I 19:31:10 Closing Track... I 19:31:11 Finalising Disc... I 19:31:19 Operation Successfully Completed! - Duration: 00:23:50 I 19:31:19 Average Write Rate: 17,334 KB/s (3.9x) - Maximum Write Rate: 18,058 KB/s (4.0x) I 19:31:19 Cycling Tray before Verify... I 19:31:38 Device Ready! I 19:31:38 Operation Started! I 19:31:38 Source Device: [0:2:0] PIONEER BD-RW BDR-205 1.11 (G:) (ATAPI) I 19:31:38 Source Media Type: BD-R (Disc ID: VERBAT-IMe-000) (Speeds: 2x, 4x, 6x, 8x, 10x, 12x) I 19:31:39 Image File: -==/\/[bUILD IMAGE]\/\==- I 19:31:39 Image File Sectors: 12,151,776 (MODE1/2048) I 19:31:39 Image File Size: 24,886,837,248 bytes I 19:31:39 Image File Volume Identifier: THE_BLUES_BROTHERS I 19:31:39 Image File Volume Set Identifier: 3F0398E600B96B76 I 19:31:39 Image File Application Identifier: ImgBurn v2.5.5.0 I 19:31:39 Image File Implementation Identifier: ImgBurn I 19:31:39 Image File File System(s): UDF (2.50) I 19:31:39 Read Speed (Data/Audio): MAX / MAX I 19:31:39 Verifying Session 1 of 1... (1 Track, LBA: 0 - 12151775) I 19:31:39 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 12151775) W 19:44:38 Miscompare at LBA: 8654868, Offset: 748, File: \BDMV\STREAM\00000.m2ts W 19:44:38 Device: 0x65 W 19:44:38 Image File: 0xE5 W 19:44:38 Total Errors in Sector: 1 I 19:44:38 Verifying Sectors... I 19:48:11 Operation Successfully Completed! - Duration: 00:16:32 I 19:48:11 Average Verify Rate: 24,499 KB/s (5.4x) - Maximum Verify Rate: 36,020 KB/s (8.0x) ----------------------------------------------------------- Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted August 4, 2011 Share Posted August 4, 2011 No, never just ignore them. When you get one, something isn't right. It could be a memory issue, it could be general I/O comms issue, it could be bad error correction on the drive's part... but there IS (or at least there was) an issue. If you use what ImgBurn tells you and then perform a 2nd test (of your choosing) to confirm/deny the issue then that's fine. Link to comment Share on other sites More sharing options...
laserfan Posted August 4, 2011 Share Posted August 4, 2011 I have encountered "Verify errors" at times, and even posted here about them myself, and then they go away for dozens of burns at a time. So I assume the errors are glitches with the media, which for me have fortunately been rare, very rare indeed (and I use the "good" Verbatims most of the time i.e. not their Life Series discs). You can try another tool e.g. Nero DiscSpeed to see if it reads your disc OK, and in this case it's a movie so you can play it and it's possibly (even likely) that it will play OK in which case you can just forget about the verify error. But if you've never run Memtest86+ on your PC or done other performance testing maybe you have a hardware problem too. BTW LUK the log entry "BD-R Verify Not Required: Yes" is confusing--what does it mean exactly when Verify is clearly ON? Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted August 4, 2011 Share Posted August 4, 2011 'Verify Not Required' is specific to BD-R and is the exact name of flag as specified in the MMC specs. It stops the drive performing automatic write/verify as it goes along (which then slows the burn to a crawl). Link to comment Share on other sites More sharing options...
laserfan Posted August 4, 2011 Share Posted August 4, 2011 'Verify Not Required [Yes]...stops the drive performing automatic write/verify as it goes along (which then slows the burn to a crawl). Thanks alot for indulging me--I vaguely recall that I've seen this before but it needs to get pounded into my head... Link to comment Share on other sites More sharing options...
baronluigi Posted December 22, 2015 Share Posted December 22, 2015 Now we talk about miscompares, I want to comment something that has recently happened to me. I have not enclosed the logfile along with this message because my question is more related to other thing, although the miscompare message imgburn showed me made me realize about that problem. Yesterday I copied an unprotected DVD disc to my computer. The process went perfectly, as can be seen in the logfile of the copy process I 23:30:51 ImgBurn Version 2.5.7.0 started!I 23:30:51 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7601 : Service Pack 1)I 23:30:51 Total Physical Memory: 3.780.256 KB - Available: 1.102.612 KBI 23:30:51 Initialising SPTI...I 23:30:51 Searching for SCSI / ATAPI devices...I 23:30:52 -> Drive 1 - Info: ELBY CLONEDRIVE 1.4 (F:) (SCSI)I 23:31:01 -> Drive 2 - Info: HL-DT-ST DVDRAM GT34N AS00-10 (E:) (SATA)I 23:31:01 Found 1 DVD±RW/RAM and 1 BD-ROM/HD DVD-ROM!I 23:31:47 Operation Started!I 23:31:47 Source Device: [2:0:0] HL-DT-ST DVDRAM GT34N AS00 (E:) (SATA)I 23:31:47 Source Media Type: DVD-ROM (Book Type: DVD-ROM)I 23:31:47 Source Media Sectors: 3.973.168 (Track Path: OTP - L0: 2.079.584 - L1: 1.893.584)I 23:31:47 Source Media Size: 8.137.048.064 bytesI 23:31:47 Source Media Volume Identifier: BERLUSCONI_TRES_IDIOMASI 23:31:47 Source Media Volume Set Identifier: 3C2F88B8I 23:31:47 Source Media Application Identifier: DVD Studio Pro:4.0.3, DSPInterface:382, DVDAuthoring:372, DVDBase:396(Encoder: 483), Oxygene:409I 23:31:47 Source Media Implementation Identifier: Apple Computer, Inc.I 23:31:47 Source Media File System(s): ISO9660; UDF (1.02)I 23:31:47 Read Speed (Data/Audio): MAX / 8xI 23:31:47 Destination File: D:\BERLUSCONI_TRES_IDIOMAS DUMP PORTATIL.ISOI 23:31:47 Destination Free Space: 27.147.956.224 Bytes (26.511.676,00 KB) (25.890,31 MB) (25,28 GB)I 23:31:47 Destination File System: NTFSI 23:31:47 File Splitting: AutoI 23:31:53 Reading Session 1 of 1... (1 Track, LBA: 0 - 3973167)I 23:31:53 Reading Track 1 of 1... (MODE1/2048, LBA: 0 - 3973167)I 23:31:53 Reading Layer 0... (LBA: 0 - 2079583)I 23:54:56 Reading Layer 1... (LBA: 2079584 - 3973167)I 00:12:59 Exporting Graph Data...I 00:13:00 Graph Data File: C:\Users\Urolakosta\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_DVDRAM_GT34N_AS00_LUNES-21-DE-DICIEMBRE-DE-2015_23-31_N-A.ibgI 00:13:00 Export Successfully Completed!I 00:13:00 Operation Successfully Completed! - Duration: 00:41:11I 00:13:00 Average Read Rate: 3.215 KB/s (2.3x) - Maximum Read Rate: 13.333 KB/s (9.6x) However, when I tried to verify the ISO image with the original disc, I received a Miscompare error message as soon the process started. The thing is that I made a checksum analysis over the ISO file aftewards and it had a different CRC32 (I have previously copied the same disc in other computer using another drive, and there I obtained another CRC, although I was able to verify the original disc, with no problem at all) Is the first time this happens to me. I cannot understand why, considering that everything went quite fine in the copy process (Sometimes to reading speed decreased almost reaching 0X, however, I never obtained any reading errors). Link to comment Share on other sites More sharing options...
baronluigi Posted December 25, 2015 Share Posted December 25, 2015 I recopied the disc again and this time everything went perfect. I still cannot understand what happened in the previous try. Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted December 26, 2015 Share Posted December 26, 2015 Please make your own thread, don't hijack someone else's from 4 years ago! Link to comment Share on other sites More sharing options...
Recommended Posts