tmpgenc + XP = problems! :(

[porto]

hello,

whenever I try to encode some DivX movie or ripped .vob file to mpeg1 with TMPGenc the program crashes with vague errormsgs, like:

illegal floating decimal point calculator error (a true scrabble word!)

read error xxxxxx in module tmpgenc.exe on xxxxxxx

and 2 other msgs which I can't remember the msg.

someone could explain to me what's going on here?? is my XP f*cked up??

[porto]

a little addendum to my original message:

under Windows 95 the encoding worked 100% perfect UNTIL I installed XP; now also Win95 encodings are pathetic! ;(

Can it have something to do with the fact that I overclocked my cpu (a bit) from original 1400 tot 1533Mhz ?? I use a cooler which holds the temp around 50C so that wouldn't be a problem, right?

[sommersby]

sounds more to me like your avi's have bad frames or are corrupted, XP is not the problem.

[JJamez]

Anything is possible once you introduce overclocking into the equation... The first signs you would notice are like those you mention - programs crashing for odd reasons.

Reset back to 1400 and see what happens - thats the only way you'll know for sure...

I think 50C is a little hot if that temp is when your PC is 'at rest.'

JJ

[porto]

I will put the speed back to 1400Mhz and see if that helps.

if my computer just rebooted and I'm doing nothing with it, after some 20 to 30 minutes it sticks to 46 to 48C... when I use the cpu alot it goes higher, to 50, 51C.
I use a Noisecontrol silverado as cooler.

[JJamez]

Thats a little warm, but not bad... If at idle you were at 50C and with CPU load it went up to 60-65C, that might be cause for concern, but your temps seem alright, especially if you're running an AMD chip.

My Duron ran very hot (without OC'ing it) until I installed CPUIdle - my idle temps dropped from ~50C to ~30-35C. Of course, during constant, long term CPU activity, like during an encode, the program has no effect, but when the CPU is idle (hence the name...lol), it makes a big difference.

JJ

[porto]

seems like the overclocking was not even the problem here; powerdvd was. The shipped versions below 4.0 aren't compatible with XP, and especially the .ax files distributed. They cause frequently crashes and errormsgs... With powerdvd 4.0 it seems like it is solved... my troublesome .avi file encoded last night in 1 step!

[JJamez]

Wow, that's weird.. Why was PowerDVD having any effect on you encoding a DivX file?

Anyway, glad you figured it out.

JJ

[ceedee]

I had clocked my P3 550 and got exactly the same error using xp.
Put it back no problems now.

[porto]

well, I know it's vague but I did a little testing:

i put my cpu 'back' to 1533Mhz (OC'ing from 1400Mhz) then I tried to encode a ripped .vob file and a DivX avi which gave errors guaranteed but to my big surprise they both encoded without a problem!

then I uninstalled powerdvd 4.0 and installed version 2.55, leaving the OC'ing untouched.

immediately they both gave the old errormsgs back while encoding. I'm not sure WHY a divx file needs a library from powerdvd but maybe those libraries are generic for all kinds of encoding?? beats me!

Just to be very certain I reinstalled version 4.0 and immediately no errors whatsoever... this can't be a coincidence