Server crash when playing or recording 3rd HDTV program.

[trummel]

I have a server with multiple DVB-T and DVB-S cards. I can watch and record as many SDTV programs as I like without any issues. I can also watch or record 2 HDTV programs without problem. However when I try to watch or record the third (even if the first 2 have finished) it appears that the server (I presume nrecord)crashes.

If the 3rd session is to watch live HDTV, nothing appears in the c:\temp folder. The previous 2 sessions created temp files and correctly deleted them when the playback was halted.

I have 2 tuners configured to handle HDTV, they are both PCTV USB cards, but one is a DVB-T2, the other is a DVB-S2. This problem has only occured since I upgraded to 2.6.2.

I do have an issue with client PC's freezing, which may or not be related to this, but I figure there is no point trying to resolve that until the server works properly.

Very odd.....

Clean set of log files attached.

[johnsonx42]

good old graph stop hang in ndigitalhost, which causes NRecord to hang forever the next time it tries to start a recording:

Code:

2013-03-27 10:56:28.533    [INFO][5]    No more streams active. Stopping device.
2013-03-27 10:56:28.533    [DEBUG][5]    About to request async graph stop
2013-03-27 10:56:28.533    [DEBUG][10]    Graph stopping... (async)
2013-03-27 10:56:36.537    [DEBUG][5]    Async stop taking way too long
2013-03-27 10:56:36.537    [DEBUG][5]    Stop() appeared to have failed. Exiting...
2013-03-27 10:56:41.264    [INFO][5]    DigitalRecorder.StartStream(E:\Media\TV\This Morning\This Morning_20130327_10301230-3.ts)
2013-03-27 10:56:41.264    [DEBUG][5]    Starting graph...

Usually when I see this, the graph that wouldn't stop never really started correctly; was E:\Media\TV\This Morning\This Morning_20130327_10301230-2.ts watchable? If not it suggests your device only works correctly once.

I really don't think sub changed anything in this area of code between 2.5.9 and 2.6.2, but I could be wrong. Were you running with all patches up to "2.5.9 Post-R2 Rollup 2", or unpatched 2.5.9?

Has anything else changed at all? Added a device, moved to different USB ports? Maybe try a powered USB hub. Update drivers?

You could also try unchecking "use out-of-process digital recording" in Settings, but I think that will only move the graph stop hang into NRecord itself. Some have seen different behavior that way though...

[trummel]

Usually when I see this, the graph that wouldn't stop never really started correctly; was E:\Media\TV\This Morning\This Morning_20130327_10301230-2.ts watchable?

Yes, in fact I watched it whilst it was recording.

Were you running with all patches up to "2.5.9 Post-R2 Rollup 2"

Yes, although I wasn't using it extensively as I'd switched to a XBMC/tvheadend solution temporarily until it seemed pretty sure the client freeze issues were resolved. Didn't much like XBMC as a solution, its too awkward to use with a remote, but my family get very irate if they can't watch live tv reliably. Hence the switch back now:-{

Has anything else changed at all? Added a device, moved to different USB ports? Maybe try a powered USB hub. Update drivers?

No nothing else changed as far as I know, except perhaps some MS updates.

You could also try unchecking "use out-of-process digital recording" in Settings, but I think that will only move the graph stop hang into NRecord itself. Some have seen different behavior that way though...

I'll give it a go and see.

Thanks for the quick response BTW.

[trummel]

I unchecked 'use out-of-process digital recording". The only noticeable difference is that when nrecord crashed, I had to reboot the PC to get the tuner card back online.

So next, I disabled all of the tuner cards except the PCTV DVB-S2 card. When I played a live HDTV program, it appeared fine. When I stopped play however, it had the same "Async stop taking way too long" message in the log and when I tried to play again it crashed. I did the same with the DVB-T2 card and it did exactly the same, played once and then crashed.

[Zeb]

Your problems appear to be way over my head; but I wonder if the HD channels involved are H.264, and what measures you might have taken with respect to the Windows 7 platform update about a month ago?

http://forums.nextpvr.com/showthread.php...out-today&

[mvallevand]

You are the second 2.6.2 user with this troubling log entry (other link here http://forums.nextpvr.com/showthread.php...post454598 )

2013-03-27 10:55:44.577 [DEBUG][10] Marking recording (0) as 'Recording service restarted during recording'

It is highly unlikely that oid zero exists

Martin

[trummel]

Zeb, yes it is h.264, but I didnt install the problematic update, so i still have the old Microsoft decoder, but I've tried it with cyberlink pdvd12 as well. I think that would only affect playback anyway and the problem occurs if I just record.

Martin, that entry exists because i crashed out of the previous nrecord with a recording set in the EPG that never started because the previous recording failed to stop properly. If I start npvr with nothing already recording it doesn't happen.

[mvallevand]

Martin, that entry exists because i crashed out of the previous nrecord with a recording set in the EPG that never started because the previous recording failed to stop properly. If I start npvr with nothing already recording it doesn't happen.

I saw the proper entry but NRecord also seems to be creating this second bogus attempt.

Martin

[mvallevand]

Yes it creates that bogus value here too

2013-03-28 18:13:10.477 [DEBUG][7] Marking recording (0) as 'Recording service restarted during recording'

Hopefully this is harmless.

Martin

[johnsonx42]

@trummel:

on your system, what are the date/time stamps of the key NPVR program files such as NShared.dll, Unmanaged.dll, NUtility.dll, NextPVR.exe, NPVRTSMon.ax, etc.?