x264 just randomly stops encoding

[frubsen]

Hi all

A new problem recently appeared where my x264 command line encodes all of a sudden will stall. Sometimes in the middle of an encode or sometimes right when it hits 100%. The file is never closed out so it ends up being a botched encode and I have to start over....usually it works on a second go, but for the life of me I can't figure out why it is randomly stalling like this now. I haven't changed anything in my avs script or x264 command line.

my avs scripts are as follows

SetMemoryMax(800)
SetFilterMTMode("QTGMC",2)
avisource("filename.avi")
ConvertToYV12(interlaced=true)
assumebff()
QTGMC(preset = "super fast", EdiThreads=4)
Crop(8, 0, -8, -0)
bicubicresize(640,480)
prefetch(threads=8)
and my x264 command line is
"x264.exe" --crf 17 --preset slow --level 3.1 -o "output.mp4" "input.avs"

Running the latest build of x264, windows 10, avisynth plus 3.5 r3106.

I've tried without the MTMode and prefetch threads.

Nothing shows in windows event logs
any idea on what could be causing this, or where I could go to see some sort of logging which would give me a clue as to what's going on?

Thanks

[Boulder]

Find and remove avstp.dll from any directory on your system. It's the most common culprit when this happens.

[FranceBB]

Find and remove avstp.dll from any directory on your system. It's the most common culprit when this happens.

Totally avstp.dll fault as he's using MVTools.

@frubsen for more information look at the "frozen as ice" issue here: https://github.com/pinterf/mvtools/issues/46

[frubsen]

Ahh thank you! I have renamed that file for now and will give it a go...hopefully this fixes the issue.

From reading through that thread..that dll deals with multi threading within MVtools2? Am I correct in that? Will removing that file have any effects in encoding speed or anything else?

[Boulder]

Avisynth+ should already do all the necessary multithreading by Prefetch.

[frubsen]

Great...thank you again for all your help...removing that file seems to have fixed the issue!