ToxicMan Posted April 29, 2012 Posted April 29, 2012 Been scouring the boards, can't find a solution. Pro help needed here please. trying to burn some bluray pron Using Verbatim BD-R 25gig 6x LTH type blu-ray discs. Get the following log from a failed burn. Drive is an HP (LG) BH20L with latest firmware, B57C Much thanks in advance ------------------ I 18:04:10 ImgBurn Version 2.5.4.0 started! I 18:04:10 Microsoft Windows 7 Professional x64 Edition (6.1, Build 7601 : Service Pack 1) I 18:04:10 Total Physical Memory: 9,428,064 KB - Available: 5,816,832 KB I 18:04:10 Initialising SPTI... I 18:04:10 Searching for SCSI / ATAPI devices... I 18:04:10 -> Drive 1 - Info: hp BD-RE BH20L B57C (F:) (ATAPI) I 18:04:10 -> Drive 2 - Info: ELBY CLONEDRIVE 1.4 (G:) (SCSI) I 18:04:10 Found 1 BD-ROM/HD DVD-ROM and 1 BD-RE! I 18:09:36 Operation Started! I 18:09:36 Source File: E:\temp_dvd\THE_CRIB_BD\THE_CRIB_BD.iso I 18:09:36 Source File Sectors: 6,502,592 (MODE1/2048) I 18:09:36 Source File Size: 13,317,308,416 bytes I 18:09:36 Source File Volume Identifier: THE_CRIB_BD I 18:09:36 Source File Volume Set Identifier: 0250f373 BDROM I 18:09:36 Source File Implementation Identifier: Developer I 18:09:36 Source File File System(s): UDF (2.50) I 18:09:36 Destination Device: [1:2:0] hp BD-RE BH20L B57C (F:) (ATAPI) I 18:09:36 Destination Media Type: BD-R (Disc ID: VERBAT-IMu-000) (Speeds: 2x) I 18:09:36 Destination Media Sectors: 12,219,392 I 18:09:36 Write Mode: BD I 18:09:36 Write Type: DAO I 18:09:36 Write Speed: 1x I 18:09:36 BD-R Verify Not Required: Yes I 18:09:36 Link Size: Auto I 18:09:36 Lock Volume: Yes I 18:09:36 Test Mode: No I 18:09:36 OPC: No I 18:09:36 BURN-Proof: Enabled W 18:09:36 Write Speed Miscompare! - Wanted: 4,496 KB/s (1x), Got: 8,991 KB/s (2x) I 18:10:22 Filling Buffer... (40 MB) I 18:10:23 Writing LeadIn... W 18:12:23 Failed to Write Sectors 0 - 31 - Reason: No Seek Complete W 18:12:23 Retrying (1 of 20)... I 18:12:23 Writing LeadIn... W 18:12:52 Failed to Write Sectors 960 - 991 - Reason: Program Memory Area Update Failure W 18:12:52 Retrying (1 of 20)... W 18:12:52 Retry Failed - Reason: Invalid Address For Write W 18:12:52 Retrying (2 of 20)... W 18:12:52 Retry Failed - Reason: Invalid Address For Write W 18:12:52 Retrying (3 of 20)... W 18:12:52 Retry Failed - Reason: Invalid Address For Write W 18:12:52 Retrying (4 of 20)... W 18:12:52 Retry Failed - Reason: Invalid Address For Write W 18:12:52 Retrying (5 of 20)... W 18:12:52 Retry Failed - Reason: Invalid Address For Write W 18:12:52 Retrying (6 of 20)... W 18:12:52 Retry Failed - Reason: Invalid Address For Write W 18:12:52 Retrying (7 of 20)... W 18:12:52 Retry Failed - Reason: Invalid Address For Write W 18:12:52 Retrying (8 of 20)... W 18:12:52 Retry Failed - Reason: Invalid Address For Write W 18:12:52 Retrying (9 of 20)... W 18:12:52 Retry Failed - Reason: Invalid Address For Write W 18:12:52 Retrying (10 of 20)... W 18:12:52 Retry Failed - Reason: Invalid Address For Write W 18:12:52 Retrying (11 of 20)... W 18:12:52 Retry Failed - Reason: Invalid Address For Write W 18:12:52 Retrying (12 of 20)... W 18:12:52 Retry Failed - Reason: Invalid Address For Write W 18:12:52 Retrying (13 of 20)... W 18:12:52 Retry Failed - Reason: Invalid Address For Write W 18:12:52 Retrying (14 of 20)... W 18:12:52 Retry Failed - Reason: Invalid Address For Write W 18:12:52 Retrying (15 of 20)... W 18:12:52 Retry Failed - Reason: Invalid Address For Write W 18:12:52 Retrying (16 of 20)... W 18:12:52 Retry Failed - Reason: Invalid Address For Write W 18:12:52 Retrying (17 of 20)... W 18:12:52 Retry Failed - Reason: Invalid Address For Write W 18:12:52 Retrying (18 of 20)... W 18:12:52 Retry Failed - Reason: Invalid Address For Write W 18:12:52 Retrying (19 of 20)... W 18:12:52 Retry Failed - Reason: Invalid Address For Write W 18:12:52 Retrying (20 of 20)... W 18:12:52 Retry Failed - Reason: Invalid Address For Write W 18:17:51 Retrying (21)... W 18:17:51 Retry Failed - Reason: Invalid Address For Write W 18:17:52 Retrying (22)... W 18:17:52 Retry Failed - Reason: Invalid Address For Write E 18:17:53 Failed to Write Sectors 960 - 991 - Reason: Program Memory Area Update Failure E 18:17:53 Next Writable Address: 0 I 18:17:53 Synchronising Cache... W 18:17:57 User opted to skip the 'Close Track/Session/Disc' functions. E 18:17:57 Failed to Write Image! E 18:17:57 Operation Failed! - Duration: 00:08:20 I 18:17:57 Average Write Rate: 0 KB/s (0.0x) - Maximum Write Rate: 0 KB/s (0.0x)
LIGHTNING UK! Posted April 29, 2012 Posted April 29, 2012 For starters, update ImgBurn. There's no reason to be using such an old version. 'VERBAT-IMu-000' is LTH media, you may have more luck with the standard HTL stuff. Yes, LTH is probably a bit cheaper but if your drive doesn't really like it (errors out / burns coasters), it's actually infinitely more expensive!
ToxicMan Posted April 30, 2012 Author Posted April 30, 2012 Thanks so much for the super fast reply! Very much appreciated... I thought I had loaded the latest version just yesterday. Guess not. I updated and here's the resulting log. Burn seemed to have worked, but disc wouldn't finalize. -------------------- I 20:14:28 ImgBurn Version 2.5.7.0 started! I 20:14:28 Microsoft Windows 7 Professional x64 Edition (6.1, Build 7601 : Service Pack 1) I 20:14:28 Total Physical Memory: 9,428,064 KB - Available: 5,670,224 KB I 20:14:29 Initialising SPTI... I 20:14:29 Searching for SCSI / ATAPI devices... I 20:14:29 -> Drive 1 - Info: hp BD-RE BH20L B57C (F:) (ATAPI) I 20:14:29 -> Drive 2 - Info: ELBY CLONEDRIVE 1.4 (G:) (SCSI) I 20:14:29 Found 1 BD-ROM/HD DVD-ROM and 1 BD-RE! I 20:17:08 Operation Started! I 20:17:08 Source File: E: emp_dvd\THE_CRIB_BD\THE_CRIB_BD.iso I 20:17:08 Source File Sectors: 6,502,592 (MODE1/2048) I 20:17:08 Source File Size: 13,317,308,416 bytes I 20:17:08 Source File Volume Identifier: THE_CRIB_BD I 20:17:08 Source File Volume Set Identifier: 0250f373 BDROM I 20:17:08 Source File Implementation Identifier: Developer I 20:17:08 Source File File System(s): UDF (2.50) I 20:17:08 Destination Device: [1:2:0] hp BD-RE BH20L B57C (F:) (ATAPI) I 20:17:08 Destination Media Type: BD-R (Disc ID: VERBAT-IMu-000) I 20:17:08 Destination Media Supported Write Speeds: 2x I 20:17:08 Destination Media Sectors: 12,219,392 I 20:17:08 Write Mode: BD I 20:17:08 Write Type: DAO I 20:17:08 Write Speed: MAX I 20:17:08 Hardware Defect Management Active: No I 20:17:08 BD-R Verify Not Required: Yes I 20:17:08 Link Size: Auto I 20:17:08 Lock Volume: Yes I 20:17:08 Test Mode: No I 20:17:08 OPC: No I 20:17:08 BURN-Proof: Enabled I 20:17:08 Write Speed Successfully Set! - Effective: 8,991 KB/s (2x) I 20:19:21 Filling Buffer... (80 MB) I 20:19:22 Writing LeadIn... W 20:21:18 Failed to Write Sectors 0 - 31 - Reason: Program Memory Area Update Failure W 20:21:18 Retrying (1 of 20)... I 20:21:18 Writing LeadIn... I 20:21:19 Writing Session 1 of 1... (1 Track, LBA: 0 - 6502591) I 20:21:19 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 6502591) I 20:46:01 Synchronising Cache... I 20:47:52 Closing Track... I 20:47:53 Finalising Disc... W 20:49:46 Finalise Disc Failed! - Reason: Cannot Write Medium - Incompatible Format W 20:49:46 Retrying (1 of 3)... W 20:49:46 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 20:49:46 Retrying (2 of 3)... W 20:49:46 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 20:49:46 Retrying (3 of 3)... W 20:49:46 Retry Failed - Reason: Cannot Write Medium - Incompatible Format E 21:19:18 Finalise Disc Failed! - Reason: Cannot Write Medium - Incompatible Format E 21:19:18 Failed to Write Image! I 21:19:18 Exporting Graph Data... I 21:19:18 Graph Data File: C:\Users\Doug\AppData\Roaming\ImgBurn\Graph Data Files\hp_BD-RE_BH20L_B57C_SUNDAY-APRIL-29-2012_8-17_PM_VERBAT-IMu-000_MAX.ibg I 21:19:18 Export Successfully Completed! E 21:19:18 Operation Failed! - Duration: 01:02:10 I 21:19:18 Average Write Rate: 8,781 KB/s (2.0x) - Maximum Write Rate: 9,070 KB/s (2.0x)
LIGHTNING UK! Posted April 30, 2012 Posted April 30, 2012 Please refer to my previous post. Updating wasn't going to fix the issue and I knew that (but it needed doing anyway). Your drive has an issue with the discs you're using.
Recommended Posts