avermedia 180 problem

[mattdcknsn]

I decided to put my Avermedia back into service and after installing the card, upgrading the drivers and rebooting; Sage crashes every time I try to add it as a source. I am running the latest stable Sage 6.1.9, the latest Java 1.6.0_01, and my other 2 OTA HD sources are running just fine. I have enabled debug, here is the pertinent info. Just FYI, the Java error log is created at 13:36:10 time.

Jave error log:

# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00c43c5f, pid=2216, tid=2860
#
# Java VM: Java HotSpot(TM) Client VM (1.6.0_01-b06 mixed mode, sharing)
# Problematic frame:
# C 0x00c43c5f
#

Sage error log:

Sat 5/5 13:36:09.227 WIN32 FAILURE HR=0x80040217 FILE=.\GraphManager.cpp LINE=536
Sat 5/5 13:36:09.227 switchToConnector0 tuningMode:
Sat 5/5 13:36:09.228 switchToConnector0 62168216 type=3 index=0 contry:1
Sat 5/5 13:36:10.048 DONE: switchToConnector0 62168216 type=3 index=0
Sat 5/5 13:36:10.049 Set capture brightness: (0 255)-127 val:126 hr:0x0 AVerMedia BDA Analog Capture-0
Sat 5/5 13:36:10.050 Setting up MMC video for recording new show & tuning channel conn=AVerMedia BDA Analog Capture Digital TV Tuner
Sat 5/5 13:36:10.051 Using quality setting "Fair" for recording
Sat 5/5 13:36:10.053 MediaFile startSegment enc=AVerMedia BDA Analog Capture MediaFile[id=3793844 FA[BAD AIRING] host=htpc-server encodedBy=AVerMedia BDA Analog Capture Digital TV Tuner format=MPEG2-PS 0:00:00 0 kbps [] \\htpc-server\Recordings\AVerMediaBDAAnalogCaptureDigitalTVTuner-0.mpgbuf, Seg0[Sat 5/5 13:35:25.702-Wed 12/31 19:00:00.000]]
Sat 5/5 13:36:10.071 Seeker channel string=
Sat 5/5 13:36:10.073 Destroying/rebuilding graph for WDM/BDA transition
Sat 5/5 13:36:10.075 teardownGraph0 called for device='AVerMedia BDA Analog Capture'

My next step if I cant figure it out here is to submit a bug report, but I have a feeling I am missing something. Thanks

[mattdcknsn]

It seems that the latest drivers are what was causing the problem. I installed their app to scan for channels and when I did that my driver went from 3.5.0.44 down to 1.2.2.23. After that Sage tuned it no problem. Guess I posted this in the wrong section. Turns out it was more hardware and end-user.