windoze Crashing on every conversion, any tool

[Roderz]

I've been making/encoding s/vcd/cvd/dvd for over 2 years now and have managed to overcome any probs b4 (some thanks to the help/advice posted here) but this is driving me nuts!

I lately formatted my HD due to windows crashing everytime I tried to convert form divx/xvid to mpeg2 (and I thought it was about time for a clean out).

But I still have the problem! (yes I checked 4 bad frames, infact I tried a file I know is good - one that I've already done b4)

Clean install of w2k, sp4, dx9, ie6
Codecs installed (just the usual ones I allways had+used) divx3/4/5 + Xvid + ac3filter.

Now weather I use Tempec or MainConcept 1.4 the system will just halt (freezing dead no errors, sometimes after a min or 2, sometimes after 40 mins) even TDA freezes if it has to re-encode audio to 48K !
Cpu temp is ok (quite low, got sides off) acording to bios + lcd monitor
as is hd temp.

Then thought of bad ram (cluthing at straws) ran memtest86 and YES bad ram!
YIPPIE I thought as I ripped out the offending 512Mb pc2700 and left in the good stick of 256 pc2700.
But nothing has changed

Any ideas welcome !!!!
(or have I forgotten about something really silly? )

Sory if this post is in the wrong place

[proggy]

Re-run the memory test with the "good" memory stick to see if it still performs ok.

Also, monitor your motherboard voltages (utility) while you are encoding. Maybe your power supply is dipping slightly causing the computer to freeze.

[redwudz]

I go with proggy. Unless something stange and alien has happened to your computer, memory failures are a major cause of crashes during encoding. Any type of video encoding is very memory intensive. Try all the regular fixes; Reseating cards and all internal cables, check PS, etc. If the MB is OK, Bios, OK, memory would be the next suspect.

[Roderz]

Re-run the memory test with the "good" memory stick to see if it still performs ok.

Yea done this and stick passed but still got same prob

As for the psu, mmmm the case+psu (300W) is about 4yrs old and running 2optical + 3HD + floppy + fornt panel and machine is never turned off -- so you could have a point (will keep and eye on V's).

So bloody anoying - feel like a complete nube!
I can still encode on my laptop, running w2k sp4 on a p2@266 !!! works fine BUT SLOW

PS even tried Windows Media Encoder (stop sniggering please) and that locks my system (not really a suprise!)

[LSchafroth]

I had a PC I built for my sister-in-law a while back that did the same thing.

I replaced teh NEW power supply with another NEW one and it's been solid ever since.

Just a thought...

LS

[Roderz]

Keept an eye on the voltages and all seemed well within the tolerances

Stripped down machine and cleaned all connectors (agp/pci/ddr/cpu...) with component cleaner - still no joy
Removed network card - still no joy
Removed Radeon 7200VIVO card replaced with old GF2 - Lots 'n' lots 'n' lots of joy

What the F*#K is going on? drivers were latest from their w/site.
Can this really be the cause of all my probs? card seems to work fine within windoze

I really don't know what gone on here - just happy to be able to encode something again.
Every prog now working again TDA, Mainconcept, Tmpgenc.

[Perro Grande]

With ATI cards, I've always found them to be very *VERY* fussy about drivers. It might be a good idea to install the original drivers that came with the card (from the CD) and see if that works properly. This will eliminate hardware, interrupts. etc. At least you will know that it is strictly a software issue.

If it still crashes with the old drivers, check a few things in BIOS. Check to make sure you don't have an interrupt-related problem. Some cards prefer (ie. require) assigning an interrupt (via BIOS) to the VGA card, other cards will not operate in this manner.

You could also try changing the way BIOS handles interrupt assignments. Typically, you can determine whether the OS or BIOS does this task. If BIOS is set to PNP OS Installed = YES, then Windows will handle interrupt assignment. If no, BIOS handles this task. You can try changing this value to see if this clears any possible conflict.