Cyclical redundancy error

[mozart]

Two Blu's ruined. I get the cyclical redundancy error, cannot source read file. Here is the log:

; //****************************************\\

;   ImgBurn Version 2.5.8.0 - Log

;   Wednesday, 10 June 2015, 06:23:53

; \\****************************************//

;

;

I 06:01:21 ImgBurn Version 2.5.8.0 started!

I 06:01:21 Microsoft Windows 8 Professional x64 Edition (6.2, Build 9200)

I 06:01:21 Total Physical Memory: 8,060,996 KiB  -  Available: 6,498,772 KiB

I 06:01:21 Initialising SPTI...

I 06:01:21 Searching for SCSI / ATAPI devices...

I 06:01:21 -> Drive 1 - Info: PIONEER BD-RW   BDR-XD04 1.00-GENERAL (I:) (USB 2.0)

I 06:01:21 -> Drive 2 - Info: HL-DT-ST DVDRAM GH24NSB0 LN00-10 (D:) (SATA)

I 06:01:21 Found 1 DVD±RW/RAM and 1 BD-RE XL!

I 06:10:49 Operation Started!

I 06:10:49 Device: [0:0:0] PIONEER BD-RW   BDR-XD04 1.00 (I:) (USB)

I 06:10:49 Media Type: BD-R (Disc ID: RITEK-BR3-000)

I 06:10:49 Media Supported Write Speeds: 2x, 4x, 6x

I 06:10:49 Quick Erase: Yes

I 06:10:49 Erasing Disc...

E 06:10:49 Cannot Quick Erase BD-R Media!

E 06:10:54 Operation Failed! - Duration: 00:00:05

I 06:17:16 Operation Started!

I 06:17:16 Source File: L:\ISO\MCO ENCORES 2013 - 2015-II.iso

I 06:17:16 Source File Sectors: 10,403,840 (MODE1/2048)

I 06:17:16 Source File Size: 21,307,064,320 bytes

I 06:17:16 Source File Volume Identifier: MCO_ENCORES_2013_2015_II

I 06:17:16 Source File Volume Set Identifier: AAAABBBBCCCCDDDDEEEEFFFF

I 06:17:16 Source File Application Identifier: DVDArchitectStudio

I 06:17:16 Source File Implementation Identifier: 0

I 06:17:16 Source File File System(s): UDF (2.50)

I 06:17:16 Destination Device: [0:0:0] PIONEER BD-RW   BDR-XD04 1.00 (I:) (USB)

I 06:17:16 Destination Media Type: BD-R (Disc ID: RITEK-BR3-000)

I 06:17:16 Destination Media Supported Write Speeds: 2x, 4x, 6x

I 06:17:16 Destination Media Sectors: 12,219,392

I 06:17:16 Write Mode: BD

I 06:17:16 Write Type: DAO

I 06:17:16 Write Speed: MAX

I 06:17:16 Hardware Defect Management Active: No

I 06:17:16 BD-R Verify Not Required: Yes

I 06:17:16 Link Size: Auto

I 06:17:16 Lock Volume: Yes

I 06:17:16 Test Mode: No

I 06:17:16 OPC: No

I 06:17:16 BURN-Proof: Enabled

I 06:17:16 Write Speed Successfully Set! - Effective: 26,970 KB/s (6x)

I 06:17:16 Advanced Settings - Optimal Writing Speed: No

I 06:17:16 Filling Buffer... (80 MiB)

W 06:17:24 Failed to read from file: MCO ENCORES 2013 - 2015-II.iso

W 06:17:24 Reason: Data error (cyclic redundancy check).

W 06:21:02 Failed to read from file: MCO ENCORES 2013 - 2015-II.iso

W 06:21:02 Reason: Data error (cyclic redundancy check).

E 06:22:38 Failed to read from file: MCO ENCORES 2013 - 2015-II.iso

E 06:22:38 Reason: Data error (cyclic redundancy check).

I 06:22:38 Synchronising Cache...

I 06:22:45 Closing Track...

I 06:23:05 Finalising Disc...

E 06:23:17 Failed to Write Image!

E 06:23:17 Operation Failed! - Duration: 00:06:01

I 06:23:17 Average Write Rate: N/A - Maximum Write Rate: N/A

I 06:23:52 Close Request Acknowledged

I 06:23:52 Closing Down...

I 06:23:53 Shutting down SPTI...

I 06:23:53 ImgBurn closed! 

[dbminter]

You're getting errors from the ISO itself it looks like.  Either the ISO you're trying to burn is bad or the source drive/disc is failing, I'd say.

 

 

Is L:\ an internal SATA HDD, an external USB HDD, an internal SATA Blu-Ray drive, or an external USB Blu-Ray drive?

 

 

If it's a write problem, it's most likely the RITEK BD-R's.  Your drive may not like them.  I know RITEK BD discs don't play back properly on the Playstation 3.

[mozart]

L:\ is an external HDD. I made a good disk from there two weeks ago. Is there a way to set IMGBRN so it first reads the source file BEFORE it writes a buffer on the blank (and ruin it if the write fails?)
 

[dbminter]

I'm not entirely sure about my diagnosis, though.  It's a CRC error, which is usually a read error, but it's showing up in a log line from a Write.  However, it could be a Write error because the Write operation could not read the data.

 

 

Do you still have the source disc that was read to an image file?  If so, try reading the disc to an image file to the internal HDD and using that as the source.  If you still get the CRC error, the next thing I'd try is using something like a Verbatim BD-R.  Is your RITEK disc a Memorex BD-R?  Some people report problems with RITEK, but I've found RITEK media to be a decent 2nd tier media.  With the occasional hiccup like the Playstation 3 not liking RITEK BD media.

[LIGHTNING UK!]

The problem is with your source drive.

 

Have windows check it for errors and do a full surface scan to look for bad sectors.

[mozart]

DSKCHK returned no errors. I ran it from CMD admin. Author UK, am I missing a program setting for IMGBRN so it first reads the source file BEFORE it writes a buffer on the blank (and ruin it if the write fails?)BTW, thanks for writing this code!

Edited June 11, 2015 by mozart

[dbminter]

Did you try checking the disc from Windows Explorer?  Sometimes CHKDSK doesn't find errors that Windows Explorer's own checker catches.  Or it returns errors that aren't really there.  I had CHKDSK return a FAT error that wasn't really there.  The only solution I could find was converting it to NTFS.  You'd think CHKDSK being more of a DOS utility would be a lower level application but sometimes it's too dumb for its own good. 

[LIGHTNING UK!]

Are you sure you made it scan the drive for bad sectors? Simply checking the file system for corruption isn't going to find this problem.

[mozart]

Do you mean the chkdsk  with the  /r switch? That's running now and it usually takes a very long time. I will post the results.

[LIGHTNING UK!]

Yes, that's the one.

[mozart]

There were indeed some bad sectors - the IMGBRN read error solved? Here is the relevant chkdsk /r report:

 

[LIGHTNING UK!]

You could try HDD regenerator or spinrite on the drive, but should probably look at replacing it ASAP.

[dbminter]

Yeah, a problem with the source drive was my initial thought, too.   I, also, recommend you look into replacing the HDD.  Although on a laptop, which I think this system was said it was, it's easier said than done. 

[mozart]

L:\ is an old laptop drive, currently used only as a USB, redundant storage for ISO's. I have since generated anew ISO for the file in question and stored it on a safe drive. Thanks you your input.

Edited June 15, 2015 by mozart