I can't off hand see why the antivirus or firewall software would cause a memory dump. It does sound (initially) like there is some conflict with the VV capture.

You mentioned that you can successfully capture using other software - so, I wouldn't go to the capture hardware as the issue.

But, you also mention that you reinstalled VV twice - but with the same results. However - you didn't mention if you removed VV prior to reinstalling it.

If the issue is software (shared DLL, etc)...just doing a reinstall over what is already there may not solve the issue. You may have to totally remove VV first....then reinstall.

I would suggest removing VV....and then reinstall to a different locationi on your PC (different folder). See if you get the same conflict.

Or...if you could - see what happens if you just have VV installed on a system and see if you get the same issue.

I just rebuild one of my PCs this weekend, so it is brand spanking new (nothin on it but the OS). So that is where my thought process is with having a system with just VV on it. If you happen to have a spare HD and some time to kill - load up that HD with just the OS and VV (and what ever you need to capture) and see if you have the same problem.

Then, if you don't - add the other software one at a time and see if the problem kicks in. If it kicks in with the third applicatioin - then it would be safe to assume that there is some sort of issue with the third applicationi.

And why am I having a problem spelling application this morning???? Must mean I need some more coffee!!

:-)

XP Pro does have the firewire networking that could possibly be causing problems. I had an issues with previewing and dropped frames because I couldn't disable XP's wanting to network thru the on-board 1394 port of my mobo.

Good luck,

Franco

Makes sense.

I totally missed the part about running XP.

What are you using to capture?

Something to STRONGLY consider:

If you are using a PCI slot device, try it in a different slot.

Some time ago, I was having capture troubles with a PCI device. Someone reccomended trying a different PCI clot. I blew that idea off, and when all was said and done, that *was* the answer.

Just a suggestion.

The switching slots trick CAN work. Today's newer devices sometimes "share" a IRQ line. Normally not a problem. However it can cause problems because if you have two devices wanting Windows attention at the same time, something got to give... The result can be a lock up situation that comes and goes.

Check in Device Manager and see what or if any IRQ's are shared. Very typical for sound cards for example.

You can easily and safely remove all programs that load when you boot (and many of which remain in the background). The following process is completely reverseable:

1. Click on "Start" and then select "Run."
2. Type "msconfig" and press Enter.
3. Click on the "Startup" tab.
4. Click on "Disable All."
5. Click on OK to exit the System Configuration Utility and re-boot.

Try capturing now and see if things are any better. If there is no change, repeat the above five steps, but in step 4 click on "Enable All" to get back to your original startup configuration.

If this does fix your problem, you will need to re-visit the Startup dialog and begin enabling certain tasks, re-booting, and recapturing until you find the culprit.

Hope this helps.

I see messages to advise of virus,firewall,haedware change,but what about settings?Did you try to increase RAM preview in settings?.
Since your system works fine with other application-look for settings in vegas.Does the software reconize you capture card.
In rare occasions-the actual ram chip my be bad,but that would affect all software specialy doing video capture or rendering.
I am using win200pro.I tryied XP, but did not like it.
Again-try settings in Vegas.