FFT3D crashes - Debug ?

[Dorc]

I got a problem using FFT3D:
VirtualDub 1.6.11 (stable)/ .13 (unstable) crashes when encoding via the following (simple) script to Xvid in the 1stpass

LoadPlugin("C:\AVSplugins\fft3dfilter185\fft3dfilter.dll")
LoadPlugin("C:\AVSplugins\ColorMatrix\Release\ColorMatrix.dll")
Import("C:\AVSplugins\mvbob\mvbob.avs")

mpeg2source("1.d2v",cpu=6,info=3)
ColorMatrix(hints=true)
mvbob().SelectOdd()
fft3dfilter(sigma=3)
Lanczos4Resize(512,384,16,3,694,570)

the .d2v is from a DVB Sorce (DVD compliant VOB Files)

there were no error reports in the Errorlog, VD just vanished
Maybe it is a memory problem (1GB phys. RAM, 900MB-1.2GB occupied during conversion) ?

I tried to narrow down the frames involved but so far no real success (XViD 1st pass log stop at different frame numbers)
Splitting the process for now is difficult (uncomp. file will be >50gb)

Is there a way to print Debug messages with FFT3D ? (I found nothing in the documentation.)

PS: I cant use FFT3DGPU because the computer is more usable with FFT3D than with FFT3DGPU (3ghz P4 with GF5200 card) - using the GPU version will overuse CPU making mousemovements jerky - encoding speed is 1fps (120k frames)

[AI]

Possible problems:

0) fftw3.dll (version?)
1) memory (timings)
2) overclock CPU/bridges/memory
3) overheat CPU/north bridge (what about bridge cooler?)
4) power supply

mvbob().SelectOdd()
fft3dfilter(sigma=3)

PS Possible better use SelectOdd after FFT3D...

[Dorc]

Possible problems:

0) fftw3.dll (version?)
1) memory (timings)
2) overclock CPU/bridges/memory
3) overheat CPU/north bridge (what about bridge cooler?)
4) power supply

PS Possible better use SelectOdd after FFT3D...

0) fft3w version was 3.0 and now i am trying with 3.1
1) memory timing is standard
2) no overclocking
3+4) i didnt change much at the internal setup/configuration and previously Boinc/Seti@Home worked flawlessly for several days (computer is running 24/7 atm)

well the source is real 50i Material and the processing time will further increase (until the bug occur) so for now each processing run is wasted (3x crash after approx 16h / 50000 frames)

[AI]

AAAAaaaaaaaaaaaaaaaaaaaaaaaaaaaaa (eureka!)

You use old version mvtools at mvbob?!!!
change mvtools.dll from http://bag.hotmail.ru/mvtools/MVTools-v1.0.3.zip

PS Excuse my bad English

[Dorc]

I changed the .dll and now it looks good: 60000/110000 frames processed (crash was at ~50000 frames))

still 16h to complete the 1st pass