I just updated the firmware to v3.10 (honestly didn't expect there to be a new version of it). Also, uninstalled and re-installed ImgBurn to be safe after that. Will post the log the next time it fails. It doesn't fail ALL the time, but often enough to get expensive

Greettings all!
I am using quality BD discs (Quantum Optical), and have never had an issue until recently. I though my burner was going bad, so I ordered a new one - but the errors continue (this is on VERIFY, not burn!)
I/O Error!
ScsiStatus: 0x02
Interpretation: Check Condition
CBD: 28 00 01 64 E1 80 00 00 01 00
Interpretation Read(10) - Sector 23388544
Sense Area: 70 00 03 00 00 00 00 DA 00 00 00 00 11 50 00 00 00 00
Sk Interpretation: Medium Error
ASC/ASCQ Interpretation: L-EC Uncorrectable Error
It's getting ridiculous and wasting me a LOT of money. Please help!
Could this be the SATA cable?
I had a BD50 blow out at 99%!!!
=====================================
I just checked the file that didn't verify and it played perfectly fine. WTH is going on???!!!!
*I should add that the SATA cable is a Monoprice cable, so not a no-name brand.
**I have also tried with OPC on and off - it doesn't seem to make a difference. Win10x64 current Insider build.

The Asus was recently rated as the best, most durable drive, which is why I got it over another LG. And yes, I got the VAST majority of the failures with the LG - I thought the LG might be dying, that's why I got the Asus. The Ritek discs are the BD50s and I only had one of those blow out - the one that had the error at 99% I tested and it played fine - it was the 12 BD25s of OTCBDR-002-000 that I had the issue with. I'm wondering if it was just a bad batch of discs. I've never had a problem with either before (on the LG) - maybe 1 or 2 discs, but that's it.

Greetings!
I have a Samsung SH-224DB (SB01) drive and am attempting to burn 2,305,344 Sectors (4502MiB) to 2,298,496 Sectors (4489MiB)
I get the following error -
Failed to Reserve Track! - Reason: Invalid Field in CDB
Is there a setting I can change to allow this or is this simply beyond any overburn amount? I would have expected to be able to overburn that slight amount.
Thanks!

Ok, this is really starting to p*** me off.
I've had this working just fine, but had to re-install Win 7 x64. I have 32gb RAM and a 200gb pagefile - no matter what I set the IO Buffer to be (even as low as 128mb!) it is not working and I get the same error every time I try to burn.
It is CLEARLY *NOT* and issue with insufficient memory - Physical Memory shows 33,493,780 with 21,584,285 available (per Process Explorer). I have even tried different Interface selections, but nothing changes. It is also being run under Admin.
Please assist. ImgBurn is the only burner software that I am aware of that does Verify, so I don't want to have to switch to another.
Thank you!

Yes, the buffer size *does* change with the slider.
Additionally, this *only* happens when I try to burn files/folders directly, if they are from an ISO/MDS file, then they burn fine.
There appears to be nothing related to my issue when [g]-ing "virtualalloc failed" - I am not a coder

That is the exact error.
Selecting Build>Burn (ISO/Joliet/UDF) - single layer
It goes from -
VirtualAlloc Failed!
Reason: Not enough storage is available to process this command.
Hit OK
Failed to initialise FIFO Buffer (<amount of IO buffer selected>)

Ok, I just re-installed Windows 7 and now I can't get multiple instances of ImgBurn ready to roll - well, I can have multiple instances OPEN, but none but the first will see the drive. I get -
This drive is currently locked for exclusive access by 'ImgBurn v2.5.8.0 - PID: 13524'.
Device->Initialise() Failed!
Device: [0:2:0] DVD-RW (X:) (ATAPI)
This drive will not be visible in the program.
Now I previously did not have this problem - I could get several instances of ImgBurn ready to burn, just awaiting the switching of discs - now I have to manually Search for devices each time
Thanks for any help!

IMHO, there is a difference between locking the drive, and making the drive "invisible" and forcing a manual search. Once the burn is completed, that should automatically release the drive to the other instances - one should not have to manually search for the drive each time.

Same mfr (diff codes), but I get a LOT of L-EC Uncorrectable Errors on the DL discs - *never* on SL discs - almost always at ~99% of verify.
ImgBurn is the only program I know of that has the VERIFY function - anyone know of any others that I could use for a comparison?
I have tried different I/o interfaces, but still get the error.
It is not "cheap" media either.
Thanks.

Ok, still kind of odd to me - it would seem it's just "ignoring" hardware errors if it's turned off ..... ?
What's stranger is that, having it set to begin with, as I said, the drives seem to start having problems after a few months of use .....