Jump to content

Buffer dropping out to 60-80%,but will recover.


Recommended Posts

Posted

Hello Imageburn community,

 

 

 

I have a Liteon ihas124 drive,i have crossflashed it to a liteon ihas 324 dvdrom.I have just encounterd a problem while using this drive.The problem is that the Buffer will drop out to 60-80% and will recover to 100% but very slow.My motherboard has set the drive to Ultra DMA 5 which i have checked,and also is set to IDE.The Imageburn logs show no errors and the burn completes fine.Here is imageburn log,as you can see i have manually shut it down after about 80%.I have opened disk management and my CPU(Fx6200) usage is 0-1% and imageburn is the only active application running.I also have 16Gb of memory which only 5% is being used.I am kinda dumbfounded on this issue thanks for any help offered.

 

My settings are set to default in imagburn.

 

 

//****************************************\\

; ImgBurn Version 2.5.7.0 - Log

; Saturday, 13 October 2012, 13:43:54

; \\****************************************//

;

;

I 13:20:31 ImgBurn Version 2.5.7.0 started!

I 13:20:31 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7601 : Service Pack 1)

I 13:20:31 Total Physical Memory: 16,772,644 KB - Available: 15,224,164 KB

I 13:20:31 Initialising SPTI...

I 13:20:31 Searching for SCSI / ATAPI devices...

I 13:20:32 -> Drive 1 - Info: ATAPI iHAS224 B GL0A (D:) (ATA)

I 13:20:32 -> Drive 2 - Info: ATAPI iHAS224 B GL0A (F:) (ATA)

I 13:20:32 -> Drive 3 - Info: ATAPI iHAS324 B AL1B (E:) (ATA)

I 13:20:32 -> Drive 4 - Info: WD Virtual CD 1110 2018 (H:) (USB)

I 13:20:32 Found 3 DVD±RW/RAMs and 1 Unknown!

I 13:21:35 Operation Started!

I 13:21:35 Source File: C:\Users\Xzander\Documents\#XBOX.ISO\blah blah blah

I 13:21:35 Source File Sectors: 4,267,015 (MODE1/2048)

I 13:21:35 Source File Size: 8,738,846,720 bytes

I 13:21:35 Source File Volume Identifier: DVD_ROM

I 13:21:35 Source File Volume Set Identifier: f15c4000MS UDFBridge

I 13:21:35 Source File Application Identifier: CDIMAGE 2.45 (12/06/2000 TM)

I 13:21:35 Source File Implementation Identifier: Microsoft CDIMAGE UDF

I 13:21:35 Source File File System(s): ISO9660, UDF (1.50)

I 13:21:35 Destination Device: [1:1:0] ATAPI iHAS324 B AL1B (E:) (ATA)

I 13:21:35 Destination Media Type: DVD+R DL (Disc ID: MKM-003-00)

I 13:21:35 Destination Media Supported Write Speeds: 2.4x, 4x, 6x, 8x

I 13:21:35 Destination Media Sectors: 4,267,040

I 13:21:35 Write Mode: DVD

I 13:21:35 Write Type: DAO

I 13:21:35 Write Speed: 4x

I 13:21:35 DVD+R DL Reserve Track: No

I 13:21:35 Link Size: Auto

I 13:21:35 Lock Volume: Yes

I 13:21:35 Test Mode: No

I 13:21:35 OPC: No

I 13:21:35 BURN-Proof: Enabled

I 13:21:35 Write Speed Successfully Set! - Effective: 5,540 KB/s (4x)

I 13:21:35 Book Type Setting: DVD-ROM

I 13:21:35 Advanced Settings - Force HT: Yes, Online HT: No, OverSpeed: No, SmartBurn: Yes

I 13:21:35 Optimal L0 Data Zone Capacity: 2,133,520

I 13:21:35 Optimal L0 Data Zone Method: Copied From Original Disc

I 13:21:35 Set L0 Data Zone Capacity Succeeded!

I 13:21:35 Filling Buffer... (80 MB)

I 13:21:36 Writing LeadIn...

I 13:22:08 Writing Session 1 of 1... (1 Track, LBA: 0 - 4267014)

I 13:22:08 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 4267014)

I 13:22:08 Writing Layer 0... (LBA: 0 - 2133519)

I 13:35:20 Writing Layer 1... (LBA: 2133520 - 4267014)

I 13:43:31 Abort Request Acknowledged

I 13:43:31 Synchronising Cache...

W 13:43:39 User opted to skip the 'Close Track/Session/Disc' functions.

E 13:43:39 Failed to Write Image!

I 13:43:44 Exporting Graph Data...

I 13:43:44 Graph Data File: C:\Users\Xzander\AppData\Roaming\ImgBurn\Graph Data Files\ATAPI_iHAS324_B_AL1B_SATURDAY-OCTOBER-13-2012_1-21_PM_MKM-003-00_4x.ibg

I 13:43:44 Export Successfully Completed!

E 13:43:44 Operation Aborted! - Duration: 00:22:04

I 13:43:44 Average Write Rate: 5,384 KB/s (3.9x) - Maximum Write Rate: 5,693 KB/s (4.1x)

I 13:43:54 Close Request Acknowledged

I 13:43:54 Closing Down...

I 13:43:54 Shutting down SPTI...

I 13:43:54 ImgBurn closed!

Posted

Well it appears that i have worked out my own problem by changing Sata ports on my motherboard.Maybe the port went to chit.well it seems to be doing well.

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

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