pilpero Posted September 5, 2012 Posted September 5, 2012 (edited) Hi, just bought a 50 disc cakebox of TDK DVD-R 16x off eBay. A very bad decision. The media code is MBI 01RG40, which are made in India I guess. I tried to burn them in my laptop, and the results have always been like this: I 21:28:14 ImgBurn Version 2.5.6.0 started!I 21:28:14 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7601 : Service Pack 1) I 21:28:14 Total Physical Memory: 16 753 952 KB - Available: 12 902 184 KB I 21:28:14 Initialising SPTI... I 21:28:14 Searching for SCSI / ATAPI devices... I 21:28:17 -> Drive 1 - Info: TSSTcorp DVDWBD SN-B063D SB00 (E:) (ATAPI) I 21:28:17 -> Drive 2 - Info: ELBY CLONEDRIVE 1.4 (F:) (SCSI) I 21:28:17 Found 1 BD-ROM/HD DVD-ROM and 1 BD-ROM/DVD±RW! I 21:28:26 Operation Started! I 21:28:26 Building Image Tree... I 21:28:27 Checking Directory Depth... I 21:28:28 Calculating Totals... I 21:28:28 Preparing Image... I 21:28:28 Checking Path Length... I 21:28:28 Contents: 135 Files, 2 Folders I 21:28:28 Content Type: DVD Video I 21:28:28 Data Type: MODE1/2048 I 21:28:28 File System(s): ISO9660, UDF (1.02) I 21:28:28 Volume Label: mel30 I 21:28:28 IFO/BUP 32K Padding: Enabled I 21:28:28 Region Code: 1; 2; 3; 4; 5; 6; 8 I 21:28:28 TV System: PAL I 21:28:28 Size: 3 677 396 992 bytes I 21:28:28 Sectors: 1 795 604 I 21:28:28 Image Size: 3 678 240 768 bytes I 21:28:28 Image Sectors: 1 796 016 I 21:28:29 Operation Successfully Completed! - Duration: 00:00:03 I 21:28:29 Operation Started! I 21:28:29 Source File: -==/\/[bUILD IMAGE]\/\==- I 21:28:29 Source File Sectors: 1 796 016 (MODE1/2048) I 21:28:29 Source File Size: 3 678 240 768 bytes I 21:28:29 Source File Volume Identifier: mel30 I 21:28:29 Source File Volume Set Identifier: 4125AB8D001B67AF I 21:28:29 Source File Application Identifier: IMGBURN V2.5.6.0 - THE ULTIMATE IMAGE BURNER! I 21:28:29 Source File Implementation Identifier: ImgBurn I 21:28:29 Source File File System(s): ISO9660; UDF (1.02) I 21:28:29 Destination Device: [0:2:0] TSSTcorp DVDWBD SN-B063D SB00 (E:) (ATAPI) I 21:28:29 Destination Media Type: DVD-R (Disc ID: MBI 01RG40) I 21:28:29 Destination Media Supported Write Speeds: 3,3x; 4x; 6x; 8x I 21:28:29 Destination Media Sectors: 2 297 888 I 21:28:29 Write Mode: DVD I 21:28:29 Write Type: DAO I 21:28:29 Write Speed: MAX I 21:28:29 Link Size: Auto I 21:28:29 Lock Volume: Yes I 21:28:29 Test Mode: No I 21:28:29 OPC: No I 21:28:30 BURN-Proof: Enabled I 21:28:30 Write Speed Successfully Set! - Effective: 11 080 KB/s (8x) I 21:28:30 Filling Buffer... (40 MB) I 21:28:31 Writing LeadIn... W 21:38:41 Failed to Write Sectors 0 - 31 - Reason: Write Error W 21:38:41 Retrying (1 of 20)... W 21:44:47 Retry Failed - Reason: Write Error W 21:44:47 Retrying (2 of 20)... I 21:51:30 Writing LeadIn... W 21:53:15 Failed to Write Sectors 32 - 63 - Reason: Write Error W 21:53:15 Retrying (1 of 20)... W 21:53:15 Retry Failed - Reason: Invalid Address For Write W 21:53:15 Retrying (2 of 20)... W 21:53:15 Retry Failed - Reason: Invalid Address For Write W 21:53:15 Retrying (3 of 20)... W 21:53:15 Retry Failed - Reason: Invalid Address For Write W 21:53:15 Retrying (4 of 20)... W 21:53:15 Retry Failed - Reason: Invalid Address For Write W 21:53:15 Retrying (5 of 20)... W 21:53:15 Retry Failed - Reason: Invalid Address For Write W 21:53:15 Retrying (6 of 20)... W 21:53:15 Retry Failed - Reason: Invalid Address For Write W 21:53:15 Retrying (7 of 20)... W 21:53:15 Retry Failed - Reason: Invalid Address For Write W 21:53:15 Retrying (8 of 20)... W 21:53:15 Retry Failed - Reason: Invalid Address For Write W 21:53:15 Retrying (9 of 20)... W 21:53:15 Retry Failed - Reason: Invalid Address For Write W 21:53:15 Retrying (10 of 20)... W 21:53:15 Retry Failed - Reason: Invalid Address For Write W 21:53:15 Retrying (11 of 20)... W 21:53:15 Retry Failed - Reason: Invalid Address For Write W 21:53:15 Retrying (12 of 20)... W 21:53:15 Retry Failed - Reason: Invalid Address For Write W 21:53:15 Retrying (13 of 20)... W 21:53:16 Retry Failed - Reason: Invalid Address For Write W 21:53:16 Retrying (14 of 20)... W 21:53:16 Retry Failed - Reason: Invalid Address For Write W 21:53:16 Retrying (15 of 20)... W 21:53:16 Retry Failed - Reason: Invalid Address For Write W 21:53:16 Retrying (16 of 20)... W 21:53:16 Retry Failed - Reason: Invalid Address For Write W 21:53:16 Retrying (17 of 20)... W 21:53:16 Retry Failed - Reason: Invalid Address For Write W 21:53:16 Retrying (18 of 20)... W 21:53:16 Retry Failed - Reason: Invalid Address For Write W 21:53:16 Retrying (19 of 20)... W 21:53:16 Retry Failed - Reason: Invalid Address For Write W 21:53:16 Retrying (20 of 20)... W 21:53:16 Retry Failed - Reason: Invalid Address For Write E 21:55:53 Failed to Write Sectors 32 - 63 - Reason: Write Error E 21:55:53 Next Writable Address: 0 I 21:55:53 Synchronising Cache... W 21:56:01 User opted to skip the 'Close Track/Session/Disc' functions. E 21:56:01 Failed to Write Image! E 21:56:01 Operation Failed! - Duration: 00:27:31 I 21:56:01 Average Write Rate: 0 KB/s (0.0x) - Maximum Write Rate: 0 KB/s (0.0x) I've failed to burn around 10 discs on my laptop. On my brothers old (year model was 2006 I guess) the discs burn like a mint, no errors what so ever, although the burn speed is limited to 4x (yeah it's OLD laptop but works though). Is there any possible solution for this, as the problem is starting to narrow on my drive? Check the timestamps also, took forever to test burn LeadIn and boom, the errors start flowing in. And finally, after 20 failed retries this pops up: I/O Error! Device: TSSTcorp DVDWBD SN-B036D SB00 (E:) (ATAPI) ScsiStatus: 0x02 Interpretation: Check Condition CDB: 2A 00 00 00 00 20 00 00 20 00 Interpretation: Write (10) - Sectors: 32 - 63 Sense Area: 71 00 03 00 00 00 00 0A 00 00 00 00 0C 00 00 00 00 00 Interpretation: Write Error Edited September 5, 2012 by pilpero
LIGHTNING UK! Posted September 5, 2012 Posted September 5, 2012 The solution would be to use better discs or a drive that has no problem with the 'MBI 01RG40' ones. Your version of ImgBurn is out of date btw.
pilpero Posted September 5, 2012 Author Posted September 5, 2012 (edited) Yeah I know, but it fails also on the newer version. Tested some other versions too. Wouldn't there be a fw update for the drive or something? Edited September 5, 2012 by pilpero
LIGHTNING UK! Posted September 5, 2012 Posted September 5, 2012 A new program version can't fix a problem between your drive and the media, that wasn't why I mentioned that your one was out of date. Sorry but there has only ever been a SB00 firmware release for your drive - and that's the one you're running now.
Recommended Posts