aoidxc Posted April 30, 2012 Share Posted April 30, 2012 (edited) Hi again I began to have problems trying to burning bluray discs. I'm not sure if it's a writer problem or a bd disc problem. The problem began at the moment i used discs from a new pack. I can't prove it with another disc but seems to be that dvd disc are burning normally. I have no problems reading BD discs. EDIT: I just burn a dvd with no problems at all. Here's the log I 20:41:16 ImgBurn Version 2.5.7.0 started! I 20:41:16 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7600) I 20:41:16 Total Physical Memory: 4.185.144 KB - Available: 3.117.756 KB W 20:41:16 Drive H:\ (FAT32) does not support single files > 4 GB in size. W 20:41:16 Drive I:\ (FAT32) does not support single files > 4 GB in size. I 20:41:16 Initialising SPTI... I 20:41:16 Searching for SCSI / ATAPI devices... I 20:41:17 -> Drive 1 - Info: ATAPI iHAS124 B AL0S (E:) (ATA) I 20:41:17 -> Drive 2 - Info: PIONEER BD-RW BDR-206D 1.04 (D:) (ATA) I 20:41:17 -> Drive 3 - Info: ELBY CLONEDRIVE 1.4 (J:) (SCSI) I 20:41:17 Found 1 DVD±RW/RAM, 1 BD-ROM/HD DVD-ROM and 1 BD-RE! I 20:51:50 Searching for SCSI / ATAPI devices... I 20:51:51 -> Drive 1 - Info: ATAPI iHAS124 B AL0S (E:) (ATA) I 20:51:51 -> Drive 2 - Info: PIONEER BD-RW BDR-206D 1.04 (D:) (ATA) I 20:51:51 -> Drive 3 - Info: ELBY CLONEDRIVE 1.4 (J:) (SCSI) I 20:51:51 Found 1 DVD±RW/RAM, 1 BD-ROM/HD DVD-ROM and 1 BD-RE! I 20:57:44 Searching for SCSI / ATAPI devices... I 20:57:44 -> Drive 1 - Info: ATAPI iHAS124 B AL0S (E:) (ATA) I 20:57:45 -> Drive 2 - Info: PIONEER BD-RW BDR-206D 1.06 (D:) (ATA) I 20:57:45 -> Drive 3 - Info: ELBY CLONEDRIVE 1.4 (J:) (SCSI) I 20:57:45 Found 1 DVD±RW/RAM, 1 BD-ROM/HD DVD-ROM and 1 BD-RE! I 20:59:01 Operation Started! I 20:59:01 Source File: G:\WARRIOR.ISO I 20:59:01 Source File Sectors: 10.713.440 (MODE1/2048) I 20:59:01 Source File Size: 21.941.125.120 bytes I 20:59:01 Source File Volume Identifier: WARRIOR I 20:59:01 Source File Volume Set Identifier: 409D9B4200A3781B I 20:59:01 Source File Application Identifier: ImgBurn v2.5.7.0 I 20:59:01 Source File Implementation Identifier: ImgBurn I 20:59:01 Source File File System(s): UDF (2.50) I 20:59:01 Destination Device: [0:0:0] PIONEER BD-RW BDR-206D 1.06 (D:) (ATA) I 20:59:01 Destination Media Type: BD-R (Disc ID: RITEK-BR2-000) I 20:59:01 Destination Media Supported Write Speeds: 2x, 4x, 6x, 8x, 10x I 20:59:01 Destination Media Sectors: 12.219.392 I 20:59:01 Write Mode: BD I 20:59:01 Write Type: DAO I 20:59:01 Write Speed: 2x I 20:59:01 Hardware Defect Management Active: No I 20:59:01 BD-R Verify Not Required: Yes I 20:59:01 Link Size: Auto I 20:59:01 Lock Volume: Yes I 20:59:01 Test Mode: No I 20:59:01 OPC: No I 20:59:01 BURN-Proof: Enabled I 20:59:02 Write Speed Successfully Set! - Effective: 8.990 KB/s (2x) I 20:59:02 Advanced Settings - Optimal Writing Speed: No I 20:59:02 Filling Buffer... (80 MB) I 20:59:03 Writing LeadIn... W 20:59:15 Failed to Write Sectors 832 - 863 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x03) W 20:59:15 Retrying (1 of 20)... W 20:59:15 Retry Failed - Reason: Invalid Address For Write W 20:59:15 Retrying (2 of 20)... W 20:59:15 Retry Failed - Reason: Invalid Address For Write W 20:59:15 Retrying (3 of 20)... W 20:59:15 Retry Failed - Reason: Invalid Address For Write W 20:59:15 Retrying (4 of 20)... W 20:59:15 Retry Failed - Reason: Invalid Address For Write W 20:59:15 Retrying (5 of 20)... W 20:59:15 Retry Failed - Reason: Invalid Address For Write W 20:59:15 Retrying (6 of 20)... W 20:59:15 Retry Failed - Reason: Invalid Address For Write W 20:59:15 Retrying (7 of 20)... W 20:59:15 Retry Failed - Reason: Invalid Address For Write W 20:59:15 Retrying (8 of 20)... W 20:59:15 Retry Failed - Reason: Invalid Address For Write W 20:59:15 Retrying (9 of 20)... W 20:59:15 Retry Failed - Reason: Invalid Address For Write W 20:59:15 Retrying (10 of 20)... W 20:59:15 Retry Failed - Reason: Invalid Address For Write W 20:59:15 Retrying (11 of 20)... W 20:59:15 Retry Failed - Reason: Invalid Address For Write W 20:59:15 Retrying (12 of 20)... W 20:59:16 Retry Failed - Reason: Invalid Address For Write W 20:59:16 Retrying (13 of 20)... W 20:59:16 Retry Failed - Reason: Invalid Address For Write W 20:59:16 Retrying (14 of 20)... W 20:59:16 Retry Failed - Reason: Invalid Address For Write W 20:59:16 Retrying (15 of 20)... W 20:59:16 Retry Failed - Reason: Invalid Address For Write W 20:59:16 Retrying (16 of 20)... W 20:59:16 Retry Failed - Reason: Invalid Address For Write W 20:59:16 Retrying (17 of 20)... W 20:59:16 Retry Failed - Reason: Invalid Address For Write W 20:59:16 Retrying (18 of 20)... W 20:59:16 Retry Failed - Reason: Invalid Address For Write W 20:59:16 Retrying (19 of 20)... W 20:59:16 Retry Failed - Reason: Invalid Address For Write W 20:59:16 Retrying (20 of 20)... W 20:59:16 Retry Failed - Reason: Invalid Address For Write E 20:59:43 Failed to Write Sectors 832 - 863 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x03) E 20:59:43 Next Writable Address: 0 I 20:59:43 Synchronising Cache... W 20:59:46 User opted to skip the 'Close Track/Session/Disc' functions. E 20:59:46 Failed to Write Image! E 20:59:46 Operation Failed! - Duration: 00:00:44 I 20:59:46 Average Write Rate: 0 KB/s (0.0x) - Maximum Write Rate: 0 KB/s (0.0x) Edited April 30, 2012 by aoidxc Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted April 30, 2012 Share Posted April 30, 2012 Try burning at a faster speed. The drive lists 2x, 4x, 6x, 8x, 10x as all being 'supported' speeds. If 2x doesn't work in reality, try one of the others. Service Pack 1 is out for Windows 7. Link to comment Share on other sites More sharing options...
aoidxc Posted April 30, 2012 Author Share Posted April 30, 2012 It worked before with same discs burning at 2x. tried burning at 6x with same error. Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted April 30, 2012 Share Posted April 30, 2012 On a brand new disc I hope, not one that had already failed. If it won't burn those discs ('RITEK-BR2-000') without erroring out, try some others. This is purely a problem between the drive, its firmware and the media you're using. ImgBurn is simply telling you the error reported by the drive. Link to comment Share on other sites More sharing options...
aoidxc Posted April 30, 2012 Author Share Posted April 30, 2012 I bought another brand of discs "verbatim VERBAT-IMw-000" and burn it perfectly i guess the problem is with that pack of 25 BD-R RIDATA "RITEK-BR2-000" I'm going to return that pack and getting a new one Here's the log of the verbatim burnt I 10:40:44 ImgBurn Version 2.5.7.0 started! I 10:40:44 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7601 : Service Pack 1) I 10:40:44 Total Physical Memory: 4.185.144 KB - Available: 2.969.612 KB W 10:40:44 Drive H:\ (FAT32) does not support single files > 4 GB in size. W 10:40:44 Drive I:\ (FAT32) does not support single files > 4 GB in size. I 10:40:44 Initialising SPTI... I 10:40:44 Searching for SCSI / ATAPI devices... I 10:40:45 -> Drive 1 - Info: ATAPI iHAS124 B AL0S (E:) (ATA) I 10:40:45 -> Drive 2 - Info: PIONEER BD-RW BDR-206D 1.06 (D:) (ATA) I 10:40:45 -> Drive 3 - Info: ELBY CLONEDRIVE 1.4 (J:) (SCSI) I 10:40:45 Found 1 DVD±RW/RAM, 1 BD-ROM/HD DVD-ROM and 1 BD-RE! I 10:41:46 Operation Started! I 10:41:46 Source File: G:\WARRIOR.ISO I 10:41:46 Source File Sectors: 10.713.440 (MODE1/2048) I 10:41:46 Source File Size: 21.941.125.120 bytes I 10:41:46 Source File Volume Identifier: WARRIOR I 10:41:46 Source File Volume Set Identifier: 409D9B4200A3781B I 10:41:46 Source File Application Identifier: ImgBurn v2.5.7.0 I 10:41:46 Source File Implementation Identifier: ImgBurn I 10:41:46 Source File File System(s): UDF (2.50) I 10:41:46 Destination Device: [0:0:0] PIONEER BD-RW BDR-206D 1.06 (D:) (ATA) I 10:41:46 Destination Media Type: BD-R (Disc ID: VERBAT-IMw-000) I 10:41:46 Destination Media Supported Write Speeds: 2x I 10:41:46 Destination Media Sectors: 12.219.392 I 10:41:46 Write Mode: BD I 10:41:46 Write Type: DAO I 10:41:46 Write Speed: 2x I 10:41:46 Hardware Defect Management Active: No I 10:41:46 BD-R Verify Not Required: Yes I 10:41:46 Link Size: Auto I 10:41:46 Lock Volume: Yes I 10:41:46 Test Mode: No I 10:41:46 OPC: No I 10:41:46 BURN-Proof: Enabled I 10:41:46 Write Speed Successfully Set! - Effective: 8.990 KB/s (2x) I 10:41:46 Advanced Settings - Optimal Writing Speed: No I 10:41:47 Filling Buffer... (80 MB) I 10:41:48 Writing LeadIn... I 10:42:00 Writing Session 1 of 1... (1 Track, LBA: 0 - 10713439) I 10:42:00 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 10713439) I 11:23:25 Synchronising Cache... I 11:23:26 Closing Track... I 11:23:27 Finalising Disc... I 11:23:37 Exporting Graph Data... I 11:23:37 Graph Data File: C:\Users\AOIOBSCURE\AppData\Roaming\ImgBurn\Graph Data Files\PIONEER_BD-RW_BDR-206D_1.06_LUNES-30-DE-ABRIL-DE-2012_10-41_a.m._VERBAT-IMw-000_2x.ibg I 11:23:37 Export Successfully Completed! I 11:23:37 Operation Successfully Completed! - Duration: 00:41:50 I 11:23:37 Average Write Rate: 8.625 KB/s (1.9x) - Maximum Write Rate: 9.278 KB/s (2.1x) Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted April 30, 2012 Share Posted April 30, 2012 I see you've gone for the cheaper LTH version BD-R discs there. If you run into problems with those, consider buying the standard (and unfortunately more expensive) HTL ones instead. Link to comment Share on other sites More sharing options...
aoidxc Posted April 30, 2012 Author Share Posted April 30, 2012 Thank you for all your answers LIGHTNING I got a new pack of RITEK-BR2-000 and are working perfectly. That concludes that the problem was the media itself. I know that i'm not using top quality discs but in my country is difficult to find better ones so i have to take the risks. Thanks for your support Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted April 30, 2012 Share Posted April 30, 2012 Cool, glad you got it sorted Link to comment Share on other sites More sharing options...
Recommended Posts