Vidcap 4 crashing PC

Geoff_Wood wrote on 1/10/2004, 12:55 PM
Vegas 4.0d VidCap hangs at seemingly random p[oints during VCiodeo Capture or Tape Capture. Scene detection disabled.

After reunning for, say, 7 minutes, CPU goes to 100%, preview stops, but HDD activity continues until either an error message or PC spontaneously reboots, with error message on re-logon saying that system has recovered from a serious error.

Only happens with Vidcap. Not sure yet if related specifically to Firewire card capture.

Firewire card and Display Adaptor are sharing IRQ16 in Dev Manager - how do I get them separated, if a factor ?

My setup:
Sony DCRPC105E Mini DV
VIA OCHI Compliant IEEE 1394
XP SP1 (brand-clean install)
Display adaptor NVIDIA Vanta
MOBO VAI / Celeron 1G1, 512MB
Separate HDD for data.

Any tips appreciated.

geoff

Comments

Geoff_Wood wrote on 1/10/2004, 1:47 PM
Have managed to move Firewire off Display IRQ by moving boards around. Now Firewire sharing with a Realtec NIC though ...

Still fails. In this particular scenario preview and recording continues until the error message is "OK"ed.

Error message "An error has occurred during the current operation. An Exception has occurred"

Abbrev. details:
Sonic Foundrty Video Capture 4.0 version 4.0d buiold 205
vicap40.exe access violation
Geoff_Wood wrote on 1/10/2004, 5:11 PM
Bugger,

Does it with analogue capture card too (AverMedia). Lasted 28 minutes before preview stopped, audio went 'HIiiiSSSS", and error the message popped up 20 sec later.

Data disk is 120BG , NTFS .

Error code:
Sonic Foundry Video Capture 4.0
Version 4.0d (Build 205)
Exception 0xC0000005 (access violation) READ:0x0 IP:0x0
In Module 'VidCap40.EXE' at Address 0x0 + 0x0
Thread: GUI ID=0x6A0 Stack=0x12F000-0x130000
PeterWright wrote on 1/10/2004, 5:12 PM
If you're capturing to an external firewire drive, there could be brief interruptions in access caused by dodgy connections or bad cable,

You could try capturing to an internal drive to see if the problem persists.
Geoff_Wood wrote on 1/10/2004, 5:14 PM
Drive is ATA-100 internal secondary master (no slave) ....

g.
Myke_Hart wrote on 1/10/2004, 8:19 PM
I was having similar problems, I tracked it down to the VIA OCHI Compliant IEEE 1394.

I purchased a Texas Instuments IEEE 1394 card by belkin $34 and disabled the VIA and all problems disappeared.

I tried everything but after reading thousands of forums I came to the conclusion that the VIA firewire drivers are not up to snuff.
Geoff_Wood wrote on 1/10/2004, 10:20 PM
Sounds likely (yeah, VIA), but it's doing it without the Firewire installed ...

geoff