DFSchmidt Posted November 22, 2016 Share Posted November 22, 2016 Hi folks, Not sure what's going on here, but I have the latest ImgBurn, just got some BD-R TL discs (100GB apiece, not cheap), and already I have two coasters on my hands. The first I used AWS to burn - when it failed rather early in the process, I thought, OK, I'll burn as slow as possible - 2x was the lowest rated speed, so I did that, but once more, same issue - see log (below). Two points, since I suspect they will be made by someone: I am aware that there is newer firmware than 1.00; that said, 1.01 indicates that it provides "Improved DVD-R Readability", while 1.02 indicates that it provides "M DISC BD R support". I don't see any reason why either one of these should matter as far as burning BD-R TL discs is concerned. I am likewise aware of the warning concerning the SPTD driver; I know it can slow things down, but I have never had it cause write errors like this, nor is there any reason it should. Typically, this sort of thing happens when folks use cheap media; as that is not the case here, I'm at a bit of a loss to understand what's going on. Has anyone else had any experiences burning BD-R TL media, and if so, how has that worked for you? Any tips in general / with this drive (the LG WH16NS40) in particular? Thanks in advance, DS I 00:38:48 ImgBurn Version 2.5.8.0 started!I 00:38:48 Microsoft Windows 8 Professional x64 Edition (6.2, Build 9200)I 00:38:48 Total Physical Memory: 8,387,540 KiB - Available: 5,386,468 KiBW 00:38:48 Duplex Secure's SPTD driver can have a detrimental effect on drive performance.I 00:38:48 Initialising SPTI...I 00:38:48 Searching for SCSI / ATAPI devices...I 00:38:48 -> Drive 1 - Info: HL-DT-ST BD-RE GGW-H20L YL07 (I:) (ATA)I 00:38:48 -> Drive 2 - Info: HL-DT-ST BD-RE WH16NS40 1.00-01 (J:) (ATA)I 00:38:49 -> Drive 3 - Info: _NEC DVD_RW ND-3500AG 2.1A (H:) (ATA)I 00:38:49 Found 1 DVD±RW, 1 BD-RE XL and 1 HD DVD-ROM/BD-RE!I 00:47:48 Operation Started!I 00:47:48 Source File: -==/\/[bUILD IMAGE]\/\==-I 00:47:48 Source File Sectors: 48,817,696 (MODE1/2048)I 00:47:48 Source File Size: 99,978,641,408 bytesI 00:47:48 Source File Volume Identifier: S115I 00:47:48 Source File Volume Set Identifier: 497505F602E8E618I 00:47:48 Source File Application Identifier: ImgBurn v2.5.8.0I 00:47:49 Source File Implementation Identifier: ImgBurnI 00:47:49 Source File File System(s): UDF (1.02)I 00:47:49 Destination Device: [1:0:0] HL-DT-ST BD-RE WH16NS40 1.00 (J:) (ATA)I 00:47:49 Destination Media Type: BD-R (Disc ID: VERBAT-IMk-000)I 00:47:49 Destination Media Supported Write Speeds: 2x, 4x, 6x, 8xI 00:47:49 Destination Media Sectors: 48,878,592I 00:47:49 Write Mode: BDI 00:47:49 Write Type: DAOI 00:47:49 Write Speed: MAXI 00:47:49 Hardware Defect Management Active: NoI 00:47:49 BD-R Verify Not Required: YesI 00:47:49 Link Size: AutoI 00:47:49 Lock Volume: YesI 00:47:49 Test Mode: NoI 00:47:49 OPC: NoI 00:47:49 BURN-Proof: EnabledI 00:47:51 Write Speed Successfully Set! - Effective: 35,968 KB/s (8x)I 00:48:54 Filling Buffer... (80 MiB)I 00:48:55 Writing LeadIn...I 00:49:06 Writing Session 1 of 1... (1 Track, LBA: 0 - 48817695)I 00:49:06 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 48817695)W 01:05:41 Failed to Write Sectors 10503008 - 10503039 - Reason: Write ErrorW 01:05:41 Retrying (1 of 20)...W 01:05:41 Retry Failed - Reason: Invalid Address For WriteW 01:05:41 Retrying (2 of 20)...W 01:05:41 Retry Failed - Reason: Invalid Address For WriteW 01:05:41 Retrying (3 of 20)...W 01:05:41 Retry Failed - Reason: Invalid Address For WriteW 01:05:41 Retrying (4 of 20)...W 01:05:41 Retry Failed - Reason: Invalid Address For WriteW 01:05:41 Retrying (5 of 20)...W 01:05:41 Retry Failed - Reason: Invalid Address For WriteW 01:05:41 Retrying (6 of 20)...W 01:05:41 Retry Failed - Reason: Invalid Address For WriteW 01:05:41 Retrying (7 of 20)...W 01:05:41 Retry Failed - Reason: Invalid Address For WriteW 01:05:41 Retrying (8 of 20)...W 01:05:42 Retry Failed - Reason: Invalid Address For WriteW 01:05:42 Retrying (9 of 20)...W 01:05:42 Retry Failed - Reason: Invalid Address For WriteW 01:05:42 Retrying (10 of 20)...W 01:05:42 Retry Failed - Reason: Invalid Address For WriteW 01:05:42 Retrying (11 of 20)...W 01:05:42 Retry Failed - Reason: Invalid Address For WriteW 01:05:42 Retrying (12 of 20)...W 01:05:42 Retry Failed - Reason: Invalid Address For WriteW 01:05:42 Retrying (13 of 20)...W 01:05:42 Retry Failed - Reason: Invalid Address For WriteW 01:05:42 Retrying (14 of 20)...W 01:05:42 Retry Failed - Reason: Invalid Address For WriteW 01:05:42 Retrying (15 of 20)...W 01:05:42 Retry Failed - Reason: Invalid Address For WriteW 01:05:42 Retrying (16 of 20)...W 01:05:42 Retry Failed - Reason: Invalid Address For WriteW 01:05:42 Retrying (17 of 20)...W 01:05:42 Retry Failed - Reason: Invalid Address For WriteW 01:05:42 Retrying (18 of 20)...W 01:05:42 Retry Failed - Reason: Invalid Address For WriteW 01:05:42 Retrying (19 of 20)...W 01:05:42 Retry Failed - Reason: Invalid Address For WriteW 01:05:42 Retrying (20 of 20)...W 01:05:42 Retry Failed - Reason: Invalid Address For WriteW 01:05:48 Retrying (21)...W 01:05:48 Retry Failed - Reason: Invalid Address For WriteW 01:05:49 Retrying (22)...W 01:05:49 Retry Failed - Reason: Invalid Address For WriteW 01:05:49 Retrying (23)...W 01:05:49 Retry Failed - Reason: Invalid Address For WriteW 01:05:50 Retrying (24)...W 01:05:50 Retry Failed - Reason: Invalid Address For WriteW 01:05:50 Retrying (25)...W 01:05:50 Retry Failed - Reason: Invalid Address For WriteW 01:05:51 Retrying (26)...W 01:05:51 Retry Failed - Reason: Invalid Address For WriteW 01:05:51 Retrying (27)...W 01:05:51 Retry Failed - Reason: Invalid Address For WriteW 01:05:52 Retrying (28)...W 01:05:52 Retry Failed - Reason: Invalid Address For WriteW 01:05:52 Retrying (29)...W 01:05:52 Retry Failed - Reason: Invalid Address For WriteW 01:05:52 Retrying (30)...W 01:05:52 Retry Failed - Reason: Invalid Address For WriteW 01:05:52 Retrying (31)...W 01:05:52 Retry Failed - Reason: Invalid Address For WriteW 01:05:52 Retrying (32)...W 01:05:52 Retry Failed - Reason: Invalid Address For WriteW 01:05:53 Retrying (33)...W 01:05:53 Retry Failed - Reason: Invalid Address For WriteW 01:05:53 Retrying (34)...W 01:05:53 Retry Failed - Reason: Invalid Address For WriteW 01:05:53 Retrying (35)...W 01:05:53 Retry Failed - Reason: Invalid Address For WriteW 01:05:53 Retrying (36)...W 01:05:53 Retry Failed - Reason: Invalid Address For WriteW 01:05:53 Retrying (37)...W 01:05:53 Retry Failed - Reason: Invalid Address For WriteW 01:05:54 Retrying (38)...W 01:05:54 Retry Failed - Reason: Invalid Address For WriteW 01:05:54 Retrying (39)...W 01:05:54 Retry Failed - Reason: Invalid Address For WriteW 01:05:54 Retrying (40)...W 01:05:54 Retry Failed - Reason: Invalid Address For WriteW 01:05:56 Retrying (41)...W 01:05:56 Retry Failed - Reason: Invalid Address For WriteW 01:05:57 Retrying (42)...W 01:05:57 Retry Failed - Reason: Invalid Address For WriteW 01:05:58 Retrying (43)...W 01:05:58 Retry Failed - Reason: Invalid Address For WriteW 01:05:58 Retrying (44)...W 01:05:58 Retry Failed - Reason: Invalid Address For WriteW 01:05:58 Retrying (45)...W 01:05:58 Retry Failed - Reason: Invalid Address For WriteW 01:05:59 Retrying (46)...W 01:05:59 Retry Failed - Reason: Invalid Address For WriteW 01:05:59 Retrying (47)...W 01:05:59 Retry Failed - Reason: Invalid Address For WriteW 01:05:59 Retrying (48)...W 01:05:59 Retry Failed - Reason: Invalid Address For WriteW 01:06:00 Retrying (49)...W 01:06:00 Retry Failed - Reason: Invalid Address For WriteW 01:06:00 Retrying (50)...W 01:06:00 Retry Failed - Reason: Invalid Address For WriteW 01:06:00 Retrying (51)...W 01:06:00 Retry Failed - Reason: Invalid Address For WriteW 01:06:00 Retrying (52)...W 01:06:00 Retry Failed - Reason: Invalid Address For WriteW 01:06:01 Retrying (53)...W 01:06:01 Retry Failed - Reason: Invalid Address For WriteE 01:11:35 Failed to Write Sectors 10503008 - 10503039 - Reason: Write ErrorE 01:11:35 Next Writable Address: 0I 01:11:35 Synchronising Cache...W 01:11:45 User opted to skip the 'Close Track/Session/Disc' functions.E 01:11:45 Failed to Write Image!I 01:11:45 Exporting Graph Data...I 01:11:45 Graph Data File: C:\Users\DFSchmidt\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_WH16NS40_1.00_MONDAY-NOVEMBER-21-2016_12-47_AM_VERBAT-IMk-000_MAX.ibgI 01:11:45 Export Successfully Completed!E 01:11:45 Operation Failed! - Duration: 00:23:56I 01:11:45 Average Write Rate: 15,583 KiB/s (3.5x) - Maximum Write Rate: 26,688 KiB/s (6.1x)I 01:13:37 Operation Started!I 01:13:37 Building Image Tree...I 01:13:37 Calculating Totals...I 01:13:37 Preparing Image...I 01:13:37 Contents: 100 Files, 40 FoldersI 01:13:37 Content Type: DataI 01:13:37 Data Type: MODE1/2048I 01:13:37 File System(s): UDF (1.02)I 01:13:37 Volume Label: S115I 01:13:37 Size: 99,977,617,992 bytesI 01:13:37 Sectors: 48,817,247I 01:13:37 Image Size: 99,978,641,408 bytesI 01:13:37 Image Sectors: 48,817,696I 01:13:37 Operation Successfully Completed! - Duration: 00:00:00I 01:13:45 Operation Started!I 01:13:45 Building Image Tree...I 01:13:45 Calculating Totals...I 01:13:45 Preparing Image...I 01:13:45 Contents: 100 Files, 40 FoldersI 01:13:45 Content Type: DataI 01:13:45 Data Type: MODE1/2048I 01:13:45 File System(s): UDF (1.02)I 01:13:45 Volume Label: Software 115I 01:13:45 Size: 99,977,617,992 bytesI 01:13:45 Sectors: 48,817,247I 01:13:45 Image Size: 99,978,641,408 bytesI 01:13:45 Image Sectors: 48,817,696I 01:13:46 Operation Successfully Completed! - Duration: 00:00:01I 01:13:47 Operation Started!I 01:13:47 Source File: -==/\/[bUILD IMAGE]\/\==-I 01:13:47 Source File Sectors: 48,817,696 (MODE1/2048)I 01:13:47 Source File Size: 99,978,641,408 bytesI 01:13:47 Source File Volume Identifier: Software 115I 01:13:47 Source File Volume Set Identifier: 497509B602E8E618I 01:13:47 Source File Application Identifier: ImgBurn v2.5.8.0I 01:13:47 Source File Implementation Identifier: ImgBurnI 01:13:47 Source File File System(s): UDF (1.02)I 01:13:47 Destination Device: [1:0:0] HL-DT-ST BD-RE WH16NS40 1.00 (J:) (ATA)I 01:13:47 Destination Media Type: BD-R (Disc ID: VERBAT-IMk-000)I 01:13:47 Destination Media Supported Write Speeds: 2x, 4x, 6x, 8xI 01:13:47 Destination Media Sectors: 48,878,592I 01:13:47 Write Mode: BDI 01:13:47 Write Type: DAOI 01:13:47 Write Speed: 2xI 01:13:47 Hardware Defect Management Active: NoI 01:13:47 BD-R Verify Not Required: YesI 01:13:47 Link Size: AutoI 01:13:47 Lock Volume: YesI 01:13:47 Test Mode: NoI 01:13:47 OPC: NoI 01:13:47 BURN-Proof: EnabledI 01:13:47 Write Speed Successfully Set! - Effective: 8,992 KB/s (2x)I 01:14:50 Filling Buffer... (80 MiB)I 01:14:51 Writing LeadIn...I 01:15:01 Writing Session 1 of 1... (1 Track, LBA: 0 - 48817695)I 01:15:01 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 48817695)W 03:15:49 Failed to Write Sectors 32724064 - 32724095 - Reason: Write ErrorW 03:15:49 Retrying (1 of 20)...W 03:15:49 Retry Failed - Reason: Invalid Address For WriteW 03:15:49 Retrying (2 of 20)...W 03:15:49 Retry Failed - Reason: Invalid Address For WriteW 03:15:49 Retrying (3 of 20)...W 03:15:49 Retry Failed - Reason: Invalid Address For WriteW 03:15:49 Retrying (4 of 20)...W 03:15:49 Retry Failed - Reason: Invalid Address For WriteW 03:15:49 Retrying (5 of 20)...W 03:15:49 Retry Failed - Reason: Invalid Address For WriteW 03:15:50 Retrying (6 of 20)...W 03:15:50 Retry Failed - Reason: Invalid Address For WriteW 03:15:50 Retrying (7 of 20)...W 03:15:50 Retry Failed - Reason: Invalid Address For WriteW 03:15:50 Retrying (8 of 20)...W 03:15:50 Retry Failed - Reason: Invalid Address For WriteW 03:15:50 Retrying (9 of 20)...W 03:15:50 Retry Failed - Reason: Invalid Address For WriteW 03:15:50 Retrying (10 of 20)...W 03:15:50 Retry Failed - Reason: Invalid Address For WriteW 03:15:50 Retrying (11 of 20)...W 03:15:50 Retry Failed - Reason: Invalid Address For WriteW 03:15:50 Retrying (12 of 20)...W 03:15:50 Retry Failed - Reason: Invalid Address For WriteW 03:15:50 Retrying (13 of 20)...W 03:15:50 Retry Failed - Reason: Invalid Address For WriteW 03:15:50 Retrying (14 of 20)...W 03:15:50 Retry Failed - Reason: Invalid Address For WriteW 03:15:50 Retrying (15 of 20)...W 03:15:50 Retry Failed - Reason: Invalid Address For WriteW 03:15:50 Retrying (16 of 20)...W 03:15:50 Retry Failed - Reason: Invalid Address For WriteW 03:15:50 Retrying (17 of 20)...W 03:15:50 Retry Failed - Reason: Invalid Address For WriteW 03:15:50 Retrying (18 of 20)...W 03:15:50 Retry Failed - Reason: Invalid Address For WriteW 03:15:50 Retrying (19 of 20)...W 03:15:50 Retry Failed - Reason: Invalid Address For WriteW 03:15:50 Retrying (20 of 20)...W 03:15:50 Retry Failed - Reason: Invalid Address For WriteW 03:15:52 Retrying (21)...W 03:15:52 Retry Failed - Reason: Invalid Address For WriteW 03:15:53 Retrying (22)...W 03:15:53 Retry Failed - Reason: Invalid Address For WriteW 03:15:53 Retrying (23)...W 03:15:53 Retry Failed - Reason: Invalid Address For WriteW 03:15:54 Retrying (24)...W 03:15:54 Retry Failed - Reason: Invalid Address For WriteW 03:15:54 Retrying (25)...W 03:15:54 Retry Failed - Reason: Invalid Address For WriteW 03:15:54 Retrying (26)...W 03:15:55 Retry Failed - Reason: Invalid Address For WriteW 03:15:55 Retrying (27)...W 03:15:55 Retry Failed - Reason: Invalid Address For WriteW 03:15:55 Retrying (28)...W 03:15:55 Retry Failed - Reason: Invalid Address For WriteW 03:15:55 Retrying (29)...W 03:15:55 Retry Failed - Reason: Invalid Address For WriteW 03:15:55 Retrying (30)...W 03:15:55 Retry Failed - Reason: Invalid Address For WriteW 03:15:55 Retrying (31)...W 03:15:55 Retry Failed - Reason: Invalid Address For WriteW 03:15:55 Retrying (32)...W 03:15:56 Retry Failed - Reason: Invalid Address For WriteW 03:15:56 Retrying (33)...W 03:15:56 Retry Failed - Reason: Invalid Address For WriteW 03:15:56 Retrying (34)...W 03:15:56 Retry Failed - Reason: Invalid Address For WriteW 03:15:56 Retrying (35)...W 03:15:56 Retry Failed - Reason: Invalid Address For WriteW 03:15:56 Retrying (36)...W 03:15:56 Retry Failed - Reason: Invalid Address For WriteW 03:15:56 Retrying (37)...W 03:15:56 Retry Failed - Reason: Invalid Address For WriteW 03:16:01 Retrying (38)...W 03:16:01 Retry Failed - Reason: Invalid Address For WriteW 03:16:01 Retrying (39)...W 03:16:01 Retry Failed - Reason: Invalid Address For WriteW 03:16:01 Retrying (40)...W 03:16:01 Retry Failed - Reason: Invalid Address For WriteW 03:16:01 Retrying (41)...W 03:16:01 Retry Failed - Reason: Invalid Address For WriteW 03:18:41 Retrying (42)...W 03:18:41 Retry Failed - Reason: Invalid Address For WriteW 03:18:41 Retrying (43)...W 03:18:41 Retry Failed - Reason: Invalid Address For WriteW 03:18:42 Retrying (44)...W 03:18:42 Retry Failed - Reason: Invalid Address For WriteW 03:18:42 Retrying (45)...W 03:18:42 Retry Failed - Reason: Invalid Address For WriteW 03:18:42 Retrying (46)...W 03:18:42 Retry Failed - Reason: Invalid Address For WriteW 03:18:42 Retrying (47)...W 03:18:42 Retry Failed - Reason: Invalid Address For WriteW 03:18:42 Retrying (48)...W 03:18:42 Retry Failed - Reason: Invalid Address For WriteW 03:18:42 Retrying (49)...W 03:18:42 Retry Failed - Reason: Invalid Address For WriteW 03:18:43 Retrying (50)...W 03:18:43 Retry Failed - Reason: Invalid Address For WriteW 03:18:43 Retrying (51)...W 03:18:43 Retry Failed - Reason: Invalid Address For WriteW 03:18:43 Retrying (52)...W 03:18:43 Retry Failed - Reason: Invalid Address For WriteW 03:18:43 Retrying (53)...W 03:18:43 Retry Failed - Reason: Invalid Address For WriteW 03:18:43 Retrying (54)...W 03:18:43 Retry Failed - Reason: Invalid Address For WriteW 03:18:43 Retrying (55)...W 03:18:43 Retry Failed - Reason: Invalid Address For WriteW 03:18:44 Retrying (56)...W 03:18:44 Retry Failed - Reason: Invalid Address For WriteW 03:18:44 Retrying (57)...W 03:18:44 Retry Failed - Reason: Invalid Address For WriteW 03:18:44 Retrying (58)...W 03:18:44 Retry Failed - Reason: Invalid Address For WriteW 03:18:44 Retrying (59)...W 03:18:44 Retry Failed - Reason: Invalid Address For WriteW 03:18:44 Retrying (60)...W 03:18:44 Retry Failed - Reason: Invalid Address For WriteW 03:18:45 Retrying (61)...W 03:18:45 Retry Failed - Reason: Invalid Address For WriteW 03:18:45 Retrying (62)...W 03:18:45 Retry Failed - Reason: Invalid Address For WriteW 03:18:45 Retrying (63)...W 03:18:45 Retry Failed - Reason: Invalid Address For WriteW 03:18:45 Retrying (64)...W 03:18:46 Retry Failed - Reason: Invalid Address For WriteW 03:18:46 Retrying (65)...W 03:18:46 Retry Failed - Reason: Invalid Address For WriteW 03:18:46 Retrying (66)...W 03:18:46 Retry Failed - Reason: Invalid Address For WriteW 03:18:46 Retrying (67)...W 03:18:46 Retry Failed - Reason: Invalid Address For WriteW 03:18:46 Retrying (68)...W 03:18:47 Retry Failed - Reason: Invalid Address For WriteW 03:18:47 Retrying (69)...W 03:18:47 Retry Failed - Reason: Invalid Address For WriteW 03:18:47 Retrying (70)...W 03:18:47 Retry Failed - Reason: Invalid Address For WriteW 03:18:47 Retrying (71)...W 03:18:47 Retry Failed - Reason: Invalid Address For WriteW 03:18:47 Retrying (72)...W 03:18:47 Retry Failed - Reason: Invalid Address For WriteW 03:18:47 Retrying (73)...W 03:18:47 Retry Failed - Reason: Invalid Address For WriteW 03:18:48 Retrying (74)...W 03:18:48 Retry Failed - Reason: Invalid Address For WriteW 03:18:48 Retrying (75)...W 03:18:48 Retry Failed - Reason: Invalid Address For WriteW 03:18:48 Retrying (76)...W 03:18:48 Retry Failed - Reason: Invalid Address For WriteW 03:18:48 Retrying (77)...W 03:18:48 Retry Failed - Reason: Invalid Address For WriteW 03:18:48 Retrying (78)...W 03:18:48 Retry Failed - Reason: Invalid Address For WriteW 03:18:49 Retrying (79)...W 03:18:49 Retry Failed - Reason: Invalid Address For WriteW 03:18:49 Retrying (80)...W 03:18:49 Retry Failed - Reason: Invalid Address For WriteW 03:18:49 Retrying (81)...W 03:18:49 Retry Failed - Reason: Invalid Address For WriteW 03:18:49 Retrying (82)...W 03:18:49 Retry Failed - Reason: Invalid Address For WriteW 03:18:49 Retrying (83)...W 03:18:49 Retry Failed - Reason: Invalid Address For WriteW 03:18:49 Retrying (84)...W 03:18:49 Retry Failed - Reason: Invalid Address For WriteW 03:18:50 Retrying (85)...W 03:18:50 Retry Failed - Reason: Invalid Address For WriteW 03:18:50 Retrying (86)...W 03:18:50 Retry Failed - Reason: Invalid Address For WriteW 03:18:50 Retrying (87)...W 03:18:50 Retry Failed - Reason: Invalid Address For WriteW 03:18:50 Retrying (88)...W 03:18:50 Retry Failed - Reason: Invalid Address For WriteW 03:18:50 Retrying (89)...W 03:18:50 Retry Failed - Reason: Invalid Address For WriteW 03:18:51 Retrying (90)...W 03:18:51 Retry Failed - Reason: Invalid Address For WriteW 03:18:51 Retrying (91)...W 03:18:51 Retry Failed - Reason: Invalid Address For WriteW 03:18:51 Retrying (92)...W 03:18:51 Retry Failed - Reason: Invalid Address For WriteW 03:18:51 Retrying (93)...W 03:18:51 Retry Failed - Reason: Invalid Address For WriteW 03:18:51 Retrying (94)...W 03:18:51 Retry Failed - Reason: Invalid Address For WriteW 03:18:51 Retrying (95)...W 03:18:51 Retry Failed - Reason: Invalid Address For WriteW 03:18:52 Retrying (96)...W 03:18:52 Retry Failed - Reason: Invalid Address For WriteW 03:18:52 Retrying (97)...W 03:18:52 Retry Failed - Reason: Invalid Address For WriteW 03:18:52 Retrying (98)...W 03:18:52 Retry Failed - Reason: Invalid Address For WriteW 03:18:52 Retrying (99)...W 03:18:52 Retry Failed - Reason: Invalid Address For WriteW 03:18:53 Retrying (100)...W 03:18:53 Retry Failed - Reason: Invalid Address For WriteE 03:18:53 Failed to Write Sectors 32724064 - 32724095 - Reason: Write ErrorE 03:18:53 Next Writable Address: 0I 03:18:53 Synchronising Cache...I 03:19:00 Closing Track...I 03:19:01 Finalising Disc...E 03:19:23 Failed to Write Image!I 03:19:23 Exporting Graph Data...I 03:19:23 Graph Data File: C:\Users\DFSchmidt\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_WH16NS40_1.00_MONDAY-NOVEMBER-21-2016_1-13_AM_VERBAT-IMk-000_2x.ibgI 03:19:23 Export Successfully Completed!E 03:19:23 Operation Failed! - Duration: 02:05:36I 03:19:23 Average Write Rate: 8,807 KiB/s (2.0x) - Maximum Write Rate: 9,179 KiB/s (2.1x) Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted November 22, 2016 Share Posted November 22, 2016 Both attempts resulted in your drive reporting a 'Write Error', so I'd just say it's unable to burn that media. You should have updated the firmware before making any attempt at burning them... or certainly after the first failure - unless you only found it existed after the second of course. Now it's down to you as to whether or not you update the firmware and try a third time. What do you do if it fails again? Try at 4x? Try some different TL discs? Buy another drive? Link to comment Share on other sites More sharing options...
DFSchmidt Posted November 22, 2016 Author Share Posted November 22, 2016 (edited) First, thanks for writing! As to the issue of the firmware, indeed, normally I keep all of my drives fully up to date in this regard. I had not had any issues with this drive up to now (received it as a gift a year or two ago), and it's been a while since I thought about its firmware revision, but I was reminded of the problem when attempting to take your advice. Specifically, when I run the official LG firmware update utility, found here: http://www.lg.com/us/support-product/lg-WH16NS40#softwareFirmware ...I get the following error: CheckSum is mismatched Drive will go to BOOT mode Please retry again. Now that I think about it, I had the same experience when I first got the drive. I seem to recall speaking with LG support about this and being told not to worry about it / that I didn't need to update the firmware anyway. The drive seemed to work, so I didn't think anything more of it. While under some circumstances I might've interpreted this to indicate that I had a bad drive, I am not alone in my experiences - see here: http://club.myce.com/f91/wh14ns40-checksum-mismatched-340420/ http://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/checksum-mismatched/48378d67-adce-4fd8-9191-7881a937e0a5 From research along these lines, this appears to be a hardware revision issue - they changed the internals without changing the model number, rendering the firmware they have online incompatible with the drive I own. This is mentioned here: http://www.avsforum.com/forum/150-blu-ray-software/2293498-uhd-blu-ray-disc-bdxl-drive-test-request-3.html ...and also here: http://club.myce.com/f91/lg-bh16ns50-bh16ns55-2nd-gen-bh14-wh14-bh16-wh16ns40-svc-code-ns50-2015-a-340457/ Not sure it'd solve my problem anyway, but, to sum up, that's why my firmware isn't up to date and why I'm not able to take your advice and update it, as much as I would agree that it's a logical step to take and something I would like to do. Given the comments concerning the nature of the hardware, I could try to cross-flash with firmware for the 2nd gen. BH16NS40 / BH16NS50 / BH16NS55, assuming it would accept such an update, but there are no official firmware releases for either drive - just the various files folks are tinkering around with in the thread my last link points to. As to the other ideas: * My understanding is that slower is always more reliable, so if 2x doesn't work, I don't see 4x working better; if you know otherwise, however, please let me know. * It's also my understanding that Verbatim media is the best there is - not that there are many choices as far as BD-R TL media is concerned - but if you have suggestions for other brands to try, I'd welcome them. * I am not against getting another drive if it turns out this thing is junk; in that case, I would welcome any recommendations you may have on that topic as well as far as drives capable of writing BD-R TL / XL media are concerned. Thanks again! -DS Edited November 22, 2016 by DFSchmidt Link to comment Share on other sites More sharing options...
DFSchmidt Posted December 3, 2016 Author Share Posted December 3, 2016 Hi all, As an update, I never was able to solve this problem with the LG drive - I ended up replacing it with a Pioneer BDR-2209 / -209UBK / -209M, updating the firmware to the latest revision and successfully burning a Verbatim BD-R TL with ImgBurn using AWS (~6x effective, consistent with the compatibility list on the Pioneer website for these discs). To bad about the LG unit, but very happy that the Pioneer is working, needless to say. -DS Link to comment Share on other sites More sharing options...
Recommended Posts