1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

I haven't burned in about a year or so, now I can't get my burn to complete.

Discussion in 'Xbox 360 - Modding & Hacking' started by breticles, Nov 28, 2014.

  1. breticles

    breticles Member

    Joined:
    Sep 30, 2005
    Messages:
    26
    Likes Received:
    0
    Trophy Points:
    11
    I used to burn many backups and never had much problem. Now I have had 3 burns fail on me all stopped around 40%. I am using a pioneer burner. I quit burning for about a year or so and now every disc fails. I used to always use Verbatim DVD-R DL. I found cheaper discs, Verbatim AZO DVD+R DL and I have been using them this time to try to back up Far Cry 4. Are these discs my problem? Since I had last burned, I have reinstalled Windows, so I had resinstalled ABGX and IMGburn. I have configured their settings many times to make sure they are on par. Do you guys have any idea what my issue may be? Again, I had previously burned many games, but after a year of absence, I can't get anything to work. Here is my log from my recent failure:

    Also, I am aware Far Cry 4 is not verified at the time of this post, but I don't mind.


    I 21:18:54 ImgBurn Version 2.5.8.0 started!
    I 21:18:54 Microsoft Windows 7 Professional x64 Edition (6.1, Build 7601 : Service Pack 1)
    I 21:18:54 Total Physical Memory: 8,387,880 KiB - Available: 5,465,444 KiB
    I 21:18:54 Initialising SPTI...
    I 21:18:54 Searching for SCSI / ATAPI devices...
    I 21:18:54 -> Drive 1 - Info: PIONEER DVD-RW DVR-216D 1.09-GENERAL (D:) (ATA)
    I 21:18:54 Found 1 DVD±RW!
    W 21:30:29 User accepted disc space warning and is attempting to overburn!
    I 21:30:29 Operation Started!
    I 21:30:29 Source File: I:\Torrent DL\Far.Cry.4.NTSC.XBOX360-iMARS\imars.fc4.360.dvd
    I 21:30:29 Source File Sectors: 4,267,015 (MODE1/2048)
    I 21:30:29 Source File Size: 8,738,846,720 bytes
    I 21:30:29 Source File Volume Identifier: DVD_ROM
    I 21:30:29 Source File Volume Set Identifier: f4fb8000MS UDFBridge
    I 21:30:29 Source File Application Identifier: CDIMAGE 2.45 (12/06/2000 TM)
    I 21:30:29 Source File Implementation Identifier: Microsoft CDIMAGE UDF
    I 21:30:29 Source File File System(s): ISO9660, UDF (1.50)
    I 21:30:29 Destination Device: [0:0:0] PIONEER DVD-RW DVR-216D 1.09 (D:) (ATA)
    I 21:30:29 Destination Media Type: DVD+R DL (Disc ID: MKM-003-00)
    I 21:30:29 Destination Media Supported Write Speeds: 2.4x, 4x, 6x, 8x, 10x
    I 21:30:29 Destination Media Sectors: 4,173,824
    I 21:30:29 Destination Media L0 Data Zone Capacity: 2,086,912 (Changeable: Yes)
    I 21:30:29 Write Mode: DVD
    I 21:30:29 Write Type: DAO
    I 21:30:29 Write Speed: 2.4x
    I 21:30:29 DVD+R DL Reserve Track: No
    I 21:30:29 Link Size: Auto
    I 21:30:29 Lock Volume: Yes
    I 21:30:29 Test Mode: No
    I 21:30:29 OPC: No
    I 21:30:29 BURN-Proof: Enabled
    I 21:30:29 Write Speed Successfully Set! - Effective: 3,324 KB/s (2.4x)
    I 21:30:30 Advanced Settings - Optimal Writing Speed: No
    W 21:31:22 User specified layer break position is such that L0 < L1.
    W 21:31:22 Image Size: 4,267,015
    W 21:31:22 User Specified L0 Sectors: 2,086,912
    W 21:31:22 Calculated L1 Sectors: 2,180,103
    I 21:31:22 User Specified L0 Data Zone Capacity: 2,086,912
    I 21:31:48 Set L0 Data Zone Capacity Succeeded!
    I 21:31:48 L0 Data Zone Capacity - Effective: 2,086,912
    I 21:31:48 Filling Buffer... (73 MiB)
    I 21:31:49 Writing LeadIn...
    I 21:31:51 Writing Session 1 of 1... (1 Track, LBA: 0 - 4267014)
    I 21:31:51 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 4267014)
    I 21:31:51 Writing Layer 0... (LBA: 0 - 2086911)
    W 21:46:51 Failed to Write Sectors 1430848 - 1430879 - Reason: Write Error
    W 21:46:51 Retrying (1 of 20)...
    W 21:46:55 Retry Failed - Reason: Invalid Address For Write
    W 21:46:55 Retrying (2 of 20)...
    W 21:46:55 Retry Failed - Reason: Invalid Address For Write
    W 21:46:55 Retrying (3 of 20)...
    W 21:46:55 Retry Failed - Reason: Invalid Address For Write
    W 21:46:55 Retrying (4 of 20)...
    W 21:46:55 Retry Failed - Reason: Invalid Address For Write
    W 21:46:55 Retrying (5 of 20)...
    W 21:46:55 Retry Failed - Reason: Invalid Address For Write
    W 21:46:55 Retrying (6 of 20)...
    W 21:46:55 Retry Failed - Reason: Invalid Address For Write
    W 21:46:55 Retrying (7 of 20)...
    W 21:46:55 Retry Failed - Reason: Invalid Address For Write
    W 21:46:55 Retrying (8 of 20)...
    W 21:46:55 Retry Failed - Reason: Invalid Address For Write
    W 21:46:55 Retrying (9 of 20)...
    W 21:46:55 Retry Failed - Reason: Invalid Address For Write
    W 21:46:55 Retrying (10 of 20)...
    W 21:46:55 Retry Failed - Reason: Invalid Address For Write
    W 21:46:55 Retrying (11 of 20)...
    W 21:46:55 Retry Failed - Reason: Invalid Address For Write
    W 21:46:55 Retrying (12 of 20)...
    W 21:46:55 Retry Failed - Reason: Invalid Address For Write
    W 21:46:55 Retrying (13 of 20)...
    W 21:46:55 Retry Failed - Reason: Invalid Address For Write
    W 21:46:55 Retrying (14 of 20)...
    W 21:46:55 Retry Failed - Reason: Invalid Address For Write
    W 21:46:55 Retrying (15 of 20)...
    W 21:46:55 Retry Failed - Reason: Invalid Address For Write
    W 21:46:55 Retrying (16 of 20)...
    W 21:46:55 Retry Failed - Reason: Invalid Address For Write
    W 21:46:55 Retrying (17 of 20)...
    W 21:46:55 Retry Failed - Reason: Invalid Address For Write
    W 21:46:55 Retrying (18 of 20)...
    W 21:46:55 Retry Failed - Reason: Invalid Address For Write
    W 21:46:55 Retrying (19 of 20)...
    W 21:46:55 Retry Failed - Reason: Invalid Address For Write
    W 21:46:55 Retrying (20 of 20)...
    W 21:46:55 Retry Failed - Reason: Invalid Address For Write
    E 22:13:30 Failed to Write Sectors 1430848 - 1430879 - Reason: Write Error
    E 22:13:30 Next Writable Address: 1430128
    I 22:13:31 Synchronising Cache...
    I 22:13:35 Closing Track...
    I 22:13:50 Finalising Disc...
    E 22:29:58 Failed to Write Image!
    I 22:29:58 Exporting Graph Data...
    I 22:29:58 Graph Data File: C:\Users\breticles\AppData\Roaming\ImgBurn\Graph Data Files\PIONEER_DVD-RW_DVR-216D_1.09_THURSDAY-NOVEMBER-27-2014_9-30_PM_MKM-003-00_2.4x.ibg
    I 22:29:58 Export Successfully Completed!
    E 22:29:58 Operation Failed! - Duration: 00:59:29
    I 22:29:58 Average Write Rate: 1,145 KiB/s (0.8x) - Maximum Write Rate: 3,282 KiB/s (2.4x)

    Thanks for any help that is able to be provided.
     
  2. Eisherz

    Eisherz Active member

    Joined:
    Nov 28, 2006
    Messages:
    2,828
    Likes Received:
    33
    Trophy Points:
    78
    Burn faster.
     
  3. attar

    attar Senior member

    Joined:
    Jun 17, 2005
    Messages:
    11,504
    Likes Received:
    29
    Trophy Points:
    128
    ImgBurn tells me that the free space on a Verbatim DVD+R DL is 8,547,991,552 bytes
     
  4. Eisherz

    Eisherz Active member

    Joined:
    Nov 28, 2006
    Messages:
    2,828
    Likes Received:
    33
    Trophy Points:
    78
    I thought you were already using a payload tool, because that is older than a year by now. You either need a burner compatible with xgd3 burning or a burner compatible with the payload tool. Both allow you to burn DL media over capacity. Just google for payload tool, you'll find the needed instructions.
     
  5. breticles

    breticles Member

    Joined:
    Sep 30, 2005
    Messages:
    26
    Likes Received:
    0
    Trophy Points:
    11
    I am almost positive I remember burning XGD3 without payload tool, because I've never really heard of it, may it has been longer since I've burned. WWE 2k13 was the last thing I burned IIRC. So, 2012, I guess that was 2 years ago. :( XGD3 was out 2 years ago though right?

    Anyway thanks, I have only 1 disc left. I will hope this does the trick, unless anyone else has any advice for me.
     
  6. Eisherz

    Eisherz Active member

    Joined:
    Nov 28, 2006
    Messages:
    2,828
    Likes Received:
    33
    Trophy Points:
    78
    Well, the very first xgd3 games could be burned by using the overburn feature of imgburn, which meant that some parts of the game were missing on the backup disk, but that doesn't work anymore.
     
  7. breticles

    breticles Member

    Joined:
    Sep 30, 2005
    Messages:
    26
    Likes Received:
    0
    Trophy Points:
    11
    Well that would make sense, thank you so much. I will follow the guide with Burnermax, I believe it is supposed to be used with overburn.
     

Share This Page