Asus BW-16D1HT Firmware crashes? Faulty drive?

[d0pamin]

Hello everyone,
first of all huge thank's to every person contributing guides, tutorials, answers and of course software to this community! It really helped me to get started with MakeMKV and Blu-rays.

I bought an Asus BW-16D1HT a few weeks ago and it came with the 3.03 Firmware. This is why I flashed it to the 3.10 MK firmware using the recommended (super easy to use) tool from this forum. Everything seemed to be just fine, I could read even UHD discs and they would rip perfectly.
But after ripping a few discs (non-UHD) I started experiencing an awkward behavior: The drive starts to spin very loudly (no "scratching" sounds just like high speed spinning) and MakeMKV says the rip failed. The eject Button in MakeMKV stops working and also pressing the physical eject button on the drive did not make the drive open. After restarting MakeMKV it says that no usable optical drives could be found. The only way to fix this was to reboot my machine (which is very annoying because the drive is connected to my home server).
So I decided to flash another firmware and see if this makes any difference. I booted up into windows and flashed the official 3.02 (from the firmware pack). UHD discs were still no problem but after ripping 2-3 discs the drive would become not-responsive again. But this time it was not spinning the disc for ever (just stopped spinning) and the physical eject button was still working. So actually a little bit better but sadly these "crashes" occurred a lot more frequent. Again: only a reboot helped.
After that I gave 3.01 a try and everything went pretty good for like 20-30 discs before it stopped working. This time even more strange since the drive seems to have lost power connection completely. It "crashed" after ejecting a disc while the tray was open: This time I was not able to close the tray anymore.

Just rebooted my server and now it is working fine again.
I tried to research this issue on Google but was not very successful (didn't even know what to search for) and this is why I am asking you for help:
- Is it possible that this is a software issue?
- Might this be a firmware problem?
- Do I need to return the drive because this probably is a hardware issue?
- How can I "debug" this issue?

Some useful info:
I am running MakeMKV on my linux server but this problem also occurred when testing the drive using Windows 10.
I swapped the SATA cable and port and the power cable but no difference.
This problem occurs with all kinds of discs: Blu-rays and DVDs

It would be very helpful if anyone could tell me what my best options are from now on

Kind regards

[mike admin]

I have never seen anything like that. I would call it a hardware glitch - sort of lame, but I never seen anything close. Especially that it reproduces on stock firmware (not that MK firmware changes any code logic, but still)...

[d0pamin]

Hi Mike,
thank's for your reply! Although there seems to be no "magic" solution it's good to hear that I wasn't just overlooking something obvious or made a mistake.
So I will try to return my drive.

Thank's to everyone for reading my post

Kind regards

[ImCoKeMaN]

Are you able to put the drive in a different machine to help determine if it's the drive or something else on the server? Could be something getting warm and flaking out, cpu, memory, motherboard components, or drive.

[d0pamin]

Are you able to put the drive in a different machine to help determine if it's the drive or something else on the server? Could be something getting warm and flaking out, cpu, memory, motherboard components, or drive.

Sadly I don't have a second computer around. I might try to get my hands on one before RMAing the drive. I think all temps are ok, CPU and Memory are also fine and nothing except the drive makes trouble. I even tried out different SATA ports. But thank's for your suggestions!

I tried to narrow down the occurrence of this issue a bit further and I think I have observed some interesting things:
1. The error occurred after I tried to rip a blu-ray after ripping several DVDs.
2. The error occurs in the "processing BD+"-stage. This is what gets written to the log:

Code: Select all

1 titles saved
Using direct disc access mode
Using LibreDrive mode (v06.2 id=E064BA3E3F81)
Loaded content hash table, will verify integrity of M2TS files.
DEBUG: Code 2399223810 at !Ko|V6~1>:Q>[Nj2M:29397219
DEBUG: Code 2399223810 at !Ko|V6~1>:Q>[Nj2M:29397219
DEBUG: Code 2399223810 at !Ko|V6~1>:Q>[Nj2M:213132399
DEBUG: Code 2 at !Ko|V6~1>:Q>[Nj2M:29396920
DEBUG: Code 2399305730 at !Ko|V6~1>:Q>[Nj2M:213132399
DEBUG: Code 3 at !Ko|V6~1>:Q>[Nj2M:29396920
DEBUG: Code 2399305730 at !Ko|V6~1>:Q>[Nj2M:213132399
DEBUG: Code 4 at !Ko|V6~1>:Q>[Nj2M:29396920
DEBUG: Code 0 at 0DqdsUZ)*@R^v:>2:29396920
DEBUG: Code 100864260 at 59\D5CLED~UVu32XvH:213131778
DEBUG: Code 100864260 at 59\D5CLED~UVu32XvH:121261934
Error 'Scsi error - MEDIUM ERROR:UNRECOVERED READ ERROR - AUTO REALLOCATE FAILED' occurred while reading 'BD-RE ASUS BW-16D1HT 3.01' at offset '3801088'
DEBUG: Code 100864260 at 59\D5CLED~UVu32XvH:213131778
DEBUG: Code 100864260 at 59\D5CLED~UVu32XvH:121261934
Error 'Scsi error - MEDIUM ERROR:UNRECOVERED READ ERROR - AUTO REALLOCATE FAILED' occurred while reading 'BD-RE ASUS BW-16D1HT 3.01' at offset '3801088'
...

(these errors keep on coming)
As stated before: a reboot fixes this issue and the same blu-ray can be ripped without any issues. The disc is in a perfect condition, I just got it.

Maybe someone else can "read" something from this log, I tried to research some of the error codes but I couldn't find anything.

Kind regards

[McStarfighter]

I've got the same problem with my 2 patched drives (ASUS BW-16D1HT & LG BH16NS55 since the 1.15.2 update (running on Debian).
On my Pioneer (not patched) I've got no problems.

I got multiple notifications of "Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading '/BDMV/STREAM/00285.m2ts' at offset '0'" on my LG, on ASUS I got "Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading 'BD-RE ASUS BW-16D1HT 3.10' at offset '4980736'"

[Navvie]

I get a similar sounding problem on my BW16D1HT, on original 3.01 firmware - and LibreDrive sdf.070.bin, with 1.15.2. I can't get any discs to rip before I get errors though. UHDs that ripped fine in previous versions are no longer detected. Those UHDs continue to rip fine when I reinstall 1.15.1.

My hardware and software hasn't changed, just the version of MakeMKV. I'll do some more testing later and post error messages, logs but right now my priority was getting my UHDs to rip.

Edited: for clarity!

[monkeymindboy]

I appear to have a similar issue since upgrading to 1.15.2. I have two UHD friendly drives in my PC, Asus BW-16D1HT and an LG WH16NS40 and now the Asus drive will not read certain 4K discs. For example, I was re-ripping several discs with 1.15.2, Saving Private Ryan, Mission Impossible Fallout, and Knives Out. Both Mission Impossible and Knives Out fail in the Asus drive while Saving Private Ryan worked. The LG drive does not have any issues with any of the 4K discs. Thinking it might be a firmware issues, I downgraded the Asus from 3.10 back to 3.01 but still experiencing the same issues.

Maybe I'll uninstall and try 1.15.1 again to see if they rip properly.

Thanks,
Eric

[monkeymindboy]

I appear to have a similar issue since upgrading to 1.15.2. I have two UHD friendly drives in my PC, Asus BW-16D1HT and an LG WH16NS40 and now the Asus drive will not read certain 4K discs. For example, I was re-ripping several discs with 1.15.2, Saving Private Ryan, Mission Impossible Fallout, and Knives Out. Both Mission Impossible and Knives Out fail in the Asus drive while Saving Private Ryan worked. The LG drive does not have any issues with any of the 4K discs. Thinking it might be a firmware issues, I downgraded the Asus from 3.10 back to 3.01 but still experiencing the same issues.

Maybe I'll uninstall and try 1.15.1 again to see if they rip properly.

Thanks,
Eric

After reading through the forums I saw a post by @Fearless Leader who crossed flashed the Asus drive with the WH16NS60 MK firmware and it solved the drive error problems. I just ripped Knives Out in the Asus drive and I was getting over 46M/s read rate at times and the file completed in about 30 minutes. I am running Mission Impossible-Fallout now and so far no errors. Eight minutes in and approaching 10x 43M/s read rate.

Update ** Mission Impossible-Fallout just failed at 14 minutes in after almost hitting 11x speed. It could be a speed issue, I'll reset the drive so UHD discs run at normal speeds and I'll clean the disc again and retry.

Update 2 ** Success - after removing all speed control settings for the drive in the registry that I had set before, we have a successful rip of Mission-Impossible Fallout. Max speeds around 8x 34M/s and completed in 1 hour.

[SamuriHL]

I have my bw-16d1ht flashed with ns60 1.00 firmware right now. For speed control on all my NS60 drives, after testing the crap out of it with re-ripping all my dolby vision discs, I came to the conclusion that for me, the best setting is:

0=99;U3=0

I had the most success with that while still retaining fast speeds for non triple layer UHD's.

[monkeymindboy]

I'll give that a try. Thank you.

[Navvie]

On the original 3.01 firmware, 1.15.2 kept giving me errors on discs or telling me tht no disc was inserted.

I flashed to NS60 1.00 firmware, rebooted... no disc.

Flashed to 3.10MK and everything seems to work. Ripped a few UHDs and Blu-Rays. Got an old Blu-Ray backing up now and it reach 10.4x speed. Can't complain.

[monkeymindboy]

I have my bw-16d1ht flashed with ns60 1.00 firmware right now. For speed control on all my NS60 drives, after testing the crap out of it with re-ripping all my dolby vision discs, I came to the conclusion that for me, the best setting is:

0=99;U3=0

I had the most success with that while still retaining fast speeds for non triple layer UHD's.

Any particular reason to stay on ns60 1.00?

[SamuriHL]

There's no particular reason not to. It's an unmodified original firmware that works for everything I need it to work for. Nothing was added to 1.01 or 1.02 or especially 1.03 that benefits me in any way. Newer is NOT better in the ODD firmware world.

[monkeymindboy]

Thank you.