Inexplicable TMPG/DVD2AVI problem driving me mad...

[lugnut_]

Okay, so I've completely ran myself out of ideas and I come to you guys seeking help. Here's the deal:

I've ripped/encoded probably a hundred DVDs to VCD over the past few months by ripping with SmartRipper, assembling with DVD2AVI, then frameserving to TMPG. Up until this point, I've never encountered even a single problem anywhere along the process.

The other day, while in the midst of an encoding job, my power supply decided to crap out and shut down the PC. After replacing the PS and getting things up and running again, I tried to restart my project. Then the trouble began.

Ever since then, I get one of those damned Read Errors in dvd2avi.vfp, but it's not consistent with just one movie or even one scene. Sometimes it'll get up to 90% before crashing, sometimes it may not even make it to 10%. It's done this on four different movies at different spots in all of them.

Now, here's where it gets weird. Sometimes it still works. After many retries, I finally got 3 of the 4 to encode. Just as soon as I think I've fixed it, however, the next video I try will screw up again in the same way. ARGH!

I've tried deleting and re-installing both TMPG and DVD2AVI, even going so far as to manually remove every reference to them in the Registry before the last re-install. Last night, I got an error in p3package.dll (which was a first), but after I re-tried (twice), it got the same old dvd2avi.vfp error again. Often it seems before the crash it will cause the entire PC to slow down massively and it shows something like 15 hours remaining on the encode project. And then sometimes it just crashes when everything is going along dandy.

I've adjusted priority settings, I've defragged, I've virus-scaned, I've tweaked everything I can think of to tweak. What the hell can possibly be causing this?

Thanks in advance,
Jesse

[lugnut_]

And now, days later, the problem continues.

Doesn't anyone have ANY suggestions for what to do about this? I've Googled around enough to know I'm far from the only one who's experienced this occurring all the sudden...

I'm really grabbing at straws here, folks.

[lugnut_]

Oh, by the way...

I found one site that suggested these read errors are caused by faulty RAM, but after using the program suggested by the site to detect RAM errors, everything came up clean.

[au7usa]

If your power supply died while you were writing to the hard drive, your file system has to have some corruption on it. I'm surprized that it started.

Go buy a UPS.....Now!

Then back up your important data, cause i have a feeling your system may mysteroiusly lockup in the near future.

Anytime power is lost during a write to the hard drive the partition table usually gets screwed up.