LIGHTNING UK!

To me, those power calibration error suggest the drive doesn't like the daxon-rx4 mid. I don't think you gave anything to worry about regarding the device buffer. That's just happening because of your other issue.

Unless I'm missing something, 1gb is divisible (exactly) by 64k.

Your drive hasn't burnt that properly. Try some other discs. Always using Sony doesn't meant anything. It's the MID/Disc ID that's important and your drive doesn't appear to like the Ritek ones you're using.

Sorry, no.

When I asked why version 9, I did so because v9 is ancient. I run v10.8 and even that's ancient.

Which chipset does your motherboard use? Is there any reason you've gone for v9 of the IRST driver? Have you tried booting into safe mode to see if it does the same thing? It looks like the OS/drive is blocking one command as the error being returned is not from the drive itself. 'FF FF' means it came from the OS/driver rather than the drive itself. So IRST could be blocking the command or swallowing the actual error and returning its own - which isn't helpful! There's also something weird going on with the subchannel requests/responses. Notice how the first 5 'Buffer' lines have values in them, then they're basically just full of zeroes. The program is asking for info but never receiving it.

Some commands are expected to fail, don't worry about it. What's the actual problem? Are you getting an actual error message?

Where was sequence or scene order mentioned? I'm only browsing on my phone but I've scanned the thread a few times and can see no mention of it before your post Ch3vr0n. John30, What db said is correct. Unless your playback device supports playing m2t files, you'll have to convert it into the proper BD Video format/structure and burn that.

The buffer is allocated via a single call to the 'VirtualAlloc' API function. So that's what's failing and this isn't really a bug, so to speak.

Hard to tell really. If they all fail, try another spindle. If that does the same, it could be the drive. If they don't, it's probably the media.

If you're getting random miscomapres, it's probably because you have a memory issue. Download and run memtest to check for errors. Windows also has its own diagnostics program in it now I seem to remember.

That doesn't even look like an opencandy detection issue. Maybe you clicked an advert rather than going to the download page and picking from the seven listed mirror sites. As such, you may have ended up with just about anything. And why are you downloading it again when you already have it? Have you reformatted?

I've never seen anything that can do that myself. It certainly isn't possible with ImgBurn and is an authoring thing rather than a burning thing.

If you go into Write mode (write image file to disc) and then right click on the drive selection box (with the BD active/selected), you can click on 'Family Tree' and it'll tell you which controller it's on. After that it's just a case of messing around with drivers etc. to find one that makes your system stable.

If they're saying it'll last 1000, I'm sure you could at least expect it to outlive you. So when you're 90, you'll be able to hunt down the last remaining optical drive in existence and pull up all of the ROMs from your mdisc backups.

You ask for my opinion and then just ignore it anyway. I'd do exactly what I've been telling you to do... burn a disc at each speed. I'd probably start with 4x though. It'll mean I don't have to wait so long to check the disc. Please don't think for a second that I know the optimal write speed for every drive/firmware/media combo. I don't.

No. And you aren't going to 'lose' them unless the burn completely fails. If they're readable and supposedly don't deteriorate, you've nothing to worry about.

Neither do I! As I've said time and time again, burn at each speed and scan them for yourself. You can then make your own mind up as to what works best for your drive/firmware/media combo.

Have you only tried burning at 'MAX' speed (6x) with the Pioneer? Maybe try the remaining 2 supported speeds (2x and 4x) to see if it does a better job of burning the discs. If it still can't produce a readable disc at either of those, you'll have to invest in another drive.

The EBK supports BDXL media and the DBK doesn't. So technically, the EBK is superior. The firmware for both drives always seems to come out at the same time and they're both at the same version, so I can't really see media support being better on one than the other - that's to say they each have *some* level of support for the same MIDs. Of course if the optics are different (in order to support BDXL), I guess it's entirely possible the fine tuning for specific MIDs (equalling better burn quality) is better on one than the other. Different drives of the same model can perform differently though, so it's not always easy to judge such things.

It would be useful to see the disc info from the box on the right (in Write mode) when the NS40 does and doesn't error out as the program attempts that format with quick certification (FST 0x03). Of course if you've packaged it up now, that won't be possible Just something for me to remember to check next time I'm able to. EDIT (because you just posted): I figured the NS40 would always produce that line on a brand new and uncertified disc. As you say then, it must be down to the state the NS55 leaves the disc in - this is where the disc info would come in really handy! After ImgBurn has tried its workaround to do a full format with quick certification and it fails, it tries it again with no certification. Only after that does it do the full format with full certification like you've actually asked it to. I've actually swapped that round now too as it's pointless quick certifying if you're then going to full certify.

Ah there's actually something a bit funny going on here. The bit I was referring to in the log is this bit... When I first saw your log, I wasn't near my computer and the exact meaning behind the values of FST escaped me. I figured it meant 'Full Certification' and the program was then falling back to 'Quick' or 'No' certification. It turns outs that 0x03 actually means 'Quick Certification' and that's then made me think something isn't quite right there as it shouldn't be attempting to perform 'Quick Certification', it should be doing 'Full Certification'. So I fired up the development environment to see what's happening and notice there's a workaround in place for LG drives in the WH1x and BH1x ranges. The workaround makes the program perform a full format with quick certification before then doing another one with full certification. Without that, the full format with full certification didn't seem to 'take' and the disc probably came out looking as if it hadn't ever been formatted. From what I can tell, the workaround was added back in 2010 for the BH10 and maybe BH12 models, but was set up to be future proof and work with any in the '10' range - so it's also being applied to BH14 and BH16 models that came out later on. Since then of course, LG have taken to using a different chipset for the BH14 and BD16 drives and these don't need the workaround anyway I expect. I will now adjust my workaround so it only applies to the 10 and 12 models. All that is of course beside the point! Your BH16NS55 seems to be having trouble with the disc and is remapping loads of duff sectors into the 'spare area' - only there are too many and the spare area has been exhausted. Additional format attempts might help matters, as might formatting on the NS40 before trying again on the NS55. It's unfortunate that the NS55 can't handle the CMC discs like your NS40 can, but that doesn't necessarily mean there's anything wrong with it. It could be better than the NS40 on all other media The Pioneer 209 is a good alternative, so yeah, try giving one of those a go. Oh and I never meant to say your discs were fake, they just aren't what I call 'true' Verbatims

Have you exhausted the actual intel sata ports on the MB and that's why it's on the Asmedia ones to begin with? Always opt for the intel ones over 3rd party. Glad the driver update fixed your issue though

If you burn using ImgBurn in Build mode (and the option to verify is enabled), it'll recreate the 'virtual' image (built up from your files/folders) and so verification will still be at byte level and miscompares will be picked up. Doing it after the fact when you don't have an ISO to compare against will mean it just checks the sectors are readable.

Your ns40 doesn't support the same format as the ns55. The ns55 can do the 'full certification' and is detecting an issue that maybe your other drive can't? Btw, your verbatim discs have the wrong MID. Yours are CMC.