paultara Posted January 16, 2018 Posted January 16, 2018 Hello, so in the past few weeks I have been trying to burn bd-r dl's. The first one worked perfectly but the rest give me I/O error with check condition (Write Error). I have an ASUS BW-16D1HT and I am using Mediarange BD-R DL 6x (appears as VERBAT-IMf-000 - I don't know why). I am using AWS speed which is set to MAX. OPC Is turned on but I tried with it turned off, no luck. Device part in ImgBurn: ASUS BW-16D1HT 3.02 (SATA) Current Profile: BD-R Disc Information: Status: Empty State of Last Session: Empty Erasable: No Free Sectors: 24.438.784 Free Space: 50.050.629.632 bytes Free Time: 5430:52:34 (MM:SS:FF) Next Writable Address: 0 MID: VERBAT-IMf-000 Supported Write Speeds: 2x; 4x; 6x; 8x BD Disc Information (L0): Disc ID: VERBAT-IMf-000 Disc Type: BD-R Disc Size: 120 mm Disc Class: 0 Disc Version: 1 Number of Layers: 2 Layer Type: Writable DVD Layer Present: No CD Layer Present: No Channel Bit Length: 74.50 nm (25 GB Per Layer) Push-Pull Polarity: Positive Recorded Mark Polarity: HTL BCA Present: Yes Maximum Transfer Rate: Not Specified First PAA of Data Zone: 131.072 Last PAA of Data Zone: 1.658.494 BD Disc Information (L1): Disc ID: VERBAT-IMf-000 Disc Type: BD-R Disc Size: 120 mm Disc Class: 0 Disc Version: 1 Number of Layers: 2 Layer Type: Writable DVD Layer Present: No CD Layer Present: No Channel Bit Length: 74.50 nm (25 GB Per Layer) Push-Pull Polarity: Positive Recorded Mark Polarity: HTL BCA Present: Yes Maximum Transfer Rate: Not Specified First PAA of Data Zone: 2.535.808 Last PAA of Data Zone: 4.063.230 Format Capacities: DT: 0x01 - NB: 24438784 (0x0174E800) - TDP: 413696 FT: 0x00 - NB: 23652352 (0x0168E800) - TDP: 24576 FT: 0x32 - NB: 23652352 (0x0168E800) - TDP: 0 FT: 0x32 - NB: 11200512 (0x00AAE800) - TDP: 0 FT: 0x32 - NB: 24307712 (0x0172E800) - TDP: 0 Performance (Write Speed): Descriptor 1... -> B0: 0x00; B1: 0x00; B2: 0x00; B3: 0x00 -> EL: 24438783 (0x0174E7FF) -> RS: 35.968 KB/s (8x) - WS: 8.992 KB/s (2x) Descriptor 2... -> B0: 0x00; B1: 0x00; B2: 0x00; B3: 0x00 -> EL: 24438783 (0x0174E7FF) -> RS: 35.968 KB/s (8x) - WS: 17.984 KB/s (4x) Descriptor 3... -> B0: 0x08; B1: 0x00; B2: 0x00; B3: 0x00 -> EL: 24438783 (0x0174E7FF) -> RS: 35.968 KB/s (8x) - WS: 26.976 KB/s (6x) Descriptor 4... -> B0: 0x08; B1: 0x00; B2: 0x00; B3: 0x00 -> EL: 24438783 (0x0174E7FF) -> RS: 35.968 KB/s (8x) - WS: 35.968 KB/s (8x) Log after error: I 01:17:00 ImgBurn Version 2.5.8.0 started! I 01:17:00 Microsoft Windows 8 Professional x64 Edition (6.2, Build 9200) I 01:17:00 Total Physical Memory: 16.716.740 KiB - Available: 13.082.928 KiB I 01:17:00 Initialising SPTI... I 01:17:00 Searching for SCSI / ATAPI devices... I 01:17:00 -> Drive 1 - Info: DiscSoft Virtual 1.0 (H:) (Virtual) I 01:17:00 -> Drive 2 - Info: DiscSoft Virtual 1.0 (G:) (Virtual) I 01:17:00 -> Drive 3 - Info: DiscSoft Virtual 1.0 (I:) (Virtual) I 01:17:01 -> Drive 4 - Info: ASUS BW-16D1HT 3.02 (E:) (SATA) I 01:17:01 Found 3 BD-ROM XLs and 1 BD-RE XL! I 01:17:16 Operation Started! I 01:17:16 Building Image Tree... I 01:17:16 Calculating Totals... I 01:17:16 Preparing Image... I 01:17:16 Contents: 400 Files, 22 Folders I 01:17:16 Content Type: BD Video I 01:17:16 Data Type: MODE1/2048 I 01:17:16 File System(s): UDF (2.50) I 01:17:16 Volume Label: [Not Configured] I 01:17:16 Size: 40.443.665.265 bytes I 01:17:16 Sectors: 19.748.101 I 01:17:16 Image Size: 40.446.853.120 bytes I 01:17:16 Image Sectors: 19.749.440 I 01:17:16 Operation Successfully Completed! - Duration: 00:00:00 I 01:17:51 Operation Started! I 01:17:51 Building Image Tree... I 01:17:51 Calculating Totals... I 01:17:51 Preparing Image... I 01:17:51 Contents: 400 Files, 22 Folders I 01:17:51 Content Type: BD Video I 01:17:51 Data Type: MODE1/2048 I 01:17:51 File System(s): UDF (2.50) I 01:17:51 Volume Label: THE_MATRIX I 01:17:51 Size: 40.443.665.265 bytes I 01:17:51 Sectors: 19.748.101 I 01:17:51 Image Size: 40.446.853.120 bytes I 01:17:51 Image Sectors: 19.749.440 I 01:17:53 Operation Successfully Completed! - Duration: 00:00:01 I 01:17:53 Operation Started! I 01:17:53 Source File: -==/\/[bUILD IMAGE]\/\==- I 01:17:53 Source File Sectors: 19.749.440 (MODE1/2048) I 01:17:53 Source File Size: 40.446.853.120 bytes I 01:17:53 Source File Volume Identifier: THE_MATRIX I 01:17:53 Source File Volume Set Identifier: 4C300A39012D5825 I 01:17:53 Source File Application Identifier: ImgBurn v2.5.8.0 I 01:17:53 Source File Implementation Identifier: ImgBurn I 01:17:53 Source File File System(s): UDF (2.50) I 01:17:53 Destination Device: [0:0:0] ASUS BW-16D1HT 3.02 (E:) (SATA) I 01:17:53 Destination Media Type: BD-R (Disc ID: VERBAT-IMf-000) I 01:17:53 Destination Media Supported Write Speeds: 2x; 4x; 6x; 8x I 01:17:53 Destination Media Sectors: 24.438.784 I 01:17:53 Write Mode: BD I 01:17:53 Write Type: DAO I 01:17:53 Write Speed: MAX I 01:17:53 Hardware Defect Management Active: No I 01:17:53 BD-R Verify Not Required: Yes I 01:17:53 Link Size: Auto I 01:17:53 Lock Volume: Yes I 01:17:53 Test Mode: No I 01:17:53 OPC: Yes I 01:17:53 BURN-Proof: Enabled I 01:17:55 Write Speed Successfully Set! - Effective: 35.968 KB/s (8x) I 01:18:35 Filling Buffer... (80 MiB) I 01:18:39 Writing LeadIn... I 01:18:40 Writing Session 1 of 1... (1 Track, LBA: 0 - 19749439) I 01:18:40 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 19749439) I 01:18:40 Writing Layer 0... (LBA: 0 - 12219391) W 01:34:30 Failed to Write Sectors 12190400 - 12190431 - Reason: Write Error W 01:34:30 Retrying (1 of 20)... W 01:34:30 Retry Failed - Reason: Invalid Address For Write W 01:34:30 Retrying (2 of 20)... W 01:34:30 Retry Failed - Reason: Invalid Address For Write W 01:34:30 Retrying (3 of 20)... W 01:34:30 Retry Failed - Reason: Invalid Address For Write W 01:34:30 Retrying (4 of 20)... W 01:34:30 Retry Failed - Reason: Invalid Address For Write W 01:34:30 Retrying (5 of 20)... W 01:34:30 Retry Failed - Reason: Invalid Address For Write W 01:34:30 Retrying (6 of 20)... W 01:34:30 Retry Failed - Reason: Invalid Address For Write W 01:34:30 Retrying (7 of 20)... W 01:34:30 Retry Failed - Reason: Invalid Address For Write W 01:34:30 Retrying (8 of 20)... W 01:34:30 Retry Failed - Reason: Invalid Address For Write W 01:34:30 Retrying (9 of 20)... W 01:34:30 Retry Failed - Reason: Invalid Address For Write W 01:34:30 Retrying (10 of 20)... W 01:34:30 Retry Failed - Reason: Invalid Address For Write W 01:34:30 Retrying (11 of 20)... W 01:34:30 Retry Failed - Reason: Invalid Address For Write W 01:34:30 Retrying (12 of 20)... W 01:34:30 Retry Failed - Reason: Invalid Address For Write W 01:34:30 Retrying (13 of 20)... W 01:34:30 Retry Failed - Reason: Invalid Address For Write W 01:34:30 Retrying (14 of 20)... W 01:34:30 Retry Failed - Reason: Invalid Address For Write W 01:34:30 Retrying (15 of 20)... W 01:34:30 Retry Failed - Reason: Invalid Address For Write W 01:34:30 Retrying (16 of 20)... W 01:34:30 Retry Failed - Reason: Invalid Address For Write W 01:34:30 Retrying (17 of 20)... W 01:34:30 Retry Failed - Reason: Invalid Address For Write W 01:34:30 Retrying (18 of 20)... W 01:34:30 Retry Failed - Reason: Invalid Address For Write W 01:34:30 Retrying (19 of 20)... W 01:34:30 Retry Failed - Reason: Invalid Address For Write W 01:34:30 Retrying (20 of 20)... W 01:34:30 Retry Failed - Reason: Invalid Address For Write Does anybody have any suggestions?
LIGHTNING UK! Posted January 16, 2018 Posted January 16, 2018 If your drive can't cope with burning at the max speed it claims to support on those discs (i.e. 8x), try the remaining 'supported' write speeds.
dbminter Posted January 16, 2018 Posted January 16, 2018 The reason ImgBurn recognizes the disc as VERBAT-IMf-000 is because Verbatim actually made those discs for Mediarange. Which is actually kind of surprising that they're not using cheap CMC Magnetics for them instead of the good stuff that Verbatim makes. IF those are true Verbatims, of course. The Disc ID can always be faked.
paultara Posted January 16, 2018 Author Posted January 16, 2018 If your drive can't cope with burning at the max speed it claims to support on those discs (i.e. 8x), try the remaining 'supported' write speeds. I wasted 14 discs trying to burn files. I tried every speed, always the same. At about 60 percent it stops and has the error. Any other ideas?
dbminter Posted January 16, 2018 Posted January 16, 2018 I have a possible suggestion, although it may not swallow well. I had one of those ASUS drives you're using here. Two of them I tested out, actually, and it's pretty much junk. I never even got to the point of testing BD-RE DL with it before I sent it back for a refund. I tried another copy of the same drive to see if maybe I just didn't get a bad drive, but they both did the same things, which means it's a problem with the drive. First failure was Ritek 8x DVD+RW. It would write to the discs but Verify would always fail because the drive borks the discs, even when they're new! They're unreadable after writing and cannot be reformatted to recover. Second failure was writing to BD-RE DL as a giant floppy. It would write to the disc but, as with the Ritek rewritable discs, render them unusable afterwards! Third failure was the same kind on a new BD-RE DL, from Verbatim, like the first failure. Same results. So, the drive doesn't write rewritable media correctly, for sure. If it can't do something that simple, I can't see it writing BD-R DL media correctly either. And some drives, like LG's, support writing to BD DL media, but they don't do it correctly. So, on to my solution: replace your ASUS drive with a Pioneer BD burner. Pioneer's have their own problems, but they seem to be the drives that have the highest success rate at writing BD DL media. I've had 4 Pioneer 2209's over the past 4 years, with a new one on the way. My first Pioneer still works save for the eject button issue that seems common to Pioneer BD drives. I've never used BD-R DL in it, but I write Verbatim BD-RE DL's every month on Day 1, with daily file backups going to BD-RE DL's. I can't see a Pioneer that writes to Verbatim BD-RE DL failing to write to Verbatim BD-R DL. Plus, a few other people with BD DL burning issues when they took my advice to replace LG's with Pioneer fixed their burning issues that way. So, as I say, it may solve your problem, too. However, it's not the "easiest" solution and definitely not the cheapest. It may be the one more likely to solve your problem, though.
paultara Posted January 16, 2018 Author Posted January 16, 2018 I have a possible suggestion, although it may not swallow well. I had one of those ASUS drives you're using here. Two of them I tested out, actually, and it's pretty much junk. I never even got to the point of testing BD-RE DL with it before I sent it back for a refund. I tried another copy of the same drive to see if maybe I just didn't get a bad drive, but they both did the same things, which means it's a problem with the drive. First failure was Ritek 8x DVD+RW. It would write to the discs but Verify would always fail because the drive borks the discs, even when they're new! They're unreadable after writing and cannot be reformatted to recover. Second failure was writing to BD-RE DL as a giant floppy. It would write to the disc but, as with the Ritek rewritable discs, render them unusable afterwards! Third failure was the same kind on a new BD-RE DL, from Verbatim, like the first failure. Same results. So, the drive doesn't write rewritable media correctly, for sure. If it can't do something that simple, I can't see it writing BD-R DL media correctly either. And some drives, like LG's, support writing to BD DL media, but they don't do it correctly. So, on to my solution: replace your ASUS drive with a Pioneer BD burner. Pioneer's have their own problems, but they seem to be the drives that have the highest success rate at writing BD DL media. I've had 4 Pioneer 2209's over the past 4 years, with a new one on the way. My first Pioneer still works save for the eject button issue that seems common to Pioneer BD drives. I've never used BD-R DL in it, but I write Verbatim BD-RE DL's every month on Day 1, with daily file backups going to BD-RE DL's. I can't see a Pioneer that writes to Verbatim BD-RE DL failing to write to Verbatim BD-R DL. Plus, a few other people with BD DL burning issues when they took my advice to replace LG's with Pioneer fixed their burning issues that way. So, as I say, it may solve your problem, too. However, it's not the "easiest" solution and definitely not the cheapest. It may be the one more likely to solve your problem, though. So the problem might be the burner itself. I thought it might be the discs. I will try to see what I can do about the drive. Thank you!
dbminter Posted January 16, 2018 Posted January 16, 2018 Well, I can't guarantee it's not the discs that are the problem. It could be the ASUS just doesn't like those Verbatims, but Verbatim BD-R SL and BD-RE DL (IF they're real Verbatim.) are the best quality BD discs out there. (Their BD-RE SL is CMC Magnetics, the worst manufacturer out there.) Or those Mediarange discs may not be true Verbatim. But, I'd be more willing to concentrate on the burner being the problem. I had pretty much nothing but major problems with that ASUS you're using and consider it to be junk. And if you do swap in a Pioneer and still have problems, you know it's not the drive being the problem. Because Pioneer is pretty much the best you can get. If the best still has a problem, then it must be a problem with the discs or some kind of Windows or PC hardware problem that would be the cause.
Recommended Posts