Recording service crash - "checking signal status"

[Mister Slimm]

Just had an odd error, first time I've seen it.

The end of one recording finished ten minutes into the start of another and this was when the service appeared to crash. My Slimm GB-PVR caught it and restarted the recording service and it appears to be fine now. The logs (see the -1 logs for GBPVRRecordingService.exe and GBPVRRecordingService.exe.Native) are full of "Checking signal status" and related on my digital tv card.

I'm not concerned about this at this time as it is a one-off but is presented here for your information. All logs enclosed.

[Mister Slimm]

The recording service crashed a total of three times now, each time with the same repeating message in the logs. I have now rebooted.

The recording appeared to complete without problem when the service was restarted.

Windows sent three error reports to Microsoft this morning. GB-PVR logs attached.

[sub]

Is there an entry in the Windows Event Viewer when this happens? If so, what does it say?

[Mister Slimm]

In reverse order for the second crash. The first crash has the same error entries but the recording service was started much earlier in the day and had successfully completed at least one recording.

Both crashes occurred trying to record BBC3.

Code:

Event Type:    Information
Event Source:    .NET Runtime 2.0 Error Reporting
Event Category:    None
Event ID:    1001
Date:        20/03/2007
Time:        11:09:55
User:        N/A
Computer:    SLIMM03
Description:
Bucket 326675306, bucket table 1, faulting application gbpvrrecordingservice.exe,
version 1.0.2445.14611, stamp 00000038, faulting module psiparser.ax, version 0.1.0.0,
stamp 44ff4dd7, debug? 0, fault address 0x000018c4.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 42 00 75 00 63 00 6b 00   B.u.c.k.
0008: 65 00 74 00 3a 00 20 00   e.t.:. .
0010: 33 00 32 00 36 00 36 00   3.2.6.6.
0018: 37 00 35 00 33 00 30 00   7.5.3.0.
0020: 36 00 0d 00 0a 00 42 00   6.....B.
0028: 75 00 63 00 6b 00 65 00   u.c.k.e.
0030: 74 00 54 00 61 00 62 00   t.T.a.b.
0038: 6c 00 65 00 20 00 31 00   l.e. .1.
0040: 0d 00 0a 00               ....

Code:

Event Type:    Information
Event Source:    .NET Runtime 2.0 Error Reporting
Event Category:    None
Event ID:    1001
Date:        20/03/2007
Time:        11:09:51
User:        N/A
Computer:    SLIMM03
Description:
Bucket 398713280, 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 0x00019eb1.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 42 00 75 00 63 00 6b 00   B.u.c.k.
0008: 65 00 74 00 3a 00 20 00   e.t.:. .
0010: 33 00 39 00 38 00 37 00   3.9.8.7.
0018: 31 00 33 00 32 00 38 00   1.3.2.8.
0020: 30 00 0d 00 0a 00 42 00   0.....B.
0028: 75 00 63 00 6b 00 65 00   u.c.k.e.
0030: 74 00 54 00 61 00 62 00   t.T.a.b.
0038: 6c 00 65 00 20 00 31 00   l.e. .1.
0040: 0d 00 0a 00               ....

Code:

Event Type:    Information
Event Source:    .NET Runtime 2.0 Error Reporting
Event Category:    None
Event ID:    1001
Date:        20/03/2007
Time:        11:09:49
User:        N/A
Computer:    SLIMM03
Description:
Bucket 398713240, 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 0x00019eb6.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 42 00 75 00 63 00 6b 00   B.u.c.k.
0008: 65 00 74 00 3a 00 20 00   e.t.:. .
0010: 33 00 39 00 38 00 37 00   3.9.8.7.
0018: 31 00 33 00 32 00 34 00   1.3.2.4.
0020: 30 00 0d 00 0a 00 42 00   0.....B.
0028: 75 00 63 00 6b 00 65 00   u.c.k.e.
0030: 74 00 54 00 61 00 62 00   t.T.a.b.
0038: 6c 00 65 00 20 00 31 00   l.e. .1.
0040: 0d 00 0a 00               ....

Code:

Event Type:    Information
Event Source:    GB-PVR Recording Service
Event Category:    None
Event ID:    0
Date:        20/03/2007
Time:        11:02:41
User:        N/A
Computer:    SLIMM03
Description:
Service started successfully.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Thanks.

[sub]

Is there a file created in c:\windows\minidump when this occurs?

[sub]

I'm guessing there is a momentary drop in signal quality and GB-PVR tries to process a garbage transport stream packet, which ends up leading to some fault. I try to be careful for these types of situations, but its hard to test every possible garbage scenario.

Alternatively, is always occurring on one particular mux? ie, one of several DVB channels sharing the same frequency. If that is the case, then its possible there is something (non-garbage) in the stream that GB-PVR doesnt like. If that is the case, we could get you to record a full ts so I can play it back here.

[Mister Slimm]

Windows\Minidump is currently empty though Windows did send a report with three GBPVRRecordingService.exe entries when I turned the machine back on this morning.

Yes it occurred on the same channel, BBC3, each time. However, the recordings also completed successfully with just a gap where the service crashed and was restarted.

I have something set to record on BBC3 tonight at 8:30pm, then 1:40am. We'll see what happens then.

[Mister Slimm]

Just successfully completed two recordings on the same channel, BBC3.

[Mister Slimm]

Hmm, it's just done it again. It was recording okay on BBC3, digital tuner 1 when a recording on analogue tuner 1 finished and the recording service crashed.

[sub]

Bump the thread if I havnt responded in a few days. PC problems at mo, so not really in a position to look into anything.