Help with RemoveNoiseMC freezing PC

[FlimsyFeet]

I really like the results from the lq_filter (http://forum.doom9.org/showthread.php?t=110078) function on VHS captures; however, it's really slow (1-2 FPS) and will not run for more than a few minutes without locking up the PC.

My PC is an Athlon XP with 1GB of RAM, running Win Xp. I'm pretty sure the hardware is stable, I did one complete pass on Memtest86 and ran the Prime95 torture test for half an hour; no errors were found on either.

I can use other denoisers like Pixiedust and fft3dfilter with no problems, it just something in this script it doesn't like.
i have all the dependant plugins installed at the same version as sown in that thread.

I'm a bit lost as tohow I might go about troubleshooting to find out where the problem is?

[foxyshadis]

Since a quick cpu & memory check hasn't found the problem, try a full-system frier:
http://www.passmark.com/products/bit.htm

taken from
http://forum.doom9.org/showthread.php?t=54130
where there's lots of other neat tools linked.

[Heini011]

Hi FlimsyFeet,

1. make sure, you have the latest plugins
2. i had used SetMemoryMax(256) in my avisynth scripts. i don't know, if it is really necessary.

3. do you have an nforce 2 mb in dual channel mode ? specify the half size of your system memory in prime95 / options / cpu : day & night available memory

4. make a prime95 torture test / blend for some hours at least!

i have an athlon xp mobile @216x10.5 / 1.625V, nForce2 400, 2 x 512MB DDR-RAM. so the filters should work on your machine too!

greetings.

[FlimsyFeet]

Thanks for the replies.

The Passmark BurnInTest passed with no errors.

I do have an nForce2 mainboard running in dual channel mode, high performance setting in BIOS. I set Prime95 to use 256MB, I can it try with 512 and leave it going for a bit longer, but I get the feeling the problem is not with my hardware.

I'm using the same versions of the plugins as in the RemoveNoiceMC thread, at least I think I am, e.g. the older MVTools 1.2.2 instaed of 1.2.4, avisynth is version 2.5.6 dated 28 October 2005.

Just to make sure, I'll try and delete everything from the plugins directory and re-download only the minimum needed dlls.

Oh, one change I made to the function - I moved the line that says global idx_c = 25 up onto the main body of the script, becasue it gave an error where it was.

My script is just:
avisource("capture.avi")
converttoyv12
global idx_c = 25
lq_filter

[FlimsyFeet]

Finally got around to trying to solve this problem. I deleted all the plugins out of the avisynth plugins folder, and put back just the minimum to get the RemoveNoiseMC funtion to work.

And still it locks up the PC!

Tried using the static dlls of removegrain, removedirt and repair instead and still no difference.

Funny how I do processing and encoding quite often, but nothing else seems to cause problems for this PC like this function. The lockups are really bad crashes as well, mouse pointer is stuck, ctrl+alt+del does not do anyhting, the only option is a hard reset.

[Pookie]

It could still be your Processor overheating. Make sure you've blown out the fan and grills with compressed air. Try the function again with your PC's cover off. If anything is overclocked, turn it off.

[FlimsyFeet]

If it was the processor overheating, wouldn't the same thing happen with other cpu-intensive scripts?

I can process using pixiedust or fft3dfilter on full lenght movies with no problems.

Neverhteless I will try installing the cpu temp monitoring software for my motherboard and see if it makes a difference with more ventilation.

Edit: BTW, nothing is overclocked.

[FlimsyFeet]

OK, I gave my script a test whilst measuring the CPU temp. The PC froze when the temperature reached 65°C. This is within the normal operating range, according to:
http://www.amd.com/us-en/assets/content_type/DownloadableAssets/FAQ_Rev05_ENG.pdf

The maximum operating temperature for an XP 2700+ is 85°C. Running prime95 for a while, the temperature went up to 70°C, but the OS was still totally stable.

[Heini011]

Hi FlimsyFeet,

65°C is a quite high temperature, cause measurement is below the cpu within the socked, the die is much hotter. Anything until 60°C should be safe. test with prime95 in-place large ffts for at least one hour. you may need better cooling.


and don't forget to insert SetMemoryMax(256) in the first line of your avisynth script. i got trouble without it too.

greetings.

[krieger2005]

I guess the function use simply too much memory. Th PC stumble to flush the Memory to HD and this is what you name "freeze".

Do you tried to use "SetMemoryMax"? If you try, then use "SetMemoryMax(450)". With 1GB RAM this should work ok.

[Pookie]

Just for experimentation, try Didee's MCNR_simple2 , which is kinda-sorta similar.

http://forum.doom9.org/showthread.php?p=752196#post752196

[FlimsyFeet]

Hi FlimsyFeet,

65°C is a quite high temperature, cause measurement is below the cpu within the socked, the die is much hotter. Anything until 60°C should be safe. test with prime95 in-place large ffts for at least one hour. you may need better cooling.


and don't forget to insert SetMemoryMax(256) in the first line of your avisynth script. i got trouble without it too.

greetings.Actually I think this motherboard reads the temperature from the chip itself rather than a diode below the socket.

But I did forget to try the setmemorymax. (256 or 450?) You suggested it before and I missed it. I'll give that a go.

Thanks for everyone's help.