Capturing problems with Asus V7700 Ti

[Windsheer]

A little explanation first. My old motherboard bit it not too long ago, so I had to replace, so I went with an upgrade at the same time, from a Athlon 1800XP to a Athlon 64 2800. I had been capturing fine previously using the 1.04h WDM drivers included on the CD. Afterwards the drivers refused to start, so I tried reinstalling. The setup program crashes every time I try and start it, so I had to reinstall manually. Now, every time I go to capture in Virtualdub, Vdub locks up, and if I close it manually, it steals the drivers so nothing else, not even a new session of Vdub, can use them. I tried reinstalling other versions to no avail. 1.04n, 1.16, and 2.20 all give the same problem. Now I have gotten 1.17 and 1.19b to work, but here's the kicker: while the video shows perfectly in overlay mode, when I try to cap and look at the resulting file, the middle third of the video is just a big white block, from one side to the other. I tried changing codecs, resolutions, and in both Vdub and VirtualVCR I get this exact same problem. Also when I try to look at the video in preview mode in Vdub, All I get is black. However, it was this way before the motherboard died, and never affected capping then.

System stats:
Athlon 64 2800+ processor
Gigabyte GAK8NSNXP motherboard
768MB RAM
Asus v7700 Ti Deluxe
Windows XP SP1 with all current updates
DirectX 9.0b
More HD space than you can shake a stick at. (Well, you can, just there's no point)

Has anyone ever run into a problem like this? What did they do to fix it? I really don't want to spend more on a new card right now if I can get this one working, considering I blew over $500 on the rest of the setup, and I've got college bills coming soon...

[Arachnotron]

I try to cap and look at the resulting file, the middle third of the video is just a big white block, from one side to the other.

Sounds like macrovision kicking in. Assuming the tape in question is not protected, the macrovision is known to kick in at certain noiselevels too. Some driver versions are more affected by this problem than others.

I forgot which, but there have been various postings about that. Try a search.