mrr19121970

New media, new error "Failed to Write Sectors 12123392 - 12123423 - Reason: Write Error - Loss of Streaming" I've no idea what this means.

I've got LG support on 'Live Chat', they say that the problem will go away if I use the burning software. I've pointed to my problems here too http://forum.imgburn.com/index.php?showtopic=14189 Update What a waste of time that was. After being told to update the chipset driver, they told me that it was a problem with the compatability of the blanks and drive. I told them they're both from LG. Finally they sugested I send the drive to their service partner "to be checked".

Is this the behaviour of a bad/dying drive or buggy firmware? Should I report it to LG? What information do they need (ie which command was sent)?

I'm trying out some new media LGEBRA-S04-00, I've burned 2 at 8x so was very pleased. The 3rd disk I tried at 8x just made ImgBurn / Windows 7 hang. ImgBurn had Reserving Tracks in the status bar, the disk was spinning and elapsed time over 5 minutes and 0% progress. ImgBurn could not be closed. At 1st I thought my drive was broken, then I tried a Verbatim (after pulling the power cord) and it worked. Then I decided the cheap media was just cheap. The 4th and 5th also just made ImgBurn / Windows hang. Even in safe mode ImgBurn just had the disk spinning and the only option was to pull the power cable. I've gone back to the 3rd disk (nothing was actually written to it) again and it's currently burning no problem at 4x. This is the current log: This is a log of OK burning at 8x

I updated the ASUS P6T mainboard BIOS (v2101), Intel X58 ICH10R Chipset driver to 9.1.1.1013 (4th June 2009). If anyone is interested, my log for the failled BD-R-SL:PHILIP-R04-000 (Auth Soft) are here: http://forum.slysoft.com/showthread.php?t=40075

I've tried 4x and 8x. There seems to be no pattern in the failures I can see, however 8x burning has so far not made a coaster. I could try Verbatim, but the new lot I've got are Japanese imports. The 6 dead PHILIP-R04-00 from as-burn.de will be going back with a request to refund or replace.

Perhaps I celebrated finding the problem too soon? Why does the retry fail? W 02:24:51 Retry Failed - Reason: Invalid Address For Write I've also had 5 coasters PHILIP-R04-00, but put that down to bad media. See here for more logs.

If you're interested the 1st cut is here http://forum.slysoft.com/showthread.php?t=40349

I'm the author of Clown_BD. This is a new project.

The log file says All the files are present and correct on the S:\ drive (which is an optical drive). I can't select S:\ as source, as there is alot of stuff there I don't need - unless it's possible to have S:\ as the input and the list exclusions of stuff I don't want. Changing to Advanced mode does what I need. Thanks!

ImgBurn created the IBB (I removed the options only in my posting). Here's the full file: Heres the directory structure ImgBurn created

I was hoping to make a movie only backup with menus, and created the following IBB However ImgBurn didn't create the BDMV I thought it would. The index.bdmv & MovieObject.bdmv got added to a BDMV_ folder and the mpls, clpi & m2ts got added to the BDMV folder without preserving full pathnames. Can ImgBurn actually do what I want? If so how can this be acheived. Many thanks. Mike.

Moving the drives from the SAS connectors to the SATA seemed to do the trick. I've now burned 2 VERBAT-IMc-00 & 2 PHILIP-R04-00 with no problems. On a side note, I complained to Verbatim about the 2 failures and they replaced them + extra goodies as a 'goodwill guesture'.

Thanks for the tip. I've done this now. Hopefully it solves my woes, strange burning a DVD+R or CD never gave problems.

It's happened again, this is now a 25% failure (2 out of 8 burns have failed. The only thing I can think of is maybe as I've got the burners connected to the SAS controllers which are supposed to be backward compatible to SATA. ; //****************************************\\ ; ImgBurn Version 2.5.1.0 - Log ; Friday, 09 April 2010, 22:27:26 ; \\****************************************// ; ; I 21:14:52 ImgBurn Version 2.5.1.0 started! I 21:14:52 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7600) I 21:14:52 Total Physical Memory: 12,573,816 KB - Available: 10,409,768 KB W 21:14:52 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! I 21:14:52 Initialising SPTI... I 21:14:52 Searching for SCSI / ATAPI devices... I 21:14:52 -> Drive 1 - Info: ELBY CLONEDRIVE 1.4 (S:) (SCSI) I 21:14:52 -> Drive 2 - Info: ELBY CLONEDRIVE 1.4 (T:) (SCSI) I 21:14:52 -> Drive 3 - Info: ELBY CLONEDRIVE 1.4 (U:) (SCSI) I 21:14:52 -> Drive 4 - Info: ELBY CLONEDRIVE 1.4 (V:) (SCSI) I 21:14:52 -> Drive 5 - Info: ELBY CLONEDRIVE 1.4 (W:) (SCSI) I 21:14:52 -> Drive 6 - Info: ELBY CLONEDRIVE 1.4 (X:) (SCSI) I 21:14:52 -> Drive 7 - Info: ELBY CLONEDRIVE 1.4 (Z:) (SCSI) I 21:14:52 -> Drive 8 - Info: ELBY CLONEDRIVE 1.4 (Y:) (SCSI) I 21:14:52 -> Drive 9 - Info: HL-DT-ST BD-RE BH10LS30 1.00 (M:) (RAID) I 21:14:52 -> Drive 10 - Info: HL-DT-ST DVDRAM GH22NS40 NL02 (L:) (RAID) I 21:14:53 Found 1 DVD±RW/RAM, 8 BD-ROM/HD DVD-ROMs and 1 BD-RE! I 21:15:12 Operation Started! I 21:15:12 Source File: E:\Frog Princess.ISO I 21:15:12 Source File Sectors: 11,161,376 (MODE1/2048) I 21:15:12 Source File Size: 22,858,498,048 bytes I 21:15:12 Source File Volume Identifier: Frog Princess I 21:15:12 Source File Volume Set Identifier: 3C89A8E500AA4EA4 I 21:15:12 Source File Application Identifier: ImgBurn v2.5.1.0 I 21:15:12 Source File Implementation Identifier: ImgBurn I 21:15:12 Source File File System(s): UDF (2.50) I 21:15:12 Destination Device: [4:1:0] HL-DT-ST BD-RE BH10LS30 1.00 (M:) (RAID) I 21:15:12 Destination Media Type: BD-R (Disc ID: VERBAT-IMc-00) (Speeds: 2x, 4x, 6x, 8x) I 21:15:12 Destination Media Sectors: 12,219,392 I 21:15:12 Write Mode: BD I 21:15:12 Write Type: DAO I 21:15:12 Write Speed: 4x I 21:15:12 BD-R Verify Not Required: Yes I 21:15:12 Link Size: Auto I 21:15:12 Lock Volume: Yes I 21:15:12 Test Mode: No I 21:15:12 OPC: No I 21:15:12 BURN-Proof: Enabled I 21:15:12 Write Speed Successfully Set! - Effective: 17,982 KB/s (4x) I 21:15:25 Filling Buffer... (40 MB) I 21:15:25 Writing LeadIn... I 21:15:27 Writing Session 1 of 1... (1 Track, LBA: 0 - 11161375) I 21:15:27 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 11161375) W 21:23:29 Failed to Write Sectors 4197280 - 4197311 - Reason: Write Error W 21:23:29 Retrying (1 of 20)... W 21:23:29 Retry Failed - Reason: Invalid Address For Write W 21:23:29 Retrying (2 of 20)... W 21:23:29 Retry Failed - Reason: Invalid Address For Write W 21:23:29 Retrying (3 of 20)... W 21:23:29 Retry Failed - Reason: Invalid Address For Write W 21:23:29 Retrying (4 of 20)... W 21:23:29 Retry Failed - Reason: Invalid Address For Write W 21:23:29 Retrying (5 of 20)... W 21:23:29 Retry Failed - Reason: Invalid Address For Write W 21:23:29 Retrying (6 of 20)... W 21:23:29 Retry Failed - Reason: Invalid Address For Write W 21:23:29 Retrying (7 of 20)... W 21:23:29 Retry Failed - Reason: Invalid Address For Write W 21:23:29 Retrying (8 of 20)... W 21:23:29 Retry Failed - Reason: Invalid Address For Write W 21:23:29 Retrying (9 of 20)... W 21:23:29 Retry Failed - Reason: Invalid Address For Write W 21:23:29 Retrying (10 of 20)... W 21:23:29 Retry Failed - Reason: Invalid Address For Write W 21:23:29 Retrying (11 of 20)... W 21:23:29 Retry Failed - Reason: Invalid Address For Write W 21:23:29 Retrying (12 of 20)... W 21:23:29 Retry Failed - Reason: Invalid Address For Write W 21:23:29 Retrying (13 of 20)... W 21:23:29 Retry Failed - Reason: Invalid Address For Write W 21:23:29 Retrying (14 of 20)... W 21:23:29 Retry Failed - Reason: Invalid Address For Write W 21:23:29 Retrying (15 of 20)... W 21:23:29 Retry Failed - Reason: Invalid Address For Write W 21:23:29 Retrying (16 of 20)... W 21:23:29 Retry Failed - Reason: Invalid Address For Write W 21:23:29 Retrying (17 of 20)... W 21:23:29 Retry Failed - Reason: Invalid Address For Write W 21:23:29 Retrying (18 of 20)... W 21:23:29 Retry Failed - Reason: Invalid Address For Write W 21:23:29 Retrying (19 of 20)... W 21:23:29 Retry Failed - Reason: Invalid Address For Write W 21:23:29 Retrying (20 of 20)... W 21:23:29 Retry Failed - Reason: Invalid Address For Write W 22:26:37 Retrying (21)... W 22:26:37 Retry Failed - Reason: Invalid Address For Write W 22:26:38 Retrying (22)... W 22:26:38 Retry Failed - Reason: Invalid Address For Write W 22:26:40 Retrying (23)... W 22:26:40 Retry Failed - Reason: Invalid Address For Write W 22:26:41 Retrying (24)... W 22:26:41 Retry Failed - Reason: Invalid Address For Write W 22:26:42 Retrying (25)... W 22:26:42 Retry Failed - Reason: Invalid Address For Write W 22:26:43 Retrying (26)... W 22:26:43 Retry Failed - Reason: Invalid Address For Write W 22:26:45 Retrying (27)... W 22:26:45 Retry Failed - Reason: Invalid Address For Write W 22:26:46 Retrying (28)... W 22:26:46 Retry Failed - Reason: Invalid Address For Write E 22:26:55 Failed to Write Sectors 4197280 - 4197311 - Reason: Write Error E 22:26:55 Next Writable Address: 0 I 22:26:55 Synchronising Cache... W 22:27:03 User opted to skip the 'Close Track/Session/Disc' functions. E 22:27:03 Failed to Write Image! I 22:27:06 Exporting Graph Data... I 22:27:06 Graph Data File: C:\Users\Mike\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_BH10LS30_1.00_09-APRIL-2010_21-15_VERBAT-IMc-00_4x.ibg I 22:27:06 Export Successfully Completed! E 22:27:06 Operation Failed! - Duration: 01:11:50 I 22:27:06 Average Write Rate: 1,957 KB/s (0.4x) - Maximum Write Rate: 18,091 KB/s (4.0x) I 22:27:26 Close Request Acknowledged I 22:27:26 Closing Down... I 22:27:26 Shutting down SPTI... I 22:27:26 ImgBurn closed! http://www.techspot.com/review/129-asus-p6t-deluxe/page2.html http://www.guru3d.com/imageview.php?image=15433 http://www.guru3d.com/article/asus-p6t-deluxe-review-x58-motherboard/8

That's excellent, just what I needed. I've had problems with my 22x writer see here by leaving it on MAX, now I can use the AWS feature. It would be nice if ImgBurn gave me a 'cheeky' message when I have a currently unknown media type, and ask me if I want to open the dialogue (or stick my head in the sand and proceed with MAX) Thanks for looking. Mike.

I've just bought a LG BH10LS30, I've patched the riplock with MCSE. I've burned a 6x Verbatim at 10x, a Verbatim 4x at 4x and another at 6x and decided 4x media at 4x burning is OK for me. On my 4th burn I got this message (and a coaster) ; //****************************************\\ ; ImgBurn Version 2.5.1.0 - Log ; Friday, 26 March 2010, 10:45:26 ; \\****************************************// ; ; I 10:19:53 ImgBurn Version 2.5.1.0 started! I 10:19:53 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7600) I 10:19:53 Total Physical Memory: 12,573,816 KB - Available: 10,619,420 KB W 10:19:53 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! I 10:19:53 Initialising SPTI... I 10:19:53 Searching for SCSI / ATAPI devices... I 10:19:53 -> Drive 1 - Info: ELBY CLONEDRIVE 1.4 (S:) (SCSI) I 10:19:53 -> Drive 2 - Info: ELBY CLONEDRIVE 1.4 (T:) (SCSI) I 10:19:53 -> Drive 3 - Info: ELBY CLONEDRIVE 1.4 (U:) (SCSI) I 10:19:53 -> Drive 4 - Info: ELBY CLONEDRIVE 1.4 (V:) (SCSI) I 10:19:53 -> Drive 5 - Info: ELBY CLONEDRIVE 1.4 (W:) (SCSI) I 10:19:53 -> Drive 6 - Info: ELBY CLONEDRIVE 1.4 (X:) (SCSI) I 10:19:53 -> Drive 7 - Info: ELBY CLONEDRIVE 1.4 (Z:) (SCSI) I 10:19:53 -> Drive 8 - Info: ELBY CLONEDRIVE 1.4 (Y:) (SCSI) I 10:19:53 -> Drive 9 - Info: HL-DT-ST BD-RE BH10LS30 1.00 (M:) (RAID) I 10:19:53 -> Drive 10 - Info: HL-DT-ST DVDRAM GH22NS40 NL02 (L:) (RAID) I 10:19:53 Found 1 DVD±RW/RAM, 8 BD-ROM/HD DVD-ROMs and 1 BD-RE! I 10:20:23 Operation Started! I 10:20:23 Building Image Tree... I 10:20:27 Corrected file system selection for Blu-ray Video disc. I 10:20:27 Corrected UDF revision selection for Blu-ray Video disc. I 10:20:32 Calculating Totals... I 10:20:32 Preparing Image... I 10:20:33 Contents: 24 Files, 14 Folders I 10:20:33 Content Type: BD Video I 10:20:33 Data Type: MODE1/2048 I 10:20:33 File System(s): UDF (2.50) I 10:20:33 Volume Label: Bolt USA I 10:20:33 Size: 21,301,567,744 bytes I 10:20:33 Sectors: 10,401,164 I 10:20:33 Image Size: 21,302,607,872 bytes I 10:20:33 Image Sectors: 10,401,664 E 10:21:01 Operation Aborted! - Duration: 00:00:38 I 10:23:10 Operation Started! I 10:23:10 Building Image Tree... I 10:23:12 Calculating Totals... I 10:23:12 Preparing Image... I 10:23:12 Contents: 24 Files, 14 Folders I 10:23:12 Content Type: BD Video I 10:23:12 Data Type: MODE1/2048 I 10:23:12 File System(s): UDF (2.50) I 10:23:12 Volume Label: Bolt USA I 10:23:12 Size: 21,301,567,744 bytes I 10:23:12 Sectors: 10,401,164 I 10:23:12 Image Size: 21,302,607,872 bytes I 10:23:12 Image Sectors: 10,401,664 I 10:23:13 Operation Successfully Completed! - Duration: 00:00:03 I 10:23:13 Operation Started! I 10:23:13 Source File: -==/\/[bUILD IMAGE]\/\==- I 10:23:13 Source File Sectors: 10,401,664 (MODE1/2048) I 10:23:13 Source File Size: 21,302,607,872 bytes I 10:23:13 Source File Volume Identifier: Bolt USA I 10:23:13 Source File Application Identifier: ImgBurn v2.5.1.0 I 10:23:13 Source File Implementation Identifier: ImgBurn I 10:23:13 Source File File System(s): UDF (2.50) I 10:23:13 Destination Device: [4:1:0] HL-DT-ST BD-RE BH10LS30 1.00 (M:) (RAID) I 10:23:13 Destination Media Type: BD-R (Disc ID: VERBAT-IMc-00) (Speeds: 2x, 4x, 6x, 8x) I 10:23:13 Destination Media Sectors: 12,219,392 I 10:23:13 Write Mode: BD I 10:23:13 Write Type: DAO I 10:23:13 Write Speed: 4x I 10:23:13 BD-R Verify Not Required: Yes I 10:23:13 Link Size: Auto I 10:23:13 Lock Volume: Yes I 10:23:13 Test Mode: No I 10:23:13 OPC: No I 10:23:13 BURN-Proof: Enabled I 10:23:13 Write Speed Successfully Set! - Effective: 17,982 KB/s (4x) I 10:23:29 Filling Buffer... (40 MB) I 10:23:30 Writing LeadIn... I 10:23:31 Writing Session 1 of 1... (1 Track, LBA: 0 - 10401663) I 10:23:31 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 10401663) W 10:29:33 Failed to Write Sectors 3148704 - 3148735 - Reason: Write Error W 10:29:33 Retrying (1 of 20)... W 10:29:33 Retry Failed - Reason: Invalid Address For Write W 10:29:33 Retrying (2 of 20)... W 10:29:33 Retry Failed - Reason: Invalid Address For Write W 10:29:33 Retrying (3 of 20)... W 10:29:33 Retry Failed - Reason: Invalid Address For Write W 10:29:33 Retrying (4 of 20)... W 10:29:33 Retry Failed - Reason: Invalid Address For Write W 10:29:33 Retrying (5 of 20)... W 10:29:33 Retry Failed - Reason: Invalid Address For Write W 10:29:33 Retrying (6 of 20)... W 10:29:33 Retry Failed - Reason: Invalid Address For Write W 10:29:33 Retrying (7 of 20)... W 10:29:33 Retry Failed - Reason: Invalid Address For Write W 10:29:33 Retrying (8 of 20)... W 10:29:33 Retry Failed - Reason: Invalid Address For Write W 10:29:33 Retrying (9 of 20)... W 10:29:33 Retry Failed - Reason: Invalid Address For Write W 10:29:33 Retrying (10 of 20)... W 10:29:33 Retry Failed - Reason: Invalid Address For Write W 10:29:33 Retrying (11 of 20)... W 10:29:33 Retry Failed - Reason: Invalid Address For Write W 10:29:33 Retrying (12 of 20)... W 10:29:33 Retry Failed - Reason: Invalid Address For Write W 10:29:33 Retrying (13 of 20)... W 10:29:33 Retry Failed - Reason: Invalid Address For Write W 10:29:33 Retrying (14 of 20)... W 10:29:33 Retry Failed - Reason: Invalid Address For Write W 10:29:33 Retrying (15 of 20)... W 10:29:33 Retry Failed - Reason: Invalid Address For Write W 10:29:33 Retrying (16 of 20)... W 10:29:34 Retry Failed - Reason: Invalid Address For Write W 10:29:34 Retrying (17 of 20)... W 10:29:34 Retry Failed - Reason: Invalid Address For Write W 10:29:34 Retrying (18 of 20)... W 10:29:34 Retry Failed - Reason: Invalid Address For Write W 10:29:34 Retrying (19 of 20)... W 10:29:34 Retry Failed - Reason: Invalid Address For Write W 10:29:34 Retrying (20 of 20)... W 10:29:34 Retry Failed - Reason: Invalid Address For Write W 10:43:07 Retrying (21)... W 10:43:07 Retry Failed - Reason: Invalid Address For Write W 10:43:11 Retrying (22)... W 10:43:11 Retry Failed - Reason: Invalid Address For Write W 10:43:17 Retrying (23)... W 10:43:17 Retry Failed - Reason: Invalid Address For Write W 10:43:18 Retrying (24)... W 10:43:18 Retry Failed - Reason: Invalid Address For Write E 10:43:22 Failed to Write Sectors 3148704 - 3148735 - Reason: Write Error E 10:43:22 Next Writable Address: 0 I 10:43:22 Synchronising Cache... W 10:43:28 User opted to skip the 'Close Track/Session/Disc' functions. E 10:43:28 Failed to Write Image! I 10:43:31 Exporting Graph Data... I 10:43:31 Graph Data File: C:\Users\Mike\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_BH10LS30_1.00_26-MARCH-2010_10-23_VERBAT-IMc-00_4x.ibg I 10:43:31 Export Successfully Completed! E 10:43:31 Operation Failed! - Duration: 00:20:15 I 10:43:31 Average Write Rate: 5,291 KB/s (1.2x) - Maximum Write Rate: 18,082 KB/s (4.0x) I 10:45:26 Close Request Acknowledged I 10:45:26 Closing Down... I 10:45:26 Shutting down SPTI... I 10:45:26 ImgBurn closed! ; I've burned 1 disk since 4x at 4x. I'm pretty alarmed as the drive is new, and I thought Verbatims are premium. Any idea what could have caused this? The Verbatim office is just around the corner form work and I plan to take the disk to them an ask for a new one, could the disk have caused this?

As the title says, my suggestion is quite simple. I'd like ImgBurn to be able to remember the last used burning speed based on both the Drive & Unique Disc Identifier. Examples: Drive=BD-REBH10LS30 MID=VERBAT-IMc-000 BurnSpeed=4x Drive=GH22NS40 MID=MCC-004-00 BurnSpeed=16x Many thanks for looking at my idea. Mike.