www.makemkv.com

Hi, trying to rip Roger Waters in the Flesh DVD and keep getting a "fatal error"
This is the debug text:
Debug log started at Tue Sep 04 21:09:12 2012 , written by MakeMKV v1.7.7 win(x86-release)
Using 524544KB for read cache.
001005:0000 MakeMKV v1.7.7 win(x86-release) started
001004:0000 Debug logging enabled, log will be saved as C:\Documents and

Settings\User/MakeMKV_log.txt
003007:0000 Using direct disc access mode
003024:1000 Complex

multiplex encountered - 28 cells and 18296 VOBUs have to be scanned. This may take some

time, please be patient - it can't be avoided.
003028:0000 Title #0 was added (28 cell(s),

2:32:20)
003024:1000 Complex multiplex encountered - 2 cells and 2199 VOBUs have to be

scanned. This may take some time, please be patient - it can't be avoided.
003028:0000 Title

#1 was added (2 cell(s), 0:18:19)
003025:0000 Title #2 has length of 10 seconds which is

less than minimum title length of 120 seconds and was therefore skipped

Any suggestions??
I have tried on 2 different computers, so I don't think it the drive and the dvd plays fine in my dvd player...

Thanks

May I ask you to do a lengthy (but unfortunately necessary) step? Please submit a crash dump per http://www.makemkv.com/onlinehelp/dump.html

I have the same problem as the original poster. MakeMKV crashes and freezes while opening disc and states: "Fatal error occurred, program will now exit." This is happening with version 1.7.7 win(x64).

Not sure if the original poster followed your instructions to send dump file. If not, here is a link to download the dump file:

http://www.sendspace.com/file/u4cacz

Let me know if you need anything else.

Thanks.

I get this same problem. Has this ever been fixed?

Well, there have been well over a dozen versions out since this thread was last active, so, the EXACT issue of this topic has probably been resolved.

However, it is still possible to have OTHER issues that cause fatal errors, and knowing some specifics about YOUR situation would be helpful...

Turn on debug logging if you have not already done so, and try recreating the error. Then post your log in a NEW topic, describing the process that triggered the error.