Symptom may also point to a transition that may be the culprit. If the other advice doesn't help try deleting the transition at that point if you have one and see if will render through.

I had a similar experience recently. I was rendering a short 3 minute video that didn't have anything that struck me as particularly fancy. It got to about 10 seconds from the end after about 15 minutes and then seemed to just stop dead. While i was scratching my head wondering what was going on, i suddenly noticed the frame count go up one more frame. I timed it and it took almost 3 minutes to get to the next frame. By this time the remaining time estimate had started jumping up to several days.

I finally realized that at that point in my video i had a crossfade to a clip that had one of the film effects applied to it. I tried removing the effect and the video rendered in about 16 minutes. I tried putting the effect back in, but not overlapping the clips. The video rendered in about 20 minutes. Overlap them again and the render dropped to a crawl again. Very odd what combination of things will suddenly cause the render to bog down.

The final solution was to render just the 10 second end clip with the film effect into a new file, then replace the end clip in the project with this new version and use that for the crossfade. Total time for both renders was about 24 minutes.

The file I'm trying to render is basically a captured TV show I have on VHS. I went back and cut out all the commercials and connected all the clips together. There are no transition effects or anything. It's just a straight forward 92 minutes. I tried rendering it a fourth time, this time using VV 4.0b, but still it stopped the second it hit 97%. I tried recapturing the last clip, too, so it's not that.

I think I might have figured it out, though I'm not sure. This might be far fetched, might not, but is there a 4 GB file size limit when rendering a project? What I noticed is that where the project stops at 97%, when I look at the canceled file, its size is 3.99 GB. Same with all the other times it failed. They all have that in common. I'm wondering if there's maybe a file size limit set somewhere, or maybe that's just the way the VV is. I tried rendering a clip of it seperately and it worked fine, so it looks like I might have to render each clip individually or split the project in half.

If you are running anything other than windows xp. you have a 4 gig limit. There is no way to get around it. That is how the hard drives are formatted, fat32 is what it is called. XP uses a format that has no limit.

Well, I'm running Windows XP (upgraded from Windows 98, which is what the hard drive was originally formatted on)...but that seems to be the problem I'm running in to, so that probably explains it.

Here's what the Sonic Foundry Knowledge base has to say, in the words of Joshua Dodge:
Issue: When I render a project in my Sonic Foundry application, I can only render up to 3.99 GB worth of data, and then I'm told I can't render any further. Why?

Solution: Under Windows 98, 98se, and ME, your drives can be formatted as FAT (File Allocation Table) or FAT32. The largest a single file can be on these operating systems is 4 GB. You can reach 4 GB rather quickly with digital video renders. For instance, NTSC DV AVI files take up about 3.5 MB per second of video. Under Windows 2000 and Windows XP the operator has the ability to format their drives as FAT, FAT32, or NTFS (New Technology File System). NTFS has no file size limitation other than the maximum amount your hard drive can carry.

So toomey96 was right, but wrong in leaving Win2000 out.

Anyway, if you are burning for a DVD you can either adjust the compression a little, to get the file under 4 GB, or split it and make part one and part two.
Tor
EDIT: Your conclusion snuck in while I was scanning the knowledge base. Now you know what you can do.