ntdll.dll error with x264 64bit? in MeGUI

[Hiritsuki]

How can I do? :confused:

http://imagewtf.com/11280.png/images/11280.png

[zmaster]

You use a filter TIVTC? It seems I've been getting this error when using "...tdecimate(hybrid=1)". But that was before began the process of encoding...
p/s: Try another x264.

[Hiritsuki]

my script is

LoadPlugin("C:\Program Files (x86)\MeGUI\tools\dgavcindex\DGAVCDecode.dll")
AVCSource("D:\BDMV\AMAGAMISS\RAW\BDISO Vol.1\BDMV\STREAM\00000.dga")
DupMC(log="01.txt")
#DeDup(threshold=0.3, maxcopies=20, maxdrops=20, log="01.txt", times="01.times.txt")
warpsharp()

[zmaster]

I do not know how to help.
Try another x264, try to find the root of the problem: try to encode the scriptLoadPlugin("C:\Program Files (x86)\MeGUI\tools\dgavcindex\DGAVCDecode.dll")
AVCSource("D:\BDMV\AMAGAMISS\RAW\BDISO Vol.1\BDMV\STREAM\00000.dga")Then append DupMC(log = "01.txt") and so on, until you get an error message. Then you can find another version of filter...
That's all I can say. :-(

[Dark Shikari]

Your crashes are most likely in your input script. Try using a different input method, or dropping filters from your Avisynth script to isolate which command is crashing.

[Hiritsuki]

Well, I'll test more possibility.
Maybe MeGUI app's crash or not.
That I'd oc test one day.

[Hiritsuki]

I just found my memory is broken one.
And found x264 64bit 1804 is will be error in MeGUI x264 Placebo mode, 32bit not.

[LoRd_MuldeR]

I just found my memory is broken one.
And found x264 64bit 1804 is will be error in MeGUI x264 Placebo mode, 32bit not.

If your memory is broken, then you'll get completely random crashes. Even if a specific build/configuartion seems to work now, it may crash at a later time :eek:

Only thing that helps here: Try to identify the faulty memory module(s) with memtest86+ and replace them!

(If you are using some of those "overclocker" memory modules, it may also help to reset the memory timings to more conservative values)

[Hiritsuki]

No. I'd remove that's broken one, now memtest and Linx or HyperPI 32M 16threads is "ALL Right".
But x264 64bit 1804 is crash that I don't know why x264 32bit 1804 is no Problem in Placebo mode.

[LoRd_MuldeR]

You should run Memtest86+ for at least 24h to be (almost) sure the memory is okay.

Moreover you should try to get rid of Avisynth input in order to find out whether the crash originates from Avisynth (or one of its plugins) or from x264 itself.

Note that you can deliver the input to x264 from another process via pipe, so Avisynth can run in its own sepaerate process...

[Hiritsuki]

I'd run 5 LinX 12threads 1GB do memory in once time with no error complete yesterday.

[Hiritsuki]

I changed to old ver. 1766 it's work with no problem.

[Hiritsuki]

I found the problem is.
That's Intel RST driver's problem.
10.0.0.1046 change to 10.1.0.1008 and run x264 with no error