the_at Posted May 2, 2014 Share Posted May 2, 2014 Hey everyone, I usually burn my BD25 Blurays with ImgBurn without problems. Recently some disc didnt finish successfully. I do not know why. Maybe someone here can help me? This is the ImgBurn log. Many thanks in advance! Cheers, the_atI 19:33:22 ImgBurn Version 2.5.7.0 started!I 19:33:22 Microsoft Windows 7 Professional x64 Edition (6.1, Build 7601 : Service Pack 1)I 19:33:22 Total Physical Memory: 4.191.432 KB - Available: 2.787.208 KBI 19:33:22 Initialising SPTI...I 19:33:22 Searching for SCSI / ATAPI devices...I 19:33:22 -> Drive 1 - Info: DTSOFT BDROM 1.05 (F (Virtual)I 19:33:24 -> Drive 2 - Info: Optiarc BD RW BD-5730S 1.02 (D (SATA)I 19:33:24 Found 1 BD-ROM and 1 BD-RE!I 19:34:39 Operation Started!I 19:34:40 Source File: E:\Bluray\Movie.isoI 19:34:40 Source File Sectors: 12.139.040 (MODE1/2048)I 19:34:40 Source File Size: 24.860.753.920 bytesI 19:34:40 Source File Volume Identifier: MovieI 19:34:40 Source File Volume Set Identifier: 449DA9E000B93893I 19:34:40 Source File Application Identifier: ImgBurn v2.5.7.0I 19:34:40 Source File Implementation Identifier: ImgBurnI 19:34:40 Source File File System(s): UDF (2.50)I 19:34:40 Destination Device: [1:0:0] Optiarc BD RW BD-5730S 1.02 (D (SATA)I 19:34:40 Destination Media Type: BD-R (Disc ID: RITEK-BR3-000)I 19:34:40 Destination Media Supported Write Speeds: 2x; 4xI 19:34:40 Destination Media Sectors: 12.219.392I 19:34:40 Write Mode: BDI 19:34:40 Write Type: DAOI 19:34:40 Write Speed: 2xI 19:34:40 Hardware Defect Management Active: NoI 19:34:40 BD-R Verify Not Required: YesI 19:34:40 Link Size: AutoI 19:34:40 Lock Volume: YesI 19:34:40 Test Mode: NoI 19:34:40 OPC: NoI 19:34:40 BURN-Proof: EnabledI 19:34:40 Write Speed Successfully Set! - Effective: 8.991 KB/s (2x)I 19:35:05 Filling Buffer... (80 MB)I 19:35:07 Writing LeadIn...I 19:35:08 Writing Session 1 of 1... (1 Track, LBA: 0 - 12139039)I 19:35:08 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 12139039)W 20:11:18 Failed to Write Sectors 9383712 - 9383743 - Reason: Write ErrorW 20:11:18 Retrying (1 of 20)...W 20:11:18 Retry Failed - Reason: Invalid Address For WriteW 20:11:18 Retrying (2 of 20)...W 20:11:18 Retry Failed - Reason: Invalid Address For WriteW 20:11:18 Retrying (3 of 20)...W 20:11:18 Retry Failed - Reason: Invalid Address For WriteW 20:11:18 Retrying (4 of 20)...W 20:11:18 Retry Failed - Reason: Invalid Address For WriteW 20:11:18 Retrying (5 of 20)...W 20:11:18 Retry Failed - Reason: Invalid Address For WriteW 20:11:18 Retrying (6 of 20)...W 20:11:18 Retry Failed - Reason: Invalid Address For WriteW 20:11:18 Retrying (7 of 20)...W 20:11:18 Retry Failed - Reason: Invalid Address For WriteW 20:11:18 Retrying (8 of 20)...W 20:11:18 Retry Failed - Reason: Invalid Address For WriteW 20:11:18 Retrying (9 of 20)...W 20:11:18 Retry Failed - Reason: Invalid Address For WriteW 20:11:18 Retrying (10 of 20)...W 20:11:18 Retry Failed - Reason: Invalid Address For WriteW 20:11:18 Retrying (11 of 20)...W 20:11:18 Retry Failed - Reason: Invalid Address For WriteW 20:11:18 Retrying (12 of 20)...W 20:11:18 Retry Failed - Reason: Invalid Address For WriteW 20:11:18 Retrying (13 of 20)...W 20:11:18 Retry Failed - Reason: Invalid Address For WriteW 20:11:18 Retrying (14 of 20)...W 20:11:18 Retry Failed - Reason: Invalid Address For WriteW 20:11:18 Retrying (15 of 20)...W 20:11:18 Retry Failed - Reason: Invalid Address For WriteW 20:11:18 Retrying (16 of 20)...W 20:11:18 Retry Failed - Reason: Invalid Address For WriteW 20:11:18 Retrying (17 of 20)...W 20:11:18 Retry Failed - Reason: Invalid Address For WriteW 20:11:18 Retrying (18 of 20)...W 20:11:18 Retry Failed - Reason: Invalid Address For WriteW 20:11:18 Retrying (19 of 20)...W 20:11:18 Retry Failed - Reason: Invalid Address For WriteW 20:11:18 Retrying (20 of 20)...W 20:11:18 Retry Failed - Reason: Invalid Address For WriteE 20:14:32 Failed to Write Sectors 9383712 - 9383743 - Reason: Write ErrorE 20:14:32 Next Writable Address: 9380736I 20:14:33 Synchronising Cache...W 20:14:36 User opted to skip the 'Close Track/Session/Disc' functions.E 20:14:36 Failed to Write Image!I 20:14:36 Exporting Graph Data...I 20:14:36 Graph Data File: C:\Blabla.ibgI 20:14:36 Export Successfully Completed!E 20:14:36 Operation Failed! - Duration: 00:39:56I 20:14:36 Average Write Rate: 7.938 KB/s (1.8x) - Maximum Write Rate: 9.038 KB/s (2.0x) Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted May 2, 2014 Share Posted May 2, 2014 The first error is the important one and your drive reported a 'Write Error' - so it had some issue burning to the disc. W 20:11:18 Failed to Write Sectors 9383712 - 9383743 - Reason: Write Error Try some other discs if your drive frequently fails to burn those 'RITEK-BR3-000' ones. Link to comment Share on other sites More sharing options...
the_at Posted May 4, 2014 Author Share Posted May 4, 2014 Thanks for the suggestion. What I dont understand is that I burned the "RITEK-BR3-000" ones for ages now without problems (approx. 250 discs). Why does this problem come up right now? Might a firmware update or something help? Is there maybe another explanation for this error? Many thanks again, the_at Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted May 4, 2014 Share Posted May 4, 2014 It could be anything... bad disc, drive no longer in optimal condition (age/dirty)... who knows! You know as much as I do. The drive was asked to write some data to the disc and it failed to do what was asked of it - simply reporting a 'Write Error'. Link to comment Share on other sites More sharing options...
the_at Posted May 21, 2014 Author Share Posted May 21, 2014 Hey, I'm still experiencing this weird problem. Please find a picture of the error attached. Maybe you know more detailed, what kind of error this is and what I can do to solve it...? If the answer is still "who knows...", then thanks anyway! Cheers, the_at Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted May 21, 2014 Share Posted May 21, 2014 That's still exactly the same error with exactly the same drive and media. Link to comment Share on other sites More sharing options...
the_at Posted May 22, 2014 Author Share Posted May 22, 2014 Yes it is. I just thought with some more info you might be able to pinpoint the error. It always happens around 90%. Why would this happen if the drive/laser had a (hardware) defect? I'm just trying to think in every direction... Link to comment Share on other sites More sharing options...
Recommended Posts