Jump to content

360 burns failing with time-out/bogus driver errors


Sigma

Recommended Posts

Hi,

 

I'm having an issue burning Xbox 360 games. I originally had a Lite-On iHAS224B cross-flashed to a 624B. It worked fine for about 11 months and then all of a sudden only about 1 in 5 discs would burn. I replaced it with a 124B which is cross-flashed to a 524B, but I am getting the exact same errors with this drive too.

 

I don't have a full log to hand right now, but most of the failures end with a string of these: -

 

Retry Failed - Reason: Invalid Address For Write

 

Followed by: -

 

Reason: Logical Unit Communication Time-Out

 

Occasionally I will get this error: -

 

Retry Failed - Reason: Invalid Address For Write

Potential Bogus Driver Error Detected!

 

I only use Verbatim MKM-003-00 discs and I have 3 different spindles of them here (all made in Singapore) and have tried discs from each spindle - same result, so it's not the discs.

 

I've tried 2 different drives, so it doesn't seem to be the drive.

 

I've tried various combinations of settings/burn speeds, even though the same settings/4X burn speed worked fine for me for months - nothing consistently works.

 

I've always used ImgBurn to burn and nothing's changed there, so it's not that.

 

Here's the specs of my PC: -

 

Core i7 3770K

Asus Maximus IV GENE-Z/GEN3 MOBO

16GB RAM

128GB SSD

2TB SATA-3 HDD

Gigabyte GTX 670 GPU

Seasonic X-760 PSU

Windows 7 Professional 64 bit

 

The PC is well maintained. I have not installed any new software on it for ages, although I have updated some software but none of those updates coincided with this issue starting. The BIOS, all drivers and Windows updates are all fully up to date.

 

Any idea what could be causing this? It's driving me crazy. I thought it had to be the drive, but now that I've replaced that and I'm getting the exact same problems I'm stumped.

 

Thanks!

Edited by Sigma
Link to comment
Share on other sites

Do you check your ISo with ABGX360 and do you perform OPC before write and write at 4x speed?

 

abgx360 - Yes and it checks out 100%.

 

OPC before write - I've tried it with that and without it. I've tried various speeds. I've tried various combinations of the options.

 

These are the settings that worked perfectly for 11 months or so: -

 

Burn speed = 4X.

OPC, OHT, OSW = Disabled.

FHT, SmartBurn = On.

 

Those settings were recommended to me by Lightning UK. When I first got a Burner Max-capable drive, I was using c4eva's recommended settings but they didn't result in good burns. I came here to ask for advice and Lightning gave me those settings which worked fine for 11 months or so (I think I had 1 or 2 burns fail at the layer break, but aside from that I had lots of excellent burns with very low error rates in Kprobe and they all worked fine on the 360).

 

@Lightning - I will post a log when I can. I've just tried 3 burns in a row and all have completed successfully, except they all have massive error rates in KProbe and they all give dirty disc errors on the 360. I'm trying to get a burn to fail so I have a log to show you, lol, but either way - I'm unable to get a burn that works any more.

Edited by Sigma
Link to comment
Share on other sites

If I go to Help - Imgburn logs... it just opens a folder where only 1 log (from the most recent burn) exists. Or am I looking in the wrong place?

 

Family tree info: -

 

RIJBx.jpg

 

Here's the filter driver load order if that's any use: -

 

tCH4M.jpg

 

As soon as I get a decent log to post, I'll post it up.

Link to comment
Share on other sites

That log file should contain the info from several burns... all on top of each other - so try and scroll down :)

 

You should probably try installing the Intel Rapid Storage Tech drivers. Try version 10.8

 

http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y...g=eng&OSVersion==

 

You want the 'STOR_allOS_10.8.0.1003.exe' one.

Link to comment
Share on other sites

Thanks! What does that do? I don't like installing stuff unless I have to and it seems weird that I had no problems for 11 months without installing this. Of course, if it can fix the issue, I will give it a go.

 

Could installing other drivers cause these issues? I recently updated the drivers for my graphics cards (onboard and discrete), my network adapter, and my Samsung phone. I wouldn't have thought that any of those things could affect burning discs, but could they? I would really like to figure out what exactly has changed about my machine to cause this as it's frustrating.

Link to comment
Share on other sites

I'm still having issues. I started burning a disc and went to get a cup of coffee and when I came back, I noticed that the light on my burner wasn't flashing. In ImgBurn, the progress bar was stuck at 15% and the write rate was at 0, but there were no errors in the log at that point. I waited a little while and cancelled the burn, and it took ages for ImgBurn to cancel and then an I/O error appeared in the log.

 

Here's the full log: -

 

I 00:17:36 ImgBurn Version 2.5.7.0 started!

I 00:17:36 Microsoft Windows 7 Professional x64 Edition (6.1, Build 7601 : Service Pack 1)

I 00:17:36 Total Physical Memory: 16,673,932 KB - Available: 15,127,972 KB

I 00:17:36 Initialising SPTI...

I 00:17:36 Searching for SCSI / ATAPI devices...

I 00:17:36 -> Drive 1 - Info: ATAPI iHAS524 B AL2A (E:) (ATAPI)

I 00:17:36 Found 1 DVD±RW/RAM!

I 00:17:40 Operation Started!

I 00:17:40 Source File: D:\Xbox ISOs\GOW3.iso

I 00:17:40 Source File Sectors: 4,267,015 (MODE1/2048)

I 00:17:40 Source File Size: 8,738,846,720 bytes

I 00:17:40 Source File Volume Identifier: DVD_ROM

I 00:17:40 Source File Volume Set Identifier: c3e78000MS UDFBridge

I 00:17:40 Source File Application Identifier: CDIMAGE 2.45 (12/06/2000 TM)

I 00:17:40 Source File Implementation Identifier: Microsoft CDIMAGE UDF

I 00:17:40 Source File File System(s): ISO9660, UDF (1.50)

I 00:17:40 Destination Device: [1:2:0] ATAPI iHAS524 B AL2A (E:) (ATAPI)

I 00:17:40 Destination Media Type: DVD+R DL (Disc ID: MKM-003-00)

I 00:17:40 Destination Media Supported Write Speeds: 2.4x, 4x, 6x, 8x

I 00:17:40 Destination Media Sectors: 4,267,040

I 00:17:40 Write Mode: DVD

I 00:17:40 Write Type: DAO

I 00:17:40 Write Speed: 4x

I 00:17:40 DVD+R DL Reserve Track: No

I 00:17:40 Link Size: Auto

I 00:17:40 Lock Volume: Yes

I 00:17:40 Test Mode: No

I 00:17:40 OPC: No

I 00:17:40 BURN-Proof: Enabled

I 00:17:40 Write Speed Successfully Set! - Effective: 5,540 KB/s (4x)

I 00:17:40 Book Type Setting: DVD-ROM

I 00:17:40 Advanced Settings - Force HT: Yes, Online HT: No, OverSpeed: No, SmartBurn: Yes

I 00:17:40 Optimal L0 Data Zone Capacity: 2,133,520

I 00:17:40 Optimal L0 Data Zone Method: Copied From Original Disc

I 00:17:40 Set L0 Data Zone Capacity Succeeded!

I 00:17:40 Filling Buffer... (80 MB)

I 00:17:42 Writing LeadIn...

I 00:18:12 Writing Session 1 of 1... (1 Track, LBA: 0 - 4267014)

I 00:18:12 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 4267014)

I 00:18:12 Writing Layer 0... (LBA: 0 - 2133519)

I 00:24:57 Abort Request Acknowledged

E 00:27:28 Failed to Write Sectors 647680 - 647711 - Reason: The request could not be performed because of an I/O device error.

I 00:27:28 Synchronising Cache...

W 00:27:31 User opted to skip the 'Close Track/Session/Disc' functions.

E 00:27:31 Failed to Write Image!

I 00:27:31 Exporting Graph Data...

I 00:27:31 Graph Data File: C:\Users\Steve\AppData\Roaming\ImgBurn\Graph Data Files\ATAPI_iHAS524_B_AL2A_07-OCTOBER-2012_00-17_MKM-003-00_4x.ibg

I 00:27:31 Export Successfully Completed!

E 00:27:31 Operation Aborted! - Duration: 00:09:51

I 00:27:31 Average Write Rate: 2,329 KB/s (1.7x) - Maximum Write Rate: 5,631 KB/s (4.1x)

 

Family tree info after installing the update you linked me to: -

 

I 00:31:18 Family Tree:

I 00:31:18 -> ACPI x64-based PC

I 00:31:18 -> Microsoft ACPI-Compliant System

I 00:31:18 -> PCI bus

I 00:31:18 -> Intel® Desktop/Workstation/Server Express Chipset SATA AHCI Controller (VEN_8086&DEV_1C02 - Intel - iaStor - v10.8.0.1003)

I 00:31:18 -> CD-ROM Drive (ATAPI iHAS524 B) (2)

 

Any ideas?

 

Oh yeah, the only thing I haven't tried is changing the SATA cable, but regular CDs and DVDs burn fine and CDs rip fine, so if the SATA cable was dodgy, would it not affect those tasks too? I'm really at a loss with this, especially as everything worked just fine for so long.

Edited by Sigma
Link to comment
Share on other sites

That's not the problem. As I said above: -

 

These are the settings that worked perfectly for 11 months or so: -

 

Burn speed = 4X.

OPC, OHT, OSW = Disabled.

FHT, SmartBurn = On.

 

Those settings were recommended to me by Lightning UK.

 

I appreciate that you're trying to help, but it seems like you've read a guide on another site and are just telling people to do what it says in that guide no matter what, which isn't really "knowledge", it's just regurgitating information, even when it may not apply.

Edited by Sigma
Link to comment
Share on other sites

Please just stop. I've already told you that I've tried various settings including having OPC on and burning at 4X, and I've told you that the settings I am using were recommended by LIGHTNING UK! - You know, the guy that actually wrote ImgBurn, so I think he knows what he's talking about!

Link to comment
Share on other sites

Have you tried burning more DVD+R DL's since post # 10?

 

If so, what happened with those?

 

Do you use DiscJuggler on your machine? I noticed the pfc filter driver being listed in the screenshot you posted before.

 

I wonder if it might be worth trying to burn from within safe mode, or perhaps inside a 'live' Windows XP as found on Hiren's Boot CD?

Link to comment
Share on other sites

I retried the burn that I attempted in post 10 and this time it worked, but I'm still getting a success rate of about 1 in 4 or 1 in 5, which means a lot of binned discs. :(

 

I haven't used Disc Juggler for years and it's never been installed on this machine. The only other burning software I have is Ashampoo Burning Studio 10, although I've had that installed for months and it hasn't been updated in that time, so I don't think it's that that's causing the issue, even if it's what placed the pfc.sys file on my machine.

 

I'll try your other suggestions next time I need to burn a dual layer disc. Thanks for your help so far.

Link to comment
Share on other sites

×
×
  • Create New...

Important Information

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