Jump to content

Recording Service restarting randomly


RenkliArif

Recommended Posts

Hi all,

 

I have recently built a new PC (GA-H81M-HD3 motherboard, 4GB RAM, i3 4130, onboard video) to use as a tv watching/recording server.

I have installed a TBS 6985 and 6991 for fta and encrypted channels (2x videoguard CAM)

I have installed recording service and configured DVBViewer as per the wiki. I'm unsure if I did it right as I am having some issues.

I have added some timers to the RS both FTA and encrypted channels. The issue is that the RS randomly crashes and sometimes restarts automatically. Whenever this happens the RS icon in the tray stays orange even though the RS is restarted with recording or not restarted at all.

I have looked at the various logs but couldn't really understand what was going on. Could anyone have a look and point me in the right direction?

(BTW, the third tuner of the 6985 isn't connected yet, that's why it doesn't have any groups enabled)

 

Link to comment

Today it has happened again twice. I am suspecting it has something to do with accessing and releasing one of the tuners from both of the cards. I think it happens when I try to tune a channel or a timer has ended. This however does not happen every time. I can reproduce it randomly.

support_new.zip

Link to comment

The issue seems to be related to TBS devices or drivers:

 

http://www.DVBViewer.tv/forum/topic/53849-DVBViewer-recording-service-goes-offline-when-deleting-a-timer/

 

Unfortunately I have no clue what can be done to work around this problem. Is the file tbsCIapi.dll present in your installation? it enables DVBViewer to access the CI, but turned out to be not very stable in the past. It may be worth to try without it, and if this doesn't work out, with an older driver version.

Link to comment

Hi Griga,

 

Thanks for your reply. Indeed I have the CI dll enabled (1.0.1.3 via the DVBViewer downloader)

I'll try different versions of the dll and see what happens. If all else fails I guess I will bother TBS about it =)

Link to comment

Well, it seems that the same thing happens with v1012 and v1010. I switched to DVBViewer only and as Griga mentioned it shows the CI dll in the error log.

I have contacted TBS and they will be sendimg me a "debug outputting dll" for testing. I will keep this thread updated whenever I book any progress on this issue :)

Link to comment

Hi RenkliArif,

 

Maybe I'm not completely understood your problem, how to use the tbsCIapi.dll?

Maybe your problem is related with my old problem (TBS6680): http://www.DVBViewer.tv/forum/topic/52956-DVBViewer-527/
"Support for multiple tbsCIapi.DLLs. If you use more than one CI in combination with more than one TBS card you should create additonal tbsCIapi's starting with tbsCIapi1.dll up to tbsCIapin.dll"
http://www.DVBViewer.tv/forum/topic/51059-dual-tuner-tbs6680/page-2#entry392146
http://www.tbsdtv.com/forum/viewtopic.php?f=89&t=8180&p=29862#p29862

 

Retiree

Edited by Tony
Link to comment

Hi Tony,

 

We seem to have similar issues with the cards. I do indeed have multiple copies of the DLL (switching them out with different versions as I go..)

The crashes usually happen whenever a tuner is being unloaded as far as I understand and look at the event log. In the CI DLL v1012 and v1010 DVBViewer just freezes with the following in event log:

 


Log Name: Application
Source: Application Hang
Date: 18.01.2014 14:59:10
Event ID: 1002
Task Category: (101)
Level: Error
Keywords: Classic
User: N/A
Computer: ArifServer-PC
Description:
The program DVBViewer.exe version 5.2.9.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: dec
Start Time: 01cf13e07a450dd6
Termination Time: 7126
Application Path: C:\Program Files (x86)\DVBViewer\DVBViewer.exe
Report Id: ad6fcc39-8048-11e3-a01c-94de80af4375

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Hang" />
<EventID Qualifiers="0">1002</EventID>
<Level>2</Level>
<Task>101</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-01-18T13:59:10.000000000Z" />
<EventRecordID>1287</EventRecordID>
<Channel>Application</Channel>
<Computer>ArifServer-PC</Computer>
<Security />
</System>
<EventData>
<Data>DVBViewer.exe</Data>
<Data>5.2.9.0</Data>
<Data>dec</Data>
<Data>01cf13e07a450dd6</Data>
<Data>7126</Data>
<Data>C:\Program Files (x86)\DVBViewer\DVBViewer.exe</Data>
<Data>ad6fcc39-8048-11e3-a01c-94de80af4375</Data>
<Binary>55006E006B006E006F0077006E0000000000</Binary>
</EventData>
</Event>

 

But if you have v1013 it actually mentions the dll itself:

 

 


Log Name: Application
Source: Application Error
Date: 18.01.2014 00:58:31
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: ArifServer-PC
Description:
Faulting application name: DVBViewer.exe, version: 5.2.9.0, time stamp: 0x2a425e19
Faulting module name: tbsCIapi1.dll_unloaded, version: 0.0.0.0, time stamp: 0x51c3c301
Exception code: 0xc0000005
Fault offset: 0x0f62c7fd
Faulting process id: 0xfb8
Faulting application start time: 0x01cf13dff5cb6020
Faulting application path: C:\Program Files (x86)\DVBViewer\DVBViewer.exe
Faulting module path: tbsCIapi1.dll
Report Id: 43e58abd-7fd3-11e3-b8ea-94de80af4375
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-01-17T23:58:31.000000000Z" />
<EventRecordID>1250</EventRecordID>
<Channel>Application</Channel>
<Computer>ArifServer-PC</Computer>
<Security />
</System>
<EventData>
<Data>DVBViewer.exe</Data>
<Data>5.2.9.0</Data>
<Data>2a425e19</Data>
<Data>tbsCIapi1.dll_unloaded</Data>
<Data>0.0.0.0</Data>
<Data>51c3c301</Data>
<Data>c0000005</Data>
<Data>0f62c7fd</Data>
<Data>fb8</Data>
<Data>01cf13dff5cb6020</Data>
<Data>C:\Program Files (x86)\DVBViewer\DVBViewer.exe</Data>
<Data>tbsCIapi1.dll</Data>
<Data>43e58abd-7fd3-11e3-b8ea-94de80af4375</Data>
</EventData>
</Event>

 

I'm still waiting for TBS to repsond. From what I have read from your posts this will probably take a long while. It is probably better to get rid of the cards and look for alternatives. I guess Digital Devices is the only way to go. Too bad they're pretty expensive.

I'll keep you all updated if something noteworthy happens along the way..

Link to comment
  • 11 months later...
×
×
  • Create New...