imgburn sticking at 50%

[sas67]

hi,ive just tried burning 2 different games with imgburn and both stuck at 50% during write sectors..i checked the layerbreak and it happened just after(a few sectors after)..im thinking the reason is because im testing out some cheaper media(Aone plus).ive never come across this problem when using verbatims,so is this because using cheaper media?should i use dvddecrypter to burn cheaper media?
this is imgburn logfile

I 22:28:49 ImgBurn Version 2.4.2.0 started!
I 22:28:49 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 3)
I 22:28:49 Total Physical Memory: 1,048,048 KB - Available: 560,128 KB
I 22:28:49 Initialising SPTI...
I 22:28:49 Searching for SCSI / ATAPI devices...
I 22:28:49 Found 1 DVD±RW!
I 22:30:45 Operation Started!
I 22:30:45 Source File: E:\xbox360 games\aur-shhp.dvd
I 22:30:45 Source File Sectors: 3,825,924 (MODE1/2048)
I 22:30:45 Source File Size: 7,835,492,352 bytes
I 22:30:45 Source File Volume Identifier: XGD2DVD_NTSC
I 22:30:45 Source File Volume Set Identifier: 34672923
I 22:30:45 Source File Implementation Identifier: Sonic Scenarist 3.1
I 22:30:45 Source File File System(s): ISO9660, UDF (1.02)
I 22:30:45 Destination Device: [1:0:0] PHILIPS PBDV1640P B3.7 (D:) (ATA)
I 22:30:45 Destination Media Type: DVD+R DL (Disc ID: RICOHJPN-D01-67) (Speeds: 2.4x)
I 22:30:45 Destination Media Sectors: 4,173,824
I 22:30:45 Write Mode: DVD
I 22:30:45 Write Type: DAO
I 22:30:45 Write Speed: 2x
I 22:30:45 Link Size: Auto
I 22:30:45 Test Mode: No
I 22:30:45 OPC: No
I 22:30:45 BURN-Proof: Enabled
I 22:30:45 Optimal L0 Data Zone Capacity: 1,913,760
I 22:30:45 Optimal L0 Data Zone Method: Copied From Original Disc
I 22:30:45 Filling Buffer... (40 MB)
I 22:30:46 Writing LeadIn...
I 22:30:53 Writing Session 1 of 1... (1 Track, LBA: 0 - 3825923)
I 22:30:53 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 3825923)
I 22:30:53 Writing Layer 0... (LBA: 0 - 1913759)
I 22:50:58 Writing Layer 1... (LBA: 1913760 - 3825923)
W 22:51:07 Failed to Write Sectors 1914080 - 1914111 - Reason: Write Error
W 22:51:07 Retrying (1 of 20)...
W 22:51:07 Retry Failed - Reason: Invalid Address For Write
W 22:51:07 Retrying (2 of 20)...
W 22:51:07 Retry Failed - Reason: Invalid Address For Write
W 22:51:07 Retrying (3 of 20)...
W 22:51:07 Retry Failed - Reason: Invalid Address For Write
W 22:51:07 Retrying (4 of 20)...
W 22:51:07 Retry Failed - Reason: Invalid Address For Write
W 22:51:07 Retrying (5 of 20)...
W 22:51:07 Retry Failed - Reason: Invalid Address For Write
W 22:51:07 Retrying (6 of 20)...
W 22:51:07 Retry Failed - Reason: Invalid Address For Write
W 22:51:07 Retrying (7 of 20)...
W 22:51:07 Retry Failed - Reason: Invalid Address For Write
W 22:51:07 Retrying (8 of 20)...
W 22:51:07 Retry Failed - Reason: Invalid Address For Write
W 22:51:07 Retrying (9 of 20)...
W 22:51:07 Retry Failed - Reason: Invalid Address For Write
W 22:51:07 Retrying (10 of 20)...
W 22:51:07 Retry Failed - Reason: Invalid Address For Write
W 22:51:07 Retrying (11 of 20)...
W 22:51:07 Retry Failed - Reason: Invalid Address For Write
W 22:51:07 Retrying (12 of 20)...
W 22:51:07 Retry Failed - Reason: Invalid Address For Write
W 22:51:07 Retrying (13 of 20)...
W 22:51:07 Retry Failed - Reason: Invalid Address For Write
W 22:51:07 Retrying (14 of 20)...
W 22:51:07 Retry Failed - Reason: Invalid Address For Write
W 22:51:07 Retrying (15 of 20)...
W 22:51:07 Retry Failed - Reason: Invalid Address For Write
W 22:51:07 Retrying (16 of 20)...
W 22:51:07 Retry Failed - Reason: Invalid Address For Write
W 22:51:07 Retrying (17 of 20)...
W 22:51:07 Retry Failed - Reason: Invalid Address For Write
W 22:51:07 Retrying (18 of 20)...
W 22:51:07 Retry Failed - Reason: Invalid Address For Write
W 22:51:07 Retrying (19 of 20)...
W 22:51:07 Retry Failed - Reason: Invalid Address For Write
W 22:51:07 Retrying (20 of 20)...
W 22:51:07 Retry Failed - Reason: Invalid Address For Write
W 00:08:52 Retrying (21)...
W 00:08:52 Retry Failed - Reason: Invalid Address For Write
W 00:08:53 Retrying (22)...
W 00:08:53 Retry Failed - Reason: Invalid Address For Write
E 00:08:58 Failed to Write Sectors 1914080 - 1914111 - Reason: Write Error
E 00:08:58 Next Writable Address: 1913760
I 00:08:58 Synchronising Cache...
W 00:09:05 User opted to skip the 'Close Track/Session/Disc' functions.
E 00:09:05 Failed to Write Image!
I 00:09:08 Exporting Graph Data...
I 00:09:09 Graph Data File: C:\Documents and Settings\steve mounsor-shaw\Application Data\ImgBurn\Graph Data Files\PHILIPS_PBDV1640P_B3.7_17-APRIL-2009_22-30_RICOHJPN-D01-67_2x.ibg
I 00:09:09 Export Successfully Completed!
E 00:09:09 Operation Failed! - Duration: 01:38:20
I 00:09:09 Average Write Rate: 650 KB/s (0.5x) - Maximum Write Rate: 3,360 KB/s (2.4x)
I 00:09:33 Close Request Acknowledged
I 00:09:33 Closing Down...
I 00:09:36 Shutting down SPTI...
I 00:09:37 ImgBurn closed!

[chrislfc]

yes its the disc i have heard of people haveing problems with this befor try xbox backup creater

[sas67]

i got it to burn and verify 100%.i went into settings and checked user defined layer break and put the same value in 1913760..it started burning,got to 50% and stopped,but then restarted and finished then verified disc..im just gonna test on 360 now and will post back if any problems arise

[technoe]

Hey, before you test that disc I strongly suggest checking it with abgx. It may take several minutes but it will be worth it.

[sas67]

i tested game with abgx prior to burning

[Backslash]

no no man just here us out run it through abgx but click "disable writes" if it restarted and whatnot during burning, the stealth files or the game files might be corrupt and can lead to a possible ban.

[technoe]

You always want to check prior and after burning. At least that's what I do. With abgx you obviously can check the file but you can also check the burnt dvd. Which comes highly recommended.

[sas67]

ok chaps,how do i check the burnt dvd?do i need a 360 drive connected to pc via sata?

[HaGGardSmurf]

ok chaps,how do i check the burnt dvd?do i need a 360 drive connected to pc via sata?

If its a 360 game, the only way to really check is your xbox. You may be able to check with a kreon drive and try dumping it... but im quite sure it would dump the game with no errors even though it may not play on your console.