mlemaire Posted March 30, 2010 Share Posted March 30, 2010 I've reproduced the log file...any insight would be greatly appreciated. My first thought is that I burned it at too high a speed, but who knows? I've done 25GB discs with no problems so far, but this was my first 50GB one. Thanks! I 14:27:57 ImgBurn Version 2.5.1.0 started! I 14:27:57 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7600) I 14:27:57 Total Physical Memory: 3,013,112 KB - Available: 1,722,964 KB W 14:27:57 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! I 14:27:57 Initialising SPTI... I 14:27:57 Searching for SCSI / ATAPI devices... I 14:27:57 -> Drive 1 - Info: ELBY CLONEDRIVE 1.4 (H:) (SCSI) I 14:27:57 -> Drive 2 - Info: HL-DT-ST BD-RE WH08LS20 2.00 (G:) (ATA) I 14:27:57 -> Drive 3 - Info: TSSTcorp CDDVDW TS-H653R 0301 (E:) (ATA) I 14:27:57 Found 1 DVD±RW/RAM, 1 BD-ROM/HD DVD-ROM and 1 BD-RE! I 14:28:35 Operation Started! I 14:28:35 Source File: F:\ML's Stuff\MOVIES\BD\TOY_STORY.iso I 14:28:35 Source File Sectors: 21,147,744 (MODE1/2048) I 14:28:35 Source File Size: 43,310,579,712 bytes I 14:28:35 Source File Volume Identifier: TOY_STORY I 14:28:35 Source File Volume Set Identifier: 8CC56996659838C9_VOLUME_SET_ID I 14:28:35 Source File Application Identifier: APPLICATION_ID I 14:28:35 Source File Implementation Identifier: IMPLEMENTATION_ID I 14:28:35 Source File File System(s): UDF (2.50) I 14:28:35 Destination Device: [1:1:0] HL-DT-ST BD-RE WH08LS20 2.00 (G:) (ATA) I 14:28:35 Destination Media Type: BD-R (Disc ID: VERBAT-IMb-00) (Speeds: 2x, 4x) I 14:28:35 Destination Media Sectors: 24,438,784 I 14:28:35 Write Mode: BD I 14:28:35 Write Type: DAO I 14:28:35 Write Speed: MAX I 14:28:35 BD-R Verify Not Required: Yes I 14:28:35 Link Size: Auto I 14:28:35 Lock Volume: Yes I 14:28:35 Test Mode: No I 14:28:35 OPC: No I 14:28:35 BURN-Proof: Enabled I 14:28:35 Write Speed Successfully Set! - Effective: 17,982 KB/s (4x) I 14:29:02 Filling Buffer... (40 MB) I 14:29:05 Writing LeadIn... I 14:29:05 Writing Session 1 of 1... (1 Track, LBA: 0 - 21147743) I 14:29:05 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 21147743) W 14:51:46 Failed to Write Sectors 11946368 - 11946399 - Reason: Write Error W 14:51:46 Retrying (1 of 20)... W 14:51:46 Retry Failed - Reason: Invalid Address For Write W 14:51:46 Retrying (2 of 20)... W 14:51:46 Retry Failed - Reason: Invalid Address For Write W 14:51:46 Retrying (3 of 20)... W 14:51:46 Retry Failed - Reason: Invalid Address For Write W 14:51:46 Retrying (4 of 20)... W 14:51:46 Retry Failed - Reason: Invalid Address For Write W 14:51:46 Retrying (5 of 20)... W 14:51:46 Retry Failed - Reason: Invalid Address For Write W 14:51:46 Retrying (6 of 20)... W 14:51:46 Retry Failed - Reason: Invalid Address For Write W 14:51:46 Retrying (7 of 20)... W 14:51:46 Retry Failed - Reason: Invalid Address For Write W 14:51:46 Retrying (8 of 20)... W 14:51:46 Retry Failed - Reason: Invalid Address For Write W 14:51:46 Retrying (9 of 20)... W 14:51:46 Retry Failed - Reason: Invalid Address For Write W 14:51:46 Retrying (10 of 20)... W 14:51:46 Retry Failed - Reason: Invalid Address For Write W 14:51:46 Retrying (11 of 20)... W 14:51:46 Retry Failed - Reason: Invalid Address For Write W 14:51:46 Retrying (12 of 20)... W 14:51:46 Retry Failed - Reason: Invalid Address For Write W 14:51:46 Retrying (13 of 20)... W 14:51:46 Retry Failed - Reason: Invalid Address For Write W 14:51:46 Retrying (14 of 20)... W 14:51:46 Retry Failed - Reason: Invalid Address For Write W 14:51:46 Retrying (15 of 20)... W 14:51:46 Retry Failed - Reason: Invalid Address For Write W 14:51:46 Retrying (16 of 20)... W 14:51:46 Retry Failed - Reason: Invalid Address For Write W 14:51:46 Retrying (17 of 20)... W 14:51:46 Retry Failed - Reason: Invalid Address For Write W 14:51:46 Retrying (18 of 20)... W 14:51:46 Retry Failed - Reason: Invalid Address For Write W 14:51:46 Retrying (19 of 20)... W 14:51:46 Retry Failed - Reason: Invalid Address For Write W 14:51:46 Retrying (20 of 20)... W 14:51:46 Retry Failed - Reason: Invalid Address For Write W 15:24:59 Retrying (21)... W 15:24:59 Retry Failed - Reason: Invalid Address For Write W 15:25:00 Retrying (22)... W 15:25:00 Retry Failed - Reason: Invalid Address For Write W 15:25:01 Retrying (23)... W 15:25:01 Retry Failed - Reason: Invalid Address For Write W 15:25:02 Retrying (24)... W 15:25:02 Retry Failed - Reason: Invalid Address For Write W 15:25:02 Retrying (25)... W 15:25:02 Retry Failed - Reason: Invalid Address For Write W 15:25:03 Retrying (26)... W 15:25:03 Retry Failed - Reason: Invalid Address For Write W 15:25:03 Retrying (27)... W 15:25:03 Retry Failed - Reason: Invalid Address For Write W 15:25:03 Retrying (28)... W 15:25:03 Retry Failed - Reason: Invalid Address For Write W 15:25:03 Retrying (29)... W 15:25:03 Retry Failed - Reason: Invalid Address For Write W 15:25:04 Retrying (30)... W 15:25:04 Retry Failed - Reason: Invalid Address For Write W 15:25:04 Retrying (31)... W 15:25:04 Retry Failed - Reason: Invalid Address For Write E 15:25:05 Failed to Write Sectors 11946368 - 11946399 - Reason: Write Error E 15:25:05 Next Writable Address: 0 I 15:25:05 Synchronising Cache... I 15:25:09 Closing Track... I 15:25:14 Finalising Disc... E 15:25:34 Failed to Write Image! I 15:25:34 Exporting Graph Data... I 15:25:34 Graph Data File: C:\Users\MJL\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_WH08LS20_2.00_MARCH-30-10_2-28_PM_VERBAT-IMb-00_MAX.ibg I 15:25:34 Export Successfully Completed! E 15:25:34 Operation Failed! - Duration: 00:56:58 I 15:25:34 Average Write Rate: 7,113 KB/s (1.6x) - Maximum Write Rate: 18,188 KB/s (4.0x) ImgBurn (toy story BD).log Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted March 30, 2010 Share Posted March 30, 2010 Your drive just bombed out during the burn, nothing you can really do about it I'm afraid. DL discs are harder to burn that SL ones. Unless you've already burnt a few (and they've all failed), there's nothing to say this wasn't a 1 off (shame it happened to be your first!). By all means give the 2x write speed a go and see if it does any better. You could also try turning off the BD-R verify not required option in the settings - but that might slow the write speed down even more. Still, it's better to go slow and have a working burn, isn't it?! Link to comment Share on other sites More sharing options...
mlemaire Posted March 30, 2010 Author Share Posted March 30, 2010 Thanks for the quick reply. I'm glad to know it's simply a "luck of the draw" thing and not something more sinister (haha). I'll do it slower (just to ease my mind) and hope it works. Has to be a DL disc though, of course. Your drive just bombed out during the burn, nothing you can really do about it I'm afraid. DL discs are harder to burn that SL ones. Unless you've already burnt a few (and they've all failed), there's nothing to say this wasn't a 1 off (shame it happened to be your first!). By all means give the 2x write speed a go and see if it does any better. You could also try turning off the BD-R verify not required option in the settings - but that might slow the write speed down even more. Still, it's better to go slow and have a working burn, isn't it?! Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted March 30, 2010 Share Posted March 30, 2010 You could always mess around on a BD-RE DL if you're testing the water so to speak. Link to comment Share on other sites More sharing options...
Recommended Posts