Jump to content

imgburn "the semaphore timeout period has expired"


padard
 Share

Recommended Posts

I have an ASUS-24B1ST c 1.05 drive connected to my laptop through an X360USB Pro. I've obviously used the burner max payload tool to increase the capacity of the size of the my disc (MKM-003) every time, but I run into this problem where I'll burn a game through imgburn and and at some random point during the burn, I get an error message somewhat along the lines of "the semaphore timeout period has expired." I've been rarely successful at burning games that actually work in my xbox due to this error and even the ones that are successfully burned will most of the time not work. I have a ton of coasters and am hoping someone will help me resolve this problem. Another thing to mention is that my drive will very very rarely recognize my verbatims (MKM-003) unless I put in a regular CD-ROM prior to inserting my verbatim and most of the time, it won't even recognize my verbatims even after doing this. Does this have something to do with the drive being connected to my laptop through a USB/SATA combo? Does this hinder the connection to my laptop somehow? I've read other topics on this forum regarding this issue and would not be asking this question unless I felt completely helpless and clueless. Here's the log: 

 

I 02:26:36 ImgBurn Version 2.5.8.0 started!
I 02:26:36 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7601 : Service Pack 1)
I 02:26:36 Total Physical Memory: 3,988,320 KiB  -  Available: 1,825,204 KiB
I 02:26:36 Initialising SPTI...
I 02:26:36 Searching for SCSI / ATAPI devices...
I 02:26:37 -> Drive 1 - Info: HL-DT-ST DVDRAM GT20F ET11 (D:) (ATAPI)
I 02:26:37 -> Drive 2 - Info: ASUS DRW-24B1ST   c 1.05 (E:) (USB 2.0)
I 02:26:37 Found 2 DVD±RW/RAMs!
I 02:27:52 Operation Started!
I 02:27:52 Source File: C:\Users\Owner\Documents\XBOX 360 GAMES\far cry 3\cry.dvd
I 02:27:52 Source File Sectors: 4,267,015 (MODE1/2048)
I 02:27:52 Source File Size: 8,738,846,720 bytes
I 02:27:52 Source File Volume Identifier: DVD_ROM
I 02:27:52 Source File Volume Set Identifier: ae9a8000MS UDFBridge
I 02:27:52 Source File Application Identifier: CDIMAGE 2.45 (12/06/2000 TM)
I 02:27:52 Source File Implementation Identifier: Microsoft CDIMAGE UDF
I 02:27:52 Source File File System(s): ISO9660, UDF (1.50)
I 02:27:52 Destination Device: [0:0:0] ASUS DRW-24B1ST   c 1.05 (E:) (USB)
I 02:27:52 Destination Media Type: DVD+R DL (Disc ID: MKM-003-00)
I 02:27:52 Destination Media Supported Write Speeds: 4x, 6x, 8x
I 02:27:52 Destination Media Sectors: 4,267,040
I 02:27:52 Destination Media L0 Data Zone Capacity: 2,133,520 (Changeable: Yes)
I 02:27:52 Write Mode: DVD
I 02:27:52 Write Type: DAO
I 02:27:52 Write Speed: 4x
I 02:27:52 DVD+R DL Reserve Track: No
I 02:27:52 Link Size: Auto
I 02:27:52 Lock Volume: Yes
I 02:27:52 Test Mode: No
I 02:27:52 OPC: No
I 02:27:52 BURN-Proof: Enabled
I 02:27:53 Write Speed Successfully Set! - Effective: 5,540 KB/s (4x)
I 02:27:53 Book Type Setting: N/A (Reason: Invalid Field in CDB)
I 02:27:53 Advanced Settings - Force HT: Yes, Online HT: No, OverSpeed: No, SmartBurn: Yes
I 02:27:53 CD/DVD Life Record Count: 10 - CD/DVD Record Count: 3
I 02:27:53 Optimal L0 Data Zone Capacity: 2,133,520
I 02:27:53 Optimal L0 Data Zone Method: Copied From Original Disc
I 02:28:20 Set L0 Data Zone Capacity Succeeded!
I 02:28:20 L0 Data Zone Capacity - Effective: 2,133,520
I 02:28:21 Filling Buffer... (512 MiB)
I 02:28:28 Writing LeadIn...
I 02:28:30 Writing Session 1 of 1... (1 Track, LBA: 0 - 4267014)
I 02:28:30 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 4267014)
I 02:28:30 Writing Layer 0... (LBA: 0 - 2133519)
I 02:41:29 Writing Layer 1... (LBA: 2133520 - 4267014)
W 02:45:02 Failed to Write Sectors 2703792 - 2703823 - Reason: The semaphore timeout period has expired.
W 02:45:02 Retrying (1 of 20)...
W 02:45:02 Retry Failed - Reason: The device is not connected.
W 02:45:02 Retrying (2 of 20)...
W 02:45:02 Retry Failed - Reason: The device is not connected.
W 02:45:02 Retrying (3 of 20)...
W 02:45:02 Retry Failed - Reason: The device is not connected.
W 02:45:02 Retrying (4 of 20)...
W 02:45:02 Retry Failed - Reason: The device is not connected.
W 02:45:02 Retrying (5 of 20)...
W 02:45:02 Retry Failed - Reason: The device is not connected.
W 02:45:02 Retrying (6 of 20)...
W 02:45:02 Retry Failed - Reason: The device is not connected.
W 02:45:02 Retrying (7 of 20)...
W 02:45:02 Retry Failed - Reason: The device is not connected.
W 02:45:02 Retrying (8 of 20)...
W 02:45:02 Retry Failed - Reason: The device is not connected.
W 02:45:02 Retrying (9 of 20)...
W 02:45:02 Retry Failed - Reason: The device is not connected.
W 02:45:02 Retrying (10 of 20)...
W 02:45:02 Retry Failed - Reason: The device is not connected.
W 02:45:02 Retrying (11 of 20)...
W 02:45:02 Retry Failed - Reason: The device is not connected.
W 02:45:02 Retrying (12 of 20)...
W 02:45:02 Retry Failed - Reason: The device is not connected.
W 02:45:02 Retrying (13 of 20)...
W 02:45:02 Retry Failed - Reason: The device is not connected.
W 02:45:02 Retrying (14 of 20)...
W 02:45:02 Retry Failed - Reason: The device is not connected.
W 02:45:02 Retrying (15 of 20)...
W 02:45:02 Retry Failed - Reason: The device is not connected.
W 02:45:02 Retrying (16 of 20)...
W 02:45:02 Retry Failed - Reason: The device is not connected.
W 02:45:02 Retrying (17 of 20)...
W 02:45:02 Retry Failed - Reason: The device is not connected.
W 02:45:02 Retrying (18 of 20)...
W 02:45:02 Retry Failed - Reason: The device is not connected.
W 02:45:02 Retrying (19 of 20)...
W 02:45:02 Retry Failed - Reason: The device is not connected.
W 02:45:02 Retrying (20 of 20)...
W 02:45:02 Retry Failed - Reason: The device is not connected.
W 02:45:02 Device Removal Detected!
W 02:45:02 The device list will be refreshed at the next available opportunity.
W 02:45:15 Device Removal Detected!
W 02:45:15 The device list will be refreshed at the next available opportunity.
E 02:55:54 Failed to Write Sectors 2703792 - 2703823 - Reason: The semaphore timeout period has expired.
I 02:55:54 Synchronising Cache...
W 02:55:54 Synchronise Cache Failed! - Reason: The device is not connected.
E 02:55:57 Synchronise Cache Failed! - Reason: The device is not connected.
W 02:55:58 User opted to skip the 'Close Track/Session/Disc' functions.
E 02:55:58 Failed to Write Image!
W 02:55:58 Device Removal Detected!
W 02:55:58 The device list will be refreshed at the next available opportunity.
I 02:55:59 Exporting Graph Data...
I 02:55:59 Graph Data File: C:\Users\Owner\AppData\Roaming\ImgBurn\Graph Data Files\ASUS_DRW-24B1ST_c_1.05_THURSDAY-AUGUST-15-2013_2-27_AM_MKM-003-00_4x.ibg
I 02:55:59 Export Successfully Completed!
E 02:55:59 Operation Failed! - Duration: 00:28:05
I 02:55:59 Average Write Rate: 3,289 KiB/s (2.4x) - Maximum Write Rate: 5,507 KiB/s (4.1x)
E 02:56:02 CreateFile Failed! - Device: '\\?\usbstor#cdrom&ven_asus&prod_drw-24b1st___c&rev_1.05#000000000002&0#{53f56308-b6bf-11d0-94f2-00a0c91efb8b}'
E 02:56:02 Reason: The system cannot find the file specified.
I 02:56:02 Searching for SCSI / ATAPI devices...
I 02:56:03 -> Drive 1 - Info: HL-DT-ST DVDRAM GT20F ET11 (D:) (ATAPI)
I 02:56:03 Found 1 DVD±RW/RAM!
 
Link to comment
Share on other sites

My experience with the semaphore time out period has expired error is a conflict between your drive and a controller on the motherboard. Unfortunately, this error rarely gets resolved except by actually replacing the controller in the drive or on the motherboard. This problem was fairly regular on USB optical drives and was caused by using certain ATA to USB bridges in the controller in the drive. So, the only solution was to replace the controller in the drive, which meant using a different drive as the controllers were never designed to be updated by software.

 

 

There might be some solutions where a software driver could be causing the problem and updating the chipset software might work. I don't have much to offer in the way of how to do that, though. So, maybe somebody else can help.

 

 

Do you get this semaphore time out when you try to burn other types of discs other than games?

Link to comment
Share on other sites

That's very odd. The drive is relatively new and replacing the controller would seem like overkill, but I feel like a direct SATA connection to my PC might do the trick, as my previous drives have faced the same problem with the "semaphore timeout period has expired" error when indirectly connected to my laptop. The thing is that I don't burn anything else besides games on my drive and so I can't say for sure if the same problem occurs with different types of media. I have inserted CD-ROM's and DVD-ROM's that already contained content on them that worked once I inserted them into my drive, but when it comes to burning through imgburn, this problem constantly arises. I will try to connect my drive to my PC directly and see if that makes a difference. I'll post here again once I'm done to keep you updated on the issue. Do you know if this might work?

Link to comment
Share on other sites

 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.