Fatal Error

[arussell87]

Hi Al

If I try reading a Blu ray using the program it stops after hitting yes to the evaluation period pop up and displays fatal error will now exit, it will also give me this error when selecting the index.bdmv in the root of a file already saved to my computer, I am not sure on where error logs are stored, If I can be pointed in the right direction I will upload one, Many thanks

[Woodstock]

The FAQ in my signature explains where the error logs will be stored, once debugging is turned on. And, when you start MakeMKV, it will say something like this in the log window:

MakeMKV v1.9.4 win(x64-release) started
Debug logging enabled, log will be saved as C:\Users\nnnnnn/MakeMKV_log.txt

[arussell87]

Log will not attatch so I have pasted the contents, Thanks Woodstock

Debug log started at Sun Jul 19 09:31:30 2015 , written by MakeMKV v1.9.4 win(x64-release)
Using 524544KB for read cache.
001005:0000 MakeMKV v1.9.4 win(x64-release) started
001004:0000 Debug logging enabled, log will be saved as C:\Users\Log\MakeMKV_log.txt
003007:0000 Using direct disc access mode
005053:0308 This functionality is shareware. You may evaluate it for 30 days after what you would need to purchase an activation key if you like the functionality. Do you want to start evaluation period now?
005050:0000 Evaluation version, 30 day(s) out of 30 remaining

[arussell87]

[Woodstock]

That's very strange - it has been a while since I've seen something like that pop up without a log entry first.

Can you check the Event Viewer, to see if Windows recorded anything about the crash?

[arussell87]

I have managed to open event viewer but I have absolutely no idea on how I would use it?

The log reports nothing which is odd, it just crashes and reports no issues.

[arussell87]

Details
Product: Windows Operating System
ID: 1000
Source: Application Error
Version: 5.2
Symbolic Name: ER_USERCRASH_LOG
Message: Faulting application %1, version %2, faulting module %3, version %4, fault address 0x%5.

Explanation
The indicated program stopped unexpectedly. The message contains details on which program and module stopped. A matching event with Event ID 1001 might also appear in the event log. This matching event displays information about the specific error that occurred.


User Action
If an error report was generated for this error, you might be able to obtain more information about the error by sending the report to Microsoft for analysis.

What to expect

Microsoft actively analyzes all error reports and prioritizes them based on the number of customers affected by the error signature contained in the report. When a report is submitted, Microsoft will try to determine the cause of the error, categorize it according to the type of issue encountered, and send you relevant information when such information is available. However, because error reports do not always contain enough information to positively identify the source of the issue, Microsoft may need to collect a number of similar reports from other customers before a pattern is discovered. Although Microsoft might not be able to provide a solution for your particular error at this time, all information submitted is used to further improve the quality and reliability of our products.

[Woodstock]

What version of Windows are you running? Are you running MakeMKV as a normal user, or using "run as Administrator"? The more clues we have, the better chance of figuring out what is causing this.

[arussell87]

Hi, Im running Windows 10, It worked fine last week, I changed my PC case and that's the last time it worked, I'm running an external Blu Ray drive via USB and this problem occurs also when selected an already ripped disc so I know its not the drive. i do not see me changing the case causing the issue I think its just coincidental.

I always run it as administrator and I have also tried compatibility mode with Win 8 and 7.

Hope this helps.

[arussell87]

Just tried without compatibility mode and something new has happened.

Debug log started at Sun Jul 19 20:32:02 2015 , written by MakeMKV v1.9.4 win(x64-release)
Using 524544KB for read cache.
001005:0000 MakeMKV v1.9.4 win(x64-release) started
001004:0000 Debug logging enabled, log will be saved as C:\Users\Aaron/MakeMKV_log.txt
003007:0000 Using direct disc access mode
005053:0308 This functionality is shareware. You may evaluate it for 30 days after what you would need to purchase an activation key if you like the functionality. Do you want to start evaluation period now?
005050:0000 Evaluation version, 30 day(s) out of 30 remaining
DAFD=PAAAADAAAAEABDQkEHwECAQ==
002004:0000 Error 'Scsi error - ILLEGAL REQUEST:COPY PROTECTION KEY EXCHANGE FAILURE - AUTHENTICATION FAILURE' occurred while issuing SCSI command A30..00200740100720..01E4073923798C4839BEA791EE9D96EEC8A to device 'SPTI:\Device\CdRom0'
001003:0020 DEBUG: Code 0 at s\7nb|$E!JnBP*ZTu:213130766
001003:0020 DEBUG: Code 0 at xP*j#q|E5A.(3E};FO:29395195
001003:0020 DEBUG: Code 0 at xP*j#q|E5A.(3E};FO:121262647
002004:0000 Error 'Scsi error - ILLEGAL REQUEST:COPY PROTECTION KEY EXCHANGE FAILURE - AUTHENTICATION FAILURE' occurred while issuing SCSI command A30..00200740100720..0550C119FB7379C5A56C8D8D129C7DD5194 to device 'SPTI:\Device\CdRom0'
001003:0020 DEBUG: Code 0 at s\7nb|$E!JnBP*ZTu:213130766
001003:0020 DEBUG: Code 0 at xP*j#q|E5A.(3E};FO:29395195
001003:0020 DEBUG: Code 1 at xP*j#q|E5A.(3E};FO:121262647
002004:0000 Error 'Scsi error - ILLEGAL REQUEST:COPY PROTECTION KEY EXCHANGE FAILURE - AUTHENTICATION FAILURE' occurred while issuing SCSI command A30..00200740100720..02006EBDEAA658358EFA8BB4A20A9032825 to device 'SPTI:\Device\CdRom0'
001003:0020 DEBUG: Code 0 at s\7nb|$E!JnBP*ZTu:213130766
001003:0020 DEBUG: Code 0 at xP*j#q|E5A.(3E};FO:29395195
001003:0020 DEBUG: Code 2 at xP*j#q|E5A.(3E};FO:121262647
002004:0000 Error 'Scsi error - ILLEGAL REQUEST:COPY PROTECTION KEY EXCHANGE FAILURE - AUTHENTICATION FAILURE' occurred while issuing SCSI command A30..00200740100720..0ADDABAED1EF20C62D81E91AEF394532BF2 to device 'SPTI:\Device\CdRom0'
001003:0020 DEBUG: Code 0 at s\7nb|$E!JnBP*ZTu:213130766
001003:0020 DEBUG: Code 0 at xP*j#q|E5A.(3E};FO:29395195
001003:0020 DEBUG: Code 3 at xP*j#q|E5A.(3E};FO:121262647
002004:0000 Error 'Scsi error - ILLEGAL REQUEST:COPY PROTECTION KEY EXCHANGE FAILURE - AUTHENTICATION FAILURE' occurred while issuing SCSI command A30..00200740100720..06BAE2106298C04C7C4C2D36BCDBB1E9D84 to device 'SPTI:\Device\CdRom0'
001003:0020 DEBUG: Code 0 at s\7nb|$E!JnBP*ZTu:213130766
001003:0020 DEBUG: Code 0 at xP*j#q|E5A.(3E};FO:29395195
001003:0020 DEBUG: Code 4 at xP*j#q|E5A.(3E};FO:121262647
DCE=NerQ3CaoiNGbn+3o21ebsEiKmw5umm82H1eKbiS8bH+V7iekmCNvzrbAFTcUjQ05Bz/6cupFq44+OVD1+JKJAvgP9N8EdI3SE5AQ9k8rpd493hqgKvuTZ16InaxT9DuFQE/3WcX54Lda6us736Lk4cXuDXCQnzs04Q==
DCE=dNBTIUTmCsDFlZTx+z4FkhOSvYFYk3Q0C3P1gcLIc2KmQ3ULaOIStMbJbDUo+XXDOG0YYCI1+uRMTSkE4KEHnI7E43Dkcubs3wgtQW8aqRq8LJWH4zXQiU//vAaO5Y3J874uryLTHrHS/FvPZHdUhLrbAlVZCGJGoA==

[Woodstock]

Ah, this gets us back into the issue that started about 2 or 3 months ago, when Microsoft released a beta of 10 that breaks MakeMKV. It seems to be blocking access to the hardware, and SOMETIMES running as administrator works, but not always. You can read through the other threads on Windows 10 for more information, but there isn't a lot to be had.

One work around that has reportedly worked is to install Windows 7 in a virtual machine on the Win10 machine. Whatever Win10 added that breaks MakeMKV doesn't seem to affect the virtual machine.

Until Win10 is actually released, I don't know if Mike will be doing much to fix it, because any fix done for the beta might not work in the released version. But only Mike can answer that question!

[arussell87]

Hi Woodstock, Thanks for all your help, I will do that until Windows 10 is supported. Thanks again.