2.5 crashes my system

[jamesp]

Just upgraded to Avisynth 2.5. However, everytime i encode with it it crashes my system. My system completely locks up though, and i don't get any form of error message and i have to reboot. This happened with the first 2 tv captures i tried. I uninstalled and put avisynth 2 back on, and the encodes went through fine. The first script i tried was:

AviSource("capture (2003-03-22 at 22-20-45).avi")
Trim(8183,144360)
DelayAudio(-0.250)
AutoCrop(mode=0,wMultOf=16,hMultOf=16,leftAdd=16,rightAdd=16,topAdd=0,bottomAdd=0)
Convolution3d (preset="animeBQ")
TemporalCleaner()
DctFilter(1,1,1,1,1,0.5,0.5,0)
Limter()
ConvertToRGB24()

Using this it crashed at 5%. I then took out all the filters and it crashed at around 35-50%. The source was a tv cap created with VirtualVCR using MJpeg(picvideo) and it was to be encoded in Tmpeg to dvd. Anyone have any ideas.

I have read that Avisynth 2.5 is dependant on having a codec installed that uses YV12. I have installed i think the nimo pack which has put all sorts of stuff (old divx codecs). Could that be the problem? Its a shame because it seems a lot faster than 2.1.

Jim

[Guest]

Originally posted by jamesp
I have installed i think the nimo pack which has put all sorts of stuff (old divx codecs). Could that be the problem? For sure. Get rid of it completely.

[jamesp]

Hi,

I've removed the NIMO pack, and I still get crashes with the latest version of AVISYNTH 2.5. I used the following script.

AviSource("capture (2003-03-22 at 22-20-45).avi")
Converttoyv12()
Trim(8183,144360)
DelayAudio(-0.250)
AutoCrop(mode=0,wMultOf=16,hMultOf=16,leftAdd=16,rightAdd=16,topAdd=0,bottomAdd=0)
Convolution3d (preset="animeBQ")
TemporalCleaner()
DctFilter(1,1,1,1,1,0.5,0.5,0)
Limter()
ConvertToRGB24()

The crash happens at around 35% when encoding with tmpeg. I took all filters out, so i had:

AviSource("capture (2003-03-22 at 22-20-45).avi")
ConvertToRGB24()


And i still get a crash. Because its a complete system lock up, i get no error message. I uninstalled, and encoded using 2.0.7 and it went through fine.

Does anyone else have any ideas? After installing the NIMO pack, there is a reference to Divx 4 on my machine. There is no dll for it and the codec can't be used, but its still there. My machine is:

Athlon 2100+, 512gb Ram, 80gb HardDriver, Winxp fully up to date. Encoding to DVD with avisynth - res 704x576. I have Div 5.0.3 installed, and picvideo mjpeg.

Jim

Originally posted by neuron2
For sure. Get rid of it completely.

[DDogg]

/edit . I need to learn to read better
The crash happens at around 35% when encoding with tmpeg. I took all filters out ...
So, that rules out a ton of stuff. With latest 2.51 from Sh0dan's signature in one of his messages installed (mar 19 - I remember he said it might fix some strange crashes), you start out with the simple version script that is located in the examples folder. Let us know if it will play, with the added rgb24 statement will it encode in tmpg?

Then move to a simple avisource statement with the rgb24 for tmpg (try other simple avi's, not just the one above). Will another avi complete the encode in tmpg?

Also, rename that avi you are using to "test.avi". May not be needed but that title with paren within paren is scary.
AviSource("test.avi")

/edit Yeah, Sh0dan (below) is probably right because you are talking about a full lockup. This thread has some related information on certain CPU's that may be of interest to you although it deals with a BeSweet crash (maybe even tougher on a machine than avisynth or CCE). http://forum.doom9.org/showthread.php?s=&threadid=48791

[sh0dan]

Try running the Prime95 "stress test", and see if your system is stable. AviSynth 2.5 stresses your system more than 2.0, simply because it's more optimized - this can lead to crashes. Link: [1] (http://www.mersenne.org/freesoft.htm) [mirror] (http://www.gamersunitednetwork.de/tools/toolsall.php?&title=Tools+%40+GUN#P)

There is almost no possible way AviSynth can crash your system - but it can trigger bad device drivers, etc. The Nimo pack is EVIL - and often there is no way to remove the mess it creates other than reinstalling the entire system. NEVER use it!

[jamesp]

The Nimo pack is EVIL - and often there is no way to remove the mess it creates other than reinstalling the entire system. NEVER use it!

Right - that does it! I'm reinstalling windows and trying again!

Jim

[jamesp]

I didn't reinstall my system but i did restore from a previous image of my os. However, i'm still getting the system hangs (note - my system doesn't crash with an error - it just stops operating). On investigating, i found that the problem only occurs if my source is a tv capture and i use avisource. I've encoded about 5 DVD's using Mpeg2Source and not one crashed. So my question is, is there a problem with aviSource in avisynth 2.5 - i'm using the latest binaries. The hang is random and doesn't occur in the same place during either playing the script, or encoding the script.

Here are the details of the source.

*) Athlon XP 2100+ , WinXp, SB Live, 512mb RAM, 120GB HD.
*) Captures with VirtualVCR using MJpeg Picvideo version 2.10.0.22. The tv card is a Wintv Go and i'm using the BtWincap drivers.
*) Using avisynth 2.5 (latest binaries from avisynth website). Using the Following script:

AviSource("DPS.avi", pixel_type="yuy2")
converttoyv12()
Trim(9469,56735) ++ Trim(62645,103589) ++ Trim(109490,141613) ++ Trim(144417,178778) ++ Trim(180843,209415)
delayaudio(-0.250)
AutoCrop(mode=0,wMultOf=16,hMultOf=16,leftAdd=16,rightAdd=16,topAdd=0,bottomAdd=0)
Fluxsmooth(temporal_threshold = 8 , spatial_threshold = 3)
TemporalCleaner()
DctFilter(1,1,1,1,1,1,0.5,0)
Limiter()
ConvertToRGB24()

Note - I have removed all filters and crash still occurs - but it seems to take longer.

*) Encoding to DVD Mpeg2 using TMpeg (however, the crash has occurred whist viewing the avisynth file in virtualdub).

Any ideas. Is there anything i can check after a crash has happened to pinpoint what it could be? I wondered if it was the ConvertToYV12 bit causing the hang as this line isnb;t in my DVD encodes?

Thanks for any guidence,


Jim


Originally posted by jamesp
Right - that does it! I'm reinstalling windows and trying again!

Jim

[DDogg]

Any ideas
I did see where you said you had run 5 encodes using Mpeg2Source without a problem, but at the risk of upsetting you, you did not mention if you had run Prime95 for 24 hours without an error or ran memtest. I don't speak for them, but I would be surprised if the devel guys will look at this until you do the tests that were suggested and completely rule this out first. Even if it is a waste of time.

The symptoms you mention sound so much like the weird random lockups caused by heat or computational error. I only bring this up because one time I thought this was a bunch of hooey and was embarrassed to find out it was not.

[jamesp]

oops - Sorry - i missed that about stress test. I ran the Torture Test, and after a few minutes i got :

FATAL ERROR: Rounding was 0.4625892639, expected less than 0.4
Hardware failure detected, consult stress.txt file.

I suppose my machine is a pile of *h*t then! Is this the cause of my problem? Its strange because i rarely ever switch my machine off and do lots of encoding and capturing and avisynth 2.5 is the only programe i know off which has hung my system like this :(

Jim


Originally posted by DDogg
I did see where you said you had run 5 encodes using Mpeg2Source without a problem, but at the risk of upsetting you, you did not mention if you had run Prime95 for 24 hours without an error or ran memtest. I don't speak for them, but I would be surprised if the devel guys will look at this until you do the tests that were suggested and completely rule this out first. Even if it is a waste of time.

The symptoms you mention sound so much like the weird random lockups caused by heat or computational error. I only bring this up because one time I thought this was a bunch of hooey and was embarrassed to find out it was not.

[DDogg]

As Sh0dan said, avisynth, and I'll add BeSweet and CCE, stress your machine like none other. Typically this might be because you have your machine tweaked out a bit. On my old tbird I reduce the speed in increments of two until I can run Prime95 without error.

Read that thread I posted above for a specific problem with a certain batch of AMD processors (I don't have personal knowledge of this, just what was said in that thread). If your machine is stock, you might have to go into bios and raise voltage to processor by .25 volts and/or memory by .10 volts. I have to do this on my machine to get it stable. Not all machines allow raising mem voltage and do be careful and not go much above .25.

Another thing is monitor your CPU temp. The other day I was having similar problem like you reported and had to go to a slightly larger heat sync. That fixed me up. Anyway, try some of these things slowly and systematically. They might help you. If they do, let us know.

Good luck!
DD

[Wilbert]

Try the suggestion in Q1.22 (http://www.avisynth.org/index.php?page=Section+1%3A+About+AviSynth#q1.22).

[theReal]

FATAL ERROR: Rounding was 0.4625892639, expected less than 0.4
Hardware failure detected, consult stress.txt file.

I suppose my machine is a pile of *h*t then! Is this the cause of my problem?

Usually, you'll only get these errors if your system is overclocked. If it isn't, then your memory or chipset isn't ok, or the voltage from your PSU is not stable enough. Check the voltages (also while running avisynth or Prime) and try to get another stick of memory (or test your memory in a friend's pc).

I got crashes with avisynth 2.5 recently and also Prime errors - then I found the possible reasons: my chipset fan wasn't plugged in and the power connection from the PSU to mobo wasn't good, so the 5V line went down below 4.7V under stress.
I repaired both possible problems and everything was fine again (btw. my system is slightly overclocked, mem @280 instead of 266 MHz, CPU @ 1680 instead of 1600 MHz)

btw. I almost forgot: it might just be too much heat, not broken parts in your computer! I forgot this because good cooling is the first I'm looking for when building a computer (so it never gets a problem for me). My CPU (Athlon XP1900) is always below 50°C, even in summer and with a lot of video encoding, also the chipset is never above 26°C and the general case-cooling is pretty good. This prevents a lot of problems, also with harddrives.

[Wilbert]

the power connection from the PSU to mobo wasn't good, so the 5V line went down below 4.7V under stress.
Sorry for asking a dumb question. How did you repair this? Did you buy a new PSU?

[theReal]

the contacts where a little "worn out", so I squeezed them a little with a (very small) screwdriver. Then I plugged it in and the 5V line was about 0.3V higher than before. Sounds silly, but it seemed to work :)