NewUserGuy1 Posted December 10, 2017 Share Posted December 10, 2017 (edited) Hello, I was told to ask here from the good folks at the AnyDVD HD forums. I tried to burn the ISO of IT (original film on BR) to a 50gig disc) and got a coaster. Any advice? Thanks. Edited December 10, 2017 by NewUserGuy1 Link to comment Share on other sites More sharing options...
Ch3vr0n Posted December 10, 2017 Share Posted December 10, 2017 (edited) As i told you there (and as is said in the pink box up top) you need to post the entire contents of the IMGBurn log window. Images alone mean squat.only then will lightningUK be able to troubleshoot the error(s) @lightning we've already confirmed at the AnyDVD forums he's using the latest firmware available for that drive and using the good stuff blank wise Sent from my Nexus 7 with Tapatalk Edited December 10, 2017 by Ch3vr0n Link to comment Share on other sites More sharing options...
NewUserGuy1 Posted December 10, 2017 Author Share Posted December 10, 2017 (edited) I 15:33:47 ImgBurn Version 2.5.8.0 started! I 15:33:47 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200) I 15:33:47 Total Physical Memory: 16,742,756 KiB - Available: 11,548,488 KiB W 15:33:47 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! I 15:33:48 Initialising SPTI... I 15:33:48 Searching for SCSI / ATAPI devices... I 15:33:48 -> Drive 1 - Info: HL-DT-ST BD-RE WH16NS40 1.02-01 (D:) (SATA) I 15:33:48 -> Drive 2 - Info: HL-DT-ST BD-RE WH16NS40 1.02-01 (G:) (SATA) I 15:33:48 Found 2 BD-RE XLs! I 15:43:30 Operation Started! I 15:43:30 Source File: E:\STEPHEN_KINGS_IT.iso I 15:43:30 Source File Sectors: 23,788,416 (MODE1/2048) I 15:43:30 Source File Size: 48,718,675,968 bytes I 15:43:30 Source File Volume Identifier: STEPHEN_KINGS_IT I 15:43:30 Source File Volume Set Identifier: 8D3C14CD63C45749_VOLUME_SET_ID I 15:43:30 Source File Application Identifier: APPLICATION_ID I 15:43:30 Source File Implementation Identifier: IMPLEMENTATION_ID I 15:43:30 Source File File System(s): UDF (2.50) I 15:43:30 Destination Device: [0:0:0] HL-DT-ST BD-RE WH16NS40 1.02 (D:) (SATA) I 15:43:30 Destination Media Type: BD-R (Disc ID: VERBAT-IMd-000) I 15:43:30 Destination Media Supported Write Speeds: 4x, 6x, 8x I 15:43:30 Destination Media Sectors: 24,438,784 I 15:43:30 Write Mode: BD I 15:43:30 Write Type: DAO I 15:43:30 Write Speed: 4x I 15:43:30 Hardware Defect Management Active: No I 15:43:30 BD-R Verify Not Required: Yes I 15:43:30 Link Size: Auto I 15:43:30 Lock Volume: Yes I 15:43:30 Test Mode: No I 15:43:30 OPC: No I 15:43:30 BURN-Proof: Enabled I 15:43:32 Write Speed Successfully Set! - Effective: 17,984 KB/s (4x) I 15:44:03 Filling Buffer... (80 MiB) I 15:44:03 Writing LeadIn... I 15:44:05 Writing Session 1 of 1... (1 Track, LBA: 0 - 23788415) I 15:44:05 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 23788415) I 15:44:05 Writing Layer 0... (LBA: 0 - 12219391) I 16:07:16 Writing Layer 1... (LBA: 12219392 - 23788415) W 16:16:23 Failed to Write Sectors 16994848 - 16994879 - Reason: Invalid Field in CDB W 16:16:23 Retrying (1 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (2 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (3 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (4 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (5 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (6 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (7 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (8 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (9 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (10 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (11 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (12 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (13 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (14 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (15 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (16 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (17 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (18 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (19 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (20 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:17:20 Retrying (21)... W 16:17:20 Retry Failed - Reason: Invalid Field in CDB W 16:17:21 Retrying (22)... W 16:17:21 Retry Failed - Reason: Invalid Field in CDB W 16:17:22 Retrying (23)... W 16:17:22 Retry Failed - Reason: Invalid Field in CDB W 16:17:22 Retrying (24)... W 16:17:22 Retry Failed - Reason: Invalid Field in CDB W 16:17:22 Retrying (25)... W 16:17:22 Retry Failed - Reason: Invalid Field in CDB W 16:17:22 Retrying (26)... W 16:17:22 Retry Failed - Reason: Invalid Field in CDB W 16:17:23 Retrying (27)... W 16:17:23 Retry Failed - Reason: Invalid Field in CDB W 16:17:23 Retrying (28)... W 16:17:23 Retry Failed - Reason: Invalid Field in CDB W 16:17:23 Retrying (29)... W 16:17:23 Retry Failed - Reason: Invalid Field in CDB W 16:17:23 Retrying (30)... W 16:17:23 Retry Failed - Reason: Invalid Field in CDB W 16:17:23 Retrying (31)... W 16:17:23 Retry Failed - Reason: Invalid Field in CDB E 16:17:25 Failed to Write Sectors 16994848 - 16994879 - Reason: Invalid Field in CDB I 16:17:25 Synchronising Cache... W 16:17:25 Synchronise Cache Failed! - Reason: Invalid Field in CDB W 16:17:56 Retrying (1)... W 16:17:56 Retrying (2)... W 16:17:56 Retrying (3)... W 16:17:56 Retry Failed - Reason: Invalid Field in CDB W 16:17:57 Retrying (4)... W 16:17:57 Retry Failed - Reason: Invalid Field in CDB W 16:17:57 Retrying (5)... W 16:17:57 Retry Failed - Reason: Invalid Field in CDB I 16:18:05 Closing Track... W 16:18:05 Close Track Failed! - Reason: Invalid Field in CDB W 16:18:07 Retrying (1)... I 16:18:07 Finalising Disc... W 16:18:07 Finalise Disc Failed! - Reason: Invalid Field in CDB W 16:18:08 Finalise Disc Failed! - Reason: Invalid Field in CDB E 16:18:08 Failed to Write Image! I 16:18:08 Exporting Graph Data... I 16:18:08 Graph Data File: C:\Users\Me\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_WH16NS40_1.02_SUNDAY-DECEMBER-10-2017_3-43_PM_VERBAT-IMd-000_4x.ibg I 16:18:08 Export Successfully Completed! E 16:18:08 Operation Failed! - Duration: 00:34:38 I 16:18:08 Average Write Rate: 17,003 KiB/s (3.9x) - Maximum Write Rate: 17,925 KiB/s (4.1x) I 16:18:12 Close Request Acknowledged I 16:18:12 Closing Down... I 16:18:13 Shutting down SPTI... I 16:18:13 ImgBurn closed! I 03:01:00 ImgBurn Version 2.5.8.0 started! I 03:01:00 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200) I 03:01:00 Total Physical Memory: 16,742,756 KiB - Available: 12,919,444 KiB W 03:01:00 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! I 03:01:00 Initialising SPTI... I 03:01:00 Searching for SCSI / ATAPI devices... I 03:01:00 -> Drive 1 - Info: HL-DT-ST BD-RE WH16NS40 1.02-01 (D:) (SATA) I 03:01:00 -> Drive 2 - Info: HL-DT-ST BD-RE WH16NS40 1.02-01 (G:) (SATA) I 03:01:00 Found 2 BD-RE XLs! I 03:02:25 Close Request Acknowledged I 03:02:25 Closing Down... I 03:02:25 Shutting down SPTI... I 03:02:25 ImgBurn closed! I 11:29:12 ImgBurn Version 2.5.8.0 started! I 11:29:12 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200) I 11:29:12 Total Physical Memory: 16,742,756 KiB - Available: 8,874,924 KiB W 11:29:12 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! I 11:29:12 Initialising SPTI... I 11:29:12 Searching for SCSI / ATAPI devices... I 11:29:12 -> Drive 1 - Info: HL-DT-ST BD-RE WH16NS40 1.02-01 (D:) (SATA) I 11:29:12 -> Drive 2 - Info: ELBY CLONEDRIVE 1.4 (F:) (SCSI) I 11:29:12 Found 1 BD-ROM/HD DVD-ROM and 1 BD-RE XL! I 20:04:38 Close Request Acknowledged I 11:26:55 ImgBurn Version 2.5.8.0 started! I 11:26:55 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200) I 11:26:55 Total Physical Memory: 16,742,756 KiB - Available: 8,885,128 KiB W 11:26:55 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! I 11:26:55 Initialising SPTI... I 11:26:55 Searching for SCSI / ATAPI devices... I 11:26:56 -> Drive 1 - Info: HL-DT-ST BD-RE WH16NS40 1.02-01 (D:) (SATA) I 11:26:56 -> Drive 2 - Info: ELBY CLONEDRIVE 1.4 (F:) (SCSI) I 11:26:56 Found 1 BD-ROM/HD DVD-ROM and 1 BD-RE XL! I 11:29:05 Close Request Acknowledged I 11:29:05 Closing Down... I 11:29:05 Shutting down SPTI... I 11:29:05 ImgBurn closed! I 11:23:25 ImgBurn Version 2.5.8.0 started! I 11:23:25 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200) I 11:23:25 Total Physical Memory: 16,742,756 KiB - Available: 8,980,688 KiB W 11:23:25 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! I 11:23:25 Initialising SPTI... I 11:23:25 Searching for SCSI / ATAPI devices... I 11:23:25 -> Drive 1 - Info: HL-DT-ST BD-RE WH16NS40 1.02-01 (D:) (SATA) I 11:23:25 -> Drive 2 - Info: ELBY CLONEDRIVE 1.4 (F:) (SCSI) I 11:23:25 Found 1 BD-ROM/HD DVD-ROM and 1 BD-RE XL! I 11:25:35 Close Request Acknowledged I 11:25:35 Closing Down... I 11:25:35 Shutting down SPTI... I 11:25:35 ImgBurn closed! I 11:21:44 ImgBurn Version 2.5.8.0 started! I 11:21:44 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200) I 11:21:44 Total Physical Memory: 16,742,756 KiB - Available: 8,891,884 KiB W 11:21:44 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! I 11:21:44 Initialising SPTI... I 11:21:44 Searching for SCSI / ATAPI devices... I 11:21:44 -> Drive 1 - Info: HL-DT-ST BD-RE WH16NS40 1.02-01 (D:) (SATA) I 11:21:44 -> Drive 2 - Info: ELBY CLONEDRIVE 1.4 (F:) (SCSI) I 11:21:44 Found 1 BD-ROM/HD DVD-ROM and 1 BD-RE XL! I 11:23:19 Close Request Acknowledged I 11:23:19 Closing Down... I 11:23:19 Shutting down SPTI... I 11:23:19 ImgBurn closed! I 17:44:10 Close Request Acknowledged I 17:44:10 Closing Down... I 17:44:10 Shutting down SPTI... I 17:44:10 ImgBurn closed! I 15:33:47 ImgBurn Version 2.5.8.0 started! I 15:33:47 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200) I 15:33:47 Total Physical Memory: 16,742,756 KiB - Available: 11,548,488 KiB W 15:33:47 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! I 15:33:48 Initialising SPTI... I 15:33:48 Searching for SCSI / ATAPI devices... I 15:33:48 -> Drive 1 - Info: HL-DT-ST BD-RE WH16NS40 1.02-01 (D:) (SATA) I 15:33:48 -> Drive 2 - Info: HL-DT-ST BD-RE WH16NS40 1.02-01 (G:) (SATA) I 15:33:48 Found 2 BD-RE XLs! I 15:43:30 Operation Started! I 15:43:30 Source File: E:\STEPHEN_KINGS_IT.iso I 15:43:30 Source File Sectors: 23,788,416 (MODE1/2048) I 15:43:30 Source File Size: 48,718,675,968 bytes I 15:43:30 Source File Volume Identifier: STEPHEN_KINGS_IT I 15:43:30 Source File Volume Set Identifier: 8D3C14CD63C45749_VOLUME_SET_ID I 15:43:30 Source File Application Identifier: APPLICATION_ID I 15:43:30 Source File Implementation Identifier: IMPLEMENTATION_ID I 15:43:30 Source File File System(s): UDF (2.50) I 15:43:30 Destination Device: [0:0:0] HL-DT-ST BD-RE WH16NS40 1.02 (D:) (SATA) I 15:43:30 Destination Media Type: BD-R (Disc ID: VERBAT-IMd-000) I 15:43:30 Destination Media Supported Write Speeds: 4x, 6x, 8x I 15:43:30 Destination Media Sectors: 24,438,784 I 15:43:30 Write Mode: BD I 15:43:30 Write Type: DAO I 15:43:30 Write Speed: 4x I 15:43:30 Hardware Defect Management Active: No I 15:43:30 BD-R Verify Not Required: Yes I 15:43:30 Link Size: Auto I 15:43:30 Lock Volume: Yes I 15:43:30 Test Mode: No I 15:43:30 OPC: No I 15:43:30 BURN-Proof: Enabled I 15:43:32 Write Speed Successfully Set! - Effective: 17,984 KB/s (4x) I 15:44:03 Filling Buffer... (80 MiB) I 15:44:03 Writing LeadIn... I 15:44:05 Writing Session 1 of 1... (1 Track, LBA: 0 - 23788415) I 15:44:05 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 23788415) I 15:44:05 Writing Layer 0... (LBA: 0 - 12219391) I 16:07:16 Writing Layer 1... (LBA: 12219392 - 23788415) W 16:16:23 Failed to Write Sectors 16994848 - 16994879 - Reason: Invalid Field in CDB W 16:16:23 Retrying (1 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (2 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (3 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (4 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (5 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (6 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (7 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (8 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (9 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (10 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (11 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (12 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (13 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (14 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (15 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (16 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (17 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (18 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (19 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:16:23 Retrying (20 of 20)... W 16:16:23 Retry Failed - Reason: Invalid Field in CDB W 16:17:20 Retrying (21)... W 16:17:20 Retry Failed - Reason: Invalid Field in CDB W 16:17:21 Retrying (22)... W 16:17:21 Retry Failed - Reason: Invalid Field in CDB W 16:17:22 Retrying (23)... W 16:17:22 Retry Failed - Reason: Invalid Field in CDB W 16:17:22 Retrying (24)... W 16:17:22 Retry Failed - Reason: Invalid Field in CDB W 16:17:22 Retrying (25)... W 16:17:22 Retry Failed - Reason: Invalid Field in CDB W 16:17:22 Retrying (26)... W 16:17:22 Retry Failed - Reason: Invalid Field in CDB W 16:17:23 Retrying (27)... W 16:17:23 Retry Failed - Reason: Invalid Field in CDB W 16:17:23 Retrying (28)... W 16:17:23 Retry Failed - Reason: Invalid Field in CDB W 16:17:23 Retrying (29)... W 16:17:23 Retry Failed - Reason: Invalid Field in CDB W 16:17:23 Retrying (30)... W 16:17:23 Retry Failed - Reason: Invalid Field in CDB W 16:17:23 Retrying (31)... W 16:17:23 Retry Failed - Reason: Invalid Field in CDB E 16:17:25 Failed to Write Sectors 16994848 - 16994879 - Reason: Invalid Field in CDB I 16:17:25 Synchronising Cache... W 16:17:25 Synchronise Cache Failed! - Reason: Invalid Field in CDB W 16:17:56 Retrying (1)... W 16:17:56 Retrying (2)... W 16:17:56 Retrying (3)... W 16:17:56 Retry Failed - Reason: Invalid Field in CDB W 16:17:57 Retrying (4)... W 16:17:57 Retry Failed - Reason: Invalid Field in CDB W 16:17:57 Retrying (5)... W 16:17:57 Retry Failed - Reason: Invalid Field in CDB I 16:18:05 Closing Track... W 16:18:05 Close Track Failed! - Reason: Invalid Field in CDB W 16:18:07 Retrying (1)... I 16:18:07 Finalising Disc... W 16:18:07 Finalise Disc Failed! - Reason: Invalid Field in CDB W 16:18:08 Finalise Disc Failed! - Reason: Invalid Field in CDB E 16:18:08 Failed to Write Image! I 16:18:08 Exporting Graph Data... I 16:18:08 Graph Data File: C:\Users\Me\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_WH16NS40_1.02_SUNDAY-DECEMBER-10-2017_3-43_PM_VERBAT-IMd-000_4x.ibg I 16:18:08 Export Successfully Completed! E 16:18:08 Operation Failed! - Duration: 00:34:38 I 16:18:08 Average Write Rate: 17,003 KiB/s (3.9x) - Maximum Write Rate: 17,925 KiB/s (4.1x) I 16:18:12 Close Request Acknowledged I 16:18:12 Closing Down... I 16:18:13 Shutting down SPTI... I 16:18:13 ImgBurn closed! I 03:01:00 ImgBurn Version 2.5.8.0 started! I 03:01:00 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200) I 03:01:00 Total Physical Memory: 16,742,756 KiB - Available: 12,919,444 KiB W 03:01:00 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! I 03:01:00 Initialising SPTI... I 03:01:00 Searching for SCSI / ATAPI devices... I 03:01:00 -> Drive 1 - Info: HL-DT-ST BD-RE WH16NS40 1.02-01 (D:) (SATA) I 03:01:00 -> Drive 2 - Info: HL-DT-ST BD-RE WH16NS40 1.02-01 (G:) (SATA) I 03:01:00 Found 2 BD-RE XLs! I 03:02:25 Close Request Acknowledged I 03:02:25 Closing Down... I 03:02:25 Shutting down SPTI... I 03:02:25 ImgBurn closed! I 11:29:12 ImgBurn Version 2.5.8.0 started! I 11:29:12 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200) I 11:29:12 Total Physical Memory: 16,742,756 KiB - Available: 8,874,924 KiB W 11:29:12 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! I 11:29:12 Initialising SPTI... I 11:29:12 Searching for SCSI / ATAPI devices... I 11:29:12 -> Drive 1 - Info: HL-DT-ST BD-RE WH16NS40 1.02-01 (D:) (SATA) I 11:29:12 -> Drive 2 - Info: ELBY CLONEDRIVE 1.4 (F:) (SCSI) I 11:29:12 Found 1 BD-ROM/HD DVD-ROM and 1 BD-RE XL! I 20:04:38 Close Request Acknowledged I 11:26:55 ImgBurn Version 2.5.8.0 started! I 11:26:55 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200) I 11:26:55 Total Physical Memory: 16,742,756 KiB - Available: 8,885,128 KiB W 11:26:55 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! I 11:26:55 Initialising SPTI... I 11:26:55 Searching for SCSI / ATAPI devices... I 11:26:56 -> Drive 1 - Info: HL-DT-ST BD-RE WH16NS40 1.02-01 (D:) (SATA) I 11:26:56 -> Drive 2 - Info: ELBY CLONEDRIVE 1.4 (F:) (SCSI) I 11:26:56 Found 1 BD-ROM/HD DVD-ROM and 1 BD-RE XL! I 11:29:05 Close Request Acknowledged I 11:29:05 Closing Down... I 11:29:05 Shutting down SPTI... I 11:29:05 ImgBurn closed! I 11:23:25 ImgBurn Version 2.5.8.0 started! I 11:23:25 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200) I 11:23:25 Total Physical Memory: 16,742,756 KiB - Available: 8,980,688 KiB W 11:23:25 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! I 11:23:25 Initialising SPTI... I 11:23:25 Searching for SCSI / ATAPI devices... I 11:23:25 -> Drive 1 - Info: HL-DT-ST BD-RE WH16NS40 1.02-01 (D:) (SATA) I 11:23:25 -> Drive 2 - Info: ELBY CLONEDRIVE 1.4 (F:) (SCSI) I 11:23:25 Found 1 BD-ROM/HD DVD-ROM and 1 BD-RE XL! I 11:25:35 Close Request Acknowledged I 11:25:35 Closing Down... I 11:25:35 Shutting down SPTI... I 11:25:35 ImgBurn closed! I 11:21:44 ImgBurn Version 2.5.8.0 started! I 11:21:44 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200) I 11:21:44 Total Physical Memory: 16,742,756 KiB - Available: 8,891,884 KiB W 11:21:44 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! I 11:21:44 Initialising SPTI... I 11:21:44 Searching for SCSI / ATAPI devices... I 11:21:44 -> Drive 1 - Info: HL-DT-ST BD-RE WH16NS40 1.02-01 (D:) (SATA) I 11:21:44 -> Drive 2 - Info: ELBY CLONEDRIVE 1.4 (F:) (SCSI) I 11:21:44 Found 1 BD-ROM/HD DVD-ROM and 1 BD-RE XL! I 11:23:19 Close Request Acknowledged I 11:23:19 Closing Down... I 11:23:19 Shutting down SPTI... I 11:23:19 ImgBurn closed! Edited December 11, 2017 by NewUserGuy1 Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted December 11, 2017 Share Posted December 11, 2017 Hard to tell with this one as it looks like something is messing up the error codes your drive is actually returning and all the program is getting back is that 'invalid field in cdb' one. Right click the drive selection box and pick 'family tree'. Close the box that comes up and copy + paste everything from the log window please. Link to comment Share on other sites More sharing options...
dbminter Posted December 11, 2017 Share Posted December 11, 2017 Could be the LG burner you're using. I've tried 5 different LG BD burners for burning Verbatim good quality BD-RE DL and only 1 didn't fail Verify. So, I've come to the conclusion that LG drives are not good at writing BD DL media. Now, I've never burned a BD-R DL before, but I would think if all the LG's I've ever tested BD-RE DL failed more times than succeeded, I would say it's the fault of LG burners. I only use my Pioneer BD burner for writing BD-RE DL, which writes to them perfectly. So, you may want to try a Pioneer BD drive if you can't get this issue resolved on your LG. Link to comment Share on other sites More sharing options...
NewUserGuy1 Posted December 11, 2017 Author Share Posted December 11, 2017 (edited) Hard to tell with this one as it looks like something is messing up the error codes your drive is actually returning and all the program is getting back is that 'invalid field in cdb' one. Right click the drive selection box and pick 'family tree'. Close the box that comes up and copy + paste everything from the log window please. D Drive Family Tree: I 14:14:01 Device: [0:0:0] HL-DT-ST BD-RE WH16NS40 1.02 (D:) (SATA) I 14:14:01 Family Tree: I 14:14:01 -> ACPI x64-based PC I 14:14:01 -> Microsoft ACPI-Compliant System I 14:14:01 -> PCI Express Root Complex I 14:14:01 -> Standard SATA AHCI Controller (VEN_8086&DEV_A282 - Intel - storahci - v10.0.16299.15) I 14:14:01 -> CD-ROM Drive (HL-DT-ST BD-RE WH16NS40) (Bus Number 1, Target Id 0, LUN 0) G Drive Tree: I 14:15:46 Device: [0:0:0] HL-DT-ST BD-RE WH16NS40 1.02 (G:) (SATA) I 14:15:46 Family Tree: I 14:15:46 -> ACPI x64-based PC I 14:15:46 -> Microsoft ACPI-Compliant System I 14:15:46 -> PCI Express Root Complex I 14:15:46 -> Standard SATA AHCI Controller (VEN_8086&DEV_A282 - Intel - storahci - v10.0.16299.15) I 14:15:46 -> CD-ROM Drive (HL-DT-ST BD-RE WH16NS40) (Bus Number 5, Target Id 0, LUN 0) Edited December 11, 2017 by NewUserGuy1 Link to comment Share on other sites More sharing options...
NewUserGuy1 Posted December 11, 2017 Author Share Posted December 11, 2017 (edited) Tried two more times and two more coasters. Even after I updated the LG firmware from 1.02 to 1.03!!! ARGH!!! I 14:55:04 ImgBurn Version 2.5.8.0 started! I 14:55:04 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200) I 14:55:04 Total Physical Memory: 16,742,756 KiB - Available: 13,831,956 KiB W 14:55:04 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! I 14:55:04 Initialising SPTI... I 14:55:04 Searching for SCSI / ATAPI devices... I 14:55:04 -> Drive 1 - Info: HL-DT-ST BD-RE WH16NS40 1.02-01 (D:) (SATA) I 14:55:04 -> Drive 2 - Info: HL-DT-ST BD-RE WH16NS40 1.03 (G:) (SATA) I 14:55:04 Found 2 BD-RE XLs! I 14:56:29 Operation Started! I 14:56:29 Source File: E:\STEPHEN_KINGS_IT.iso I 14:56:29 Source File Sectors: 23,788,416 (MODE1/2048) I 14:56:29 Source File Size: 48,718,675,968 bytes I 14:56:29 Source File Volume Identifier: STEPHEN_KINGS_IT I 14:56:29 Source File Volume Set Identifier: 8D3C14CD63C45749_VOLUME_SET_ID I 14:56:29 Source File Application Identifier: APPLICATION_ID I 14:56:29 Source File Implementation Identifier: IMPLEMENTATION_ID I 14:56:29 Source File File System(s): UDF (2.50) I 14:56:29 Destination Device: [0:0:0] HL-DT-ST BD-RE WH16NS40 1.03 (G:) (SATA) I 14:56:29 Destination Media Type: BD-R (Disc ID: VERBAT-IMd-000) I 14:56:29 Destination Media Supported Write Speeds: 4x, 6x, 8x I 14:56:29 Destination Media Sectors: 24,438,784 I 14:56:29 Write Mode: BD I 14:56:29 Write Type: DAO I 14:56:29 Write Speed: 4x I 14:56:29 Hardware Defect Management Active: No I 14:56:29 BD-R Verify Not Required: Yes I 14:56:29 Link Size: Auto I 14:56:29 Lock Volume: Yes I 14:56:29 Test Mode: No I 14:56:29 OPC: No I 14:56:29 BURN-Proof: Enabled I 14:56:29 Write Speed Successfully Set! - Effective: 17,984 KB/s (4x) I 14:56:57 Filling Buffer... (80 MiB) I 14:56:57 Writing LeadIn... I 14:56:58 Writing Session 1 of 1... (1 Track, LBA: 0 - 23788415) I 14:56:58 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 23788415) I 14:56:58 Writing Layer 0... (LBA: 0 - 12219391) Edited December 11, 2017 by NewUserGuy1 Link to comment Share on other sites More sharing options...
dbminter Posted December 11, 2017 Share Posted December 11, 2017 I still will fall back on it's the fault of the LG drive. See this thread for a similar issue that was "resolved." http://forum.imgburn.com/index.php?/topic/24807-errors-when-verifying/ Link to comment Share on other sites More sharing options...
dbminter Posted December 11, 2017 Share Posted December 11, 2017 Wait, there's a 1.03 firmware update to that drive? I have that LG drive because it writes properly to all other media except for BD-RE DL and firmwarehq only lists 1.02, my firmware. Found the firmware on LG's site for the drive. It appears it was just released 3 days ago. After over 3 years of no new firmware updates, it seems LG finally updated this drive. Seems it didn't fix the BD-RE DL issue, but I'll test it out, anyway. If it makes you feel any better, I, at least, found some useful information from this post. Thanks! Link to comment Share on other sites More sharing options...
NewUserGuy1 Posted December 11, 2017 Author Share Posted December 11, 2017 If it makes you feel any better, I, at least, found some useful information from this post. Thanks! You are very welcome . Now hopefully we can see what's going on. Lightning? Link to comment Share on other sites More sharing options...
dbminter Posted December 11, 2017 Share Posted December 11, 2017 The problem is with LG drives and Verbatim BD DL. I updated the firmware to 1.03, performed another BD-RE DL test. Of course, it STILL failed Verify at the layer break change. I 15:23:00 Operation Started!I 15:23:00 Source File Sectors: 15,957,344 (MODE1/2048)I 15:23:00 Source File Size: 32,680,640,512 bytesI 15:23:00 Source File Volume Set Identifier: 4B8B79FA00F37D0AI 15:23:00 Source File Application Identifier: ImgBurn v2.5.8.0I 15:23:00 Source File Implementation Identifier: ImgBurnI 15:23:00 Source File File System(s): UDF (2.60)I 15:23:00 Destination Device: [0:0:0] HL-DT-ST BD-RE WH16NS40 1.03 (S:) (SATA)I 15:23:00 Destination Media Type: BD-RE (Disc ID: VERBAT-IM1-000)I 15:23:00 Destination Media Supported Write Speeds: 2xI 15:23:00 Destination Media Sectors: 24,438,784I 15:23:01 Write Mode: BDI 15:23:01 Write Type: DAOI 15:23:01 Write Speed: MAXI 15:23:01 Hardware Defect Management Active: NoI 15:23:01 BD-RE FastWrite: NoI 15:23:01 Link Size: AutoI 15:23:01 Lock Volume: YesI 15:23:01 Test Mode: NoI 15:23:01 OPC: NoI 15:23:01 BURN-Proof: EnabledI 15:23:01 Write Speed Successfully Set! - Effective: 8,992 KB/s (2x)I 15:23:02 Filling Buffer... (40 MiB)I 15:23:03 Writing LeadIn...I 15:23:27 Writing Session 1 of 1... (1 Track, LBA: 0 - 15957343)I 15:23:27 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 15957343)I 15:23:27 Writing Layer 0... (LBA: 0 - 12219391)I 16:08:25 Writing Layer 1... (LBA: 12219392 - 15957343)I 16:22:34 Synchronising Cache...I 16:22:58 Exporting Graph Data...I 16:22:58 Export Successfully Completed!I 16:22:58 Operation Successfully Completed! - Duration: 00:59:57I 16:22:58 Average Write Rate: 9,000 KiB/s (2.1x) - Maximum Write Rate: 9,560 KiB/s (2.2x)I 16:22:58 Cycling Tray before Verify...W 16:23:05 Waiting for device to become ready...I 16:23:20 Device Ready!I 16:23:24 Operation Started!I 16:23:24 Source Device: [0:0:0] HL-DT-ST BD-RE WH16NS40 1.03 (S:) (SATA)I 16:23:24 Source Media Type: BD-RE (Disc ID: VERBAT-IM1-000)I 16:23:24 Source Media Supported Read Speeds: 2x, 4x, 6xI 16:23:24 Source Media Supported Write Speeds: 2xI 16:23:24 Source Media Sectors: 24,438,784I 16:23:24 Source Media Size: 50,050,629,632 bytesI 16:23:24 Image File Sectors: 15,957,344 (MODE1/2048)I 16:23:24 Image File Size: 32,680,640,512 bytesI 16:23:24 Image File Volume Identifier: 12 - DecemberI 16:23:24 Image File Volume Set Identifier: 4B8B79FA00F37D0AI 16:23:24 Image File Application Identifier: ImgBurn v2.5.8.0I 16:23:24 Image File Implementation Identifier: ImgBurnI 16:23:24 Image File File System(s): UDF (2.60)I 16:23:24 Read Speed (Data/Audio): MAX / MAXI 16:23:25 Read Speed - Effective: 2x - 6x, 6x - 2xI 16:23:25 Verifying Session 1 of 1... (1 Track, LBA: 0 - 15957343)I 16:23:25 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 15957343)I 16:23:25 Verifying Layer 0... (LBA: 0 - 12219391)I 16:59:06 Verifying Layer 1... (LBA: 12219392 - 15957343)W 16:59:10 Failed to Read Sectors 12219616 - 12219647 - Reason: L-EC Uncorrectable ErrorW 16:59:16 Failed to Read Sector 12219616 - Reason: L-EC Uncorrectable ErrorW 16:59:16 Sector 12219616 maps to File: \12 - December\12 - December-00-03.mrimgE 17:31:27 Failed to Read Sector 12219616 - Reason: L-EC Uncorrectable ErrorE 17:31:27 Sector 12219616 maps to File: \12 - December\12 - December-00-03.mrimgE 17:31:27 Failed to Verify Sectors!I 17:31:33 Exporting Graph Data...I 17:31:33 Export Successfully Completed!E 17:31:33 Operation Failed! - Duration: 01:08:03I 17:31:33 Average Verify Rate: 5,987 KiB/s (1.4x) - Maximum Verify Rate: 32,591 KiB/s (7.4x) Notice how it failed Verify with less than 300 sectors into the 2nd layer? The issue is an inherent problem with LG drives and (at least) Verbatim BD-RE DL. Since it happens on your drive, too, it happens on all Verbatim BD-R DL and BD-RE DL. And it may even happen on ALL manufacturers of BD DL media. Nothing had ever been written to this Verbatim BD-RE DL before. It had only been "written once" when it was formatted in a Pioneer drive. So, it's highly unlikely the disc is bad. And it's highly unlikely that the Pioneer formatted it wrong because the Pioneer and my USB ASUS write to these kinds of discs fine. Only the 5 LG's I've tested do this. They all fail Verify except for one Verify, and the contents were NOT written correctly to the disc when I compared the written contents with the source. Ergo, the problem is with all LG drives. QED. Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted December 11, 2017 Share Posted December 11, 2017 As I said previously, I'm not convinced the software is getting the actual error code back from the drive. Can you try booting into safe mode and burning another disc? After that, I'd start looking at various drivers for your SATA controller. Is the bios up-to-date for your motherboard? Link to comment Share on other sites More sharing options...
NewUserGuy1 Posted December 11, 2017 Author Share Posted December 11, 2017 After that, I'd start looking at various drivers for your SATA controller. Is the bios up-to-date for your motherboard? Bios up to date. Brand new, top of the line Core I7 7700. Link to comment Share on other sites More sharing options...
dbminter Posted December 12, 2017 Share Posted December 12, 2017 Discovered another LG/Verbatim incompatibility after testing more 1.03 media burns. The LG's never liked writing to Verbatim 6x DVD-RW media, either. 1.03 does nothing to fix this. They still fail at the, guess where? Verify! My Pioneer writes them fine. Link to comment Share on other sites More sharing options...
NewUserGuy1 Posted December 12, 2017 Author Share Posted December 12, 2017 I just ordered this Pioneer: https://www.amazon.com/gp/product/B00GD792US/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1 Wills see how it works and if better, will return the LG. Link to comment Share on other sites More sharing options...
dbminter Posted December 12, 2017 Share Posted December 12, 2017 Good to have both on hand. That way, when you get one, you can test it and if it doesn't work, send it back. Then, you'll have the other on hand, too, to try next. That model of Pioneer is the one I have always used. In fact, I have 2 of them. The 2nd one I got I still use and the first one I got still works. Just sitting around to swap in. Pioneer's have a few flaws of their own. After a few months, the eject button doesn't always work the first time it's pressed. Pressing it again works. Issuing an Eject command in ImgBurn does the same thing. However, all eject commands issued after a write if directed by ImgBurn seem to work. The current firmware is borked for Ritek 8x DVD+RW media. However, it's a moot point as you can't find 8x DVD+RW new anymore. The quality of that drive may have declined if my experience is any indication. I don't know yet. Can only relate my story. As I said, my first 2 drives have performed well. My first is almost 3 years old and still works. My current one is almost 2 years old and still works. The 3rd one I had, though, I had to replace after 7 months. The 4th one I got I had to send back to Amazon.com because it was borked for writing Verbatim BD-R out of the box. However, with all that said, I'd still recommend trying a Pioneer first for a BD burner. Link to comment Share on other sites More sharing options...
NewUserGuy1 Posted December 12, 2017 Author Share Posted December 12, 2017 Any additional insight Lightning? Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted December 13, 2017 Share Posted December 13, 2017 My previous post covered everything thus far. There's no magical fix I'm afraid, you just need to mess around (troubleshoot) until it works. Without the proper error code, it's impossible to see what's actually happening. If your drive had thrown a 'Write Error', that would be easier. Yours is throwing 'invalid field in cdb'... which is nonsense. Link to comment Share on other sites More sharing options...
NewUserGuy1 Posted December 13, 2017 Author Share Posted December 13, 2017 Thanks for the reply Lightning, but I am confused. Didn't I print your programs error logs? Shouldn't they provide what you need ? Let me know what you need or if I did not provide the right information. Thanks again . Link to comment Share on other sites More sharing options...
Ch3vr0n Posted December 13, 2017 Share Posted December 13, 2017 Thanks for the reply Lightning, but I am confused. Didn't I print your programs error logs? Shouldn't they provide what you need ? Let me know what you need or if I did not provide the right information. Thanks again . You did everything right, the issue is that the DRIVE is reporting a generic error (invalid field in cdb) that doesn't mean much, instead of reporting an actual real informative error such as 'write error...'. combining both topics on 2 forums and the fact that you're using quality media, I'd go with faulty drive. Sent from my Nexus 6P with Tapatalk Link to comment Share on other sites More sharing options...
dbminter Posted December 13, 2017 Share Posted December 13, 2017 I still reiterate my idea that LG drives just are terrible with BD DL media. Try a Pioneer and I think that will probably fix your issue. Can't guarantee it, of course. As has been said, there really isn't much that can be done at this point beyond that. Your LG drive is returning generic errors that don't help much. Or it's returning the wrong errors. Even if it was returning wrong errors and you fixed that issue, I still doubt that would fix your BD DL issue. Experience has taught me that LG's just aren't reliable for writing BD DL media. Link to comment Share on other sites More sharing options...
NewUserGuy1 Posted December 14, 2017 Author Share Posted December 14, 2017 (edited) I seemed to have figured this out by trial an error. Received the replacement same model LG drive today as well as this Pioneer I ordered at the same time: https://www.amazon.com/gp/product/B00GD792US/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1 Guess what? The replacement LG worked fine and has burned 7 50gig BR, and a few 25gig ones, with no issues. I did them ALL on the fly without burning ISO to HD. I put the original BR film in my first LG drive D, and the blank 50gig Verbatim in the replacement second new LG drive F as my burner, and my Hellraiser 45 gig disc burned in 45 min! I then changed the second LG drive for the Pioneer I also got to test that, and it did the same over 45 gig Hellraiser disc disc in 31 min disc to disc! Amazing how the Pioneer burned the same 50gig Verbatim 4x speed blank at 8x (or at least that is what Cyberlink Power2Go 7 said) in 31 minutes! It's Copy to Copy featured worked perfectly and I have done this about 7 times with different films both 50 gig and 25 gig blanks. Not one coaster. Edited December 14, 2017 by NewUserGuy1 Link to comment Share on other sites More sharing options...
dbminter Posted December 14, 2017 Share Posted December 14, 2017 I'd be curious to see the results of an ISO burn on this new LG drive. I think it's just coincidence. If it works on the fly, it should work on ISO. Burning from an ISO should make no difference as to whether a burn will fail Verify or not. If it were an ISO issue, it would fail on Pioneer as well. Unfortunately, I can't do that. The only DL media I burn have to be bootable. So, I need to edit a bootable ISO with UltraIISO to inject files into it. Link to comment Share on other sites More sharing options...
NewUserGuy1 Posted December 14, 2017 Author Share Posted December 14, 2017 I prefer burning on the fly between two drives as it is much faster. You don't have to rip ISO to hard drive then burn that. Link to comment Share on other sites More sharing options...
Ch3vr0n Posted December 14, 2017 Share Posted December 14, 2017 It's faster yes, but there is a risk. 1 faulty sector on the source disc that the drive can't handle and you either have a successful burn but faulty on playback or the drive can't handle the faulty sector and data stops flowing and the backup burn ends too. Sent from my Nexus 6P with Tapatalk Link to comment Share on other sites More sharing options...
Recommended Posts