TMPGEnc error, keeps coming up

[TheWulf]

"At address 42E31008 , Read error occured against address 42E31008."

I'm guessing it has to do with my ram gone bad. Can someone confirm? This happens on most long conversions with tmpg, different input files, different out put formats.

[eKa]

bugger, having the same problem ! Started several days ago. I though that it may have something to do with conflicting versions of ripping software, as I inadvertently re-installed older versions of DVD2SVCD and EZYVCD.

Have tried the latest versions of tmpGenc, problem stil there, runs for 24-28 minutes or about 10-11 minutes into the conversion when the message appears. Have tried several movies with the same result ?

Will try removing/swapping ram to see if it makes a difference.

Anyone else with some suggestions ?

[TMPGuser]

i am having similar problem when encoding home DV movies from AVI to SVCD. Read error keeps coming upat different times, could never do variable bit rate -- it crashes. Crashes the program, sometimes crashes the whole computer.
errors are read error at address blah-blah and illegal floatingpoint errors.
wha could be the reason?

[ZippyP.]

...sometimes crashes the whole computer.

Sounds like a hardware problem. Ram, CPU, power supply etc.

[berra]

well i have got the same problem before with my amd cpu i unlocked it and down grade it and now i didnt have any problems with tmpgenc. this is maybe not a solution for you but worth to try .

[secretagent]

usually this happens when too much information is given to tmpgenc for it to handlw. that is your computer is doing other things at the same time, like being on the internet or a background process kicking in or some dlls from previous programs were not unloaded. meaning free up all ram, close all other programs, unload dlls, defrag your hard drive and hope it works.