ecormie24

The image is to big for your current media. You need a Blu-ray disc for that size of image. ----Wow that was fast! Thanks!---- I know the image is larger than the media, but its also doing the same when I try and burn smaller images. Just for the hell of it I installed the latest imgburn on my girlfriends Toshiba laptop and tried burning the same image file, to the same media, and it work. I 19:57:51 ImgBurn Version 2.5.6.0 started! I 19:57:51 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7600) I 19:57:51 Total Physical Memory: 2,878,360 KB - Available: 1,928,912 KB I 19:57:51 Initialising SPTI... I 19:57:51 Searching for SCSI / ATAPI devices... I 19:57:51 -> Drive 1 - Info: MATSHITA DVD-RAM UJ890AS 1.40 (D:) (SATA) I 19:57:51 Found 1 DVD±RW/RAM! W 20:33:21 User accepted disc space warning and is attempting to truncate! I 20:33:21 Operation Started! I 20:33:21 Source File: C:\Users\Owner\Desktop\rrod-gow3.dvd I 20:33:21 Source File Sectors: 4,267,015 (MODE1/2048) I 20:33:21 Source File Size: 8,738,846,720 bytes I 20:33:21 Source File Volume Identifier: DVD_ROM I 20:33:21 Source File Volume Set Identifier: cd690000MS UDFBridge I 20:33:21 Source File Application Identifier: CDIMAGE 2.45 (12/06/2000 TM) I 20:33:21 Source File Implementation Identifier: Microsoft CDIMAGE UDF I 20:33:21 Source File File System(s): ISO9660, UDF (1.50) I 20:33:21 Destination Device: [2:0:0] MATSHITA DVD-RAM UJ890AS 1.40 (D:) (SATA) I 20:33:21 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) I 20:33:21 Destination Media Supported Write Speeds: 2.4x I 20:33:21 Destination Media Sectors: 4,173,824 I 20:33:21 Write Mode: DVD I 20:33:21 Write Type: DAO I 20:33:21 Write Speed: 2.4x I 20:33:21 Link Size: Auto I 20:33:21 Lock Volume: Yes I 20:33:21 Test Mode: No I 20:33:21 OPC: No I 20:33:21 BURN-Proof: Enabled I 20:33:21 Write Speed Successfully Set! - Effective: 3,324 KB/s (2.4x) W 20:33:21 Optimal layer break position exceeds L0 capacity. W 20:33:21 Optimal L0 Sectors: 2,133,520 W 20:33:22 Maximum L0 Sectors: 2,086,912 I 20:33:22 Optimal L0 Data Zone Capacity: 2,133,520 I 20:33:22 Optimal L0 Data Zone Method: Copied From Original Disc W 20:33:22 Set L0 Data Zone Capacity Failed! - Reason: Invalid Field in Parameter List I 20:33:22 Filling Buffer... (40 MB) I 20:33:23 Writing LeadIn... I 20:33:42 Writing Session 1 of 1... (1 Track, LBA: 0 - 4267014) I 20:33:42 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 4267014) I 20:33:42 Writing Layer 0... (LBA: 0 - 2086911) I 20:55:34 Writing Layer 1... (LBA: 2086912 - 4267014) I 21:17:32 Synchronising Cache... I 21:17:36 Closing Track... I 21:17:37 Finalising Disc... I 21:18:34 Exporting Graph Data... I 21:18:34 Graph Data File: C:\Users\Owner\AppData\Roaming\ImgBurn\Graph Data Files\MATSHITA_DVD-RAM_UJ890AS_1.40_TUESDAY-OCTOBER-04-2011_8-33_PM_MKM-001-00_2.4x.ibg I 21:18:34 Export Successfully Completed! I 21:18:34 Operation Successfully Completed! - Duration: 00:45:13 I 21:18:34 Average Write Rate: 3,175 KB/s (2.3x) - Maximum Write Rate: 3,435 KB/s (2.5x)

Hello I'm new to this forum, and have problem i cant seem to figure out. Any help is much appreciated I Can't burn my xbox360 image. After 71% the burning stops and than appears this message "IEenvalidOp", the mirror said "Burn Thread Runtime Exception"........ I never got this kind of problems burning my xbox360 images Please help me, I've wasted four dvd DL Verbatim!!! I 18:59:39 ImgBurn Version 2.5.6.0 started! I 18:59:39 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7601 : Service Pack 1) I 18:59:39 Total Physical Memory: 4,160,544 KB - Available: 2,094,088 KB W 18:59:39 Duplex Secure's SPTD driver can have a detrimental effect on drive performance. I 18:59:39 Initialising SPTI... I 18:59:39 Searching for SCSI / ATAPI devices... I 18:59:39 -> Drive 1 - Info: Optiarc BD ROM BC-5500S4 1.Va (E:) (ATAPI) I 18:59:39 -> Drive 2 - Info: JEVOF VCTMB4LY3 3.5Z (H:) (SCSI) I 18:59:39 -> Drive 3 - Info: SZWXOBS 4TUJS9UV 1.04 (G:) (SCSI) I 18:59:39 Found 1 BD-ROM, 1 BD-ROM/HD DVD-ROM and 1 BD-ROM/DVD±RW! W 19:00:14 User accepted disc space warning and is attempting to truncate! I 19:00:14 Operation Started! I 19:00:14 Source File: C:\Users\Edward\Desktop\Downloads\Gears_of_War_3_READNFO_XGD3_0800_USA_RF-XBOX360-RRoD {BOOBSMAN}\rrod-gow3.dvd I 19:00:14 Source File Sectors: 4,267,015 (MODE1/2048) I 19:00:14 Source File Size: 8,738,846,720 bytes I 19:00:14 Source File Volume Identifier: DVD_ROM I 19:00:14 Source File Volume Set Identifier: cd690000MS UDFBridge I 19:00:14 Source File Application Identifier: CDIMAGE 2.45 (12/06/2000 TM) I 19:00:14 Source File Implementation Identifier: Microsoft CDIMAGE UDF I 19:00:14 Source File File System(s): ISO9660, UDF (1.50) I 19:00:14 Destination Device: [0:1:0] Optiarc BD ROM BC-5500S4 1.Va (E:) (ATAPI) I 19:00:14 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) I 19:00:14 Destination Media Supported Write Speeds: 2.4x, 4x I 19:00:14 Destination Media Sectors: 4,173,824 I 19:00:14 Write Mode: DVD I 19:00:14 Write Type: DAO I 19:00:14 Write Speed: 2.4x I 19:00:14 Link Size: Auto I 19:00:14 Lock Volume: Yes I 19:00:14 Test Mode: No I 19:00:14 OPC: No I 19:00:14 BURN-Proof: Enabled I 19:00:14 Write Speed Successfully Set! - Effective: 3,324 KB/s (2.4x) I 19:00:14 Book Type Setting: DVD-ROM W 19:00:14 Optimal layer break position exceeds L0 capacity. W 19:00:14 Optimal L0 Sectors: 2,133,520 W 19:00:14 Maximum L0 Sectors: 2,086,912 I 19:00:14 Optimal L0 Data Zone Capacity: 2,133,520 I 19:00:14 Optimal L0 Data Zone Method: Copied From Original Disc W 19:00:14 Set L0 Data Zone Capacity Failed! - Reason: Invalid Field in Parameter List I 19:00:15 Filling Buffer... (40 MB) I 19:00:16 Writing LeadIn... I 19:00:47 Writing Session 1 of 1... (1 Track, LBA: 0 - 4267014) I 19:00:47 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 4267014) I 19:00:47 Writing Layer 0... (LBA: 0 - 2086911) I 19:21:49 Writing Layer 1... (LBA: 2086912 - 4267014) W 19:36:16 Failed to Write Sectors 2997408 - 2997439 - Reason: Invalid Address For Write W 19:36:16 Retrying (1 of 20)... W 19:36:16 Retry Failed - Reason: Invalid Address For Write W 19:36:16 Retrying (2 of 20)... W 19:36:16 Retry Failed - Reason: Invalid Address For Write W 19:36:16 Retrying (3 of 20)... W 19:36:16 Retry Failed - Reason: Invalid Address For Write W 19:36:16 Retrying (4 of 20)... W 19:36:16 Retry Failed - Reason: Invalid Address For Write W 19:36:16 Retrying (5 of 20)... W 19:36:16 Retry Failed - Reason: Invalid Address For Write W 19:36:16 Retrying (6 of 20)... W 19:36:16 Retry Failed - Reason: Invalid Address For Write W 19:36:16 Retrying (7 of 20)... W 19:36:16 Retry Failed - Reason: Invalid Address For Write W 19:36:16 Retrying (8 of 20)... W 19:36:16 Retry Failed - Reason: Invalid Address For Write W 19:36:16 Retrying (9 of 20)... W 19:36:16 Retry Failed - Reason: Invalid Address For Write W 19:36:16 Retrying (10 of 20)... W 19:36:16 Retry Failed - Reason: Invalid Address For Write W 19:36:16 Retrying (11 of 20)... W 19:36:16 Retry Failed - Reason: Invalid Address For Write W 19:36:16 Retrying (12 of 20)... W 19:36:16 Retry Failed - Reason: Invalid Address For Write W 19:36:16 Retrying (13 of 20)... W 19:36:16 Retry Failed - Reason: Invalid Address For Write W 19:36:16 Retrying (14 of 20)... W 19:36:16 Retry Failed - Reason: Invalid Address For Write W 19:36:16 Retrying (15 of 20)... W 19:36:16 Retry Failed - Reason: Invalid Address For Write W 19:36:16 Retrying (16 of 20)... W 19:36:17 Retry Failed - Reason: Invalid Address For Write W 19:36:17 Retrying (17 of 20)... W 19:36:17 Retry Failed - Reason: Invalid Address For Write W 19:36:17 Retrying (18 of 20)... W 19:36:17 Retry Failed - Reason: Invalid Address For Write W 19:36:17 Retrying (19 of 20)... W 19:36:17 Retry Failed - Reason: Invalid Address For Write W 19:36:17 Retrying (20 of 20)... W 19:36:17 Retry Failed - Reason: Invalid Address For Write E 19:50:41 Failed to Write Sectors 2997408 - 2997439 - Reason: Invalid Address For Write E 19:50:41 Next Writable Address: 2997376 I 19:50:42 Synchronising Cache... Its currently stuck at 92% of the "Synchronizing Cache..." part. I thought this was an isolated problem with one specific img file but its now happened on two different occasions. Again, PLZ HELP!! lol