Recordings fail after first few

[three_sheds]

I have a long standing problem with recordings failing. It seems that the first dozen or so recordings work fine, then all subsequent recordings fail. A reboot will allow the next dozen or so recordings to work, then they start to fail again etc....

I've had the problem since I upgraded from 0.99 to 1.2.13. I recently upgraded to 1.3.11 in the hope that the problem may have been addressed, but I still have the same symptoms. It happened the first time with 1.3.11 tonight, so I have zipped and attached the logs. I've also included a jpg to show the times/names of failed recordings (and the last good one). I copied the logs after a reboot (which I did out of habit), so I'm not sure whether the useful log data would have been overwritten or not?

Any help would be much appreciated, as the recordings invariably fail when my wife wants to record somethings that she's really keen to watch - you can guess the rest!

I'm using a dual Nova T500 tuner card, by the way.

Many thanks.

[three_sheds]

I’ve been trawling through my logs of the above problem (although I don’t know what half of it means) and re-reading some posts. I noticed that ‘GBPVRRecordingService.exe-native-1.log’ spans the period from 12th March – 22nd March (04:29) and ‘GBPVRRecordingService.exe-native.log’ starts on 25th March at 22:21, when I re-booted my PC. Given that the first failed recording was on 22nd March (18:55), can I deduce that the recording service was not running from 04:29 on 22nd until I re-booted?

My off-air EPG updates around 04:00, there always appears to be a lot of activity around this time in the GBPVRRecordingService logs, but none after 22nd until the re-boot.

Also, the EPG activity (assuming that’s what it is), usually seems to finish around 04:15, but on 22nd it went on until 04:29 (again I’m assuming that this was EPG activity). Could something have gone wrong with the EPG on this night and crashed the recording service?

Assuming that the recording service has stopped, presumably I can just configure the windows service so it auto restarts if it stops (as in this thread: http://forums.nextpvr.com/showthread.php?t=25751)? Although my preference would be to address the underlying problem, rather than masking it.

Any feedback very much appreciated.

Thanks.

[three_sheds]

I've just been looking at my event logs from the problem period, there are 3 relevant ones:

04:14 [System Event] : Virtual memory too low
04:29 [Application Event] : Faulting application gbpvrrecordingservice.exe, version 1.0.3299.13249, stamp 00000033, faulting module wmvcore.dll, version 9.0.0.3267, stamp 4720cbc0, debug? 0, fault address 0x0006c9ba. [Source: .NET Runtime 2.0 Error Reporting]
04:43 [System Event] : GB-PVR Recording Service terminated unexpectedly

I can see anything relevant in the forums about wmvcore.dll, but understand that it's required to replay .wmv files. So, I'm not entirely sure why it would be being used during an EPG update..?

I've set up the recording service to (hopefully) re-start on failure via services.msc, but I'd really like to stop it crashing in the first place. Anyone got any suggestions??

Thanks in anticipation.