I have been trying to fix a problem for a number of weeks now with no luck, all similar threads on here either don't quite describe the same issue or the solutions havn't worked. Hope you guys can help.

I can setup the tv within media centre and watch dvb-t/t2 and dvb-s/s2 signals fine, but after a while (anything from a few minutes to a few hours) I get an error come up on screen when trying to watch a channel.

tuner conflict

Cancel

All TV tuners are currently in use.

To change the channel, select the program or

recording that you want to stop.

But it lists no channel or recording to stop.

There are no extenders, the tuners are not shared across a network or anything, and I wasn't even watching or recording any other channel at the time.

I am unable to record as well, I get a pop up saying Recorder Failure. the recorder experienced a failure and is unable to start.

the hotfix from article 2277775 and kb981129 says not applicable to your computer but I think thay already installed them through windows update.

Deleting the tuners and reinstalling them hasn't worked. Setting up TV signal again hasn't worked. Formatting and starting from scratch hasn't worked.

I have tried stopping / restarting ehrecvr / Windows media center receiver service but that times out giving the "windows could not stop the windows media center receiver service" error with code 1503.  Setting ehrecvr to start automatically hasnt worked, nor has setting it to log on as local system account.

Any more ideas would be very welcome, this is driving me nuts. I bought the quad tuner cards thinking I would be able to record 4 satellite and 4 terrestrial channels at once, but at the moment I can't even watch one.

I don't know if it's a bug with media centre or a bug with the drivers, but I need a solution soon.

I have the pci-e dvb-s2 quad tuner 6984 and the pci-e dvb-t2 quad tuner 6284 installed on an asus m4a88t-m motherboard, with an athlon II x2 240 am2+ cpu, a single ddr3 kingston 4gb stick and an ati radeon 5450 graphics card running on windows 7 home premium media centre.

Thank you.

Can you look in your Application event log to see if you if you see an ehrecvr crash logged at that time, and see if the module it is crashing in is psidec.dll?  I have a theory.

erkotz AKA Sherlock Holmes

can't look just yet as it's in use by the family, hopefully I will have a look later and post back.

Cheers for the help.

Not entirely sure what I'm looking for. Can't see any errors that relate to the tuner devices, or eshell, or ehrecvr.

Have spotted that bonjour is giving errors and it turns out it's installed twice so I've just removed them both, will see what happens.

Related, it was suggested i remove a card and test.

disabling the dvb-t card gave trouble free viewing, no tuner conflict message after 28 hours on.

enabled dvb-t, disabled dvb-s, rebooted, no tuner conflict message after 5 hours on.

enabled both, rebooted, tuner conflict message came up after a few hours.

so why is having 2 tuner cards giving this message? media centre supports 4 tuners of each type.

would tuner salad fix my problem? or dvblogic? would rather not spend more money though.

Sorry for being unclear.  Look for an error (at the time this occurs) in your Application event log.  It will have the source "Application Error" and an Event ID of 1000.  Text will be similar to:

Faulting application name: ehRecvr.exe, version: 6.1.7601.17514, time stamp: 0x4ce7aea5

Faulting module name: psisdecd.dll, version: 6.6.7601.17669, time stamp: 0x4e4b502f

Exception code: 0xc0000005

Fault offset: 0x000000000002be26

Faulting process id: 0x1338

Faulting application start time: 0x01ccef3c39a4c517

Faulting application path: C:\Windows\ehome\ehRecvr.exe

Faulting module path: C:\Windows\System32\psisdecd.dll

Report Id: 775bb9a1-5b30-11e1-95b2-001a4d5a54c0

If that's the error you are hitting, we're already working with Microsoft on the issue, though it would be useful to know that people are seeing this on other continents, too.

Sorry for not replying in my own thread. Had work and been ill.

Had the dvb-t card disabled for a few days and tv has been fine. enabled it yesterday, this morning I get the the error.

I've looked through the event log again but see no mention of "application error" or "ehRecvr.exe" like you suggested.

Guess it's a different situation.

Just to check, the application viewer is controol panel - administrative tools - event viewer - then look in log summary?

I am in the US. Never watch Live TV and so am not sure if I have that issue. I have seen the "All TV tuners are currently in use" message though when recording programs (pre-set to record and not recording from the guide). I have 8 tuners in my system. This usually happens when there are multiple programs being recorded at the same time, but the recordings go through. These tuners sometimes seem flakey when viewing Live TV but work for recording. Not sure if the system retries for longer when recording or what. Not sure if the reason you watch Live TV is the ability to channel surf. If not, you can try recording the program that you want to watch from the guide. Then start watching the recording. If this works, you may get some more clues as to what is going on. Recording failures also typically describe the reason for the failure. This can be seen in Recorded TV->Scheduled Recordings->History.

One more question is if your two tuners are using 2 different sets of drivers written by different companies. Could these be conflicting in any way?

So, still got the same problem, just been living with 1 card disabled so we can watch most live tv.

Tried a fresh windows install on another hard drive, this time I tried 32bit. Its a bare system, only installed drivers and lav splitter (to watch mkv, not using for wtv/dvrms) and I still got the same error (was hoping it might be a 64bit bug, but no).

mm60 - I am unable to record either, got the recorder failure pop up. Also, i get your point about different cards and drivers, but they are both made by TBS. I bought them thinking I wouldnt have problems if made by same company.

I think the next step would be to turn on ehrecvr logging