Is Avermedia A188d Suitable? (3 Viewers)

[gonzo90017]

Have you confirmed that both cards work individually?

 

[mm1352000]

Yeah, good question gonzo90017.
I also wondered...
In your profile your country is set to America. ATSC is used for OTA TV broadcasts in the US.
Dave80 seems to be from Australia. DVB-T is used for OTA TV broadcasts in Australia.
DVB-T tuners don't do ATSC, and ATSC tuners don't do DVB-T.
So I'm wondering whether your profile is out of date or wires have been crossed somewhere...

 

[Dave80]

sorry i never updated my profile i live in queensland australia. i have been vigourously testing this bit by bit.

i contacted avermedia and they said it may be hardware conflict and if possible to test in different rig. they also suggested to return the cards under the stores return policy.

i had previouslty been swapping slots etc trying to get the cards to work together. then i got sick of it and put a single card into the pcie x1 slot above the first pcie16 and wala for some reason it works no worries with a single card in that slot. so i left it run for a day to test and all was fine. so im sitting on the couch thinkin wtf im missing shows i want to watch i cannot just sit here with 2 tuners... its not enough i may as well go back to my tivo. then it dawned on me... i tried 2 cards (1 in each pcie x1 slot) then i tried 2 cards (1 in each pcie x16 slot with a vid card in the top pcie x16 slot) and i remember reading something about how when running tri sli that the last slot can only run at half speed because it runs through a different chipset to the other 2 pcie slots.. . so i started thinking i didnt try one card in the top pcie x1 slot and 1 card in the bottom pcie x16 slot. BAM it works!!!!! no lag at all!!

HOWEVER!!! now i have a new problem.... (or at least the other half of my problem?) i average around 1000us dpc latecy which still is fine really. and then it spikes incredibly high when it fires up an extra tuner. which i can live with..

BUT ive discovered if i try to tune to any SBS channels that DPC latency goes into the red again... so to test this out i did this

manual tune.
open 1 tuner to 7two (strong signal)
open 1 tuner to sbs.. (causing DPC Latency issues again)
then manual stop.. (still has DPC Latency issues)
stop tv service (still has DPC Latency issues)
restarted service (still has DPC Latency Issues)

now only 2 things will stop the high DPC latency
1. disable the tuner i tryed to watch sbs on in device manager
2. manually tune all tuners to channels with excellent tv reception signal (almost like it has to manually retune the card to move away from sbs before it will stop causing problems)

then bam the high dpc latency stops and is if it was never a problem

so.. i gather 2 things from this..
1. my sbs signal is weak i guess?
2. either my card is staying actively tuned in to the channel with weak signal or media portal isnt closing the channel properly and moving the card to idle?

how do i proceed? do i buy a amplifier?
something like this?
http://www.bunnings.com.au/products...&searchType=any&searchSubType=products&page=2
or anything else recommended?

 

[Dave80]

ok so i decided to setup windows media centre and see if it has the same issues, and it didnt even pickup SBS in the channel scans so i was unable to try to tune to them to see if it causes the DPC latency issue. I will disable SBS channels in media portal until i can get better reception and see if that helps.

 

[gonzo90017]

Yeah, good question gonzo90017.
I also wondered...
In your profile your country is set to America. ATSC is used for OTA TV broadcasts in the US.
Dave80 seems to be from Australia. DVB-T is used for OTA TV broadcasts in Australia.
DVB-T tuners don't do ATSC, and ATSC tuners don't do DVB-T.
So I'm wondering whether your profile is out of date or wires have been crossed somewhere...

DOH!
My mistake. I own the A188c which is the ATSC version of the card.

 

[mm1352000]

My mistake. I own the A188c which is the ATSC version of the card.

The drivers will still be similar.

@Dave80
The latency thing is probably related to the low signal quality/strength. It indicates the tuner driver/firmware/micro-code is working hard against the errors... but probably a poor design, as a good design should not do that. An amplifier may help but only for weak signal strength. If the signal quality is poor then you may need to investigate your options for a better aerial or replacing cabling etc.

 

[Dave80]

so out of the blue the DPC latency has jumped up, not insanely its just steadily about twice what it is when its running well, thats not really effecting the computer but its also turned off when i come out now and then so i opened the crash dumps and this is what i got,

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.
On Sat 6/22/2013 7:20:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062313-14133-01.dmp
This was probably caused by the following module: averbda716x_x64.sys (AVerBDA716x_x64+0xBB4D7)
Bugcheck code: 0xD1 (0x390FE16, 0x2, 0x1, 0xFFFFF880059154D7)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\averbda716x_x64.sys
company: AVerMedia TECHNOLOGIES, Inc.
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: averbda716x_x64.sys (AVerMedia TECHNOLOGIES, Inc.).
Google query: AVerMedia TECHNOLOGIES, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL


On Sat 6/22/2013 7:20:54 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: averbda716x_x64.sys (AVerBDA716x_x64+0xBB4D7)
Bugcheck code: 0xD1 (0x390FE16, 0x2, 0x1, 0xFFFFF880059154D7)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\averbda716x_x64.sys
company: AVerMedia TECHNOLOGIES, Inc.
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: averbda716x_x64.sys (AVerMedia TECHNOLOGIES, Inc.).
Google query: AVerMedia TECHNOLOGIES, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL


On Fri 6/21/2013 12:52:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062113-16239-01.dmp
This was probably caused by the following module: averbda716x_x64.sys (AVerBDA716x_x64+0xBB4D7)
Bugcheck code: 0xD1 (0x399FE16, 0x2, 0x1, 0xFFFFF880058DA4D7)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\averbda716x_x64.sys
company: AVerMedia TECHNOLOGIES, Inc.
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: averbda716x_x64.sys (AVerMedia TECHNOLOGIES, Inc.).
Google query: AVerMedia TECHNOLOGIES, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL


On Tue 6/18/2013 7:52:04 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061813-12994-01.dmp
This was probably caused by the following module: averbda716x_x64.sys (AVerBDA716x_x64+0xB87F)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800883987F, 0xFFFFF880038D5D60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\averbda716x_x64.sys
company: AVerMedia TECHNOLOGIES, Inc.
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: averbda716x_x64.sys (AVerMedia TECHNOLOGIES, Inc.).
Google query: AVerMedia TECHNOLOGIES, Inc. SYSTEM_SERVICE_EXCEPTION

 

[mm1352000]

Well, as you can see, the tuner driver is crashing. "averbda716x_x64.sys" is the main driver binary...

 

[gonzo90017]

Just like to mention that my avermedia atsc cards are installed on a Windows 32bit system.

 

[Dave80]

do you think i should try reinstalling all over again with a 32bit OS and see if that works better?