Megui \ xvid encraw Error

[wickedrami]

Hello folks.. Getting an error in megui upon the completion of the second pass.. As soon as the process windows strucks 100% on the 2nd pass, it disappears.. Normally one would expect the encoding to be finished but na says an error occured.. :(

http://i44.tinypic.com/dpu8vc.jpg

The following is a screenshot of the log.. It looks pretty gay to me.. Since it's got no details regarding the error..

http://i39.tinypic.com/34xjigi.jpg

Let the experts have a look..

Nd yh I've searched before creating the thread.. Nobodys got a similiar problem.. :sad:

HALP! please :)

[wickedrami]

This is what the Xvid Config looks like.. If it helps.. :(

http://i40.tinypic.com/m09oi.jpg

[ankurs]

seems xvid's been acting wierd lately for quiet a lot off people .. :(

[Sharktooth]

since ankurs found a solution for his problems, id suggest to give try what he did: http://forum.doom9.org/showthread.php?p=1240603#post1240603

[wickedrami]

I don't have symantec installed.. Nyone interesting in having a look?
It doesn't stop at 16mb all the time.. Sometimes @ 200-300mbish.. Never completed the second pass..
And the log produced by the error is vague..

I'll give in the RDC.. Nyhelp is really appreciated..

[Sharktooth]

the log is empty since probably xvid crashed silently.
check your hardware with burn-in tests.

[squid_80]

Shouldn't there at least be some log from the standard error stream? I don't know how it could run for 2 minutes without even giving the xvid [info]: messages.

[Sharktooth]

megui prints the stderr on the log but from what the user posted, there is no output.

[squid_80]

Then the only thing I can think of is maybe there's an avisynth plugin screwing with stdout/stderr... Don't know why it would only happen in the second pass though.

[wickedrami]

the log is empty since probably xvid crashed silently.
check your hardware with burn-in tests.

Burn-in tests?
Elaborate please newbie here..
The CMD test from Ankurs thread is positive in my case..
Talking about this one: http://forum.doom9.org/showpost.php?p=1224540&postcount=38

Then the only thing I can think of is maybe there's an avisynth plugin screwing with stdout/stderr... Don't know why it would only happen in the second pass though.

stdout\stderr? Newb here.. Sowwie

[Sharktooth]

burn-in tests: memtest86+ for testing your system ram. Prime95 for testing your CPU under stress.... etc.