Jump to content
RealModScene
Anonymous

how to fix i/o error for burning xgd3 games

Recommended Posts

hi guys

i am using non verbatim disc for burning games ,my drive is I has 124d today i was try to burn xgd3 game (gta 5) i was use truncate method my sector L0 value is 2086912

but after 49% complete i am getting i/o error this is why,??

image.png

 

here is my log

I 11:29:14 ImgBurn Version 2.5.7.0 started!

I 11:29:14 Microsoft Windows 7 Ultimate Edition (6.1, Build 7600)

I 11:29:14 Total Physical Memory: 2,330,568 KB - Available: 1,088,880 KB

I 11:29:14 Initialising SPTI...

I 11:29:14 Searching for SCSI / ATAPI devices...

I 11:29:15 -> Drive 1 - Info: ATAPI iHAS124 D 8L0A (D:) (ATA)

I 11:29:15 Found 1 DVD±RW/RAM!

I 11:30:29 Operation Started!

I 11:30:29 Source File: F:\x360 games\gta v full image\dvd 2\New folder\gta5truncate.dvd

I 11:30:29 Source File Sectors: 4,173,824 (MODE1/2048)

I 11:30:29 Source File Size: 8,547,991,552 bytes

I 11:30:29 Source File Volume Identifier: DVD_ROM

I 11:30:29 Source File Volume Set Identifier: b75b0000MS UDFBridge

I 11:30:29 Source File Application Identifier: CDIMAGE 2.45 (12/06/2000 TM)

I 11:30:29 Source File Implementation Identifier: Microsoft CDIMAGE UDF

I 11:30:29 Source File File System(s): ISO9660, UDF (1.50)

I 11:30:29 Destination Device: [1:1:0] ATAPI iHAS124 D 8L0A (D:) (ATA)

I 11:30:29 Destination Media Type: DVD+R DL (Disc ID: MBIPG101-R10-65)

I 11:30:29 Destination Media Supported Write Speeds: 4x, 6x, 8x

I 11:30:29 Destination Media Sectors: 4,173,824

I 11:30:29 Write Mode: DVD

I 11:30:29 Write Type: DAO

I 11:30:29 Write Speed: 4x

I 11:30:29 DVD+R DL Reserve Track: No

I 11:30:29 Link Size: Auto

I 11:30:29 Lock Volume: Yes

I 11:30:29 Test Mode: No

I 11:30:29 OPC: No

I 11:30:29 BURN-Proof: Enabled

I 11:30:29 Write Speed Successfully Set! - Effective: 5,540 KB/s (4x)

I 11:30:29 Book Type Setting: DVD-ROM

I 11:30:29 Advanced Settings - Force HT: Yes, Online HT: No, OverSpeed: No, SmartBurn: Yes

I 11:30:29 User Specified L0 Data Zone Capacity: 2,086,912

I 11:30:29 Set L0 Data Zone Capacity Succeeded!

I 11:30:29 Filling Buffer... (80 MB)

I 11:30:31 Writing LeadIn...

I 11:31:02 Writing Session 1 of 1... (1 Track, LBA: 0 - 4173823)

I 11:31:02 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 4173823)

I 11:31:02 Writing Layer 0... (LBA: 0 - 2086911)

W 11:43:51 Failed to Write Sectors 2084832 - 2084863 - Reason: Write Error

W 11:43:51 Retrying (1 of 20)...

W 11:43:51 Retry Failed - Reason: Invalid Address For Write

W 11:43:51 Retrying (2 of 20)...

W 11:43:51 Retry Failed - Reason: Invalid Address For Write

W 11:43:51 Retrying (3 of 20)...

W 11:43:51 Retry Failed - Reason: Invalid Address For Write

W 11:43:51 Retrying (4 of 20)...

W 11:43:51 Retry Failed - Reason: Invalid Address For Write

W 11:43:51 Retrying (5 of 20)...

W 11:43:51 Retry Failed - Reason: Invalid Address For Write

W 11:43:51 Retrying (6 of 20)...

W 11:43:51 Retry Failed - Reason: Invalid Address For Write

W 11:43:51 Retrying (7 of 20)...

W 11:43:51 Retry Failed - Reason: Invalid Address For Write

W 11:43:51 Retrying (8 of 20)...

W 11:43:51 Retry Failed - Reason: Invalid Address For Write

W 11:43:51 Retrying (9 of 20)...

W 11:43:51 Retry Failed - Reason: Invalid Address For Write

W 11:43:51 Retrying (10 of 20)...

W 11:43:51 Retry Failed - Reason: Invalid Address For Write

W 11:43:51 Retrying (11 of 20)...

W 11:43:51 Retry Failed - Reason: Invalid Address For Write

W 11:43:51 Retrying (12 of 20)...

W 11:43:51 Retry Failed - Reason: Invalid Address For Write

W 11:43:51 Retrying (13 of 20)...

W 11:43:51 Retry Failed - Reason: Invalid Address For Write

W 11:43:51 Retrying (14 of 20)...

W 11:43:51 Retry Failed - Reason: Invalid Address For Write

W 11:43:51 Retrying (15 of 20)...

W 11:43:51 Retry Failed - Reason: Invalid Address For Write

W 11:43:51 Retrying (16 of 20)...

W 11:43:51 Retry Failed - Reason: Invalid Address For Write

W 11:43:51 Retrying (17 of 20)...

W 11:43:51 Retry Failed - Reason: Invalid Address For Write

W 11:43:51 Retrying (18 of 20)...

W 11:43:51 Retry Failed - Reason: Invalid Address For Write

W 11:43:51 Retrying (19 of 20)...

W 11:43:51 Retry Failed - Reason: Invalid Address For Write

W 11:43:51 Retrying (20 of 20)...

W 11:43:51 Retry Failed - Reason: Invalid Address For Write

W 11:45:42 Retrying (21)...

W 11:45:42 Retry Failed - Reason: Invalid Address For Write

W 11:46:03 Retrying (22)...

W 11:46:03 Retry Failed - Reason: Invalid Address For Write

W 11:46:03 Retrying (23)...

W 11:46:03 Retry Failed - Reason: Invalid Address For Write

W 11:46:04 Retrying (24)...

W 11:46:04 Retry Failed - Reason: Invalid Address For Write

W 11:46:05 Retrying (25)...

W 11:46:05 Retry Failed - Reason: Invalid Address For Write

W 11:46:05 Retrying (26)...

W 11:46:05 Retry Failed - Reason: Invalid Address For Write

W 11:46:06 Retrying (27)...

W 11:46:06 Retry Failed - Reason: Invalid Address For Write

W 11:46:07 Retrying (28)...

W 11:46:07 Retry Failed - Reason: Invalid Address For Write

W 11:46:08 Retrying (29)...

W 11:46:08 Retry Failed - Reason: Invalid Address For Write

W 11:46:09 Retrying (30)...

W 11:46:09 Retry Failed - Reason: Invalid Address For Write

W 11:46:09 Retrying (31)...

W 11:46:09 Retry Failed - Reason: Invalid Address For Write

W 11:46:10 Retrying (32)...

W 11:46:10 Retry Failed - Reason: Invalid Address For Write

W 11:46:11 Retrying (33)...

W 11:46:11 Retry Failed - Reason: Invalid Address For Write

W 11:46:12 Retrying (34)...

W 11:46:12 Retry Failed - Reason: Invalid Address For Write

W 11:46:15 Retrying (35)...

W 11:46:15 Retry Failed - Reason: Invalid Address For Write

W 11:46:16 Retrying (36)...

W 11:46:16 Retry Failed - Reason: Invalid Address For Write

W 11:46:18 Retrying (37)...

W 11:46:18 Retry Failed - Reason: Invalid Address For Write

W 11:46:20 Retrying (38)...

W 11:46:20 Retry Failed - Reason: Invalid Address For Write

W 11:46:23 Retrying (39)...

W 11:46:23 Retry Failed - Reason: Invalid Address For Write

W 11:46:25 Retrying (40)...

W 11:46:25 Retry Failed - Reason: Invalid Address For Write

W 11:46:26 Retrying (41)...

W 11:46:26 Retry Failed - Reason: Invalid Address For Write

W 11:46:29 Retrying (42)...

W 11:46:29 Retry Failed - Reason: Invalid Address For Write

W 11:46:30 Retrying (43)...

W 11:46:30 Retry Failed - Reason: Invalid Address For Write

W 11:46:31 Retrying (44)...

W 11:46:31 Retry Failed - Reason: Invalid Address For Write

W 11:46:32 Retrying (45)...

W 11:46:32 Retry Failed - Reason: Invalid Address For Write

W 11:46:32 Retrying (46)...

W 11:46:33 Retry Failed - Reason: Invalid Address For Write

W 11:46:33 Retrying (47)...

W 11:46:33 Retry Failed - Reason: Invalid Address For Write

W 11:46:38 Retrying (48)...

W 11:46:38 Retry Failed - Reason: Invalid Address For Write

W 11:46:38 Retrying (49)...

W 11:46:38 Retry Failed - Reason: Invalid Address For Write

W 11:46:39 Retrying (50)...

W 11:46:39 Retry Failed - Reason: Invalid Address For Write

E 11:46:46 Failed to Write Sectors 2084832 - 2084863 - Reason: Write Error

E 11:46:46 Next Writable Address: 2084293

I 11:46:46 Synchronising Cache...

I 11:46:49 Closing Track...

I 11:46:50 Finalising Disc... 

Edited by Swizzy
Cleaned up the bb tags and put the log in a spoiler

Share this post


Link to post
Share on other sites

Use higher quality discs... try clearing the cache etc. etc.

I/O errors are generally caused by sucky discs or sucky laser...

You should also be using the BurnerMax Payload tool to write full XGD3's and not truncate them...

  • Like 1

Share this post


Link to post
Share on other sites

Use higher quality discs... try clearing the cache etc. etc.

I/O errors are generally caused by sucky discs or sucky laser...

You should also be using the BurnerMax Payload tool to write full XGD3's and not truncate them...

yes i did try full burn it was sucessfully 100% done but  unreadable disc error 

Share this post


Link to post
Share on other sites

yes i did try full burn it was sucessfully 100% done but  unreadable disc error

That'd be because you are etheir using bad discs... (low quality) or because you used wrong settings for the burn (you need to adjust your settings so the burn quality is good for your discs with your burner and computer) or... because the console laser is simply unable to read the disc (it's at the end of it's life cycle perhaps?)

Burning XGD3 games is a whole science, before when we had XGD2 it was very easy to burn Xbox 360 games, few errors and such... but now a days they're quite difficult because you have to mix and match various settings to increase the burn quality...

If you want to know why, it's because you are burning more data to the disc then it was designed for... because of that you have to have a really high quality burn...

  • Like 1

Share this post


Link to post
Share on other sites

Use higher quality discs... try clearing the cache etc. etc.

I/O errors are generally caused by sucky discs or sucky laser...

You should also be using the BurnerMax Payload tool to write full XGD3's and not truncate them...

Each time i visit this forum i learn something new... now what's this XGD3's and Burnermax payload tool? :)

Share this post


Link to post
Share on other sites

Each time i visit this forum i learn something new... now what's this XGD3's and Burnermax payload tool? :)

XGD3 is the latest Xbox 360 disc format, XGD stands for Xbox Game Disc, and 3... well, it's the 3:rd one... the first one is for Xbox 1, the second is the first Xbox 360 format and the third is the extended format (slightly bigger discs)

The burnermax payload tool is a tool c4eva wrote that sends a payload to your burner enabling it to "overburn" the disc easier... this tool doesn't work with ALL drives tho, you'll have to read the readme for it to find out which ones are working...

Share this post


Link to post
Share on other sites

XGD3 is the latest Xbox 360 disc format, XGD stands for Xbox Game Disc, and 3... well, it's the 3:rd one... the first one is for Xbox 1, the second is the first Xbox 360 format and the third is the extended format (slightly bigger discs)

The burnermax payload tool is a tool c4eva wrote that sends a payload to your burner enabling it to "overburn" the disc easier... this tool doesn't work with ALL drives tho, you'll have to read the readme for it to find out which ones are working...

Oh that's what XGD means and by xbox 1 u mean the latest console or the very first one.

Cheerz

Share this post


Link to post
Share on other sites

Xbox 1 means not latest console that is first xbox console, XGD IS Abbreviation of xbox game disc ,

Sent from my ST23i using Tapatalk

Share this post


Link to post
Share on other sites

Xbox 1 means not latest console that is first xbox console, XGD IS Abbreviation of xbox game disc ,

Sent from my ST23i using Tapatalk

Oh so means when we say emulators to play xbox 1 games we mean xbox old games not the latest ones. 

Thanx.

Share this post


Link to post
Share on other sites

Oh so means when we say emulators to play xbox 1 games we mean xbox old games not the latest ones. 

Thanx.

Yes, it's kinda confusing... but Xbox 1 (number) is in 9 out of 10 cases related to Classic Xbox, while Xbox One (spelt out) is in 9 out of 10 cases related to Xbox One, the new console

Share this post


Link to post
Share on other sites

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

×