Interesting configuration. You are running a 1333 FSB but you are running 800Mhz memory. I think the first thing that I would do is load a program like Everest that will list the actual speeds that your system is running at and see if everything is actually performing the way you think it is. I always suspect the memory when a system locks up. That's not always the reason, but that is what I look at first. I assume that you are not overclocking, your PCI buss is running at 133Mhz, and you haven't set any BIOS parameters that override the default CPU and memory related settings. The avermedia drivers have been pretty stable, and while we have had a few problems with the scan tool, etc. I don't recall any lockup type problems. Are you using the standard Avermedia drivers or the clear QAM drivers?

First I used the standard drivers, and then I tried the clear QAM ones.  I haven't really changed any of the settings in my BIOS.  I'll try using that program you suggested.

Well, I looked at information from everest and cpu-z, and though it doesn't make too much sense to me, my neighbor, a computer science major, looked at the speeds and thinks there shouldn't be a problem with them.

If you tried both sets of drivers and still experienced the problem I think that excludes them as a cause. I really didn't think it was the drivers anyhow. I suppose it could be a defective card or an interrupt conflict but you have a really unique problem. I am out of ideas, but you might try putting the tuner card in a different slot which would would help if it actually is an interrupt conflict. It would be nice if you had another card you could try.

Can anyone help me figure this out?

Ever since I upgraded from the .21 drivers to the .25 drivers, I started experiecing a daily occurance of a pop-up box warning me that the guide update created scheduling conflicts.  Every time I go in, I see no conflicts. 

Additionally, ever since updating to the .25 drivers, I started losing my QAM guide info (not every time I got the pop-up window, but it did happen).  So, I implemented Mold's solution.

I also set the Guide Update in Settings to "manual" per Aver's pop-up message in the QAM mapping tool. 

Yet, I still get the daily pop-up window saying the guide update has created scheduling conflicts (annoying and a bit disconcerting), and just yesterday, it did the equivalent of the disappearing guide:  VMC told me I was running out of guide info (since it was set to manual updates) and I needed to download guide info.  So, I said "OK."  As a result (or just coincidence?), VMC re-enabled all the stations that I manually hid/unselected in the channel management tool in Settings/TV/Guide.  

I'm convinced that this would have been a "guide disappearing" event if not for Mold's solution, but I need to know what's going on so I can stop going through Guide Hell with my VMC.

Now I have to go in and re-hide/disable the QAM channels that I do not want to show in the guide.  And, I presume that this will happen again and again unless I do something else.

What can I do?  Why did this only start happening to me after I upgraded from the original .21 drivers?  Why do I get the daily conflict pop-up?  How can Aver ask us to set the guide update to "manual" so that we no longer automatically get 7-days-ahead guide data?

Any insights?

Thanks,
Jon

Thanks! I moved the card from the PCI-E X1 to the X16 slot, and now the tuner works fine.  I guess that means it is an interrupt conflict.  Do you know how to fix this, so I can move the card back later?

JonDeutsch:

What can I do?  Why did this only start happening to me after I upgraded from the original .21 drivers?  Why do I get the daily conflict pop-up?  How can Aver ask us to set the guide update to "manual" so that we no longer automatically get 7-days-ahead guide data?

Any insights?

Thanks,
Jon

hey jon,

seems like a strange problem, but then again vmc is full of these things. do you have a lot of scheduled programs? are you using the "any" channel recording option?

here's what i would do:
1. remove all scheduled programs under the "Recorded TV", "view scheduled" menu.
2. set the "Recording Defaults", "Channels" option to "One channel only". this will reduce the opportunity for conflicts.
3. redo the guide setup for your zipcode
4. enter just a few recordings and verify no more conflicts before adding all of them back.

also, i would re-enable guide updates. the only reason Aver said to disable automatic updates was to avoid guide loss. if you've modified atscprefs.xml then this should no longer be an issue.

good luck!

Thanks Mold!

Yes, I do have many now set to "any" channel.... only due to the fact that I've needed to do rescans many times recently and the QAM channel #s keep changing. 

Before I go ahead and remove all scheduled programs and redo them, I have two questions:

1. Is there any way at all (registry, or whatever) to change the base channel of a scheduled program?  Through the GUI, I can only select the original channel # or "any" -- I cannot modify the channel #.   (BTW, It's a shame that VMC's scheduled program app doesn't go by call_sign, isn't it?)
2. Is there anyway through ATSCPREFS to set the actual channel # so I can ensure future consistency of my call_signs and channel #s?

Thanks,
Jon

I tried to reply a couple of times, but it wouldn't go through. Third time is the charm. If the conflict is between the tuner and something built into the motherboard you will not be able to use the tuner in that X1 slot. If it is between the tuner and some other card, maybe a regular pci card, you might be able to move the other card around. Look in your motherboard manual and you will probably find a table that tells what slots share interrupts with what else. That will help you find the guilty party.

Hi All,

On Beta FTP side I posted a new set of drivers for AVerTV Combo PCIe (x32 and x64) version 2.5.x.26.

In this drivers we fixed isuse with BSOD when scanning for HRC QAM frequency.
Plesae give it a shot and let us know how this drivers work for you.

best regards,

Felix Kolotinsky

AVerMedia Technologies, Inc.

Hey Felix,

Thanks for the update, but I dont see a x64 driver version. Is it up yet? Thanks

royalkilla408:

Hey Felix,

Thanks for the update, but I dont see a x64 driver version. Is it up yet? Thanks

They are both there, in the /m780/M780_Drv_x86_v2.5.x.26 directory.

I see my mistake

I've had an intermittent problem for a long time now that I need some help with.

When I click the channel up/down on the remote (accessing my QAM channels) I will sometimes get a VMC blue screen that says:

"Cannot Play Program

Windows Media Center is unable to play the requested program. Please close all other applications, restart Windows Media Center, and then try again."

If I follow the instructions it does recover, but this problem occurs much too often for me. This only happens with QAM channels, not with analog, so I think it's something related to the Aver drivers. Has anyone else seen this, and do you have any suggestions on how to fix it? Thanks!

CV42:

Thanks! I moved the card from the PCI-E X1 to the X16 slot, and now the tuner works fine.  I guess that means it is an interrupt conflict.  Do you know how to fix this, so I can move the card back later?

 

This _MAY_ help.......

http://support.microsoft.com/kb/942959/en-us