www.makemkv.com

It scans the disc as normal and finds the five tracks that are on there. However, it keeps on scanning for about another 40 minutes and eventually bombs out and takes me back to the main menu.

Log file below:

001003:0020 DEBUG: Code 2 at h>],P[s5:P^nIwLz:213137827
001003:0020 DEBUG: Code 2 at h>],P[s5:P^nIwLz:213137827
001003:0020 DEBUG: Code 2 at h>],P[s5:P^nIwLz:213137827
001003:0020 DEBUG: Code 2 at h>],P[s5:P^nIwLz:213137827
001003:0020 DEBUG: Code 2 at h>],P[s5:P^nIwLz:213137827
001003:0020 DEBUG: Code 101019395 at OL&Xb3FS+b&d<qn>9j:213132100
001003:0020 DEBUG: Code 101019395 at OL&Xb3FS+b&d<qn>9j:29393930
002003:0000 Error 'Scsi error - ILLEGAL REQUEST:READ OF SCRAMBLED SECTOR WITHOUT AUTHENTICATION' occurred while reading 'BD-ROM ATAPI iHES112 3 ML02' at offset '1048576'
001003:0020 DEBUG: Code 134219780 at }JU5Ga]}4/-w tNP`:121261957
001003:0020 DEBUG: Code 0 at }JU5Ga]}4/-w tNP`:121263774
003031:0000 Drive BD-ROM ATAPI iHES112 3 ML02 has RPC protection that can not be bypassed. Change drive region or update drive firmware from http://tdb.rpc1.org. Errors likely to follow.
003007:0000 Using direct disc access mode
003002:0000 Calculated BUP offset for VTS #1 does not match one in IFO header.
003002:0000 Calculated BUP offset for VTS #2 does not match one in IFO header.
003025:0000 Title #1 has length of 19 seconds which is less than minimum title length of 30 seconds and was therefore skipped
003028:0000 Title #2 was added (22 cell(s), 1:48:08)
003028:0000 Title #3 was added (4 cell(s), 0:20:45)
003028:0000 Title #4 was added (5 cell(s), 0:24:38)
003028:0000 Title #5 was added (4 cell(s), 0:19:19)
003028:0000 Title #6 was added (5 cell(s), 0:22:47)
003028:0000 Title #7 was added (4 cell(s), 0:20:39)
001003:0020 DEBUG: Code 2 at S\:fk^YQu> ,|:213132054
001003:0020 DEBUG: Code 0 at 8Dj\BhE5O.w'2 9W`F:29402900
001003:0020 DEBUG: Code 0 at 8Dj\BhE5O.w'2 9W`F:121275067
001003:0020 DEBUG: Code 1 at <Hk5v#hBwA$=_":M:121262532
001003:0020 DEBUG: Code 0 at HK%Pcog`}(?l}R>:213138678
001003:0020 DEBUG: Code 0 at Uqv%qYy!$OG:d0:213133710
001003:0020 DEBUG: Code 0 at 8Dj\BhE5O.w'2 9W`F:29402900
001003:0020 DEBUG: Code 0 at 8Dj\BhE5O.w'2 9W`F:121275067
001003:0020 DEBUG: Code 1 at <Hk5v#hBwA$=_":M:121262532
001003:0020 DEBUG: Code 0 at HK%Pcog`}(?l}R>:213138678
001003:0020 DEBUG: Code 0 at Uqv%qYy!$OG:d0:29397219
001003:0020 DEBUG: Code 0 at 8Dj\BhE5O.w'2 9W`F:29402900
001003:0020 DEBUG: Code 0 at 8Dj\BhE5O.w'2 9W`F:121275067
001003:0020 DEBUG: Code 1 at <Hk5v#hBwA$=_":M:121262532
001003:0020 DEBUG: Code 0 at HK%Pcog`}(?l}R>:213138678
001003:0020 DEBUG: Code 0 at Uqv%qYy!$OG:d0:29397219
001003:0020 DEBUG: Code 0 at 8Dj\BhE5O.w'2 9W`F:29402900
001003:0020 DEBUG: Code 0 at 8Dj\BhE5O.w'2 9W`F:121275067
001003:0020 DEBUG: Code 1 at <Hk5v#hBwA$=_":M:121262532
001003:0020 DEBUG: Code 0 at HK%Pcog`}(?l}R>:213138678
001003:0020 DEBUG: Code 0 at Uqv%qYy!$OG:d0:29397219
001003:0020 DEBUG: Code 0 at 8Dj\BhE5O.w'2 9W`F:29402900
001003:0020 DEBUG: Code 0 at 8Dj\BhE5O.w'2 9W`F:121275067
001003:0020 DEBUG: Code 1 at <Hk5v#hBwA$=_":M:121262532
001003:0020 DEBUG: Code 0 at HK%Pcog`}(?l}R>:213138678
001003:0020 DEBUG: Code 0 at Uqv%qYy!$OG:d0:29397219
001003:0020 DEBUG: Code 0 at 8Dj\BhE5O.w'2 9W`F:29402900
001003:0020 DEBUG: Code 0 at 8Dj\BhE5O.w'2 9W`F:121275067
001003:0020 DEBUG: Code 1 at <Hk5v#hBwA$=_":M:121262532
001003:0020 DEBUG: Code 0 at HK%Pcog`}(?l}R>:213138678
001003:0020 DEBUG: Code 0 at Uqv%qYy!$OG:d0:29397219
005010:0000 Failed to open disc
Application exited at Sat Feb 08 15:46:24 2014

Twowit2woo wrote: 003031:0000 Drive BD-ROM ATAPI iHES112 3 ML02 has RPC protection that can not be bypassed. Change drive region or update drive firmware from http://tdb.rpc1.org. Errors likely to follow.

Just follow the advice - you have to change something - the drive, region or firmware.

mike admin wrote: Just follow the advice - you have to change something - the drive, region or firmware.

Hmm. I'm not so convinced.

I get that message all the time and never had a problem. I'm region 2, as is my drive, as are the discs. I never use discs outside my region and have never changed the region on the drive.

This is an 11 disc boxset. 8 of the 11 work fine but three experience this error. I'm not entirely convinced your suggestion would help - unless you can elaborate further.

Regards,

If it helps, DVD Decrypter did these without any bother

Regards,

I encountered the same problem:

MakeMKV v1.8.9 win(x86-release) started
Using direct disc access mode
Failed to open disc

Then I uninstalled v1.8.9 and used v1.8.8 instead. All worked well and I ripped all DVD.
I re-installed v1.8.9 again and I got the error message again.

I think it is a bug of v1.8.9.

1.89 wasn't out when I reported this, it was happening with 1.88

I also tried 1.87 - same problem

I have just tried 1.89 - same problem.

On the basis that DVD Decrypter can handle these discs it has to be a bug

I have to agree that I believe it is a bug.

Yesterday I was running 1.8.7 and processed a DVD to an MKV file. I then ran it through handbrake to compress and convert to MP4 to use with plex. For some reason this DVD did not maintain the aspect ratio so I decided to run through the process again.

Before processing the DVD for the second time I saw the notice that 1.8.9 was available so I upgraded. Now, the same DVD I just processed an hour earlier says "Failed to open disc" with the following output:

MakeMKV v1.8.9 win(x64-release) started
Debug logging enabled, log will be saved as C:\Users\.../MakeMKV_log.txt
Using direct disc access mode
Title #3 has length of 7 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #4 has length of 17 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Failed to open disc

Since I could not finish I uninstalled the 1.8.9 and re-installed 1.8.7 but now when I start it says "This application version is too old. Please download the latest or enter an registration key". When I click ok it closes...

So now I'm stuck on this DVD. A couple others I tried have worked so far.

Set your system date back to, say, 1/1/14 when you start MakeMKV, then you can enter the updated beta key.