v1.9.5 crashes on startup: "Fatal error occured, program wil

Everything related to MakeMKV
Post Reply
Message
Author
blurb
Posts: 2
Joined: Thu Aug 20, 2015 5:13 pm

v1.9.5 crashes on startup: "Fatal error occured, program wil

#1 Post by blurb » Fri Aug 21, 2015 12:30 pm

Since installing v1.9.5 when I attempt to start Make MKV it initially fires up but displays the 'wheel of death' cursor and then after half a minute says it says unresponsive in the title bar and finally displays a dialog box saying: "Fatal error occured, program will now exit".

The previous version of Make MKV I had was v1.9.2 which ran perfectly. I'm running Windows 7, 64 bit.

I have tried uninstalling and doing a clean install of v1.9.5 but it still fails to start, in exactly the same way.


The Windows Application Log lists an error containing the following information:
----------------------------------------------
Faulting application name: makemkvcon64.exe, version: 0.0.0.0, time stamp: 0x55b55755
Faulting module name: ntdll.dll, version: 6.1.7601.18939, time stamp: 0x55b02e88
Exception code: 0xc0000005
Fault offset: 0x000000000004df08
Faulting process id: 0x185c
Faulting application start time: 0x01d0dbf04cc229be
Faulting application path: C:\Program Files (x86)\MakeMKV\makemkvcon64.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 8c593655-47e3-11e5-8347-0009dd648f61
----------------------------------------------

Some help would be greatly appreciated, thanks.

Tapioka
Posts: 26
Joined: Fri Jun 26, 2015 6:32 pm

Re: v1.9.5 crashes on startup: "Fatal error occured, program

#2 Post by Tapioka » Fri Aug 21, 2015 1:16 pm

Maybe check out this thread, people there had a problem with 1.9.5 too (albeit with Windows 10). Turns out it was related to BitDefender.

blurb
Posts: 2
Joined: Thu Aug 20, 2015 5:13 pm

Re: v1.9.5 crashes on startup: "Fatal error occured, program

#3 Post by blurb » Wed Aug 26, 2015 8:59 am

Many thanks for your help Tapioka. I had searched through the forum but hadn't found the thread that you referred to. Yes, it was BitDefender and the advice in that thread worked a treat :D

Post Reply