Another burning problem

HomeForumsGeneral DiscussionAnother burning problem

This topic has 3 voices, contains 5 replies, and was last updated by avatar Elev8r 2846 days ago.

Viewing 6 posts - 1 through 6 (of 6 total)
Author Posts
Author Posts
2011-11-06 at 08:34PM UTC #3534
avatar
Elev8r

Hi guys

I have a Liteon iHAS 524 B flashed with the Burner Max FW, its connected via SATA to my motherboard, the SATA controller is a JMicron one. The flashing process went without a hitch, but I cannot seem to burn XGD3 iso’s without errors.

I use Verbatim MKM-003-00 discs, with OPC on and verify ticked. I’ve tried 2.4x and 4x, but I get a device I/O error each time.

Here’s what ImgBurn says:

I 16:41:54 ImgBurn Version 2.5.6.0 started!
I 16:41:54 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7601 : Service Pack 1)
I 16:41:54 Total Physical Memory: 6 282 352 KB – Available: 4 173 376 KB
W 16:41:54 Duplex Secure’s SPTD driver can have a detrimental effect on drive performance.
I 16:41:55 Initialising SPTI…
I 16:41:55 Searching for SCSI / ATAPI devices…
I 16:41:55 -> Drive 1 – Info: Optiarc DVD RW AD-7260S 1.03 (H:) (SATA)
I 16:41:55 -> Drive 2 – Info: ATAPI iHAS524 B AL2A (I:) (SATA)
I 16:41:55 -> Drive 3 – Info: LIFWHA VSDQJS1E 1.04 (J:) (SCSI)
I 16:41:55 Found 2 DVD±RW/RAMs and 1 BD-ROM!
I 16:42:48 Operation Started!
I 16:42:48 Source File: D:#LOLXCall_of_Duty_Modern_Warfare_3_XBOX360-STRANGEs-mw3.dvd
I 16:42:48 Source File Sectors: 4 267 015 (MODE1/2048)
I 16:42:48 Source File Size: 8 738 846 720 bytes
I 16:42:48 Source File Volume Identifier: DVD_ROM
I 16:42:48 Source File Volume Set Identifier: 67d90000MS UDFBridge
I 16:42:48 Source File Application Identifier: CDIMAGE 2.45 (12/06/2000 TM)
I 16:42:48 Source File Implementation Identifier: Microsoft CDIMAGE UDF
I 16:42:48 Source File File System(s): ISO9660, UDF (1.50)
I 16:42:48 Destination Device: [7:0:0] ATAPI iHAS524 B AL2A (I:) (SATA)
I 16:42:48 Destination Media Type: DVD+R DL (Disc ID: MKM-003-00)
I 16:42:48 Destination Media Supported Write Speeds: 2.4x, 4x, 6x, 8x
I 16:42:48 Destination Media Sectors: 4 267 040
I 16:42:48 Write Mode: DVD
I 16:42:48 Write Type: DAO
I 16:42:48 Write Speed: 4x
I 16:42:48 Link Size: Auto
I 16:42:48 Lock Volume: Yes
I 16:42:48 Test Mode: No
I 16:42:48 OPC: Yes
I 16:42:48 BURN-Proof: Enabled
I 16:42:48 Write Speed Successfully Set! – Effective: 5 540 KB/s (4x)
I 16:42:48 Book Type Setting: DVD-ROM
I 16:42:48 Advanced Settings – Force HT: No, Online HT: No, OverSpeed: No, SmartBurn: Yes
I 16:43:20 Optimal L0 Data Zone Capacity: 2 133 520
I 16:43:20 Optimal L0 Data Zone Method: Copied From Original Disc
I 16:43:20 Set L0 Data Zone Capacity Succeeded!
I 16:43:20 Filling Buffer… (40 MB)
I 16:43:21 Writing LeadIn…
W 16:43:23 Failed to Write Sectors 576 – 607 – Reason: The request could not be performed because of an I/O device error.
W 16:43:23 Retrying (1 of 20)…
W 16:43:23 Retry Failed – Reason: The request could not be performed because of an I/O device error.
W 16:43:23 Retrying (2 of 20)…
I 16:43:23 Writing LeadIn…
I 16:43:24 Writing Session 1 of 1… (1 Track, LBA: 0 – 4267014)
I 16:43:24 Writing Track 1 of 1… (MODE1/2048, LBA: 0 – 4267014)
I 16:43:24 Writing Layer 0… (LBA: 0 – 2133519)
W 16:43:30 Failed to Write Sectors 17536 – 17567 – Reason: The request could not be performed because of an I/O device error.
W 16:43:30 Retrying (1 of 20)…
W 16:43:30 Retry Failed – Reason: The request could not be performed because of an I/O device error.
W 16:43:30 Retrying (2 of 20)…
W 16:43:30 Retry Failed – Reason: The request could not be performed because of an I/O device error.
W 16:43:30 Retrying (3 of 20)…
I 16:43:30 Writing Sectors…
W 16:44:21 Failed to Write Sectors 158112 – 158143 – Reason: The request could not be performed because of an I/O device error.
W 16:44:21 Retrying (1 of 20)…
W 16:44:22 Retry Failed – Reason: The request could not be performed because of an I/O device error.
W 16:44:22 Retrying (2 of 20)…
W 16:44:22 Retry Failed – Reason: The request could not be performed because of an I/O device error.
W 16:44:22 Retrying (3 of 20)…
W 16:44:22 Retry Failed – Reason: The request could not be performed because of an I/O device error.
W 16:44:22 Retrying (4 of 20)…
W 16:44:22 Retry Failed – Reason: The request could not be performed because of an I/O device error.
W 16:44:22 Retrying (5 of 20)…
W 16:44:22 Retry Failed – Reason: The request could not be performed because of an I/O device error.
W 16:44:22 Retrying (6 of 20)…
W 16:44:22 Retry Failed – Reason: The request could not be performed because of an I/O device error.
W 16:44:22 Retrying (7 of 20)…
W 16:44:22 Retry Failed – Reason: The request could not be performed because of an I/O device error.
W 16:44:22 Retrying (8 of 20)…
I 16:44:22 Writing Sectors…
W 16:44:37 Failed to Write Sectors 198336 – 198367 – Reason: The request could not be performed because of an I/O device error.
W 16:44:37 Retrying (1 of 20)…
W 16:44:37 Retry Failed – Reason: The request could not be performed because of an I/O device error.
W 16:44:37 Retrying (2 of 20)…
W 16:44:37 Retry Failed – Reason: No Additional Sense Information
W 16:44:37 Retrying (3 of 20)…
W 16:44:38 Retry Failed – Reason: The request could not be performed because of an I/O device error.
W 16:44:38 Retrying (4 of 20)…
W 16:44:38 Retry Failed – Reason: The request could not be performed because of an I/O device error.
W 16:44:38 Retrying (5 of 20)…
W 16:44:38 Retry Failed – Reason: The request could not be performed because of an I/O device error.
W 16:44:38 Retrying (6 of 20)…
W 16:44:38 Retry Failed – Reason: The request could not be performed because of an I/O device error.
W 16:44:38 Retrying (7 of 20)…
W 16:44:38 Retry Failed – Reason: The request could not be performed because of an I/O device error.
W 16:44:38 Retrying (8 of 20)…
W 16:44:38 Retry Failed – Reason: The request could not be performed because of an I/O device error.
W 16:44:38 Retrying (9 of 20)…
W 16:44:38 Retry Failed – Reason: The request could not be performed because of an I/O device error.
W 16:44:38 Retrying (10 of 20)…
W 16:44:38 Retry Failed – Reason: The request could not be performed because of an I/O device error.
W 16:44:38 Retrying (11 of 20)…
W 16:44:38 Retry Failed – Reason: The request could not be performed because of an I/O device error.
W 16:44:38 Retrying (12 of 20)…
W 16:44:38 Retry Failed – Reason: The request could not be performed because of an I/O device error.
W 16:44:38 Retrying (13 of 20)…
W 16:44:38 Retry Failed – Reason: The request could not be performed because of an I/O device error.
W 16:44:38 Retrying (14 of 20)…
W 16:44:38 Retry Failed – Reason: The request could not be performed because of an I/O device error.
W 16:44:38 Retrying (15 of 20)…
W 16:44:38 Retry Failed – Reason: The request could not be performed because of an I/O device error.
W 16:44:38 Retrying (16 of 20)…
W 16:44:38 Retry Failed – Reason: The request could not be performed because of an I/O device error.
W 16:44:38 Retrying (17 of 20)…
W 16:44:38 Retry Failed – Reason: The request could not be performed because of an I/O device error.
W 16:44:38 Retrying (18 of 20)…
W 16:44:39 Retry Failed – Reason: The request could not be performed because of an I/O device error.
W 16:44:39 Retrying (19 of 20)…
W 16:44:39 Retry Failed – Reason: The request could not be performed because of an I/O device error.
W 16:44:39 Retrying (20 of 20)…
W 16:44:39 Retry Failed – Reason: The request could not be performed because of an I/O device error.
E 16:44:59 Failed to Write Sectors 198336 – 198367 – Reason: The request could not be performed because of an I/O device error.
I 16:44:59 Synchronising Cache…
W 16:45:05 User opted to skip the ‘Close Track/Session/Disc’ functions.
E 16:45:05 Failed to Write Image!
I 16:45:05 Exporting Graph Data…
I 16:45:05 Graph Data File: C:UsersGregAppDataRoamingImgBurnGraph Data FilesATAPI_iHAS524_B_AL2A_06-NOVEMBER-2011_04-42_PM_MKM-003-00_4x.ibg
I 16:45:05 Export Successfully Completed!
E 16:45:05 Operation Failed! – Duration: 00:02:16
I 16:45:05 Average Write Rate: 4 175 KB/s (3.0x) – Maximum Write Rate: 5 631 KB/s (4.1x)
I 16:45:09 Close Request Acknowledged
I 16:45:09 Closing Down…
I 16:45:10 Shutting down SPTI…
I 16:45:10 ImgBurn closed!

Does anyone know how I can fix this? Thanks in advance for your replies.

2011-11-06 at 09:05PM UTC #3535
avatar
One1Nut

16:42:48 Advanced Settings – Force HT: No, Online HT: No, OverSpeed: No, SmartBurn: Yes

Force HT and Online HT should be on for MKM-003s

Try that and see what happens also, MKM-003s should be burned at 4x

2011-11-06 at 09:10PM UTC #3536
avatar
phrizz

You could try to increase your buffer size from 40MiB to 75MiB or more.

Open ImgBurn, goto Tools -> Settings -> I/O tab, Page 2. Increase the “Buffer Size”

I hate to see people wasting their expensive media, so you might also want to try a different SATA port if you have one available. The only other thing I can think of is to update your SATA chipset drivers. Worst case scenario, try a SATA-to-USB adapter as a last ditch effort, some people have success going that route.

Also, at 2.4x burning OPC should be UNticked I believe.

2011-11-06 at 09:12PM UTC #3537
avatar
phrizz

The settings One1Nut is referring to are within the Eeprom tool packaged with the MAX Burner FW. I would also recommend turning both HyperTuning options on along with SmartBurn on (overspeed off like One1Nut said)

2011-11-06 at 09:21PM UTC #3540
avatar
One1Nut

Yep and like Phrizz said try switching to a different sata port if you have one. I was getting PI and PIF spikes thru the roof in kprobe2 and when I went ahead and switched sata ports (mine has 3 total) the problem went away.

2011-11-07 at 08:55AM UTC #3544
avatar
Elev8r

Switched SATA ports (drive was connected to a port that used a 3rd party controller (JMicron 6GB/s one), switched to the onboard 3GB/s), enabled those two options and now discs burn and verify without errors.

Thank you kind sirs!

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.