What would you do if you saw this and then everything was hunky dory?

[btrcp2000]

In my never ending quest to find a stable HDPVR setup, I had my old buggy one tested (multiple failures acc to hauppauge) replaced with a new one. Everything ran for a few days without incident, then I started seeing the familiar red icon, but it wasn't just the hdpvr. To sum up, I had a five hour period on Monday where multiple tuners had halts and failures (including the HDPVR), and then everything was functioning properly and has ever since.

The 2250 driver needs to be updated from the 2009 one, but all others are up to date. I can't find anything in event viewer that shows what the computer was doing at the time, but then again I'm not sure where to look other than to check all five headings.

What do I look for first with all the mayhem here?

Halt Detected in Recording (x1) Tue, Aug 10
12:31:07 AM

Warning Message Details

The device input "Dish211-100544E on 127.0.0.1:6969 USB" stopped producing data while recording "South Park" on WGNHD on physical channel 9446. SageTV will try to reset the device. This may be caused by a channel that is no longer available.


4) Recording Missed Due to Conflict (x1) Mon, Aug 9
11:00:08 PM

Information Message Details

The recording of "Caillou" on SPROUT at Mon 8/9 22:27 was not performed because of conflicts recording on other tuners.


5) Halt Detected in Recording (x1) Mon, Aug 9
10:01:06 PM

Warning Message Details

The device input "Hauppauge WinTV-7164 Analog Capture #2 Digital TV Tuner" stopped producing data while recording "Ten O'Clock News" on WXIXDT on physical channel 78-19-1. SageTV will try to reset the device. This may be caused by a channel that is no longer available.


6) Capture Device Failure while Starting Recording (x1) Mon, Aug 9
10:00:01 PM

Error Message Details

The capture device input Hauppauge WinTV-7164 Analog Capture #2 Digital TV Tuner had a failure while trying to start the recording of "Ten O'Clock News" on WXIXDT on physical channel 78-19-1 at Mon 8/9 22:00.


7) Capture Device Failure while Starting Recording (x3) Mon, Aug 9
8:15:02 PM

Error Message Details

The capture device input Hauppauge WinTV-7164 Analog Capture #2 TV Tuner had a failure while trying to start the recording of "SpongeBob SquarePants" on NIK on physical channel 28 at Mon 8/9 20:15.

3 Messages. Last Occurrence: Mon, Aug 9 8:17:22 PM


8) Capture Device Failure while Starting Recording (x3) Mon, Aug 9
8:00:02 PM

Error Message Details

The capture device input Hauppauge WinTV-7164 Analog Capture #2 TV Tuner had a failure while trying to start the recording of "SpongeBob SquarePants" on NIK on physical channel 28 at Mon 8/9 20:00.

3 Messages. Last Occurrence: Mon, Aug 9 8:02:22 PM


9) Capture Device Failure while Starting Recording (x2) Mon, Aug 9
7:45:02 PM

Error Message Details

The capture device input Hauppauge WinTV-7164 Analog Capture #2 TV Tuner had a failure while trying to start the recording of "SpongeBob SquarePants" on NIK on physical channel 28 at Mon 8/9 19:45.

2 Messages. Last Occurrence: Mon, Aug 9 7:46:07 PM


10) Capture Device Failure while Starting Recording (x3) Mon, Aug 9
7:30:02 PM

Error Message Details

The capture device input Hauppauge WinTV-7164 Analog Capture #2 TV Tuner had a failure while trying to start the recording of "SpongeBob SquarePants" on NIK on physical channel 28 at Mon 8/9 19:30.

3 Messages. Last Occurrence: Mon, Aug 9 7:32:22 PM


11) Halt Detected in Recording (x1) Mon, Aug 9
6:47:38 PM

Error Message Details

The device input "Hauppauge HD PVR Capture Device Component+SPDIF" stopped producing data while recording "Kid vs. Kat" on DXD on physical channel 102. SageTV will try to reset the device. This may be caused by a channel that is no longer available.


12) Halt Detected in Recording (x1) Mon, Aug 9
6:46:21 PM

Warning Message Details

The device input "Hauppauge HD PVR Capture Device Component+SPDIF" stopped producing data while recording "Kid vs. Kat" on DXD on physical channel 102. SageTV will try to reset the device. This may be caused by a channel that is no longer available.


13) Capture Device Failure while Starting Recording (x2) Mon, Aug 9
6:45:12 PM

Error Message Details

The capture device input Hauppauge HD PVR Capture Device Component+SPDIF had a failure while trying to start the recording of "Kid vs. Kat" on DXD on physical channel 102 at Mon 8/9 18:45.

2 Messages. Last Occurrence: Mon, Aug 9 6:46:21 PM


14) Capture Device Failure while Starting Recording (x3) Mon, Aug 9
6:45:02 PM

Error Message Details

The capture device input Hauppauge WinTV-7164 Analog Capture #2 TV Tuner had a failure while trying to start the recording of "SpongeBob SquarePants" on NIK on physical channel 28 at Mon 8/9 18:45.

3 Messages. Last Occurrence: Mon, Aug 9 6:47:33 PM


15) Capture Device Failure while Starting Recording (x3) Mon, Aug 9
6:30:02 PM

Error Message Details

The capture device input Hauppauge WinTV-7164 Analog Capture #2 TV Tuner had a failure while trying to start the recording of "SpongeBob SquarePants" on NIK on physical channel 28 at Mon 8/9 18:30.

3 Messages. Last Occurrence: Mon, Aug 9 6:32:33 PM


16) Halt Detected in Recording (x13) Mon, Aug 9
6:17:18 PM

Error Message Details

The device input "Hauppauge WinTV-7164 Analog Capture #2 TV Tuner" stopped producing data while recording "SpongeBob SquarePants" on NIK on physical channel 28. SageTV will try to reset the device. This may be caused by a channel that is no longer available.

13 Messages. Last Occurrence: Mon, Aug 9 8:18:36 PM


17) Capture Device Failure while Starting Recording (x3) Mon, Aug 9
6:15:02 PM

Error Message Details

The capture device input Hauppauge WinTV-7164 Analog Capture #2 TV Tuner had a failure while trying to start the recording of "SpongeBob SquarePants" on NIK on physical channel 28 at Mon 8/9 18:15.

3 Messages. Last Occurrence: Mon, Aug 9 6:17:18 PM


18) Capture Device Failure while Starting Recording (x1) Mon, Aug 9
6:00:02 PM

Error Message Details

The capture device input Hauppauge WinTV-7164 Analog Capture #2 TV Tuner had a failure while trying to start the recording of "SpongeBob SquarePants" on NIK on physical channel 28 at Mon 8/9 18:00.


19) Halt Detected in Recording (x9) Mon, Aug 9
5:16:15 PM

Warning Message Details

The device input "Hauppauge WinTV-7164 Analog Capture #2 TV Tuner" stopped producing data while recording "SpongeBob SquarePants" on NIK on physical channel 28. SageTV will try to reset the device. This may be caused by a channel that is no longer available.

9 Messages. Last Occurrence: Mon, Aug 9 8:16:07 PM


20) Capture Device Failure while Starting Recording (x1) Mon, Aug 9
5:15:02 PM

Error Message Details

The capture device input Hauppauge WinTV-7164 Analog Capture #2 TV Tuner had a failure while trying to start the recording of "SpongeBob SquarePants" on NIK on physical channel 28 at Mon 8/9 17:15.

[StephaneM]

Originally Posted by btrcp2000

To sum up, I had a five hour period on Monday where multiple tuners had halts and failures (including the HDPVR), and then everything was functioning properly and has ever since.

Well I cannot say for sure why halts occured, though here is a few things I have learned when dealing with Directshow capture myself:

* Card will stop producing data when it doesn't receive anything from the antenna. Some tuners recover when the signal returns, some other don't (so this apply to regular tuners not HDPVR).

* Driver can be the issue. I have one Cinergy 2400i dt (DVB-T : so European Digital Terrestrial capture card) that was stopping producing data a few times per week, whereas another capture card (connected to the same antenna) wasn't. I updated the driver : no more halting

* Memory issues (software / driver memory leak). When I was creating my capture filter (the directshow filter responsible for getting data from the capture card), I noticed that if I wasn't releasing memory, the directshow graph stopped producing data (though it was relatively quick : data was flowing 1 or 2 min. then no more data was received)


Regards,
Stéphane.

[wayner]

I had similar strange problems in the past and I reinstalled WHS and that seemed to help.

The problems came back so I have set up a new Sage Server running XP rather than WHS - I will keep WHS as a file server and for backing up my clients.

I am starting to feel that WHS and Sage don't always play nicely. At least running XP means that you can rebuild your system using the WHS backup in a matter of minutes (or hours at worst).

My hunch is that there may be something wrong with your system drive or the system is unable to write to your TV recording drivers.

Either that or there is something that causes WHS and Sage to have issues. I don't think you and I are the only ones having these sorts of errors - I have seen others have them as well. I used to think that WHS was the best OS for Sage - I am really beginning to have my doubts.

[StephaneM]

Originally Posted by wayner

My hunch is that there may be something wrong with your system drive or the system is unable to write to your TV recording drivers.

Yes this is something to add to the list: SageTV check the recording file size to know if the recording is halted or not. So if the file size is not growing : SageTV assume the rec. halted. But what if the file size reported (by Windows) is not correct...

Otherwise, having a disk subsystem not behaving correctly would only drop packets severly in the recording but not halt it (depends on the implementation of the rec. engine though)

[miloj]

I've had "Halt detected" problems with a mix of ATSC USB tuners (Hauppauge and CatsEye), and it remains my #1 WAF issue. Part of the problem in debugging it is the limited diagnostic info. While Sage depends on 3rd party hardware and drivers, it would be nice if it could do a better job of isolating and reporting one of several possible causes:
1) Weak antenna signal
2) USB communication issues
3) Tuner driver
4) Storage performance

At the very least, storage performance shouldn't be in the mix of causes for this specific error message. Maybe it isn't, but I've heard several cases of changes to the storage system fixing this issue.

I have a HDHR on the way hoping to eliminate several of these variables.

[Hunter69]

I can't say that my issues have totally gone away but since I moved to V7, I do not have many hdpvr issues. Coincidental, maybe