ImgBurn continuously giving failed burns

[Conqueror]

I'm sick and tired of ImgBurn giving me coasters after coasters.

 

I use 8x TDK DVDs and burn them at 2x with ImgBurn.

 

Out of every 10 dual layer DVDs, 6 burns fail with ImgBurn.

 

Before, you say it's bad media or something wrong with my PC, every time I try to burn the same image with built in Windows Disc Image Burner, it succeeds. FIRST TIME. EVERY TIME.

 

See the screens below to see what happens with ImgBurn and what happens with Windows Disc Image Burner.

 

I don't think I will ever use ImgBurn again. Too many bugs and discrepancies.

 

 

With ImgBurn:

 

 

 

With Windows Disc Image Burner:

 

Edited December 4, 2009 by Conqueror

[Cynthia]

Can you post the full log? Main Menu -> Help -> ImgBurn Logs

 

Are you burning with the same speed in both Windows and with ImgBurn? The wrong write speed can make coasters.

[Conqueror]

Can you post the full log? Main Menu -> Help -> ImgBurn Logs

 

Are you burning with the same speed in both Windows and with ImgBurn? The wrong write speed can make coasters.

 

If the speed at which you write is wrong, then ImgBurn shouldn't give you the option to write at that speed. I've always written at 2X with other burners without problems.

 

My media supports: 8X 4X 2X 1X

 

 

Anyway, here's the log, not that it's gona help:

 

 

; //****************************************\\
;   ImgBurn Version 2.5.0.0 - Log
;   Friday, 04 December 2009, 12:39:07
; \\****************************************//
;
;
I 07:54:56 ImgBurn Version 2.5.0.0 started!
I 07:54:56 Microsoft Windows 7 Ultimate Edition (6.1, Build 7600)
I 07:54:56 Total Physical Memory: 3,406,968 KB  -  Available: 2,405,592 KB
W 07:54:56 SPTD can have a detrimental effect on drive performance.
I 07:54:56 Initialising SPTI...
I 07:54:56 Searching for SCSI / ATAPI devices...
I 07:54:56 Found 1 DVD±RW/RAM and 1 BD-ROM/HD DVD-ROM!
I 08:12:54 Operation Started!
I 08:12:54 Source File: C:\......iso (information removed for privacy reasons)
I 08:12:54 Source File Sectors: 4,059,008 (MODE1/2048)
I 08:12:54 Source File Size: 8,312,848,384 bytes
I 08:12:54 Source File Volume Identifier: ... (information removed for privacy reasons)
I 08:12:54 Source File Volume Set Identifier: 492055064920545E
I 08:12:54 Source File Application Identifier: NERO BURNING ROM
I 08:12:54 Source File Implementation Identifier: AHEAD Nero
I 08:12:54 Source File File System(s): ISO9660, Joliet, UDF (1.02)
I 08:12:54 Destination Device: [1:0:0] TSSTcorp CD/DVDW SH-S162L TS06 (E:) (ATA)
I 08:12:54 Destination Media Type: DVD+R DL (Disc ID: CMC MAG-D03-64) (Speeds: 2.4x)
I 08:12:54 Destination Media Sectors: 4,173,824
I 08:12:54 Write Mode: DVD
I 08:12:54 Write Type: DAO
I 08:12:54 Write Speed: 2x
I 08:12:54 Link Size: Auto
I 08:12:54 Lock Volume: Yes
I 08:12:54 Test Mode: No
I 08:12:54 OPC: No
I 08:12:54 BURN-Proof: Enabled
I 08:12:56 Book Type Setting: DVD-ROM
I 08:12:56 Optimal L0 Data Zone Capacity: 2,029,504
I 08:12:56 Optimal L0 Data Zone Method: ECC Block Boundary
I 08:16:38 Set L0 Data Zone Capacity Succeeded!
I 08:16:39 Filling Buffer... (40 MB)
I 08:16:48 Writing LeadIn...
I 08:19:39 Writing Session 1 of 1... (1 Track, LBA: 0 - 4059007)
I 08:19:39 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 4059007)
I 08:19:39 Writing Layer 0... (LBA: 0 - 2029503)
I 08:40:11 Writing Layer 1... (LBA: 2029504 - 4059007)
W 09:00:18 Failed to Write Sectors 4013120 - 4013151 - Reason: Write Error
W 09:00:18 Retrying (1 of 20)...
W 09:00:18 Retry Failed - Reason: Invalid Address For Write
W 09:00:18 Retrying (2 of 20)...
W 09:00:18 Retry Failed - Reason: Invalid Address For Write
W 09:00:18 Retrying (3 of 20)...
W 09:00:18 Retry Failed - Reason: Invalid Address For Write
W 09:00:18 Retrying (4 of 20)...
W 09:00:18 Retry Failed - Reason: Invalid Address For Write
W 09:00:18 Retrying (5 of 20)...
W 09:00:18 Retry Failed - Reason: Invalid Address For Write
W 09:00:18 Retrying (6 of 20)...
W 09:00:18 Retry Failed - Reason: Invalid Address For Write
W 09:00:18 Retrying (7 of 20)...
W 09:00:18 Retry Failed - Reason: Invalid Address For Write
W 09:00:18 Retrying (8 of 20)...
W 09:00:18 Retry Failed - Reason: Invalid Address For Write
W 09:00:18 Retrying (9 of 20)...
W 09:00:18 Retry Failed - Reason: Invalid Address For Write
W 09:00:18 Retrying (10 of 20)...
W 09:00:18 Retry Failed - Reason: Invalid Address For Write
W 09:00:18 Retrying (11 of 20)...
W 09:00:18 Retry Failed - Reason: Invalid Address For Write
W 09:00:18 Retrying (12 of 20)...
W 09:00:18 Retry Failed - Reason: Invalid Address For Write
W 09:00:18 Retrying (13 of 20)...
W 09:00:18 Retry Failed - Reason: Invalid Address For Write
W 09:00:18 Retrying (14 of 20)...
W 09:00:18 Retry Failed - Reason: Invalid Address For Write
W 09:00:18 Retrying (15 of 20)...
W 09:00:18 Retry Failed - Reason: Invalid Address For Write
W 09:00:18 Retrying (16 of 20)...
W 09:00:18 Retry Failed - Reason: Invalid Address For Write
W 09:00:18 Retrying (17 of 20)...
W 09:00:18 Retry Failed - Reason: Invalid Address For Write
W 09:00:18 Retrying (18 of 20)...
W 09:00:18 Retry Failed - Reason: Invalid Address For Write
W 09:00:18 Retrying (19 of 20)...
W 09:00:18 Retry Failed - Reason: Invalid Address For Write
W 09:00:18 Retrying (20 of 20)...
W 09:00:18 Retry Failed - Reason: Invalid Address For Write
W 12:33:44 Retrying (21)...
W 12:33:44 Retry Failed - Reason: Invalid Address For Write
W 12:33:46 Retrying (22)...
W 12:33:46 Retry Failed - Reason: Invalid Address For Write
W 12:33:47 Retrying (23)...
W 12:33:47 Retry Failed - Reason: Invalid Address For Write
W 12:33:47 Retrying (24)...
W 12:33:47 Retry Failed - Reason: Invalid Address For Write
W 12:33:48 Retrying (25)...
W 12:33:48 Retry Failed - Reason: Invalid Address For Write
W 12:33:48 Retrying (26)...
W 12:33:48 Retry Failed - Reason: Invalid Address For Write
W 12:33:48 Retrying (27)...
W 12:33:48 Retry Failed - Reason: Invalid Address For Write
W 12:33:49 Retrying (28)...
W 12:33:49 Retry Failed - Reason: Invalid Address For Write
W 12:33:49 Retrying (29)...
W 12:33:49 Retry Failed - Reason: Invalid Address For Write
W 12:33:49 Retrying (30)...
W 12:34:04 Retry Failed - Reason: Invalid Address For Write
E 12:36:26 Failed to Write Sectors 4013120 - 4013151 - Reason: Write Error
E 12:36:26 Next Writable Address: 4012632
I 12:36:26 Synchronising Cache...
W 12:36:41 User opted to skip the 'Close Track/Session/Disc' functions.
E 12:36:41 Failed to Write Image!
I 12:36:41 Exporting Graph Data...
I 12:36:41 Graph Data File: C:\Users\...\AppData\Roaming\ImgBurn\Graph Data Files\TSSTcorp_CD-DVDW_SH-S162L_TS06_04-DECEMBER-2009_8-12_AM_CMC_MAG-D03-64_2x.ibg (information removed for privacy reasons)
I 12:36:41 Export Successfully Completed!
E 12:36:41 Operation Failed! - Duration: 04:23:47
I 12:36:41 Average Write Rate: 520 KB/s (0.4x) - Maximum Write Rate: 3,430 KB/s (2.5x)
I 12:39:06 Close Request Acknowledged
I 12:39:06 Closing Down...
I 12:39:07 Shutting down SPTI...
I 12:39:07 ImgBurn closed!

[Cynthia]

The only speed you can burn with is 2.4x as that is what the media/firmware/drive combination allows you to.

 

I 08:12:54 Destination Media Type: DVD+R DL (Disc ID: CMC MAG-D03-64) (Speeds: 2.4x)

Have you tried to read back the burned disc (the one you burned with Microsoft) to the hard disk? (Just to rule out that it is burned ok).

[Conqueror]

The only speed you can burn with is 2.4x as that is what the media/firmware/drive combination allows you to.

 

I 08:12:54 Destination Media Type: DVD+R DL (Disc ID: CMC MAG-D03-64) (Speeds: 2.4x)

 

I have always burned the same media with 1X or 2X with Nero with the same drive. And they haven't given any coasters.

 

I don't know why ImgBurn is showing 2.4X.

 

Besides, if 2.4 is the speed at which I can ONLY write at, then all other options SHOULD NOT be made available to me.

 

But I don't think that's the problem since I've burned at 2X with other programs.

 

Have you tried to read back the burned disc (the one you burned with Microsoft) to the hard disk? (Just to rule out that it is burned ok).

 

Yes, I have. And no problems with it. I've checked not one or two DVDs, but packs of them. Most of the times I choose "verify" in the programs and always verify myself by physically loading the DVD and installing or browsing images/videos on the DVD from start to end.

Edited December 4, 2009 by Conqueror

[mmalves]

If all "other" programs work then why are you posting here? It's not a problem with ImgBurn, and even though I could easily prove it, you don't seem interested in anything but bashing ImgBurn, so move along and don't waste our time.

[Conqueror]

If all "other" programs work then why are you posting here? It's not a problem with ImgBurn, and even though I could easily prove it, you don't seem interested in anything but bashing ImgBurn, so move along and don't waste our time.

 

That is exactly what I was going to do after making 6 coasters with ImgBurn. Moving along. But someone tried to label the fault on me, or my media or burner. And now, even you want to have a go at proving that ImgBurn is not the fault. So why are you wasting time?

 

ImgBurn isn't some supernatural flawless software that no one should be "bashing". No software if perfect. if you don't want people to complain about it, then why make this forum? And why discuss about problems if you don't care?

 

So maybe you should not be wasting your time here if you don't like listening to people complaining about ImgBurn.

 

I'm not afraid to call a spade a spade. if I see a fault, I will report it. it doesn't mean I'm bashing ImgBurn or against it. I don't even care. I'm not the owner of Nero or something. It wouldn't matter to me if ImgBurn was great and all others were not. In fact, i would like that.

 

But as current trend is showing, ImgBurn isn't that great. From my experience at least.

[mmalves]

If you knew anything about burning you would know it's all down to the burner/firmware/media combination: the software just feeds the data.

 

There are a few things you could try in order to make those rubbish blanks work with your burner, but since you were so honest and polite, I'll let you figure it out by yourself.

[LIGHTNING UK!]

Incremental write type?

[Conqueror]

If you knew anything about burning you would know it's all down to the burner/firmware/media combination: the software just feeds the data.

 

If it was all down to simply burner/firmware/media, then it shouldn't matter what software you use, right? That's what you trying to say aren't you?

 

Then why do someone software give coasters (like ImgBurn) and some burn without problems (like the basic windows disc image burner)?

 

In my generosity and to remove the shadow of doubt, I tried one final test before I abandon this software.

 

Your "colleague" stated that the error was due to the fact that I was burning at 2X when I should be burning at 2.4X.

 

Well that's exactly what I did. I tried burning at 2.4X and guess what? I got an error in the log complaining that I was selected the wrong write speed:

 

 

 

But I wasn't stupid enough to continue with the burn and make another coaster. So I cancelled it and used windows disc image burner without problems once again.

 

Like I said, I know that my dual layer TDK DVDs supports 8X, 4X, 2X and 1X.

For DVD+R, my drive supports: 16X, 8X, 4X, 2X, 1X

 

So I don't know where this 2.4X number came from in ImgBurn.

 

Looks like I'm the one who should be in the "Beta Team" and not all you lot who come and jump on anyone who complains.

[Cynthia]

Perhaps you should first learn what a firmware is and what media codes are...

 

There was also a hint in post #9, that you didn't knew what to do with.

[LIGHTNING UK!]

Windows Image Burner (WIB) doesn't set the layer break, so it burns to the default end of L0 and then moves onto L1 (i.e. they're not split 50/50 - which makes a more 'readable' and compatible disc according to the MMC specs)

 

So if you work it out (based on the one log you've provided)...

 

Image size = 4,059,008 sectors

 

Default size of L0 = 2,086,912 sectors

Adjusted size of L0 = 2,029,504 sectors (this is the one to make a proper 50/50 split between layers)

Difference in size of L0 = 2,086,912 - 2,029,504 = 57,408 sectors

 

'Write Error' reported at adjusted LBA 4013120.

Physical LBA = 4013120 + 57408 = 4070528

 

Physical LBA of 4070528 exceeds image size of 4,059,008 sectors and therefore the WIB never actually attempts to write to that sector.

 

WIB implements the 'Send OPC Information' command before burning starts - that's what the 'Perform OPC' setting in ImgBurn does (off by default).

 

WIB uses the 'Incremental' write type rather than 'SAO/DAO'. Working with one and not with another is purely a drive/firmware/media combo issue.

 

WIB burns with multisession enabled - thus the disc isn't finalised.

[Conqueror]

Perhaps you should first learn what a firmware is and what media codes are...

You're wrong there. I had already updated my firmware to latest firmware and I know what speeds my drive supports.

[Cynthia]

Perhaps you should first learn what a firmware is and what media codes are...

You're wrong there. I had already updated my firmware to latest firmware and I know what speeds my drive supports.

I 08:12:54 Destination Device: [1:0:0] TSSTcorp CD/DVDW SH-S162L TS06 (E:) (ATA)

As the latest firmware update was released around 2.5 years ago and the log you posted a day ago shows that it wasn't updated, I'm more than certain that you don't know what you are talking about.

 

A burner can support 24x speeds, but the limitation in the firmware + media code still sets the rules for the available speeds. You could try to get any faster speed than 2.4x with that burner in any other program.

 

The major issue with the firmware for that burner is that the media code (discs) that you are using, is not even supported in the firmware. Instead it's probably using a generic write approach.

 

[laserfan]

...the media code (discs) that you are using, is not even supported in the firmware. Instead it's probably using a generic write approach.

I've looked thru this thread and am trying to understand. So the "bottom line" for the OP is:

 

1. He's using a media type CMC MAG-D03-64 which is not in the list as exposed by Media Code Speed Edit

 

2. The latest firmware for the drive is not TS06, but now TS08 (2007-03-17)

 

3. He should update to the latest firmware and use Media Code Speed Edit to check if his media is supported now, and try again

 

Do I understand this right?

Edited December 6, 2009 by laserfan

[mmalves]

1- Yes

2- Yes

3- Yes, he should update to TS08, but it still doesn't support CMC MAG-D03-64 blanks.

[Cynthia]

4. Try the Incremental write function.

[laserfan]

1- Yes

2- Yes

3- Yes, he should update to TS08, but it still doesn't support CMC MAG-D03-64 blanks.

Thanks for confirming!

[Conqueror]

OK, a lot to reply to.

 

@Lightning UK!,

Thanks for the technical info. I see what you're saying. Although the disc created with WIB is finalised. I have checked and confirmed this using discspeed tool.

 

Also, are you saying that some data was not written to the disc using WIB? But I have verified and it's all there. I've even reinstalled the game I was backing from Steam and it worked fine.

 

@Cynthia,

Sorry I was wrong. I wasn't aware that there was a new firmware. Last time I check couple of years ago and nothing was out after T06. They released versions TS07 and TS08 one year after TS06, which I missed. Nevertheless, as mmalves pointed out, the new firmware still doesn't support the TDK (CMC MAG-D03) media that I'm using - so says the latest Media Code Speed Edit v1.2.0.5. The list is exactly the same as the one posted in the screenshot by Cynthia. Here's the screenshot for the TS08 firmware that's I'm using now:

 

 

 

But I'm surprised that although I've been getting some coasters, I've been able to burn quite a few successfully with programs other than Nero and ImgBurn.

 

Anyways guys. Your responses were different to how they were when i came to this forum, maybe I saw that because I came here with a bad mood after making a lot coasters. I've had time to relax and look at this objectively. Looks like I've been using bad media. Firmware was out of date but even the latest one doesn't make my drive better for dual layer DVDs.

 

Can anyone recommend me some good dual layer DVDs, which are not too costly. Thanks.

 

 

Oh, and yeh I got the message about incremental write function. I'll try that.

Edited December 7, 2009 by Conqueror

[mmalves]

The only dual-layer media we recommend is Verbatim, and even though they're more expensive than other brands, you'll save money in the end by not making a lot of coasters.

 

Anyway, if you feel like testing dual-layer media, these are the dual-layer media IDs that your burner supports:

Media Code Speed Edit V 1.2.0.5
------------------------------------------

Firmware: TSSTcorpCD/DVDW SH-S162LTS08  0222 MULT  
Bootcode: TSSTcorpCD/DVDW SH-S162LBOOT
------------------------------------------

Overall  supported media types:  363
------------------------------------------
DVD+R9   supported media types:   11
DVD+R    supported media types:  123
DVD+RW   supported media types:   33
DVD-R9   supported media types:    3
DVD-R    supported media types:  141
DVD-RW   supported media types:   33
DVD-RAM  supported media types:   19
------------------------------------------


DVD+R9   supported media types:   11
------------------------------------------
CMC MAG  D01    2.4x
INFOME   D01    2.4x
MKM      001    2.4x
MKM      003    8x,6x,4x
PHILIPS  CD2    2.4x
PHILIPS  PD2    2.4x
PRODISC  D01    2.4x
RICOHJPN D00    2.4x
RICOHJPN D01    8x,6x,4x,2.4x
RITEK    D01    2.4x
RITEK    S04    6x,4x,2.4x

 

MKM-001-00 and MKM-003-00 are Verbatim 2.4x and 8x rated (respectively) DVD+R DL blanks. If you buy DVD+R DL blanks from "big" brands (e.g. Sony/Maxell/Samsung/etc) you'll probably get RITEK-S04 dye, which your burner does support.

[Conqueror]

OK. Thanks.

[Conqueror]

MKM-001-00 and MKM-003-00 are Verbatim 2.4x and 8x rated (respectively) DVD+R DL blanks. If you buy DVD+R DL blanks from "big" brands (e.g. Sony/Maxell/Samsung/etc) you'll probably get RITEK-S04 dye, which your burner does support.

 

How can I tell what the actual brand of the media will be before buying the pack, opening them and checking with some tool.

 

The DL disks that I use have the covers 100% like this:

 

http://www.shopneo.co.uk/tdk-ritek-s04-8x-double-layer-dvdr-10-pack-pr-17042.html

 

But as you can see, those are RITEK-S04, whereas mine were CMC MAG-D03.

[jeff_nz]

That's the thing, you generally can't tell by looking at the packaging what dye you're getting, also most "brands" get the disc's from several manufacturers (CMC, Ritek, Ricoh, etc) and depending on the batch and where you buy them from it could be any one of them.

 

The one exception is Verbatim, all their double layer discs are manufactured by their parent company and will be the MKM dye.

 

You might want to instead check out an online retailer that specialize in blank DVD's like SVP.co.uk since they list the dye used and is probably the only way to know what you're getting in advance, that is if you really want to buy one of those other brands, although I just noticed that on some products even they can't be sure and have listed several possibilities... or just get some Verbs and give them a go.

Edited December 8, 2009 by jeff_nz

[Conqueror]

Yeh, I think I'll save the hassle and start using Verbatim only. I always knew they were best, but still kept getting cheap TDK from a local store since I had always used TDK single layer without any problems. Looks like it's a different story with dual layers.

 

But I heard that even Verbatim have dodgy inferior quality ones. The ones you buy in a spindle.

Edited December 8, 2009 by Conqueror

[Conqueror]

Yeh, so I'm back after burning a DVD using "Incremental" and "Perform OPC" settings in ImgBurn.

 

First of all, the burn FAILED once again. DVD drive can't even detect the disc and keep looping endlessly trying to detect it, with green light flashing.

 

Secondly, as I have complained HERE, when I woke up, there was no log. The computer was still on but the program was closed because I chose "close program" after burning. I did not choose "shutdown computer". Therefore there was no shutdown process that interfered with log writing, yet log was not written. So I could not find out what the problem was with burn.

 

I wrote the same Image with Nero, and it wrote it first time. Verified it. I even installed the game I was backing up and it worked fine. Nero did warn me before burn that the media isn't in the database and that I should verify after burning. I continued anyway and verified and no problems.

 

Looks like no hope for me with ImgBurn with these DVDs. I'll try again when I buy a new pack of different DVD.

 

Looks like ImgBurn is only good with supported DVDs, whereas other programs like Nero, Windows Image Burner, IsoMagic, MagicIso, Alcohol20% all have no trouble writing unsupported DVDs (yes I have tested all those with the TDK discs I use). So why is ImgBurn the only one having problems?

Edited December 10, 2009 by Conqueror