blue screen when attempting to record analog with HVR-2250

[oostertoaster]

Hi all,
I'm having a small issue with my HVR-2250. Currently I have it configured for clearQAM and standard definition analog, both recieved over cable. The digital recording works fine (now that I've got it configured correctly.) My issue is with analog recordings. Every so often a recording will fail. Instead of recording the program, I get a constant blue screen without any sound. This appears to be a random issue, as I am able to record analog successfully one day, and the next day the recording will fail. The failure is not due to a tuner conflict, as the failed recording was the only scheduled recording that night, and I was not using the computer for live TV. Any thoughts? I'm running version 1.3.7.

[whurlston]

Do you get the blue screen on specific channels?

http://forums.gbpvr.com/showpost.php?p=3...stcount=36

[oostertoaster]

Do you get the blue screen on specific channels?

I'm not sure. This is a channel that I don't normally watch (my wife sets the recordings on this channel). The problem appears to be confined to this channel (channel 31 specifically). I've checked the frequency as shown in the thread you linked to, and it is identical to the frequency generated by the qam.ini manager tool you mentioned.

[oostertoaster]

I managed to find the logs of my wife's failed recording (see attached). I'm not terribly experienced at reading these log outputs, but a couple of things jump out at me:

1) 2009-01-18 19:59:00.671 VERBOSE ConnectPins failed: hr = 80040217


2) 2009-01-18 19:59:02.156 VERBOSE get_VideoFrequency() returns 264000000


Item number 1 sticks out because its a failure (don't know much beyond that though). Item number 2 sticks out because that is not the frequency I would expect. The qam.ini manager tool spits out a center frequency of 265250000.

[whurlston]

Well I was going to say that if the channel sometimes works, the tuning can't be the issue but I just noticed that the channel that was giving me trouble now tunes correctly. I'm not sure how that could happen since nothing changed on my machine.

More testing I guess.

[whurlston]

I managed to find the logs of my wife's failed recording (see attached). I'm not terribly experienced at reading these log outputs, but a couple of things jump out at me:

1) 2009-01-18 19:59:00.671 VERBOSE ConnectPins failed: hr = 80040217


2) 2009-01-18 19:59:02.156 VERBOSE get_VideoFrequency() returns 264000000


Item number 1 sticks out because its a failure (don't know much beyond that though). Item number 2 sticks out because that is not the frequency I would expect. The qam.ini manager tool spits out a center frequency of 265250000.

Yup, that's the problem I was encountering but I can't figure out why it tunes the correct frequency sometimes and not others.

[Jovec]

I don't think this is a specific GB-PVR issue. My two different VMC computers with 2250s have this issue, and while it won't help with recordings, a simply channel change will fix it (and then you can change back to your desired channel). It probably has to do with the 2250 not setting an individual tuner properly for NTSC.

[sub]

I don't think this is a specific GB-PVR issue.

I dont think so either. There recent release notes for the 2250 drivers have had comments about fixing issues that can cause blue screens, so it sounds like something they actively working through.

[oostertoaster]

Ok, well at least I'm not the only one with the issue. I'll try updating the 2250's drivers and do some more testing.
Thanks guys

[whurlston]

I don't think this is a specific GB-PVR issue.

I dont think so either.

I can confirm it's not a GBPVR issue. The screenshots I posted were using GraphStudio and the tuner filters were added manually. Completely separate from GBPVR. I'm sure they'll get it resolved soon. Until then, all we can do is wait I guess.