jaimedm Posted February 23, 2017 Share Posted February 23, 2017 Hi, I was burning a second copy of a 17Gb ISO on a BD-25 disc. The previous burn of the same ISO on the same discs went through with no problem at all, and the disc plays fine in my computer and PS3. however, I went to burn another copy of it and it stopped midway through. I've burnt several ISOs on these same discs in the last months, and this is the first one that fails. Here's the Log: I 23:20:05 ImgBurn Version 2.5.8.0 started! I 23:20:05 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7601 : Service Pack 1) I 23:20:05 Total Physical Memory: 8.370.296 KiB - Available: 5.285.848 KiB W 23:20:05 Duplex Secure's SPTD driver can have a detrimental effect on drive performance. I 23:20:05 Initialising SPTI... I 23:20:05 Searching for SCSI / ATAPI devices... I 23:20:06 -> Drive 1 - Info: DTSOFT BDROM 1.05 (H:) (Virtual) I 23:20:06 -> Drive 2 - Info: DTSOFT BDROM 1.05 (J:) (Virtual) I 23:20:06 -> Drive 3 - Info: HL-DT-ST BD-RE BH16NS55 1.02 (G:) (ATA) I 23:20:07 -> Drive 4 - Info: HL-DT-ST DVDRAM GH24NS95 RN01-33 (F:) (ATA) I 23:20:07 Found 1 DVD±RW/RAM, 2 BD-ROMs and 1 BD-RE XL! I 23:20:26 Operation Started! I 23:20:26 Source File: I:\Bibliotecas\Alfa y Omega Blu-Ray.iso I 23:20:26 Source File Sectors: 9.252.416 (MODE1/2048) I 23:20:26 Source File Size: 18.948.947.968 bytes I 23:20:26 Source File Volume Identifier: Alfa y Omega I 23:20:26 Source File Volume Set Identifier: 4A54B681008D2D68 I 23:20:26 Source File Application Identifier: ImgBurn v2.5.8.0 I 23:20:26 Source File Implementation Identifier: ImgBurn I 23:20:26 Source File File System(s): UDF (2.50) I 23:20:26 Destination Device: [1:1:0] HL-DT-ST BD-RE BH16NS55 1.02 (G:) (ATA) I 23:20:26 Destination Media Type: BD-R (Disc ID: VERBAT-IMu-000) I 23:20:26 Destination Media Supported Write Speeds: 2x; 4x; 6x; 8x I 23:20:26 Destination Media Sectors: 12.219.392 I 23:20:26 Write Mode: BD I 23:20:26 Write Type: DAO I 23:20:26 Write Speed: 2x I 23:20:26 Hardware Defect Management Active: No I 23:20:26 BD-R Verify Not Required: Yes I 23:20:26 Link Size: Auto I 23:20:26 Lock Volume: Yes I 23:20:26 Test Mode: No I 23:20:26 OPC: No I 23:20:26 BURN-Proof: Enabled I 23:20:29 Write Speed Successfully Set! - Effective: 8.992 KB/s (2x) I 23:20:46 Filling Buffer... (80 MiB) I 23:20:47 Writing LeadIn... I 23:20:48 Writing Session 1 of 1... (1 Track, LBA: 0 - 9252415) I 23:20:48 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 9252415) W 23:42:15 Failed to Write Sectors 5819104 - 5819135 - Reason: Write Error W 23:42:15 Retrying (1 of 20)... W 23:42:15 Retry Failed - Reason: Invalid Address For Write W 23:42:15 Retrying (2 of 20)... W 23:42:15 Retry Failed - Reason: Invalid Address For Write W 23:42:15 Retrying (3 of 20)... W 23:42:15 Retry Failed - Reason: Invalid Address For Write W 23:42:15 Retrying (4 of 20)... W 23:42:15 Retry Failed - Reason: Invalid Address For Write W 23:42:15 Retrying (5 of 20)... W 23:42:15 Retry Failed - Reason: Invalid Address For Write W 23:42:15 Retrying (6 of 20)... W 23:42:15 Retry Failed - Reason: Invalid Address For Write W 23:42:15 Retrying (7 of 20)... W 23:42:15 Retry Failed - Reason: Invalid Address For Write W 23:42:16 Retrying (8 of 20)... W 23:42:16 Retry Failed - Reason: Invalid Address For Write W 23:42:16 Retrying (9 of 20)... W 23:42:16 Retry Failed - Reason: Invalid Address For Write W 23:42:16 Retrying (10 of 20)... W 23:42:16 Retry Failed - Reason: Invalid Address For Write W 23:42:16 Retrying (11 of 20)... W 23:42:16 Retry Failed - Reason: Invalid Address For Write W 23:42:16 Retrying (12 of 20)... W 23:42:16 Retry Failed - Reason: Invalid Address For Write W 23:42:16 Retrying (13 of 20)... W 23:42:16 Retry Failed - Reason: Invalid Address For Write W 23:42:16 Retrying (14 of 20)... W 23:42:16 Retry Failed - Reason: Invalid Address For Write W 23:42:16 Retrying (15 of 20)... W 23:42:16 Retry Failed - Reason: Invalid Address For Write W 23:42:16 Retrying (16 of 20)... W 23:42:16 Retry Failed - Reason: Invalid Address For Write W 23:42:16 Retrying (17 of 20)... W 23:42:16 Retry Failed - Reason: Invalid Address For Write W 23:42:16 Retrying (18 of 20)... W 23:42:16 Retry Failed - Reason: Invalid Address For Write W 23:42:16 Retrying (19 of 20)... W 23:42:16 Retry Failed - Reason: Invalid Address For Write W 23:42:16 Retrying (20 of 20)... W 23:42:16 Retry Failed - Reason: Invalid Address For Write W 23:42:23 Retrying (21)... W 23:42:23 Retry Failed - Reason: Invalid Address For Write W 23:42:24 Retrying (22)... W 23:42:24 Retry Failed - Reason: Invalid Address For Write E 23:42:24 Failed to Write Sectors 5819104 - 5819135 - Reason: Write Error E 23:42:24 Next Writable Address: 0 I 23:42:24 Synchronising Cache... W 23:42:42 User opted to skip the 'Close Track/Session/Disc' functions. E 23:42:42 Failed to Write Image! I 23:42:42 Exporting Graph Data... I 23:42:42 Graph Data File: C:\Users\Jaime\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_BH16NS55_1.02_JUEVES-23-DE-FEBRERO-DE-2017_23-20_VERBAT-IMu-000_2x.ibg I 23:42:42 Export Successfully Completed! E 23:42:42 Operation Failed! - Duration: 00:22:15 I 23:42:42 Average Write Rate: 8.987 KiB/s (2.0x) - Maximum Write Rate: 9.219 KiB/s (2.1x) Link to comment Share on other sites More sharing options...
dbminter Posted February 23, 2017 Share Posted February 23, 2017 Could be a fluke. Could be a bad disc out of the whole batch. Best bet is to shut down Windows and power off the PC, just to make sure you clear out the drive. Then, after restarting Windows, try burning another disc and see if it happens again. If it does happen again, it could be more than 1 bad disc in that batch. Or it could be your drive has finally given up the ghost. You'll have to then ask yourself how old is this drive. If it's anything older than a year, it would probably need replacing. You're using Verbatim BD-R's so you're not using junk media as far as I can see. I'm not familiar with that exact Disc ID brand of Verbatim BD-R, but it does say VERBAT-IM in it. This would lead me to believe it's decent quality media. Although it could be a fake DID. Why would Verbatim use VERBAT-IM and not VERBATIM? However, I'm not too worried here that you're using junk media. Link to comment Share on other sites More sharing options...
jaimedm Posted February 24, 2017 Author Share Posted February 24, 2017 Hi. Thank you for the answer. The drive is barely 6 months old, and I bought the discs from Amazon Spain, and they appear to be sold by the Verbatim brand itself. I'll try with another disc tomorrow and let's see what happens. Link to comment Share on other sites More sharing options...
dbminter Posted February 24, 2017 Share Posted February 24, 2017 6 months old is not outside the realm of possibility for needing to be replaced. I had a cheap LiteOn, back when they made Blu-Ray burners, that died after 3 months. My last Pioneer died after 7. My general time frame is usually after 9 months a drive needs replacing. Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted February 24, 2017 Share Posted February 24, 2017 They're LTH discs rather than the more reliable HTL ones. Avoid LTH where possible. Link to comment Share on other sites More sharing options...
dbminter Posted February 24, 2017 Share Posted February 24, 2017 Ah, that would explain it. Yes, don't use Low To High. They don't last as long as High To Low and have a higher failure rate of burning. Link to comment Share on other sites More sharing options...
Recommended Posts