Ntdll.dll crash on x264 in MeGUI...

[MechaVizard]

Hi, i just changed mi HDD to a new one. Then installed Win 7 32 bits. When i encode anything with megui-xvid4psp-vdm etc, i get the error of crash from windows:

Problem signature:
Problem Event Name: APPCRASH
Application Name: x264.exe
Application Version: 0.0.0.0
Application Timestamp: 4d2b7e9a
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7600.16385
Fault Module Timestamp: 4a5bdadb
Exception Code: c0000005
Exception Offset: 00051f70
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 2058
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Got CCCP to decode and use MeGUI to encode videos, usually mp4 (h264+AAC).
But i do not know what to do?!!
I read in some other post here that the problem is the intel RST driver, but that is for 64 bits and x264, that will solve my problem too?!

[roozhou]

Use x264.exe to encode your video directly without MeGUI. If there is no more crash, this should be a crash in avisynth.

[MechaVizard]

Use x264.exe to encode your video directly without MeGUI. If there is no more crash, this should be a crash in avisynth.
Ok, i will try CLI with x264.

[LoRd_MuldeR]

That the crash happens in "ntdll.dll" doesn't mean much. NTDLL is the "native API" of the Windows operating system. A crash in that module doesn't mean that the cause of the crash is in the same module. Most likely the crash is caused somewhere else! The crash might be caused by x264 itself, but it might be caused by Avisynth or one of the Avisyth plug-ins just as well. And, if you use DirectShowSouce(), it might also be caused by one of the DirectShow filters. The crash might even be the result of an out-of-memory error. So, as roozhou suggested, try to get rid of Avisynth and see what happens. Alternatively you can also try to use a different source filter in your Avisynth script, e.g. FFVideoSource() rather than DirectShowSource(). If nothing else helps, load up your debugger and make a stacktrace...

[MechaVizard]

That the crash happens in "ntdll.dll" doesn't mean much. NTDLL is the "native API" of the Windows operating system. A crash in that module doesn't mean that the cause of the crash is in the same module. Most likely the crash is caused somewhere else! The crash might be caused by x264 itself, but it might be caused by Avisynth or one of the Avisyth plug-ins just as well. And, if you use DirectShowSouce(), it might also be caused by one of the DirectShow filters. The crash might even be the result of an out-of-memory error. So, as roozhou suggested, try to get rid of Avisynth and see what happens. Alternatively you can also try to use a different source filter in your Avisynth script, e.g. FFVideoSource() rather than DirectShowSource(). If nothing else helps, load up your debugger and make a stacktrace...

Well, i almost always use DSS2() to call the video. I'm a fansuber, and the thing is that to add the new karaoke from a serie, the karaoke maker told me that i should need the new VSFilter /VSFilterMod.dll and call the ass with TextSubMod(). Is there possible that this filter is causing the crashes?!!
I never used this filter before, and this time i was trying to encode with this, i have a lot of crashes with ntdll.dll and Stackhash.804...
I made a encode with x264.exe in CLI and the encode went well.
Also i have issues with the audio, some times the audio came with nothing after the endode or if not, the audio plays faster than normal (x3). Right now, i'm using CCCP with haali(included un CCCP) as decoders.
Well, i hope someone can help me.
And thank for the previous coments.

[LoRd_MuldeR]

Well, i almost always use DSS2() to call the video.

So the problem might very well be in one of the DirectShow filters that are used on your system. As there are a zillions of possibilities how the DirectShow graph might look on an individual system, it is hard to guess which filter in particular causes the problem. For the purpose of isolating the problem, I can only recommend to get rid of DirectShowSource() as well as DSS2()!

I'm a fansuber, and the thing is that to add the new karaoke from a serie, the karaoke maker told me that i should need the new VSFilter /VSFilterMod.dll and call the ass with TextSubMod(). Is there possible that this filter is causing the crashes?!!

Yes, of course. Any Avsynth filter/plug-in that is loaded in the process might cause the crash. Try to kick out that particular plug-in/filter and see what happens...

I never used this filter before, and this time i was trying to encode with this, i have a lot of crashes with ntdll.dll and Stackhash.804...

Again: The fact that it finally crashed in 'ntdll.dll' does not reveal anything about the actual cause of the crash. A stacktrace might...

I made a encode with x264.exe in CLI and the encode went well.

This doesn't say much without your full command-line.

However if using x264 with "native" FFMS2 input instead of Avisynth/DSS2 input fixed the crash, then you know that either Avisynth or DirectShow is to blame.

(Still this might also be an out-of-memory problem, as Avisynth tends to occupy a lot if memory. Watch your "private bytes" in ProcessExplorer!)