DeathStalker Posted May 11, 2019 Posted May 11, 2019 I am using only branded Verbatim discs. It happens on all types - BD single/dual, DVD single/dual. SCSIStatus: 0x02 Interpretation: Check Condition SK Interpretation: Hardware Error ASC/ASCQ Interpretation: Timeout on logical unit Settings are ImgBurn default. ASUS BW-16D1HT (firmware v3.03) Win10x64 I have previously chalked this issue up to cheaper discs, but now Verbatims are blowing out (and they ate NOT cheap)
LIGHTNING UK! Posted May 11, 2019 Posted May 11, 2019 Post the log please. If you've already changed discs, changing the drive would be the next logical step.
DeathStalker Posted May 11, 2019 Author Posted May 11, 2019 I just updated the firmware to v3.10 (honestly didn't expect there to be a new version of it). Also, uninstalled and re-installed ImgBurn to be safe after that. Will post the log the next time it fails. It doesn't fail ALL the time, but often enough to get expensive
dbminter Posted May 11, 2019 Posted May 11, 2019 You can access old failed logs under Help --> ImgBurn Logs. Open the log file, find the last failed instance where this error occurs, and copy and paste its entire operation log.
DeathStalker Posted May 11, 2019 Author Posted May 11, 2019 Ok, tried it again on an Optical Quantum disc this time - it blew out I 18:11:52 ImgBurn Version 2.5.8.0 started! I 18:11:52 Microsoft Windows 8 Enterprise x64 Edition (6.2, Build 9200) I 18:11:52 Total Physical Memory: 67,017,688 KiB - Available: 51,981,968 KiB I 18:11:52 Initialising SPTI... I 18:11:52 Searching for SCSI / ATAPI devices... I 18:11:52 -> Drive 1 - Info: ELBY CLONEDRIVE 1.4 (P:) (SCSI) I 18:11:53 -> Drive 2 - Info: ASUS BW-16D1HT 3.10 (X:) (SATA) I 18:11:53 Found 1 BD-ROM/HD DVD-ROM and 1 BD-RE XL! I 18:11:58 Operation Started! I 18:11:58 Source File: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX I 18:11:58 Source File Sectors: 24,244,416 (MODE1/2048) I 18:11:58 Source File Size: 49,652,563,968 bytes I 18:11:58 Source File Volume Identifier: xxxxxxxxxxxxxxxxxxxxxxx I 18:11:58 Source File Volume Set Identifier: xxxxxxxxxxxxxxxxxxxxxxxxxxx I 18:11:58 Source File Application Identifier: vso_hwe.dll 4.0.19.487 I 18:11:58 Source File Implementation Identifier: VsoSoftware I 18:11:58 Source File File System(s): UDF (2.50) I 18:11:58 Destination Device: [2:0:0] ASUS BW-16D1HT 3.10 (X:) (SATA) I 18:11:58 Destination Media Type: BD-R (Disc ID: RITEK-DR3-000) I 18:11:58 Destination Media Supported Write Speeds: 2x, 4x, 6x I 18:11:58 Destination Media Sectors: 24,438,784 I 18:11:58 Write Mode: BD I 18:11:58 Write Type: DAO I 18:11:58 Write Speed: MAX I 18:11:58 Hardware Defect Management Active: No I 18:11:58 BD-R Verify Not Required: Yes I 18:11:58 Link Size: Auto I 18:11:58 Lock Volume: Yes I 18:11:58 Test Mode: No I 18:11:58 OPC: No I 18:11:58 BURN-Proof: Enabled I 18:11:58 Write Speed Successfully Set! - Effective: 26,976 KB/s (6x) I 18:12:28 Filling Buffer... (80 MiB) I 18:12:28 Writing LeadIn... I 18:12:29 Writing Session 1 of 1... (1 Track, LBA: 0 - 24244415) I 18:12:29 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 24244415) I 18:12:29 Writing Layer 0... (LBA: 0 - 12219391) I 18:28:11 Writing Layer 1... (LBA: 12219392 - 24244415) I 18:43:42 Synchronising Cache... I 18:43:43 Closing Track... I 18:43:44 Finalising Disc... I 18:44:01 Operation Successfully Completed! - Duration: 00:32:03 I 18:44:01 Average Write Rate: 25,902 KiB/s (5.9x) - Maximum Write Rate: 26,758 KiB/s (6.1x) I 18:44:01 Cycling Tray before Verify... W 18:44:09 Waiting for device to become ready... I 18:44:24 Device Ready! I 18:44:25 Operation Started! I 18:44:25 Source Device: [2:0:0] ASUS BW-16D1HT 3.10 (X:) (SATA) I 18:44:25 Source Media Type: BD-R (Disc ID: RITEK-DR3-000) I 18:44:25 Source Media Supported Read Speeds: 2x, 4x, 6x, 8x I 18:44:25 Source Media Supported Write Speeds: 2x, 4x, 6x I 18:44:25 Source Media Sectors: 24,244,416 I 18:44:25 Source Media Size: 49,652,563,968 bytes I 18:44:25 Image File: XXXXXXXXXXXXXXXXXXXXXXXXXXXX I 18:44:25 Image File Sectors: 24,244,416 (MODE1/2048) I 18:44:25 Image File Size: 49,652,563,968 bytes I 18:44:25 Image File Volume Identifier: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX I 18:44:25 Image File Volume Set Identifier: XXXXXXXXXXXXXXXXXXXXXXXX I 18:44:25 Image File Application Identifier: vso_hwe.dll 4.0.19.487 I 18:44:25 Image File Implementation Identifier: VsoSoftware I 18:44:25 Image File File System(s): UDF (2.50) I 18:44:25 Read Speed (Data/Audio): MAX / MAX I 18:44:26 Read Speed - Effective: 3x - 8x, 8x - 3x I 18:44:26 Verifying Session 1 of 1... (1 Track, LBA: 0 - 24244415) I 18:44:26 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 24244415) I 18:44:26 Verifying Layer 0... (LBA: 0 - 12219391) I 19:00:36 Verifying Layer 1... (LBA: 12219392 - 24244415) W 19:00:52 Failed to Read Sectors 12219808 - 12219839 - Reason: Timeout on Logical Unit W 19:01:01 Failed to Read Sector 12219808 - Reason: Timeout on Logical Unit W 19:01:01 Sector 12219808 maps to File: \BDMV\STREAM\00042.m2ts W 19:01:06 Retrying (1)... W 19:01:18 Retry Failed - Reason: Timeout on Logical Unit W 19:01:19 Retrying (2)... W 19:01:29 Retry Failed - Reason: Timeout on Logical Unit W 19:01:34 Retrying (3)... W 19:01:46 Retry Failed - Reason: Timeout on Logical Unit E 19:01:48 Failed to Read Sector 12219808 - Reason: Timeout on Logical Unit E 19:01:48 Sector 12219808 maps to File: \BDMV\STREAM\00042.m2ts E 19:01:49 Failed to Verify Sectors! E 19:01:50 Operation Failed! - Duration: 00:17:23 I 19:01:50 Average Verify Rate: 23,454 KiB/s (5.3x) - Maximum Verify Rate: 36,139 KiB/s (8.2x) I 19:01:51 Close Request Acknowledged I 19:01:51 Closing Down... I 19:01:51 Shutting down SPTI... I 19:01:51 ImgBurn closed!
dbminter Posted May 11, 2019 Posted May 11, 2019 Open the log and find a failed Verbatim BD-R burn. Look for a line that looks like this one from the above: Destination Media Type: BD-R (Disc ID: RITEK-DR3-000) What is the Disc ID? Look for a failed DVD burn, too. Copy and paste the log from a failed DVD burn as well. Also, in particular, note the same Destination Media Type log. It's probably not related to the type of media you're using, but it could be. Particularly if you're using the same kind of "bad" Verbatim media for both BD and DVD. There's good Verbatim and there's bad Verbatim. However, given you're getting random failures on DVD and BD media, it's probably down to the drive itself needing replacing. However, the very reason it could be random is that sometimes bad media was used and sometimes good media was. For instance, Ritek is pretty bad media for dual layer writing, either BD or DVD. It's common to have problems burning DL Ritek media. Without knowing if you've used good media, like the good kind of Verbatim and not the CMC MAG type of media, it's hard to tell.
Recommended Posts