Recording service crashes

[Bobins]

Updated to the latest version last week without problems but since then, the recording service has become unreliable.

I'm getting several odd errors in the event log such as:-

The GB-PVR Recording Service service terminated unexpectedly. It has done this 1 time(s). (It always says 1 time !)

.NET Runtime version 2.0.50727.42 - Fatal Execution Engine Error (7A05E2B3) (80131506)

Faulting application gbpvrrecordingservice.exe, version 1.0.2614.27227, stamp 00000009, faulting module psiparser.ax, version 0.1.0.0, stamp 45be4d97, debug? 0, fault address 0x00019ea8.

Bucket 390438569, bucket table 1, faulting application gbpvrrecordingservice.exe, version 1.0.2614.27227, stamp 00000009, faulting module psiparser.ax, version 0.1.0.0, stamp 45be4d97, debug? 0, fault address 0x00019ea8.


I can't find anything in the log files about this and the recording icon on the task bar indicates it was recording at the time. Obviously that recording was lost and any other programmed recordings failed :mad:

Any ideas?

[HtV]

My 2cts: I'd do the "reregister filters". Hope it helps.

[sub]

Updated to the latest version last week without problems but since then, the recording service has become unreliable.

I'm getting several odd errors in the event log such as:-

The GB-PVR Recording Service service terminated unexpectedly. It has done this 1 time(s). (It always says 1 time !)

.NET Runtime version 2.0.50727.42 - Fatal Execution Engine Error (7A05E2B3) (80131506)

Faulting application gbpvrrecordingservice.exe, version 1.0.2614.27227, stamp 00000009, faulting module psiparser.ax, version 0.1.0.0, stamp 45be4d97, debug? 0, fault address 0x00019ea8.

Bucket 390438569, bucket table 1, faulting application gbpvrrecordingservice.exe, version 1.0.2614.27227, stamp 00000009, faulting module psiparser.ax, version 0.1.0.0, stamp 45be4d97, debug? 0, fault address 0x00019ea8.


I can't find anything in the log files about this and the recording icon on the task bar indicates it was recording at the time. Obviously that recording was lost and any other programmed recordings failed :mad:

Any ideas?

Are you running the most recent version of GB-PVR?

What capture device are you using?

[Bobins]

Hi Sub,

Was running 99.05 on a straight WindowsXP SP2 dedicated box. Cyberlink mux. I run 3 mpvs and 3 instances of GBPVR server (started manually).
Backed up database & xml files. Installed 99.12 and everything works as you would expect then, after about 24 hrs, the recording service bombs.

Tuner is Hauppauge Nova-T 500 dual digital tuner.

Just come home now to discover it bombed again last night :mad:

Last Night's errors :-

Service Control Manager
Event ID 7034
The GB-PVR Recording Service service terminated unexpectedly. It has done this 1 time(s).

.NET Runtime 2.0 Error
Event ID 5000
EventType clr20r3, P1 gbpvr.exe, P2 1.0.2614.27229, P3 5, P4 system, P5 2.0.0.0, P6 4333ae87, P7 2bb9, P8 17, P9 system.net.sockets.socket, P10 NIL.

NET Runtime 2.0 Error
Event ID 5000
Bucket 21200149, bucket table 5, EventType clr20r3, P1 gbpvr.exe, P2 1.0.2614.27229, P3 5, P4 system, P5 2.0.0.0, P6 4333ae87, P7 2bb9, P8 17, P9 system.net.sockets.socket, P10 NIL.

There are no apparent errors in the GBPVR logs.

Considering re-installing 99.05....too much grief from better half for losing her recordings!

[sub]

Hi Sub,

Was running 99.05 on a straight WindowsXP SP2 dedicated box. Cyberlink mux. I run 3 mpvs and 3 instances of GBPVR server (started manually).
Backed up database & xml files. Installed 99.12 and everything works as you would expect then, after about 24 hrs, the recording service bombs.

Tuner is Hauppauge Nova-T 500 dual digital tuner.

Just come home now to discover it bombed again last night :mad:

Last Night's errors :-

Service Control Manager
Event ID 7034
The GB-PVR Recording Service service terminated unexpectedly. It has done this 1 time(s).

.NET Runtime 2.0 Error
Event ID 5000
EventType clr20r3, P1 gbpvr.exe, P2 1.0.2614.27229, P3 5, P4 system, P5 2.0.0.0, P6 4333ae87, P7 2bb9, P8 17, P9 system.net.sockets.socket, P10 NIL.

NET Runtime 2.0 Error
Event ID 5000
Bucket 21200149, bucket table 5, EventType clr20r3, P1 gbpvr.exe, P2 1.0.2614.27229, P3 5, P4 system, P5 2.0.0.0, P6 4333ae87, P7 2bb9, P8 17, P9 system.net.sockets.socket, P10 NIL.

There are no apparent errors in the GBPVR logs.

Can you zip and attach the GB-PVR logs?

[Bobins]

Sub,

Logs as requested. I think the ones for the last crash (on 08/03/07) as still there. I have rebooted the system a couple of times since.

[Bobins]

Sub,
Just noticed that in the Search Guide if I search for a programme which should have multiple dates (say The News), I only see one time/date in the right hand box but it repeats multiple times all the way down the box. The same for any programme which should only show once. The same time/dat fills the box.
Is this likely to be connected to the DVB EPG bug and/or related to my problem?

[sub]

Sub,

Logs as requested. I think the ones for the last crash (on 08/03/07) as still there. I have rebooted the system a couple of times since.

I'm not really sure. I cant see an obvious cause in the logs.

[sub]

Sub,
Just noticed that in the Search Guide if I search for a programme which should have multiple dates (say The News), I only see one time/date in the right hand box but it repeats multiple times all the way down the box. The same for any programme which should only show once. The same time/dat fills the box.
Is this likely to be connected to the DVB EPG bug and/or related to my problem?

Yes. Did you apply the patch from the survival guide? Remember to do an 'empty EPG' after applying the patch.

[Bobins]

Hi,
Applied the patch, rebooted to a clean start, purged EPG and re-loaded.
Duplicates have now disssappeared.

Programmed a couple of shows for last night. Bombed again @00:54 :mad: no errors orher than the one in the system Event Log. Absolutely nothing shows in the GBPVR logs :confused:

The crash only happens whilst recording is actually taking place. The programmes are left flagged as "recording" in the recording schedule until the service is re-started. The 1st programme was 50% recorded and the 2nd one had been recording for 4 minutes. Both terminated at 00:54