Frequent crashes while encoding

[addi72]

Until recently, I have successfully used Gordian Knot (v. 0.35.0) to backup/convert DVDs to DivX. I have also used tmpgenc to encode captured home videos to mpg, without problems.

Then suddenly, my computer starts to crash when I encode avi to mpg with tmpgenc. When tmpgenc reaches the 2nd pass, the computer simply powers off without any warning and I can't start it again unless I use the ON/OFF switch on the power supply.

This problem then seemed to spread to GK. I have seen crashes after besweet finishes and when Virtualdubmod reaches the second pass. I have checked the XP event log, and there is no mention of any crash there!

Does anyone have a clue as to what can cause this?

I even formatted the C: drive and installed everything clean and to my utter disappointment, the problem persisted. Here are some details about my system:

AMD Athlon 2500
512 RAM
Shuttle AN-35 mobo
winxp pro with SP2

[Baldrick]

Sounds like cpu overheating problems and automatic shutdown at cpu overheating. Check the cpu temperature and check for shutdown settings in your motherboard bios.

[redwudz]

Common causes: CPU overheat, Power Supply overload or beginning of failure, Memory module failure.

Most of these are easy to check. CPU temp is usually monitored in BIOS and takes a few minutes for the temp to get high enough to shut down.

PS problems can be checked by unplugging extra drives to lighten the load on the PS.

Memory can be tested by exchanging it out or using a program like Memtest86.

Encoding tends to be CPU and memory intensive and stresses these components.

This is all assuming hardware problems, but if it is happening with CPU intensive programs like encoders, it's a good probability.

Sounds to be temp related with the MB shutting down to protect the system. Check your MB to see if it has a auto shutdown feature.

[addi72]

Yes, the symptoms do point to overheating, but the timing of the crashes feels wierd. tmpgenc crashes always at 50% done, on some mpgs. On some it does not crash at all.

I checked my BIOS and found this:
System: 48 °C
CPU: 67 °C
PWM: 61 °C

but the MB temp autoshutdown feature is disabled in BIOS! (can be set at 60,65and70)

I ran Memtest86 for 20 min (how long will it go?) without any errors and then checked the temp again:
System: 50 °C
CPU: 70 °C
PWM: 66 °C

[johns0]

Get a better heatsink for your cpu right away,one day it will burn out.

[redwudz]

I don't know the specifics of your system, but 70C is not good. If I remember, you can run a XP2500 up to 85C or so, but I wouldn't. When I ran that CPU, I kept it about 58C max.

Depending on your case, you might want to add some intake or outlet fans. Round cables help airflow also.

An improved CPU cooler would help considerably. Anyway, that is generally not enough temp to shut down the computer. BTW, you can easily OC that processor with sufficient cooling, the right MB and memory.

Memtest86 will run a long, long time. If it doesn't find anything in an hour or so, probably OK.

Check your PS. If it's OK, then a little more complex.

Then it begins to look like a software problem or (Not good) a MB problem.

Anyway, check all the possibilites.

[addi72]

Thanks for all your comments.

I am starting to suspect my power supply. When the computer crashes, I need to switch the PS off and then on again before I can do anything.

[sanjayk]

addi72,

Have you by chance loaded the .NET framework even after reformat. Because recently I wanted to use Cutterman which required .NET, so I promptly loaded .NET and the subsequent hotfixes & pathches. And I observed the SAME thing. TMPGEnc crashed in between. PC suddenly switched off. Then I had to switch off & on to start the PC again. This happened MANY times so I ruled out any random event.

My conclusion the culprit is .NET. Its actually = Never Ending Trouble

I have now promptly removed .NET and I am happy now.

Also if you have a "Smart CPU Fan" option in your BIOS then enable it. This will increase the CPU fan's RPM after a particular temp. I have set it to 55C in my PC.

Good Luck

[addi72]

Sanjayk,

Lord knows what I have been getting through MS automatic updates. Should I see this if I go into "Add/remove programs"? But I am tempted to reformat/reinstall everything again and check for crashes on a "really" fresh PC, without any updates. Just gotta remeber to unhook it from the internet

[sanjayk]

Yeah, format your PC then. Start afresh. Load only Win XP + SP1. Then proceed gradually to SP2. And IMO, dont load .NET if you dont require. Hopefully you will be able to pinpoint on something.

[addi72]

But before I wipe the slate clean again, I am testing a few things. First of all, I got my vaccum cleaner out and removed all the 65 tons of dust that was stuck in the heatsink. The PC is encoding and the CPU has leveled off at 66 deg.C

And since I hate it when threads like this die out when the problem is fixed, without knowing how everything was done, I'll keep in touch

[addi72]

CPU heat is now 58°C idle and encoding at 64-65°C.
No more crashes. Removing the dust from the heatsink did the trick.

But I am unsure what process it was that shut the PC down, since the autoshutdown feature is definitely OFF in the BIOS.

But I'll be watching that CPU temp more closely from now on. (I downloaded mbm5)

[sanjayk]

It could be in the OS also.

[addi72]

I am run XPproSP2. Does XP monitor CPU heat?
I have never seen anything in the system event log about these crashes.

[sanjayk]

I am also not sure whether the power management module in XP monitors the CPU heat. I also havent seen any log related to CPU heat.

[RabidDog]

Dont forget to unplug and replug all your drives ..it may also be prudent to swap your memory modules around . it could be a loose connex on the C: drive maybe, causing intermittent power flux ... sounds like its either heat or the power supply.. try encoding with the sides off the case and only one hard drive connected, no other drives ... also "things" downloaded from the internet can get corrupted .. if one particular file is causing trouble then maybe its best to delete it and move on.