HyperX Posted September 28, 2011 Posted September 28, 2011 (edited) So i wanted to burn DL dvd and it stopped at Synchronising cache any idea what i can do? I 15:53:50 ImgBurn Version 2.5.5.0 started! I 15:53:50 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7601 : Service Pack 1) I 15:53:50 Total Physical Memory: 4.193.576 KB - Available: 2.275.708 KB I 15:53:50 Initialising SPTI... I 15:53:50 Searching for SCSI / ATAPI devices... I 15:53:50 -> Drive 1 - Info: DTSOFT BDROM 1.05 (K:) (Virtual) I 15:53:50 -> Drive 2 - Info: TSSTcorp CDDVDW SH-S223C me01 (E:) (SATA) I 15:53:50 Found 1 DVD±RW/RAM and 1 BD-ROM! I 15:58:26 Operation Started! I 15:58:26 Source File: C:\Users\xxx\Downloads\lalalala I 15:58:26 Source File Sectors: 3.827.488 (MODE1/2048) I 15:58:26 Source File Size: 7.838.695.424 bytes I 15:58:26 Source File Volume Identifier: DVD_ROM I 15:58:26 Source File Volume Set Identifier: 1b018000MS UDFBridge I 15:58:26 Source File Application Identifier: CDIMAGE 2.45 (12/06/2000 TM) I 15:58:26 Source File Implementation Identifier: Microsoft CDIMAGE UDF I 15:58:26 Source File File System(s): ISO9660; UDF (1.50) I 15:58:26 Destination Device: [0:0:0] TSSTcorp CDDVDW SH-S223C me01 (E:) (SATA) I 15:58:26 Destination Media Type: DVD+R DL (Disc ID: MKM-003-00) (Speeds: 4x; 6x; 8x; 10x) I 15:58:26 Destination Media Sectors: 4.173.824 I 15:58:26 Write Mode: DVD I 15:58:26 Write Type: DAO I 15:58:26 Write Speed: 2,4x I 15:58:26 Link Size: Auto I 15:58:26 Lock Volume: Yes I 15:58:26 Test Mode: No I 15:58:26 OPC: No I 15:58:26 BURN-Proof: Enabled W 15:58:26 Write Speed Miscompare! - MODE SENSE: 5.540 KB/s (4x), GET PERFORMANCE: 8.310 KB/s (6x) W 15:58:26 Write Speed Miscompare! - MODE SENSE: 5.540 KB/s (4x), GET PERFORMANCE: 8.310 KB/s (6x) W 15:58:26 Write Speed Miscompare! - MODE SENSE: 5.540 KB/s (4x), GET PERFORMANCE: 8.310 KB/s (6x) W 15:58:26 Write Speed Miscompare! - MODE SENSE: 5.540 KB/s (4x), GET PERFORMANCE: 8.310 KB/s (6x) W 15:58:26 Write Speed Miscompare! - Wanted: 3.324 KB/s (2,4x), Got: 5.540 KB/s (4x) / 8.310 KB/s (6x) I 15:58:26 Book Type Setting: N/A (Reason: The request could not be performed because of an I/O device error.) I 15:58:26 User Specified L0 Data Zone Capacity: 1.913.760 I 15:58:51 Set L0 Data Zone Capacity Succeeded! I 15:58:52 Filling Buffer... (40 MB) I 15:58:52 Writing LeadIn... I 15:58:53 Writing Session 1 of 1... (1 Track, LBA: 0 - 3827487) I 15:58:53 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 3827487) I 15:58:53 Writing Layer 0... (LBA: 0 - 1913759) I 16:10:49 Writing Layer 1... (LBA: 1913760 - 3827487) I 16:23:14 Synchronising Cache... Edited September 28, 2011 by HyperX
LIGHTNING UK! Posted September 28, 2011 Posted September 28, 2011 Does your motherboard use an Intel chipset? If so, install the latest Intel Rapid Storage Technology drivers. http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=3409&DwnldID=20215&keyword=%22rapid%22&lang=eng There's an me02 firmware update available too. http://www.medion.com/au/service/_lightbox/treiber_details.php?did=9505
HyperX Posted September 28, 2011 Author Posted September 28, 2011 Actualy mother board is MEDIONPC MS-7713
LIGHTNING UK! Posted September 28, 2011 Posted September 28, 2011 Ok so put the latest ATI drivers on then.
HyperX Posted September 28, 2011 Author Posted September 28, 2011 (edited) Ok so put the latest ATI drivers on then. Can you link me ? Please Edited September 28, 2011 by HyperX
LIGHTNING UK! Posted September 28, 2011 Posted September 28, 2011 I'm sure you're every bit as capable of using Google as I am.
HyperX Posted September 29, 2011 Author Posted September 29, 2011 Thanks for help i fixed it with just Firmware update.
LIGHTNING UK! Posted September 29, 2011 Posted September 29, 2011 I'm glad the firmware update appears to have solved your 'sync cache' issue That won't have fixed this issue though... I 15:58:26 Book Type Setting: N/A (Reason: The request could not be performed because of an I/O device error.) That typically comes from the drivers blocking the command - because it's not one they recognise. Updated drivers for the motherboard/controller may or may not fix it.
Recommended Posts