LIGHTNING UK!

It's not worth reflashing, no. This is a controller/driver issue.

If it burns without error, it overburnt. It'll be fine, just try it.

1 sector = 1 frame = 1/75th of a second. So that's all you'd lose if it fails at the end - but it might overburn anyway.

Yes, optical drives don't like 3rd party controllers very much. Stick with the real chipset ports where possible.

Does your board have native 6gbps or is that 6gbps controller a Marvell or something? Right click the drive selection drop down box and click 'Family Tree'. Close the prompt and then copy + paste the family tree info from the log window.

Isn't that just the drive spinning a badly balanced disc? Regarding the KProbe results, it's so much easier to look at the graph rather than read/interpret numbers. If you only provide one or the other, please provide the screenshot/graph. I did say later burns might play up again. It took me 7 attempts from a spindle of 20 to get settings that produced consistent burns.

Do you have the drive on a Via card by any chance? If so, get it off it... they don't work well together. Put the drive on your motherboard chipset's SATA controller. Oh and don't write in CAPS.

These are general cd/dvd terms. I'm sure Googling would return some results.

Right click the drive selection drop down box and select 'Family Tree'. Close the prompt that comes up and then copy + paste the family tree info from the log window.

Mount them in DAEMON Tools and read to a new image?

What I'm saying is that the error might not actually exist at all. Had you not have built+burn on the fly, I'd have told you to verify the disc against the same image again. Now you'll have to use something like Beyond Compare to re-check the file on the disc against the file on your hdd. Don't forget about memtest.

2.5.6.1 shouldn't be doing it. If it is, please go back in the beta forum and let's deal with it in there.

ImgBurn is written around the MMC specs and all drives (in the last X years anyway) comply with them. No, it's nothing to do with the layer break either. Your drive is reporting a 'Write Error' at the end of the burn as it tries to write what's in its cache to the disc. It looks like the retry was successful but you never really know with these things. Then of course the drive had a problem trying to finalise the disc. As you burnt that disc at max speed (6x), do one of the things recommended in that thread I linked you to and try the remaining supported write speeds - start with 4x.

Are you using the 2.5.6.1 beta?

It's 1 bit in a byte. I can't tell you what it'll do to the stream... at a guess though, nothing. Such errors are usually related to memory issues. Run memtest86+ for a few passes to test it. btw, you should be using ImgBurn v2.5.6.0 and your Pioneer drive could do with having its firmware updated - http://www.firmwarehq.com/Pioneer/DVR-108/files.html

The program version has no bearing on your drive's ability to burn a disc. http://forum.imgburn.com/index.php?showtopic=8000

It doesn't look like that disc is fully readable in your drive. That could be due to a fault / scratch / dirt, or it could be some sort of copy protection.

Your drive might burn those discs or it might not. Try it and see. The burn quality probably won't be up there with the likes of Verbatim discs but it might just be enough to pass the Verify phase. Mount the ISO in a virtual drive (or just extract it to a folder somewhere) and try building a new image from said virtual drive (or folder) with ImgBurn.

Yes, it works fine with whatever discs you throw at it... even the BDXL ones (which your drive doesn't support). Failure to format is down to your drive/firmware/media combo. The drive is doing the work, not the program.

There are some BD media scans in the 'Drives' section (only for Blu-ray drives obviously!). Have a look and see how various ones performed. I didn't test many DL discs... and certainly not any Taiyo Yuden ones. The cdfreaks/MyCE forums might have a few though.

That looks fine but you may find it gets worse again as you burn more discs (like mine did when I tested about 12 discs from a spindle). Keep an eye on it.

Can you scan the disc you got from your friend and post the screenshot of the results please. If it looks the same as the others you've posted, just say it's producing bad burns at the end of Verbatim MKM003 DL discs - and that you've tried 2 spindles. It might be worth you loading the latest official firmware and burning one more with that (still at 4x) just to double check it's bad (post the scan screenshot of that too).

Is your friend able to (over)burn their MKM003 without issues? Can they burn yours too? I guess you could have a faulty drive (or at least one that can't overburn very well), yeah.

You must have a bad spindle of discs. You aren't even just getting a spike at the overburnt layer break position (as is the norm for most 'bad' burns), you're getting high error levels before, in and after the overburnt area. When looking at my results (with the iHAS124 drive) you have to take into account that some of the tests may have been done without using anything beyond normal disc capacity (so no overburning as allowed by the 'max' firmware). My Aone discs wouldn't overburn without failing to verify.

If the OS doesn't see the disc, normally it's because you (or some other app) has killed (disabled) the autoinsert / media control notification stuff built into Windows. I have no problem with it here, Windows usually pops up the 'Autorun' box between a Write and Verify operation - exactly as it should do. Your drive totally vanishing from Explorer isn't a good sign! Look at post #6 here - http://forum.imgburn.com/index.php?showtopic=19159