Another Bad BD Drive?

Please post here for issues related to Blu-ray discs
Post Reply
Mondays
Posts: 42
Joined: Wed Apr 20, 2011 5:37 pm

Another Bad BD Drive?

Post by Mondays » Sat Aug 22, 2020 11:31 pm

It seems I go through BD drives every few years. This latest one, an Asus SUS_BW-16D1HT was working great until the last week. I have tried 3 different BDs and Disc won't open and then I need to reboot my computer and remove the disc during start up to get it out. (I had BD players go bad but never had a problem closing MakeMKV and getting the dis out).

After 2 or 3 tries I was able to rip 2 standard DVDs but no luck anymore with BDs. I seem to have so many problems with BD drives I always buy the squaretrade insurance so if needed I can send in for repair or get most of the cost back as a credit on Amazon.

Anyway here is the MakeMKV_Log.txt after trying to rip Hustlers.

Debug log started at Sat Aug 22 23:05:25 2020 , written by MakeMKV v1.15.2 win(x64-release)
Using 262272KB for read cache.
001005:0000 MakeMKV v1.15.2 win(x64-release) started
001004:0000 Debug logging enabled, log will be saved as file://C:\Users\John/MakeMKV_log.txt
SDF v07a: ASUS_BW-16D1HT_3.10_211901041014_KLZK15G5050
SDF v07a: ASUS_BW-16D1HT_3.10_211901041014_KLZK15G5050
001011:0000 Using LibreDrive mode (v06.2 id=0FA242DD4D0B)
002004:0000 Error 'OS error - The I/O device reported an I/O error' occurred while issuing SCSI command AD010..003F000 to device 'SPTI:\Device\CdRom0'
002004:0000 Error 'OS error - The I/O device reported an I/O error' occurred while issuing SCSI command AD0..003F000 to device 'SPTI:\Device\CdRom0'
001003:0020 DEBUG: Code 3221225861 at <n#P\T%TRbfQ<%b::213130559
001003:0020 DEBUG: Code 3221225861 at <n#P\T%TRbfQ<%b::213130559
001003:0020 DEBUG: Code 3221225861 at <n#P\T%TRbfQ<%b::213130559
001003:0020 DEBUG: Code 3221225861 at <n#P\T%TRbfQ<%b::213130559
001003:0020 DEBUG: Code 3221225861 at <n#P\T%TRbfQ<%b::213130559
001003:0020 DEBUG: Code 3221225861 at WeCdm# ?*))&YS;*<2:121263360
001003:0020 DEBUG: Code 3221225861 at WeCdm# ?*))&YS;*<2:121261957
002003:0000 Error 'OS error - The I/O device reported an I/O error' occurred while reading 'BD-RE ASUS BW-16D1HT 3.10' at offset '524288'
001003:0020 DEBUG: Code 3221225861 at <n#P\T%TRbfQ<%b::213130559
001003:0020 DEBUG: Code 3221225861 at <n#P\T%TRbfQ<%b::213130559
001003:0020 DEBUG: Code 3221225861 at <n#P\T%TRbfQ<%b::213130559
001003:0020 DEBUG: Code 3221225861 at <n#P\T%TRbfQ<%b::213130559
001003:0020 DEBUG: Code 3221225861 at <n#P\T%TRbfQ<%b::213130559
001003:0020 DEBUG: Code 3221225861 at WeCdm# ?*))&YS;*<2:121263360
001003:0020 DEBUG: Code 3221225861 at WeCdm# ?*))&YS;*<2:121261957
002003:0000 Error 'OS error - The I/O device reported an I/O error' occurred while reading 'BD-RE ASUS BW-16D1HT 3.10' at offset '1048576'
001003:0020 DEBUG: Code 3221225861 at <n#P\T%TRbfQ<%b::213130559
001003:0020 DEBUG: Code 3221225861 at <n#P\T%TRbfQ<%b::213130559
001003:0020 DEBUG: Code 3221225861 at <n#P\T%TRbfQ<%b::213130559
001003:0020 DEBUG: Code 3221225861 at <n#P\T%TRbfQ<%b::213130559
001003:0020 DEBUG: Code 3221225861 at <n#P\T%TRbfQ<%b::213130559
001003:0020 DEBUG: Code 3221225861 at WeCdm# ?*))&YS;*<2:121263360
001003:0020 DEBUG: Code 3221225861 at WeCdm# ?*))&YS;*<2:121261957
002003:0000 Error 'OS error - The I/O device reported an I/O error' occurred while reading 'BD-RE ASUS BW-16D1HT 3.10' at offset '32768'
001003:0020 DEBUG: Code 0 at uklS2`{:wGm9\#Eo;TD:213129777
005010:0000 Failed to open disc
001003:0020 DEBUG: Code 3221225861 at SnjLlET?7*kAC=V3:121267431
Application exited at Sat Aug 22 23:19:33 2020


Mondays
Posts: 42
Joined: Wed Apr 20, 2011 5:37 pm

Re: Another Bad BD Drive?

Post by Mondays » Sun Aug 23, 2020 3:07 pm

No I haven't I'll move any questions on this there but a quick read tells me a replacement drive will be needed again.

d00zah
Posts: 1586
Joined: Mon Jun 06, 2016 8:23 pm

Re: Another Bad BD Drive?

Post by d00zah » Sun Aug 23, 2020 3:24 pm

Wrong take-away, I THINK...
At least one report of cross-flashing to WH16NS60 firmware seeming to fix things?

viewtopic.php?f=16&t=22676#p93899
viewtopic.php?f=16&t=22676#p93915

Or... try downgrading MakeMKV to v1.5.1 (link to old versions in my sig).

Mondays
Posts: 42
Joined: Wed Apr 20, 2011 5:37 pm

Re: Another Bad BD Drive?

Post by Mondays » Mon Aug 24, 2020 4:43 pm

I did the path of least resistance and downgraded MakeMKV to v1.5.1 and I was able to just rip a BD. Yea!

If I start to run into disks MakeMKV does not work on I will try flashing my ASUS with the LG firmware viewtopic.php?f=16&t=19928

Post Reply