dbminter

My experience has been that Sony quality is pretty low. It used to be pretty high. Then, they switched to 2nd tier Ritek. Now they're back to their own brand, it seems, but, IMO, Sony has made little but junk since 2002. The screenshots don't do much to help. We'll need the log of the failed burn. Under Help, choose ImgBurn logs. Find the failed burn entry in the .log file and copy and paste everything related to that burn. In general, my experience with Invalid field in CBD errors is caused by a drive and media incompatibility. Either your drive doesn't like that Sony brand of DVD-R or the DVD-R may be a cheap disc. LUK can probably tell you more from the log. Just in a general evaluation, I'd say try Verbatim DataLifePlus DVD-R and see what results you get. NOT Life Series. Life Series is Verbatm's junk media. You can generally only find DataLifePlus media online. However, it is the best quality media out there. Oh, LUK replied while I was typing.

It would be nice to see that feature again, but it's probably beyond the extent of ImgBurn. If we just go by its name, technically, the application should only burn images. The fact that it can create images it can burn is even a little bit beyond its initial function. Don't get me wrong; I'm glad ImgBurn can create images! But anything beyond burning images is really just gravy. I could something with an IFO feature, myself. For processing DVD's I make with my stand alone DVD recorder, converting my old camcorder tapes to DVD's.

Yeah, if the 4x doesn't work for you, try investing in the best discs to begin with, to rule out any media issues. The best out there is Verbatim's DataLifePlus media which you'll only find online. Do NOT get the Life series, which you'll find online and also in brick and mortar stores. They will be CMC Magnetics, the worst manufacturer out there.

Ah, NOW I see why LG released a firmware update for this drive after 3 years of inactivity. It appears they were forced to. This update apparently only patches some ability that the drive used to be able to rip UHD discs. Yeah, don't do anything like fix incompatibility issues with media or anything like that.

Depends on the non-Verbatim DVD-R you get. If you get a cheap one, it could be made by CMC Magnetics. CMC causes about half of the problems we see on this board. Verbatim is most likely not the problem. If you get the DataLifePlus media Verbatim makes, it's the best stuff out there you can find. Your DVD+RW was an MKM Verbatim, which is Mistubishi made. And they make the best stuff out there. It's most likely just a case of your LG drive not liking MKM DVD+RW. Like how my LG doesn't like Verbatim MKM 6x DVD-RW but my Pioneer and ASUS do. And you could probably still use DVD+RW. Just get some 4x ones, which is all they make anymore. 4x DVD+RW will most likely have a higher drive compatibility than 8x.

Yeah, another manufacturer of DVD might solve the problem. Or, depending on the maker and your drive, could open a new avenue of problems. Plus, if you went to write once media, like DVD-R, you'd probably have a better chance of compatibility. Again, depends on the manufacturer and your drive. However, a write once media will last longer than a DVD+RW, so there's the added longevity. And DVD+RW might have a higher incompatibility rate with a stand alone DVD player versus a DVD-/+R.

My guess is it's a Verbatim rewritable disc? It seems LG drives might be pretty bad at writing them. 5 LG BD drives I've had don't like Verbatim BD-RE DL, always failing at the layer change, and they fail Verify on Verbatim 6x DVD-RW. Try this if you're attempting to burn an image file to these DVD+RW. It might work. Don't write to an image file but in EZ picker mode, try Write files/folders to disc. Try burning those same files/folders to the same disc in the same drive, but with EZ Pick mode's Write files/folders to disc. I've discovered that if ImgBurn burns an ISO to a Verbatim BD-RE DL in my LG drive, it will fail the Verify. If I use Write files/folders to disc, the Verify doesn't fail. It's not a guaranteed solution, but it's worth a try. I never got a chance to test my 6x Verbatim DVD-RW, but this does work on Verbatim BD-RE DL. In fact, if another application writes the image file, it doesn't fail in the LG. And a manual Verify run from ImgBurn against the file passes, too. I can't take credit for this. Someone else experiencing my same issues discovered this workaround. And I've discovered it worked for me, too. Doesn't mean it will work for Verbatim DVD+RW, but it's worth a shot. Have you had those 8x DVD+RW for a while? Last I checked, Ritek was the only manufacturer making 8x DVD+RW anymore. And they stopped. I bought the last 3 cake stacks that were on Amazon.com. And I haven't found any 8x DVD+RW anywhere online with Google. If bypassing the image file doesn't work, it may be those discs just aren't supported by your LG drive properly. Notice how it doesn't accept the maximum write speed of 8x for that media in that drive. Now, bypassing the image file has its own drawbacks. If there's a read error during the write, it could be copied over to the target disc and the resulting files may be corrupt on the disc. So, be sure to test the files afterwards to make sure they were written properly.

Yeah, I remember when I first encountered a case where a Cancel didn't cancel and I selected Cancel again. And it bitched at me! I had to laugh out loud at it, too. It's always nice to see a good sense of humor.

A little late with my annual, cynical tradition. Unfortunately, I've pretty much exhausted my choices for songs. I'm not sure I've done this one, yet, but I think going forward, most of what I'll copy and paste will be repeats. Anyway, here's A Christmas Carol by Tom Lehrer: Christmas time is here, by golly, Disapproval would be folly, Deck the halls with hunks of holly, Fill the cup and don't say "when." Kill the turkeys, ducks and chickens, Mix the punch, drag out the Dickens, Even though the prospect sickens, Brother, here we go again. On Christmas day you can't get sore, Your fellow man you must adore, There's time to rob him all the more The other three hundred and sixty-four. Relations, sparing no expense'll Send some useless old utensil, Or a matching pen and pencil. "Just the thing I need! How nice!" It doesn't matter how sincere it Is, nor how heartfelt the spirit, Sentiment will not endear it, What's important is the price. Hark the herald tribune sings, Advertising wondrous things. God rest ye merry merchants, May ye make the yuletide pay. Angels we have heard on high Tell us to go out and buy! So let the raucous sleigh bells jingle, That hail our dear old friend Kris Kringle, Driving his reindeer across the sky. Don't stand underneath when they fly by.

Well, looks like I never got a chance to test out the Verbatim 6x DVD-RW Roxio write test in the LG. Roxio crapped out at the verify stage and when I tried to eject the disc with ImgBurn, it said a long write was in progress. The drive light kept flashing, so it was caught in a loop. Only thing for it was powering off the PC. Inserting the disc in either my Pioneer or LG caused the drive light to flash infinitely, so the disc was borked. It either had reached the natural end of its life just conveniently at the time I needed it for testing or Roxio NXT 4 destroyed it. Either way, it's moot because that was the only Verbatim 6x DVD-RW I had. At least, that I could find.

I wonder if Roxio is doing writes with the bit set to verify not required. That that is why it's not crapping out. Although if it was a Write issue, it would still be bad data on the disc. And my Reflect verify tests bear out that that is not the case. Have to fault Roxio for one thing, though. With my Pioneer Ritek 8x DVD+RW test, it encountered a Verify error, as I guessed it would. Instead of reporting it to the user or cancelling the operation, the entire Roxio burning application just crashed! I did an ImgBurn manual Verify and it crapped out right at the start of the Verify, like it always does on that media on the 1.34 Pioneer firmware.

Ah, the story of my damn life. No wonder it's not worth living. Because I needed a failure, I got the one time out of 10 where Verifiy completed! An hour and 25 minutes wasted. And I'm not going to waste any more time on this. I have a solution that works for me: not use ImgBurn to burn BD DL,media from ISO files in an LG drive and use my Pioneer to do that. I will still perform the verify in Macrium Reflect on the contents because I believe the only time this worked before, Verify completed with no errors, but the contents were not verifiable in Reflect. Unexpectedly, verify in Reflect passed with no errors. So, it's a somewhat random issue, with more failures than successes. Now, it could be I just got 3 random good results in a row. However, I performed 2 on the fly writes and 1 Roxio write with no Verify errors in ImgBurn and 2 out of 3 ISO writes with Verify failures in ImgBurn.

What's the difference between the two commands? Is one, like write(10), for writing to Layer 0 and the other for writing to Layer 1? Probably not because what would then be the command to write Layer 2 or Layer 3 for BD TL and QL?

Oh, trust me, I'm not denying there's any difference in the two implementations. But, you can't deny the results, which are different. Well, as I said, you can't deny the results until I finish this test and see if it's a Write or Verify issue. It could be a Verify against the contents issue versus a Write issue. Because there is no verify against the contents in an on the fly write as there's no image file to compare against. However, since it always fails at the layer change, that's indicative of a Write issue. What I'm doing now is a write of a 32 GB ISO of verifiable contents in another application that will spread across the 2 layers. ImgBurn is writing this ISO to a Verbatim BD-RE DL in the LG. It should fail Verify at the layer change. And, I'm hoping it does. What I don't want right now is a random Verify that succeeds. Because I want to manually issue a Verify of the contents against the ISO in my Pioneer to see if it fails Verify. If there's a Verify fail in the Pioneer at the layer change, it's a Write issue in the LG's. As I said, whatever this issue is boils down to how LG is interpreting the commands sent by ImgBurn when burning the layer change. The LG isn't handling them correctly. Because at least one other application, Roxio NXT 4, does seem to be sending a different implementation of commands to the drive that the LG "likes" better than ImgBurn's. As I also said, ImgBurn just sends write commands to the drive and it's up to the drive to interpret how those commands are received. However, we have seen in the past cases where a "certain other 15 year old application" writes just weren't liked by some drives but tolerated by other application's writes.

That's what I would think. But, you can't deny empirical results from 2 different users. For whatever reason, burning from an ISO file to Verbatim BD-R DL and BD-RE DL in an LG drive with ImgBurn causes an error at the layer change. I can't explain it but I can't deny it exists. Actually, I shouldn't say that for sure without one other test. Burning an ISO with ImgBurn in an LG and performing a manual Verify of the ISO on that disc in my Pioneer. It may be an issue in the actual Verify on an LG versus the Write. I would say it's more of an issue of the Write versus a Verify, though. I will perform that test and post my results.

Well, this was illuminating. After Roxio NXT 4 wrote the image, I did a verify of the contents in the other application. The files passed verify on both layers. So, I performed a manual Verify of the ISO that Roxio NXT 4 burned with ImgBurn, with verification against contents in the ISO file. ImgBurn Verify passed! So, the inescapable conclusion is there's something going wrong when ImgBurn switches layers writing Verbatim BD DL media in an LG drive when it's burning an ISO file. I can't see why that would happen, but it sure seems to be the case. Verify doesn't fail when ImgBurn doesn't write the ISO. ImgBurn Verifies pass when an on the fly write is performed on these media in an LG drive. So, what could be going wrong with writing from an ISO file to a Verbatim BD DL disc in an LG drive with ImgBurn? I realize ImgBurn only burns what it's given. And it only sends commands to drives. How the drive interprets those commands isn't up to ImgBurn, I know that. But, what could be the cause in this case? It is repeatable as I never burned anything but ISO's with ImgBurn in the LG before with Verbatim BD DL media. And it happened on 2 different Dell machines, and the OP's machine. And it happened on 2 different kinds of LG drives in my tests, with about 10 burns tested in the past. My LG drive also fails when writing ISO's to Verbatim 6x DVD-RW. I wonder if I repeated this test with Roxio NXT 4 as the writer of the image file in my LG and used ImgBurn to perform a Verify on it if it would pass? Something to try if I can remember do it. Another thing to ponder. For a year, I've been saying Pioneer borked writing to Ritek 8x DVD+RW with its 1.34 firmware. ImgBurn always failed Verify on them. I think I'll try the Roxio NXT burn/ImgBurn manual Verify test in that scenario. See if it's ONLY the firmware writing these discs that causes the problem. So, it seems my initial advice I've been giving people over the years is incorrect. LG drives apparently aren't lousy writers when it comes to Verbatim BD DL media. They're just lousy at interpreting the commands ImgBurn sends them when it writes an ISO file to that media, it seems. No, I can verify (HA!) that the firmware IS borked in the Pioneer. Roxio NXT failed right at the start of Verify as did ImgBurn when Verifying the contents.

I wrote another set of data that was about 32 GB that I could perform a verify of the contents on in another application. If it was going to fail at the layer change, this verify in the other application would fail to read the file. The verify on all files across both layers ended correctly, so the data was written properly by ImgBurn when done on the fly and not a Verify against an ISO file's contents. Next, just to see what kind of results I get, I'm going to use UltraISO to create a BD-50 image with the same contents as above. These types of burns I always create with UltraISO but burn with ImgBurn in my Pioneer drive to Verbatim BD-RE DL because the Verifies always failed on the LG. I'll use UltraISO or something else to burn the image in the LG drive to a Verbatim BD-RE DL. Then, I'm going to use ImgBurn to perform a Verify of the contents it didn't burn against the ISO file it created. See if that fails at the layer change. If it doesn't fail at the layer change, then it would seem that, for whatever reason, the ISO files aren't being written correctly by ImgBurn to Verbatim BD-R DL and BD-RE DL at the layer change. EDIT: Couldn't use UltraISO for burning. I forgot that most of its features don't work right. The only thing I've found it does right is that it will inject files properly into existing images, which is helpful for adding files to bootable images. The only feature I use it for. I've started the burn with Roxio NXT 4.

Well, I'll be damned! I tried an on the fly burn of a BD-50 contents (30 GB) in my LG with a Verbatim BD-RE DL and it successfully passed the Verify! Now, this could be a fluke. I had 1 in 10 test burns of BD-RE DL in the LG that passed Verify, but the contents were corrupted on the disc. I need to perform another test to make sure the contents are good. LUK, my question here is: why would an on the fly write Verify pass but a Verify of an ISO with verifying against the contents in the ISO file fail? And always at the layer break?

I'd be curious to see the results of an ISO burn on this new LG drive. I think it's just coincidence. If it works on the fly, it should work on ISO. Burning from an ISO should make no difference as to whether a burn will fail Verify or not. If it were an ISO issue, it would fail on Pioneer as well. Unfortunately, I can't do that. The only DL media I burn have to be bootable. So, I need to edit a bootable ISO with UltraIISO to inject files into it.

I still reiterate my idea that LG drives just are terrible with BD DL media. Try a Pioneer and I think that will probably fix your issue. Can't guarantee it, of course. As has been said, there really isn't much that can be done at this point beyond that. Your LG drive is returning generic errors that don't help much. Or it's returning the wrong errors. Even if it was returning wrong errors and you fixed that issue, I still doubt that would fix your BD DL issue. Experience has taught me that LG's just aren't reliable for writing BD DL media.

What might work is to use USB ImgTool to make an .IMG file of the bootable flash drive. Virtual CloneDrive should mount this .IMG as a virtual optical drive. Then you could try using ImgBurn to read the mounted virtual drive to an .ISO file. I don't know if this will work, but it's about the only thing I can think of that might work. Good luck.

Good to have both on hand. That way, when you get one, you can test it and if it doesn't work, send it back. Then, you'll have the other on hand, too, to try next. That model of Pioneer is the one I have always used. In fact, I have 2 of them. The 2nd one I got I still use and the first one I got still works. Just sitting around to swap in. Pioneer's have a few flaws of their own. After a few months, the eject button doesn't always work the first time it's pressed. Pressing it again works. Issuing an Eject command in ImgBurn does the same thing. However, all eject commands issued after a write if directed by ImgBurn seem to work. The current firmware is borked for Ritek 8x DVD+RW media. However, it's a moot point as you can't find 8x DVD+RW new anymore. The quality of that drive may have declined if my experience is any indication. I don't know yet. Can only relate my story. As I said, my first 2 drives have performed well. My first is almost 3 years old and still works. My current one is almost 2 years old and still works. The 3rd one I had, though, I had to replace after 7 months. The 4th one I got I had to send back to Amazon.com because it was borked for writing Verbatim BD-R out of the box. However, with all that said, I'd still recommend trying a Pioneer first for a BD burner.

Discovered another LG/Verbatim incompatibility after testing more 1.03 media burns. The LG's never liked writing to Verbatim 6x DVD-RW media, either. 1.03 does nothing to fix this. They still fail at the, guess where? Verify! My Pioneer writes them fine.

The problem is with LG drives and Verbatim BD DL. I updated the firmware to 1.03, performed another BD-RE DL test. Of course, it STILL failed Verify at the layer break change. I 15:23:00 Operation Started! I 15:23:00 Source File Sectors: 15,957,344 (MODE1/2048) I 15:23:00 Source File Size: 32,680,640,512 bytes I 15:23:00 Source File Volume Set Identifier: 4B8B79FA00F37D0A I 15:23:00 Source File Application Identifier: ImgBurn v2.5.8.0 I 15:23:00 Source File Implementation Identifier: ImgBurn I 15:23:00 Source File File System(s): UDF (2.60) I 15:23:00 Destination Device: [0:0:0] HL-DT-ST BD-RE WH16NS40 1.03 (S:) (SATA) I 15:23:00 Destination Media Type: BD-RE (Disc ID: VERBAT-IM1-000) I 15:23:00 Destination Media Supported Write Speeds: 2x I 15:23:00 Destination Media Sectors: 24,438,784 I 15:23:01 Write Mode: BD I 15:23:01 Write Type: DAO I 15:23:01 Write Speed: MAX I 15:23:01 Hardware Defect Management Active: No I 15:23:01 BD-RE FastWrite: No I 15:23:01 Link Size: Auto I 15:23:01 Lock Volume: Yes I 15:23:01 Test Mode: No I 15:23:01 OPC: No I 15:23:01 BURN-Proof: Enabled I 15:23:01 Write Speed Successfully Set! - Effective: 8,992 KB/s (2x) I 15:23:02 Filling Buffer... (40 MiB) I 15:23:03 Writing LeadIn... I 15:23:27 Writing Session 1 of 1... (1 Track, LBA: 0 - 15957343) I 15:23:27 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 15957343) I 15:23:27 Writing Layer 0... (LBA: 0 - 12219391) I 16:08:25 Writing Layer 1... (LBA: 12219392 - 15957343) I 16:22:34 Synchronising Cache... I 16:22:58 Exporting Graph Data... I 16:22:58 Export Successfully Completed! I 16:22:58 Operation Successfully Completed! - Duration: 00:59:57 I 16:22:58 Average Write Rate: 9,000 KiB/s (2.1x) - Maximum Write Rate: 9,560 KiB/s (2.2x) I 16:22:58 Cycling Tray before Verify... W 16:23:05 Waiting for device to become ready... I 16:23:20 Device Ready! I 16:23:24 Operation Started! I 16:23:24 Source Device: [0:0:0] HL-DT-ST BD-RE WH16NS40 1.03 (S:) (SATA) I 16:23:24 Source Media Type: BD-RE (Disc ID: VERBAT-IM1-000) I 16:23:24 Source Media Supported Read Speeds: 2x, 4x, 6x I 16:23:24 Source Media Supported Write Speeds: 2x I 16:23:24 Source Media Sectors: 24,438,784 I 16:23:24 Source Media Size: 50,050,629,632 bytes I 16:23:24 Image File Sectors: 15,957,344 (MODE1/2048) I 16:23:24 Image File Size: 32,680,640,512 bytes I 16:23:24 Image File Volume Identifier: 12 - December I 16:23:24 Image File Volume Set Identifier: 4B8B79FA00F37D0A I 16:23:24 Image File Application Identifier: ImgBurn v2.5.8.0 I 16:23:24 Image File Implementation Identifier: ImgBurn I 16:23:24 Image File File System(s): UDF (2.60) I 16:23:24 Read Speed (Data/Audio): MAX / MAX I 16:23:25 Read Speed - Effective: 2x - 6x, 6x - 2x I 16:23:25 Verifying Session 1 of 1... (1 Track, LBA: 0 - 15957343) I 16:23:25 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 15957343) I 16:23:25 Verifying Layer 0... (LBA: 0 - 12219391) I 16:59:06 Verifying Layer 1... (LBA: 12219392 - 15957343) W 16:59:10 Failed to Read Sectors 12219616 - 12219647 - Reason: L-EC Uncorrectable Error W 16:59:16 Failed to Read Sector 12219616 - Reason: L-EC Uncorrectable Error W 16:59:16 Sector 12219616 maps to File: \12 - December\12 - December-00-03.mrimg E 17:31:27 Failed to Read Sector 12219616 - Reason: L-EC Uncorrectable Error E 17:31:27 Sector 12219616 maps to File: \12 - December\12 - December-00-03.mrimg E 17:31:27 Failed to Verify Sectors! I 17:31:33 Exporting Graph Data... I 17:31:33 Export Successfully Completed! E 17:31:33 Operation Failed! - Duration: 01:08:03 I 17:31:33 Average Verify Rate: 5,987 KiB/s (1.4x) - Maximum Verify Rate: 32,591 KiB/s (7.4x) Notice how it failed Verify with less than 300 sectors into the 2nd layer? The issue is an inherent problem with LG drives and (at least) Verbatim BD-RE DL. Since it happens on your drive, too, it happens on all Verbatim BD-R DL and BD-RE DL. And it may even happen on ALL manufacturers of BD DL media. Nothing had ever been written to this Verbatim BD-RE DL before. It had only been "written once" when it was formatted in a Pioneer drive. So, it's highly unlikely the disc is bad. And it's highly unlikely that the Pioneer formatted it wrong because the Pioneer and my USB ASUS write to these kinds of discs fine. Only the 5 LG's I've tested do this. They all fail Verify except for one Verify, and the contents were NOT written correctly to the disc when I compared the written contents with the source. Ergo, the problem is with all LG drives. QED.

Wait, there's a 1.03 firmware update to that drive? I have that LG drive because it writes properly to all other media except for BD-RE DL and firmwarehq only lists 1.02, my firmware. Found the firmware on LG's site for the drive. It appears it was just released 3 days ago. After over 3 years of no new firmware updates, it seems LG finally updated this drive. Seems it didn't fix the BD-RE DL issue, but I'll test it out, anyway. If it makes you feel any better, I, at least, found some useful information from this post. Thanks!