Read Error With TMPGEnc.... Please Help!!!!!!

[Cru]

I have a XP1800, Gigabyte GA-7VRXP,512 PC2700, 80GIG ATA133, ATI 8500DV..... I am Running WINXP SP1. When I am trying to encode AVI, DIVX, VCD, SVCD to DVD format to burn I keep getting a 'Read Error at address (Some Number) with TMPGEnc.exe' It happens at different spots while encoding and I can't seem to figure out what it is.
TMPG V 2.510.49.157
Solutions I have tried:
Replaced Ram with 512 PC2100
Scanned Ram for errors and found none
Changed settings it TPMG Environmental-VFAPI
- Directshow Priority to (2)
- BMP/PPM to (-2)
- Project File Reader (-1)
- Everything Else to (0)

My Bios is the latest build and I have set everything to the lowest settings.
One more thing, is that occationaly my computer will just reboot in the middle of the encoding.

That is about it... If have any suggestions I would love them

Thanx in advance
Cru

[legionpc]

Normally I'd just say change directshow priority to 2, as that fixed the problem for me... but since you have done that, I'm at a loss as to whats causing it

EDIT: The rebooting problem may be due to overheating. Can you run other intensive applications ok? If you have 3d mark, try setting it to loop mode and see if your computer reboots then. If it stays stable for a while, its probably fair to say the problem is not heat.

[ZippyP.]

Yes, I have talked to others that had a rebooting problem when encoding. It it is CPU intensive operation and can cause flakey components to fail. Things to look at are the Ram (oops, you did that), power supply or even the CPU. Make sure your CPU fan is working.! If you can, you may need to do some part-swapping to pinpoint the problem.

[legionpc]

Another thing you can try is this:

My Computer (right click) > Properties > Advanced > Startup & Recovery > Uncheck 'Automatically Restart'.

XP is set by default to simply reboot your computer instead of displaying any BSOD you may get. If you disable this with the above steps, you can determine whether you are gettign BSODs during the encode.

BSODs are usually because of RAM problems, but since you said you replaced your RAM with a different type, that may not be the cause in this case. Give it a go anyway.