Tuners also not available after sleep (not just hibernate)
Thought I'd post this here as many years later, this problem still exists and it appears to be a Windows / Media Centre problem and not a hardware / driver issue.
I built my Windows 7 based Home Theater computer over two years ago and have had the 'no tuners available' after resuming from sleep problem ever since I added the 2nd tuner (can't remember which order I added them but I had both a DVB-S & a DVB-T). They always come back after a reboot/cold boot. I got round it by scheduling a task to reset the tuners when the machine resumes from sleep. Works every time as long as the reset runs before I hit the Media Centre button which is always every time now since I put an SSD in for the OS and as long as I remember to quit WMC before sleeping the machine (as the tuners can't be reset if WMC is already running).
The key points I want to make however are these:
Search the internet for 'no tuners after sleep Windows Media Centre' and you will get thousands of results from people using many different make/models of motherboard, TV card, graphics card and they all have the same problem. There's simply no way all these diverse makes/models of motherboards, BIOS', TV Cards would all have the same bug in exactly the same place.
1. I don't think it's anything to do with PCI-E link power state management as two of my tuners are PCI and not PCI-E. And it was like this before I added the USB one as well. And changing the power setting hasn't fixed it for many people.
2. It doesn't appear to be anything to do with power management setting for any of the devices as I (and many others) have tried every combination under the sun to no avail.
3. It's nothing to do with the 'backgroundscan' WMC performs either as plenty of people have disabled this (myself included) and still have the problem
4. I DO NOT THINK IT IS ANYTHING TO DO WITH TUNERS, MOTHERBOARDS, BIOS' OR DRIVERS
The reason I think 4. is the key bit is this: I have seen loads of reports across the internet from different people with the same problem and they are all using different motherboards, different tuners, different BIOS versions and different drivers/versions of drivers. The problem occurs no matter which manufacturer's hardware you use. I'm using two Hauppauge tuners (DVB-T and DVB-S) and a PCTV USB 290e Nano and I get the problem. I've seen reports from people using Black Gold (e.g. BGT-3620's) with the same problem. I've seen reports from people with TBS TV cards with the same problem. I've seen people with AnySee TV cards having the same problem? I've seen people using AMD chipset motherboards with the same problem. Ditto Intel (Core 2 Duo era, Core-i5 era), nVidia chipset boards and all manner of other peripherals, all with the same problem. What are the chances of independently developed hardware and drivers by all these different manufacturers having exactly the same bug in exactly the same place? Once is chance, twice is a co-incidence, but three is a pattern. The only common denominator is Windows & Media Centre.
The problem has to be in Windows and/or Media Centre. There can be no other explanation. And the sooner MS realise and fix this, the better for everyone.
To me, it is a big hurdle in the wider adoption of Windows Media Centre as a home entertainment hub. I know I could have recommended and sold many more Home Theatre computers if I had the confidence that my customers wouldn't face this problem. As it stands, I hesitate to recommend it as a viable product/solution for this and this reason alone.
Come on MS, this is not a hard to replicate issue. Replicate it in your labs, debug and fix the issue now and make many hundreds of thousands of existing customers (and potentially many millions more) very happy. You owe it to us for standing by you and loyally buying your otherwise good products.
