More XGD3 woes :(

[bwbag]

Hi all

 

Been using my iHas 524b with Singapore MKM003, had it running a good while ago and it was turning out fantastic backups, with Pi max/average in the region of 10/1, and PIF average about 0.02!

 

For some reason, after attempting to back up Test Drive Unlimited 2 it started turning out very poor backups, with a spike at the layerbreak in the region of 500. I hadnt changed any settings prior to this, so I thought maybe it was a dodgy pack of discs.

 

Bought some new discs at the weekend from two different shops, but met with the same layerbreak issues. I followed Lightnings settings as per the settings thread; after erasing OPC and then switching the system off and back on, I set FHT and SB to enabled. Tried again, with poor results. Once more, I erased OPC, system off and then on, and used a disc from another spindle.

 

Attempted backup is Dragons Dogma using my iHas524b,burnermax f/w, Singapore MKM003. Log is as follows

 

"I 21:54:54 ImgBurn Version 2.5.7.0 started!

I 21:54:54 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3)

I 21:54:54 Total Physical Memory: 1,048,092 KB - Available: 572,000 KB

I 21:54:54 Initialising SPTI...

I 21:54:54 Searching for SCSI / ATAPI devices...

I 21:54:55 -> Drive 1 - Info: ATAPI iHAS524 B AL2A (E:) (RAID)

I 21:54:55 Found 1 DVD±RW/RAM!

I 21:55:47 Operation Started!

I 21:55:47 Source File: C:\Documents and Settings\David\Desktop\dragonsdomga\imars-dragon-RF.dvd

I 21:55:47 Source File Sectors: 4,267,015 (MODE1/2048)

I 21:55:47 Source File Size: 8,738,846,720 bytes

I 21:55:47 Source File Volume Identifier: DVD_ROM

I 21:55:47 Source File Volume Set Identifier: cbf4000

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

I 21:55:47 Source File Implementation Identifier: Microsoft CDIMAGE UDF

I 21:55:47 Source File File System(s): ISO9660, UDF (1.50)

I 21:55:47 Destination Device: [2:2:0] ATAPI iHAS524 B AL2A (E:) (RAID)

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

I 21:55:47 Destination Media Supported Write Speeds: 2.4x, 4x, 6x, 8x

I 21:55:47 Destination Media Sectors: 4,267,040

I 21:55:47 Write Mode: DVD

I 21:55:47 Write Type: DAO

I 21:55:47 Write Speed: 4x

I 21:55:47 DVD+R DL Reserve Track: No

I 21:55:47 Link Size: Auto

I 21:55:47 Lock Volume: Yes

I 21:55:47 Test Mode: No

I 21:55:47 OPC: No

I 21:55:47 BURN-Proof: Disabled

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

I 21:55:47 Book Type Setting: DVD-ROM

I 21:55:47 Advanced Settings - Force HT: Yes, Online HT: No, OverSpeed: No, SmartBurn: Yes

I 21:55:47 Optimal L0 Data Zone Capacity: 2,133,520

I 21:55:47 Optimal L0 Data Zone Method: Copied From Original Disc

I 21:55:47 Set L0 Data Zone Capacity Succeeded!

I 21:56:01 Filling Buffer... (512 MB)

I 21:56:16 Writing LeadIn...

I 21:56:47 Writing Session 1 of 1... (1 Track, LBA: 0 - 4267014)

I 21:56:47 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 4267014)

I 21:56:47 Writing Layer 0... (LBA: 0 - 2133519)

I 22:09:58 Writing Layer 1... (LBA: 2133520 - 4267014)

I 22:26:25 Synchronising Cache...

I 22:26:29 Closing Track...

I 22:26:30 Finalising Disc...

I 22:27:04 Exporting Graph Data...

I 22:27:04 Graph Data File: C:\Documents and Settings\David\Application Data\ImgBurn\Graph Data Files\ATAPI_iHAS524_B_AL2A_13-NOVEMBER-2012_21-55_MKM-003-00_4x.ibg

I 22:27:04 Export Successfully Completed!

I 22:27:04 Operation Successfully Completed! - Duration: 00:31:16

I 22:27:04 Average Write Rate: 4,802 KB/s (3.5x) - Maximum Write Rate: 5,645 KB/s (4.1x)

 

"

 

and heres the Kprobe result graph and log.

 

 

Date : 13/11/2012 22:55:31

Model : 2-0-2-0 ATAPI iHAS524 B AL2A

Disc : DVD+R DL , MKM003 [Mitsubishi Chemical Corporation]

Speed : 4x

ECC blocks sum (PI/PIF) : 8/1

Scanned range : 0 - 4267008

Sampling count : 250306

Errors : 0

PI Max : 464

PI Average : 9.39

PI Total : 294186

PIF Max : 10

PIF Average : 0.32

PIF Total : 10077

 

 

Ive tried a few different games, but it just seems like it really doesnt want to burn decent backups anymore for some reason.

 

Many thanks in advance for help/advice

[LIGHTNING UK!]

I guess the best thing to do now would simply be to try another drive.... but of course that isn't simple at all because they've stopped making the 'B' chipset drives.

 

You could try flashing back to the standard firmware and then back again to the modified one.

 

It might also be worth a shot at burning a full disc in discovery mode whilst on the standard firmware with eeprom settings at defaults values and see how that disc scans.

 

If you get a bad scan from that when there's no overburning involved, you don't really stand a chance of getting a decent overburnt one!

[bwbag]

Thanks for the prompt reply

 

Strangely enough I was in my local PC World the other day, and they had rev B 524s in stock - Im sure they were anyway, as the box barcode listed them as "524 B" on the barcode? I might take a trip in and take the gamble on a new drive. Hoped it wouldnt come to that, but it might be more cost effective. Ill check and see if they still have them, if not, then Ill take a punt at reflashing the drive and teh discovery mode.

 

Much appreciated

[supanova]

I can sencond PC world stocking these . I brought mine from here.They have/had plenty in stock since mergin with curries. Mine were the rev B drive. Also cheapest ive seen.

[bwbag]

Went to PC World, got a new 524-32B for the princely sum of £19.99 Got home and burnermaxed it. Tried a first burn tonight with

 

Smart Burn - on

FHT - on

OS - off

OHT - off

 

OPC - no

 

Heres the kprobe results

 

 

Date : 17/11/2012 00:07:13

Model : 2-0-2-0 ATAPI iHAS524 B AL2A

Disc : DVD+R DL , MKM003 [Mitsubishi Chemical Corporation]

Speed : 4x

ECC blocks sum (PI/PIF) : 8/1

Scanned range : 0 - 4267017

Sampling count : 250554

Errors : 0

PI Max : 35

PI Average : 1.31

PI Total : 40990

PIF Max : 6

PIF Average : 0.08

PIF Total : 2630

 

Thats obviously the first burn so should improve a bit Id imagine. Though the PIF result of 6 is a bit disappointing

 

 

Looks like its solved my problem though, will update again after a few more backups.

 

Many thanks