Recording service crash report

[Mister Slimm]

At the risk of being extraordinarily unhelpful, my recording service crashed.

The computer had been running fine for days, successfully recording this that and the other. Several recordings had completed throughout Saturday including ones on the channel which seemed to cause the final crash (Film Four).

One film was recording on ITV3, another started on Film Four but it didn't seem to start very successfully. A good number of minutes (may have been about 10 minutes) after the Film Four recording started, the recording service crashed out. I restarted the recording service and looked at the partial video file but it was corrupted in some way and displayed a new frame only every few seconds. It was also less than a minute in length despite being started a while ago.

I wasn't doing anything intensive on the computer at the time, I was just reading some web pages on interface design.

Anyways, here are all my logs if that's any help. [ATTACHMENT NOT FOUND]

[Mister Slimm]

Windows Error Reporting got around to sending its report about 12 hours later.

Error signature
AppName: gbpvrrecordingservice.exe
AppVer: 1.0.2379.26393
AppStamp:00000014
ModName: psiparser.ax
ModVer: 0.1.0.0
ModStamp:449f6f14
fDebug: 0
Offset: 000018c4

Looking at this signature, I can comment that this is about the sixth time I've seen an error report where the ModName was psiparser.ax.

There is a 15Mb memory dump also but I suspect you won't want to be looking through that!

[sub]

It sounds like a bug in my PSI Parser module. It will be caused by something in the DVB transmission that GB-PVR does not like. Its hard to guess what exactly that is.

How often is this happening? There is a registry setting I can get you to enable to give more info, but it generates massive files, so it might not be something we want to unless we can predict the error is going to occur.

[Mister Slimm]

How often is this happening?

Since 97xx about once a week which was often enough for me to write an auto-restart into SlimmGBPVR when it couldn't get any info from the recording service.

Oddly, even though I have instructed Windows to restart the recording service up to three times if its crashes, it never does. But Windows does know it has crashed because, hours later, it asks me to send a delayed report to Microsoft.

There is a registry setting I can get you to enable to give more info, but it generates massive files, so it might not be something we want to unless we can predict the error is going to occur.

I can do that. I have plenty of hard drive space but I cannot recreate the error purposefully and, while I get the impression it tends to happen when using both tuners on my card, I have plenty of side-by-side recordings that occur just fine.

Thanks

[sub]

Please note, I did warn you in advance that this could be a massive file...

If you set HKEY_LOCAL_MACHINE\Software\devnz\LogPSIProcessing=1 (DWORD), then it'll produce a c:\psi.log whenever the DVB card is in use.

[sub]

Terratec Cinergy 2400i Twin Digital Tuner

I can do that. I have plenty of hard drive space but I cannot recreate the error purposefully and, while I get the impression it tends to happen when using both tuners on my card, I have plenty of side-by-side recordings that occur just fine.

Hmm, this may be a problem. The psi.log will probably only contain the logs for one device. I'll think about this some more. Probably still worth trying it though...

[Mister Slimm]

Hmm, now this didn't cause the recording service to crash but I did get a zero-byte recording. World Rally Championship was recording on ITV (tuner freeview #2). That finished and I stopped the recording and deleted it. A French film started about five minutes later on Film Four. The recording service reported that it was recording merrily but it wasnt. The file was 0 bytes long. The recording service was still running in services.msc.

I only noticed that the recording was zero bytes after 10 or so minutes. I didn't restart the recording service though I am certain that the recording would have progressed normally from then on if I had. I manually stopped the recording, zipped the psi.log ([ATTACHMENT NOT FOUND]), then restarted the recording service.

[sub]

That isnt really the sort of thing that would show anything in psi.log. It'll only really be useful in the case where the recording service crashes.

[Mister Slimm]

Okay, recording service finally did it's "I've crashed but I've not" thing last night. I've attached the [ATTACHMENT NOT FOUND] which froze in length as is. The .mpg file it was supposed to be recording froze at 5,422KB but misreported its' length when you try to play it as just 40 seconds.

According to the services snap-in, GB-PVR Recording Service was still running. I haven't had the Windows error report appear yet but it only tends to appear after a few hours of uptime the following day. Restarting the recording service brought everything back to normal.

I've recorded about 40 hours of shows since the last crash. There is 16.5Gb of free space on the recording drive.

Thanks

[Mister Slimm]

In addenda, the Microsoft report finally materialised:
AppName: gbpvrrecordingservice.exe
AppVer: 1.0.2379.26393
AppStamp:00000014
ModName: psiparser.ax
ModVer: 0.1.0.0
ModStamp:449f6f14
fDebug: 0
Offset: 000018c4