SavOak Posted December 23, 2016 Posted December 23, 2016 This is the first error that shows up in every log of every BD-R disk I've tried to burn since mid-October 2016. The burn starts, reserving track and writing lead in, but then the speed never goes above 1x (it's set to 4x) and quickly goes to 0. This has happened to 30+ disks recently, but only after successfully burning 100's of BD-Rs, and nothing changed - except for Windows updates. I use an Asus ROG (very fast) laptop with USB 3 and now 2x 5 1/4" external enclosures because I recently got a new drive. (Note that I only use one at a time, however). The issue started on an Asus BW-12B1ST and continues on the recently purchased Asus BW-16D1HT. I know Asus aren't the preferred drives in this forum (even though both of these were manufactured by LG, I think), but I had excellent results with the first one after doing a firmware update a couple of years ago. I've tried changing cables, changing enclosures, and changing drives, but always get the same result: I 19:08:25 ImgBurn Version 2.5.8.0 started!I 19:08:25 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200)I 19:08:25 Total Physical Memory: 25,117,908 KiB - Available: 16,110,788 KiBI 19:08:25 Initialising SPTI...I 19:08:25 Searching for SCSI / ATAPI devices...I 19:08:25 -> Drive 1 - Info: Slimtype DVD A DS8A8SH KAA3 (E:) (SATA)I 19:10:12 -> Drive 2 - Info: ASUS BW-16D1HT 3.00 (G:) (USB 2.0)I 19:10:12 Found 1 DVD±RW/RAM and 1 BD-RE XL!I 19:15:52 Operation Started!I 19:15:52 Building Image Tree...I 19:15:52 Calculating Totals...I 19:15:52 Preparing Image...I 19:15:52 Contents: 34 Files, 9 FoldersI 19:15:52 Content Type: DataI 19:15:52 Data Type: MODE1/2048I 19:15:52 File System(s): UDF (2.50)I 19:15:52 Volume Label: Morton Salt 20151217-3 (of 4)I 19:15:52 Size: 24,429,781,585 bytesI 19:15:52 Sectors: 11,928,623I 19:15:52 Image Size: 24,430,837,760 bytesI 19:15:52 Image Sectors: 11,929,120I 19:15:52 Operation Successfully Completed! - Duration: 00:00:00I 19:16:00 Operation Started!I 19:16:00 Building Image Tree...I 19:16:00 Calculating Totals...I 19:16:00 Preparing Image...I 19:16:01 Contents: 34 Files, 9 FoldersI 19:16:01 Content Type: DataI 19:16:01 Data Type: MODE1/2048I 19:16:01 File System(s): UDF (2.50)I 19:16:01 Volume Label: _client_name_ 20151217-3 (of 4)I 19:16:01 Size: 24,429,781,585 bytesI 19:16:01 Sectors: 11,928,623I 19:16:01 Image Size: 24,430,837,760 bytesI 19:16:01 Image Sectors: 11,929,120I 19:16:05 Operation Successfully Completed! - Duration: 00:00:04I 19:16:05 Operation Started!I 19:16:05 Source File: -==/\/[bUILD IMAGE]\/\==-I 19:16:05 Source File Sectors: 11,929,120 (MODE1/2048)I 19:16:05 Source File Size: 24,430,837,760 bytesI 19:16:05 Source File Volume Identifier: _client_name_ 20151217-3 (of 4)I 19:16:05 Source File Volume Set Identifier: 499699FD00B605AFI 19:16:05 Source File Application Identifier: ImgBurn v2.5.8.0I 19:16:05 Source File Implementation Identifier: ImgBurnI 19:16:05 Source File File System(s): UDF (2.50)I 19:16:05 Destination Device: [0:0:0] ASUS BW-16D1HT 3.00 (G:) (USB)I 19:16:05 Destination Media Type: BD-R (Disc ID: UMEBDR-016-000)I 19:16:05 Destination Media Supported Write Speeds: 4x, 6x, 8xI 19:16:05 Destination Media Sectors: 12,219,392I 19:16:05 Write Mode: BDI 19:16:05 Write Type: DAOI 19:16:05 Write Speed: 4xI 19:16:05 Hardware Defect Management Active: NoI 19:16:05 BD-R Verify Not Required: YesI 19:16:05 Link Size: AutoI 19:16:05 Lock Volume: YesI 19:16:05 Test Mode: NoI 19:16:05 OPC: NoI 19:16:05 BURN-Proof: EnabledI 19:16:08 Write Speed Successfully Set! - Effective: 17,984 KB/s (4x)I 19:16:23 Filling Buffer... (80 MiB)I 19:16:24 Writing LeadIn...I 19:16:25 Writing Session 1 of 1... (1 Track, LBA: 0 - 11929119)I 19:16:25 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 11929119)W 19:16:26 Failed to Write Sectors 7904 - 7935 - Reason: The semaphore timeout period has expired.W 19:16:26 Retrying (1 of 20)...W 19:17:24 Retry Failed - Reason: The semaphore timeout period has expired.W 19:17:24 Retrying (2 of 20)... At this point the program hangs and I can't get it to abort - not until I physically remove the USB cable. Even if I reboot the machine the drive keeps "writing", although it's not really writing the files... I've updated and re-installed every possible driver that would have an influence on it. I thought for a while that my machine might not have been recognizing the enclosure as a USB 3 model and that might be causing a bottleneck, but that's not the case with the new enclosure and the16D1HT drive at all, and once I found out where to check it, that wasn't the issue anyway. Out of other options, I tried burning a disk with the included CyberLink PowerBackup software, and amazingly it worked. I successfully burned a BD-R and also restored it successfully. The files all compared OK. I'd much prefer using ImgBurn, so that I have direct access to individual files, but it seems something happened suddenly that I can't explain. I've read many of the posts in this forum that talk about chipset driver issues, but that wasn't something that changed. Why would ImgBurn suddenly start having trouble with the drives and CyberLink not?
LIGHTNING UK! Posted December 23, 2016 Posted December 23, 2016 Boot into safe mode and see if you have the same issue. It's weird that something (Windows or a driver) is timing out after such a short period of time to begin with - literally, 1 second - and then after about 1 minute following the first 'retry'. That doesn't make much sense. There isn't much I can do with I/O comms issues I'm afraid. ImgBurn just submits commands and waits for a response.
SavOak Posted December 23, 2016 Author Posted December 23, 2016 I tried it in Safe Mode, with similar results. Only difference is that I thought it was going to be OK - almost reached 4x speed at the beginning of the burn, but then stopped after about 3%. This time the program hung on the second retry: I 12:16:30 ImgBurn Version 2.5.8.0 started!I 12:16:30 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200, Safe Mode)I 12:16:30 Total Physical Memory: 25,117,908 KiB - Available: 24,083,608 KiBE 12:16:30 Failed to check for ImgBurn update!I 12:16:30 Initialising SPTI...I 12:16:30 Searching for SCSI / ATAPI devices...I 12:16:30 -> Drive 1 - Info: ASUS BW-16D1HT 3.00 (G:) (USB 2.0)I 12:16:30 -> Drive 2 - Info: Slimtype DVD A DS8A8SH KAA3 (E:) (SATA)I 12:16:30 Found 1 DVD±RW/RAM and 1 BD-RE XL!I 12:19:12 Operation Started!I 12:19:12 Building Image Tree...I 12:19:12 Checking Directory Depth...I 12:19:12 Calculating Totals...I 12:19:12 Preparing Image...I 12:19:13 Checking Path Length...I 12:19:13 Contents: 372 Files, 33 FoldersI 12:19:13 Content Type: DataI 12:19:13 Data Type: MODE1/2048I 12:19:13 File System(s): ISO9660, UDF (1.02)I 12:19:13 Volume Label: [Not Configured]I 12:19:13 Size: 24,901,550,282 bytesI 12:19:13 Sectors: 12,159,168I 12:19:13 Image Size: 24,903,548,928 bytesI 12:19:13 Image Sectors: 12,159,936I 12:19:13 Operation Successfully Completed! - Duration: 00:00:00I 12:33:55 Operation Started!I 12:33:55 Building Image Tree...I 12:33:55 Calculating Totals...I 12:33:55 Preparing Image...I 12:33:56 Contents: 372 Files, 33 FoldersI 12:33:56 Content Type: DataI 12:33:56 Data Type: MODE1/2048I 12:33:56 File System(s): UDF (2.50)I 12:33:56 Volume Label: _private_ 20160914,0921,0924,0928,1001,1005,1008_1I 12:33:56 Size: 24,901,550,282 bytesI 12:33:56 Sectors: 12,159,168I 12:33:56 Image Size: 24,904,597,504 bytesI 12:33:56 Image Sectors: 12,160,448I 12:34:03 Operation Successfully Completed! - Duration: 00:00:07I 12:34:03 Operation Started!I 12:34:03 Source File: -==/\/[bUILD IMAGE]\/\==-I 12:34:03 Source File Sectors: 12,160,448 (MODE1/2048)I 12:34:03 Source File Size: 24,904,597,504 bytesI 12:34:03 Source File Volume Identifier: _private_ 20160914,0921,0924,0928,1001,1005,1008_1I 12:34:03 Source File Volume Set Identifier: 4997643B00B98BC0I 12:34:03 Source File Application Identifier: ImgBurn v2.5.8.0I 12:34:03 Source File Implementation Identifier: ImgBurnI 12:34:03 Source File File System(s): UDF (2.50)I 12:34:03 Destination Device: [0:0:0] ASUS BW-16D1HT 3.00 (G:) (USB)I 12:34:03 Destination Media Type: BD-R (Disc ID: UMEBDR-016-000)I 12:34:03 Destination Media Supported Write Speeds: 4x, 6x, 8xI 12:34:03 Destination Media Sectors: 12,219,392I 12:34:03 Write Mode: BDI 12:34:03 Write Type: DAOI 12:34:03 Write Speed: 4xI 12:34:03 Hardware Defect Management Active: NoI 12:34:03 BD-R Verify Not Required: YesI 12:34:03 Link Size: AutoI 12:34:03 Lock Volume: YesI 12:34:03 Test Mode: NoI 12:34:03 OPC: NoI 12:34:03 BURN-Proof: EnabledI 12:34:03 Write Speed Successfully Set! - Effective: 17,984 KB/s (4x)I 12:34:18 Filling Buffer... (80 MiB)I 12:34:19 Writing LeadIn...I 12:34:20 Writing Session 1 of 1... (1 Track, LBA: 0 - 12160447)I 12:34:20 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 12160447)W 12:35:13 Failed to Write Sectors 458336 - 458367 - Reason: The semaphore timeout period has expired.W 12:35:13 Retrying (1 of 20)...W 12:36:11 Retry Failed - Reason: The semaphore timeout period has expired.W 12:36:11 Retrying (2 of 20)... I tried again thinking that it might have something to do with the UDF version, but of course it didn't: I 13:12:57 ImgBurn Version 2.5.8.0 started!I 13:12:57 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200)I 13:12:57 Total Physical Memory: 25,117,908 KiB - Available: 22,261,024 KiBI 13:12:57 Initialising SPTI...I 13:12:57 Searching for SCSI / ATAPI devices...I 13:12:57 -> Drive 1 - Info: ASUS BW-16D1HT 3.00 (G:) (USB 2.0)I 13:12:57 -> Drive 2 - Info: Slimtype DVD A DS8A8SH KAA3 (E:) (SATA)I 13:12:57 Found 1 DVD±RW/RAM and 1 BD-RE XL!I 13:15:16 Operation Started!I 13:15:16 Building Image Tree...I 13:15:17 Calculating Totals...I 13:15:17 Preparing Image...I 13:15:17 Contents: 372 Files, 33 FoldersI 13:15:17 Content Type: DataI 13:15:17 Data Type: MODE1/2048I 13:15:17 File System(s): UDF (1.02)I 13:15:17 Volume Label: sundrops 20160914,0921,0924,0928,1001,1005,1008_1I 13:15:17 Size: 24,901,550,282 bytesI 13:15:17 Sectors: 12,159,168I 13:15:17 Image Size: 24,903,483,392 bytesI 13:15:17 Image Sectors: 12,159,904I 13:15:17 Operation Successfully Completed! - Duration: 00:00:00I 13:15:32 Operation Started!I 13:15:32 Building Image Tree...I 13:15:32 Calculating Totals...I 13:15:32 Preparing Image...I 13:15:32 Contents: 372 Files, 33 FoldersI 13:15:32 Content Type: DataI 13:15:32 Data Type: MODE1/2048I 13:15:32 File System(s): UDF (1.02)I 13:15:32 Volume Label: _private_ 20160914,0921,0924,0928,1001,1005,1008_1I 13:15:32 Size: 24,901,550,282 bytesI 13:15:33 Sectors: 12,159,168I 13:15:33 Image Size: 24,903,483,392 bytesI 13:15:33 Image Sectors: 12,159,904I 13:15:36 Operation Successfully Completed! - Duration: 00:00:03I 13:15:36 Operation Started!I 13:15:36 Source File: -==/\/[bUILD IMAGE]\/\==-I 13:15:36 Source File Sectors: 12,159,904 (MODE1/2048)I 13:15:36 Source File Size: 24,903,483,392 bytesI 13:15:36 Source File Volume Identifier: _private_ 20160914,0921,0924,0928,1001,1005,1008_1I 13:15:36 Source File Volume Set Identifier: 499769F000B98B81I 13:15:36 Source File Application Identifier: ImgBurn v2.5.8.0I 13:15:36 Source File Implementation Identifier: ImgBurnI 13:15:36 Source File File System(s): UDF (1.02)I 13:15:36 Destination Device: [0:0:0] ASUS BW-16D1HT 3.00 (G:) (USB)I 13:15:36 Destination Media Type: BD-R (Disc ID: UMEBDR-016-000)I 13:15:36 Destination Media Supported Write Speeds: 4x, 6x, 8xI 13:15:36 Destination Media Sectors: 12,219,392I 13:15:36 Write Mode: BDI 13:15:36 Write Type: DAOI 13:15:36 Write Speed: 4xI 13:15:36 Hardware Defect Management Active: NoI 13:15:36 BD-R Verify Not Required: YesI 13:15:36 Link Size: AutoI 13:15:36 Lock Volume: YesI 13:15:36 Test Mode: NoI 13:15:36 OPC: NoI 13:15:36 BURN-Proof: EnabledI 13:15:36 Write Speed Successfully Set! - Effective: 17,984 KB/s (4x)I 13:15:51 Filling Buffer... (80 MiB)I 13:15:52 Writing LeadIn...I 13:15:54 Writing Session 1 of 1... (1 Track, LBA: 0 - 12159903)I 13:15:54 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 12159903)W 13:16:33 Failed to Write Sectors 341120 - 341151 - Reason: The semaphore timeout period has expired.W 13:16:33 Retrying (1 of 20)...I 13:16:57 Abort Request AcknowledgedW 13:17:02 Retry Failed - Reason: The semaphore timeout period has expired.E 13:17:02 Failed to Write Sectors 341120 - 341151 - Reason: The semaphore timeout period has expired. Hangs again, until I physically disconnect the USB drive, then reconnect: W 13:17:02 Device Removal Detected!W 13:17:02 The device list will be refreshed at the next available opportunity.I 13:17:02 Synchronising Cache...W 13:17:02 Synchronise Cache Failed! - Reason: The specified network resource or device is no longer available.W 13:17:04 Device Arrival Detected!W 13:17:04 The device list will be refreshed at the next available opportunity.W 13:17:07 Synchronise Cache Failed! - Reason: The specified network resource or device is no longer available.W 13:17:09 User opted to skip the 'Close Track/Session/Disc' functions.E 13:17:09 Failed to Write Image!I 13:17:10 Exporting Graph Data...I 13:17:10 Graph Data File: _private_\AppData\Roaming\ImgBurn\Graph Data Files\ASUS_BW-16D1HT_3.00_FRIDAY-DECEMBER-23-2016_1-15_PM_UMEBDR-016-000_4x.ibgI 13:17:10 Export Successfully Completed!E 13:17:10 Operation Failed! - Duration: 00:01:33I 13:17:10 Average Write Rate: 10,032 KiB/s (2.3x) - Maximum Write Rate: 17,915 KiB/s (4.1x)I 13:17:10 Searching for SCSI / ATAPI devices...I 13:17:10 -> Drive 1 - Info: Slimtype DVD A DS8A8SH KAA3 (E:) (SATA)I 13:17:11 -> Drive 2 - Info: ASUS BW-16D1HT 3.00 (F:) (USB 2.0)I 13:17:11 Found 1 DVD±RW/RAM and 1 BD-RE XL! The directory structure and filenames are written to the disk, and whatever files do get written are OK.I can't imagin e what is going on, but it only seems to be a problem for ImgBurn. BurnAware Free also works OK. I guess I'll just try it again when I mount one of the drives in a different computer.
LIGHTNING UK! Posted December 24, 2016 Posted December 24, 2016 You'll have to try a different I/O interface. That could mean installing another program that installs one of the supported ones.
SavOak Posted December 24, 2016 Author Posted December 24, 2016 Not sure I know exactly what you're be referring to. Are you talking about software that would install a different USB 3 driver? Or do you mean something like eSATA? I wish I had that on this machine, but I don't. Maybe there's some way I can use the Thunderbolt port, I'm reluctant to buy a Blu-Ray burner to install in place of the OEM DVD multi-writer, which is on the SATA bus, because I'm looking forward to upgrading to a more current model with Thunderbolt 3 this year. The system uses the "Intel® USB 3.0 eXtensible Host Controller - Microsoft", which I've already uninstalled and reinstalled. The one other suggestion that I haven't tried was reinstalling the USB drivers in Windows 8.1 compatibility mode, but I was running Windows 10 on this machine for over a year without any problems. It's just strange. I'll post again if I can get something figured out, in case anyone else has this issue.
Ch3vr0n Posted December 24, 2016 Posted December 24, 2016 I think what lightning means it's installing something that installs an io controller. Like virtual clone drive from elaborate bytes (free) which installs elbycdio.dll that can then be selected in IMGBurn, or daemon tools (which installs sptd but I nor ImgBurn like that one very much). See if that makes any difference, an io controller is completely different from the physical connection the drive uses. The USB driver is also a different component to the overall equation.
SavOak Posted December 24, 2016 Author Posted December 24, 2016 @Ch3vr0n Thanks for the clarification; I wasn't aware of that. I'll give it a try when I have time after the holidays and report back.
Ch3vr0n Posted December 24, 2016 Posted December 24, 2016 If you'll look in your logs you'll see a line referring 'SPTI', that's the default one and issued by Microsoft in Windows. Elbycdio is about and sptd yet another. Sent from my Nexus 6P with Tapatalk.
SavOak Posted January 20, 2017 Author Posted January 20, 2017 Excellent suggestion. I don't know what MS did to screw SPTI up for me, but switching to Elbycdio did the trick. ImgBurn and the drive have been working fine as of late. Right after I made the switch, the program would sometimes hang when it was calculating the image size (or getting ready to burn the disk), giving me a message about having to terminate a process. That only lasted for about 30 or 60 seconds, then it would proceed. After a few reboots and another Windows 10 update, I'm having no problems at all. Thanks for the tip!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now