PDA

View Full Version : Access Violation (CAviStreamSynth memory) error


n2k3
19th April 2009, 01:55
-to mods: delete the older post-

Heyho everybody,

I've been camping with an annoying problem for a while. The infamous Access Violation memory error in AviSynth. I know this can be caused by a lot of things but I don't know where to look anymore :(

raw: [some licensed anime]
d2v'ed with DGIndex v1.5.4 (http://neuron2.net/dgmpgdec/dgmpgdec154.zip) with default settings except the iDCT_Algorithm = 5 (IEEE-1180 Reference)

import the d2v

MPEG2Source("C:\Encoding\[m2]ts\nameoflicensedanime.d2v", cpu=0)

using one of these filters will make the memory error appear 'in no time' at random frames

LSFmod(ss_x=2.0, ss_y=2.0, strength=80, soft=-2) # v1.7
MCTemporalDenoise(settings="high", GPU=true, edgeclean=true, flat=true, ncpu=2) # v1.2.02
AnimeIVTC(mode=1,aa=4,omode=1,MT=true,overlap=6,pel=4,search=3) # v1.06.1
with or without default settings, it really doesn't matter that much, I've had errors on all filters.

On the avisynth wiki it says that the SetMemoryMax() option could help, no luck for me, with or without it at variable values in MB; 512 (default), 1024, 1536, 2048 leads to the same result.

I've 4GB of memory tested with Memtest86+ (http://www.memtest.org/) a few months ago for 8+ hours with no errors.

Specific info:
Corsair TWIN2X2048-6400C4 (x2) DDR2-800MHz (4-4-4-12 @ 333MHz) to be exact, meaning 4 DIMMs of 1GB each totaling in 4GB, and yes you're right they're running on 333MHz instead of 400MHz to be able to boot at all.
I run Windows XP x64 with SP2 with Avisynth v2.58 (http://sourceforge.net/project/showfiles.php?group_id=57023) (version() picture (http://i41.tinypic.com/kbewci.jpg)).
I use AvsP v2.0.2 (http://avisynth.org/qwerpoi/Download.html) as avs editor, displaying the avs in either the AvsP internal player, or Media Player Classic - Homecinema v1.2.908.0 (http://sourceforge.net/project/showfiles.php?group_id=170561) (32bit version), or VirtualDubMod v1.5.10 build 2542 (http://sourceforge.net/project/showfiles.php?group_id=65889) with the same result - the memory error.

It could be that the 3 filters used above have memory leakage problems, but I doubt that they all have.
1 thing is certain the error happens more often with HD content, then with SD content.
The error is never "CAVIStreamSynth: System exception - Access Violations at 0x0, reading from 0x0" 0xyyyyyyy[y] where 'y' can be a number or any character and the last y is optional :)

neuron2
19th April 2009, 02:11
You can't repost a closed rule 6 thread with deceptive deletions.

Wake up, or you'll get the hammer.