Avisynth crashing (reading out of allocated memory)

[U977]

Hi all,

I've been using avisynth since about 2 years without a single problem.
But since last week-end, I keep getting a pop-up error claiming that Avisynth is trying to read out of allocated memory.

I was using Gknot 2.8.4 with Avisynth 2.52. Trying both DivX Kaukura and XviD (Koepi's 24062003), I get the same error. I disinstalled Gknot (including Avisynth) and reinstalled teh latest version (2.8.5.2), and reset the codec settings to default, but the problem is still present.

Every encode is crashing that ways at some time after 1 hour of encoding. I've also tried with the latest Virtuldubmod, but it did not solve anything.

The only thing taht changed on my computer since my last successfull encode was that I installed DivX Kaukura instead of DivX Kauehi, for test purposes (I almost alwayts uses XviD).

I did not catch any fish using a search on the forum...

Does anyone have a direction to solve this?
I checked the avisynth DLL, and it's indeed the version 2.52.

Thanks... It's question of life for me to get it working again :-)
PS: enough free space on all my HDs, and I did not change any hardware.
I can't believe this happens because of Kaukura: even XviD can't escape to that crash, and the pop-up error is mentionning avisynth.

[Wilbert]

Maybe Q1.24 is of any help:

http://www.avisynth.org/index.php?page=Section+1%3A+About+AviSynth#q1.24

Is it each time at a random frame?

[U977]

Indeed, it's crashing during the 2nd pass, at random points...
However, no component is overclocked, on my computer.

So, either it's something else, or my computer is getting too old.

Anyway, thanks for the stress test, I'll give it a try!

[sh0dan]

Run Prime95 for at least an hour. Just because your system isn't overclocked, it doesn't mean it's stable - unfortunately. :(

Otherwise you might want to try doing a two-pass with XviD - just to check that it isn't DivX.

[U977]

Thanks, Sh0dan.

Actually, I already did tests with XviD, and I end up with the same crash.

Yesterday evening, I decided to disinstall the whole GKnot package again, reboot, and reinstall, checking that all the files were deleted, including the avisynth.dll in the Windows\system32 folder.
I wanted to give it one more try... So after having reinstalled everything, I launched a XviD encode this morning. I'll see teh restult tonigh.

What surprises me is that just few days ago, I was still able to encode without that problem. My system was very stable since 2 years.
But I remember that explorer crashed when I was using the Windows explorer, and clicking (simple click, not even opening) on an avi file, too. That was after the very first avisynth error, though. This error was the first that I met.
So, I guess my CPU may have heated too much (although I've configured a protection tah tforces shut down at more than 70°C) since the weather is quite hot right now. Or maybe after about 2 years of usage, my CPU is starting having troubles. 2 years? Still a bit short, isn't it? Maybe not, for an AMD 2000 XP? :-)

I'll let you know the outcome of this :-)
Thanks again!

[PowerMacG4]

if all else fails

reformat

[Wilbert]

I recommend to lower your bus-speed 133->125 MHz before any formatting. I also need to do that when encoding :(

[U977]

Hello,

An update, just in case you're interested to know, and for those who will have the same problem.

I realized yesterday that my CPU is working at a temperature of 69°C (it's very hot, right now, with quite exceptional temperatures). And my two fans could not help with that situation.

So, I guess this is why my system becaume unstable. For now, I'll just wait that the weather becomes cooler, and I'll run another test without modifying bus or CPU speed.

Yesterday, the stress test halted after only 10 minutes. It had already found a computation error.

I'll post another update after the test with cooler temperatures.

[cweb]

Either get air conditioning, or place a fan directed towards the PC. It helps with hot weather.

[U977]

£Hi all,

As promised: final word :-)

Weather is back to lower temperatures, and my system is back to a stable state. My awaiting encodes are now in progress! :-)

Thanks for your advices!