Megui: Process exits with error code: -1073741819

[leocgomes]

I'm not being able to encode a video using Megui. The process is started but ends in 15 seconds.

The log says:

--[Information] [14/04/2011 22:41:43] Job commandline: "D:\megui\tools\x264\x264.exe" --tune animation --crf 20 --b-adapt 0 --ref 16 --qpmin 10 --qpmax 51 --aq-mode 0 --me esa --partitions all --psnr --ssim --sar 1:1 --output "I:\Gokigenyou\Kannazuki_no_Miko\[Gokigenyou]Kannazuki_No_Miko_10.mp4" "I:\Gokigenyou\Kannazuki_no_Miko\[Gokigenyou]Kannazuki_No_Miko_10.avs"
--[Information] [14/04/2011 22:41:43] Encoding started
--[Error] [14/04/2011 22:41:55] Process exits with error code: -1073741819
--[Information] [14/04/2011 22:41:55] Standard output stream
--[Information] [14/04/2011 22:41:55] Standard error stream
--[Information] [14/04/2011 22:41:55] Job completed

If anyone could help...

[GG-Xtreme]

I'm having the same issue. I queued up 7 jobs, for source files of identical format. The first 4 completed successfully, but every job after that is erroring out with that error. Latest MeGUI and components (development update server).

Edit: After much searching, it seems that this issue is caused by memory (running out? conflict with other threads?). But I have 6GB of memory and nothing else is running =/ This error seems to happen entirely at random, because I got it for 3 straight jobs and then the rest started completing normally again.

[Rat Killer]

I am having the same issue. If you click the link in the error message, it shows that the error is actually related to avisynth.dll

No idea what is causing it or how to fix.

[LoRd_MuldeR]

If an application exists with such a "strange" exit code, this usually indicated the application just crashed.

[Bluedan]

I had this error message a couple times. AFAIR it was always the x64 version. That's why I need a seperate installation of megui x86, because this way I was able to do the indexing and work on with the created index file via the x64 version of megui.

I have no clue, what is causing this error.
I updated ffmpeg (x64 static) manually, which didn't solve it at all.

Posted as well on zeranoes board.

EDIT: I forgot to add, that everytime this error occurs I was about to do indexing of video files via ffmpeg.

[IanB]

-1073741819 => 0xC0000005 => "Access Violation"

I wish the Megui crew would start printing the error codes in the same format as everybody documents them.

For bonus points print the text associated with the error code so users do not have to lookup hex error codes.

Scratch that, given Megui is supposed to be for the average user, no bonus points, make that a mandatory requirement.

[Zathor]

Thanks for your feedback. Do you have a list of all possible error codes and the corresponding error text? But I assume that cannot be used in general as some applications are using custom exit codes in case of an error.
EDIT: As I understand you do not like MeGUI at all. That's of course ok - but I would like to know why so that MeGUI can be enhanced.

[Groucho2004]

Do you have a list of all possible error codes and the corresponding error text?

Here:
http://msdn.microsoft.com/en-us/library/cc704588%28v=PROT.10%29.aspx

[IanB]

Thanks for your feedback. Do you have a list of all possible error codes and the corresponding error text? But I assume that cannot be used in general as some applications are using custom exit codes in case of an error.There is a whole chasm of M$ code to do with error messages, and yes I accept it is overwhelming. Googling with the "site:microsoft.com" modifier can help zero in on the resources needed. Groucho2004 just pointed to a good one.

EDIT: As I understand you do not like MeGUI at all. That's of course ok - but I would like to know why so that MeGUI can be enhanced.Sorry if my dislike for signed decimal error numbers came across as dislike for MeGUI. I don't remember ever stating an opinion, I wouldn't say I do not like it, I just don't use it, so far I have not needed to. I guess my opinion is I don't have an opinion. My experience so far is from supporting users that use it and get stuck. Printing the error status in a normal form and interpreting the error status to a text message might allow the users to help themselves a bit more.