Avatar: Fire and Ash UHD - BW-16D1HT fails at same offset during both MKV extraction and full Backup

[Andyg4000]

Thanks for that — useful data point. Between your PS5 glitch (recoverable) and my Panasonic UB820 playing the original disc perfectly fine, it seems like normal playback tolerates this disc a lot better than ripping does — buffered/retry-friendly playback vs. raw sector-by-sector extraction.
Your MakeMKV log is interesting too: "corrupt or invalid... attempting to work around" is a softer failure mode than the hard ILLEGAL REQUEST errors I was getting, and it's a different file (00681.m2ts) and a different drive (\Device\CdRom1 — what drive/mechanism are you running?). Combined with my results, it looks less like a single bad disc and more like this pressing having some genuinely marginal sectors that different drives/players handle with very different tolerance.
For what it's worth, my fix was switching from the ASUS BW-16D1HT to a Pioneer BDR-UD04 (Verbatim external), which ripped clean in Direct disc access mode. Might be worth trying a different drive if you can before giving up on the disc — curious whether it's specifically ASUS/MediaTek-based drives struggling here, or something else.

Exactly :
Hitachi - LG Data Storage
Model BU40N

Originally Rom Ver 1.04, but restored to 1.0

We will send the Disc back to Amazon as we are in the 30 day window and ask for a replacement

[Andyg4000]

The New UHD disc arrived from Amazon.

Good news it copied clean!

When first used, it saw lots of errors and failed pretty quick. This was the _Eng first file.

So I resarted my PC and used the 2nd file without the _Eng and obviously copied no problems, just over an hour or so.

Checking both disc, the new disc is perfect, but you can definitely see 'rings' NOT scratches in the original disc.

Good luck for anybody who reads this thread - it is more than likely you have a bad UHD disc.

USB-
Drive Information
OS device name: K:
Current profile: BD-ROM
Manufacturer: HL-DT-ST
Product: BD-RE BU40N
Revision: 1.00
Serial number: xxxxxxxxxxxxx
Firmware date: 2116-12-20 15:28
Bus encryption flags: 17
Highest AACS version: 82

LibreDrive Information
Status: Enabled
Drive platform: MT1959
Firmware type: Original (unpatched)
Firmware version: 1.00
DVD all regions: Yes
BD raw data read: Yes
BD raw metadata read: Yes
Unrestricted read speed: Yes

[whswede]

That's a really useful data point — thanks for following up. Two things stand out: your BU40N reports "Drive platform: MT1959", which is the same underlying chip platform as the ASUS BW-16D1HT (different brand, same silicon). So this may be more of an MT1959-platform-specific sensitivity than a purely ASUS-branded issue??

And the visible "rings" you found on the original disc but not the replacement is compelling evidence for genuine disc-to-disc quality variance in this print run — a clean disc reads fine even on the MT1959 platform that failed on the bad one. That fits better with "bad individual discs" than a pure drive incompatibility.

I'd guess my case was a milder version of the same thing — my replacement disc had marginal sectors severe enough to trip up the ASUS/MT1959 platform but not severe enough to stop a Pioneer drive with a more forgiving read strategy from getting through clean.

Sounds like the practical takeaway for anyone hitting this: if you're on an MT1959-based drive and hitting these errors, it's worth trying a replacement disc before assuming it's the drive — but if that doesn't work, a different drive platform (or checking for visible surface marks under good lighting) might be the next step.

[Andyg4000]

That's a really useful data point — thanks for following up. Two things stand out: your BU40N reports "Drive platform: MT1959", which is the same underlying chip platform as the ASUS BW-16D1HT (different brand, same silicon). So this may be more of an MT1959-platform-specific sensitivity than a purely ASUS-branded issue??

And the visible "rings" you found on the original disc but not the replacement is compelling evidence for genuine disc-to-disc quality variance in this print run — a clean disc reads fine even on the MT1959 platform that failed on the bad one. That fits better with "bad individual discs" than a pure drive incompatibility.

I'd guess my case was a milder version of the same thing — my replacement disc had marginal sectors severe enough to trip up the ASUS/MT1959 platform but not severe enough to stop a Pioneer drive with a more forgiving read strategy from getting through clean.

Sounds like the practical takeaway for anyone hitting this: if you're on an MT1959-based drive and hitting these errors, it's worth trying a replacement disc before assuming it's the drive — but if that doesn't work, a different drive platform (or checking for visible surface marks under good lighting) might be the next step.

Totally agree - so worth buying from Amazon as easy to return.