v1.1.5 recording service stopping

[tgp]

ok, thanks, the patch is in... let's see what develops

[tgp]

Recording service stopped recording mid-day today.

It appears to have successfully recorded 11:00-12:00, and 2 or 3 LiveTVs during the 1300 hour, but a 14:00 there was an error for a LiveTV event, and later recording events at 1700,1800, 1900 did not record.

My son, doing the LiveTV events, was "watching" from the Guide Menu, and when the program ended at 1400, he selected another, but received the NoTuners available msg on GBPVR. He's doing this via MVP, btw.

Code:

2008-01-03 14:00:14.906    VERBOSE    [12]    About to switch live tv file to: F:\Recordings\LiveTV\The Emperors New School_2_20080103_14001430.mpg
2008-01-03 14:00:15.609    VERBOSE    [12]    Finished switch
2008-01-03 14:00:15.687    VERBOSE    [12]    RenewLease finished
2008-01-03 14:00:31.484    VERBOSE    [12]    Received request to stop livetv: 2
2008-01-03 14:00:31.484    VERBOSE    [12]    Stopping live tv recording...
2008-01-03 14:00:31.484    VERBOSE    [12]    Stopping recording oid:2
2008-01-03 14:00:31.671    VERBOSE    [7]    Received request to stop livetv: 2
2008-01-03 14:00:31.671    VERBOSE    [7]    Stopping live tv recording...
2008-01-03 14:00:31.671    VERBOSE    [7]    Stopping recording oid:2
2008-01-03 14:00:43.843    VERBOSE    [7]    Starting LiveTV for captureSource: 2 channel oid: 31  filename:
2008-01-03 14:00:43.843    VERBOSE    [7]    getValue cached value: /settings/LiveTVDirectory : F:\Recordings\LiveTV
2008-01-03 14:00:43.859    VERBOSE    [7]    Temporary live TV filename: F:\Recordings\LiveTV\Cheat!_2_20080103_14001430.mpg
2008-01-03 14:00:43.859    VERBOSE    [7]    DirectRecordingSource about to start recording  oid:2 channel:57
2008-01-03 14:00:44.078    ERROR    [7]    Error starting live tv recording: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
2008-01-03 14:05:16.156    VERBOSE    [10]    Checking if GB-PVR can remove: F:\Recordings\LiveTV\Kim Possible_2_20080103_13301400.mpg
2008-01-03 14:05:16.156    VERBOSE    [10]    LiveTV file removed: F:\Recordings\LiveTV\Kim Possible_2_20080103_13301400.mpg
2008-01-03 14:05:17.234    VERBOSE    [10]    Checking if GB-PVR can remove: F:\Recordings\LiveTV\The Emperors New School_2_20080103_14001430.mpg
2008-01-03 14:05:17.234    VERBOSE    [10]    LiveTV file removed: F:\Recordings\LiveTV\The Emperors New School_2_20080103_14

in native log:

Code:

2008-01-03 13:30:17.453    VERBOSE    ConexantRecorder::StartNewFile() finished
2008-01-03 14:00:14.906    VERBOSE    ConexantRecorder::StartNewFile(F:\Recordings\LiveTV\The Emperors New School_2_20080103_14001430.mpg, 48)
2008-01-03 14:00:14.906    VERBOSE    getSetting(LiveTVAnalogQuickFileSwitch)
2008-01-03 14:00:15.031    VERBOSE    put_Channel(48, AMTUNER_SUBCHAN_DEFAULT, AMTUNER_SUBCHAN_DEFAULT)
2008-01-03 14:00:15.234    VERBOSE    Hardware Revision: 0x0117
2008-01-03 14:00:15.234    VERBOSE    Product ROM: 0x0117
2008-01-03 14:00:15.250    VERBOSE    Attempting to auto detect MSP Standard
2008-01-03 14:00:15.453    VERBOSE    Standard Result = 0x0020
2008-01-03 14:00:15.453    VERBOSE    Status = 0x0110
2008-01-03 14:00:15.609    VERBOSE    ConexantRecorder::StartNewFile() finished
2008-01-03 14:00:31.484    VERBOSE    ConexantRecorder::StopRecording()
2008-01-03 14:00:31.671    VERBOSE    ConexantRecorder::StopRecording()
2008-01-03 14:00:32.109    ERROR    Unexpected error stopping recording. No details available.
2008-01-03 14:00:32.109    ERROR    Unexpected error stopping recording. No details available.
2008-01-03 14:00:32.109    VERBOSE    ConexantRecorder::Done()
2008-01-03 14:00:32.203    VERBOSE    ConexantRecorder::Done()
2008-01-03 14:00:43.859    VERBOSE    ConexantRecorder::StartRecording(2, 1, 57, 0)
2008-01-03 14:00:43.859    VERBOSE    target filename: F:\Recordings\LiveTV\Cheat!_2_20080103_14001430.mpg
2008-01-03 14:00:43.859    VERBOSE    Loading filter names
2008-01-03 14:00:43.859    VERBOSE    Found names:

also in the native log at the 132209 mark is

2008-01-03 13:22:09.343 VERBOSE ConnectPins: 'Audio Decoder Out' to 'Analog Audio In'
2008-01-03 13:22:09.359 VERBOSE FindFilterByName(refCLSID, GB-PVR Writer, 1)
2008-01-03 13:22:09.359 VERBOSE FindFilterByName:1
2008-01-03 13:22:09.359 VERBOSE FindFilterByName:2
2008-01-03 13:22:09.359 VERBOSE FindFilterByName:3.1
2008-01-03 13:22:09.359 VERBOSE FindFilterByName:3.2
2008-01-03 13:22:09.359 VERBOSE FindFilterByName:3.3
2008-01-03 13:22:09.359 VERBOSE FindFilterByName:3.1
2008-01-03 13:22:09.359 VERBOSE FindFilterByName:3.2
2008-01-03 13:22:09.359 VERBOSE FindFilterByName:3.3

this FindFilterByName repeats for pages and pages in the log prior to the
ConexantRecorder::StartRecording() done

is this a clue?

full logs attached, minus the MVP logs

[sub]

Next time this error happens, but before you restart the recording service, can you run the FilterCheck.exe from the GB-PVR directory, then zip and attach the filtercheck.log that gets created?

[tgp]

ok, failed to record Dr. Who at 5am (darn)

filtercheck logs attached

[sub]

Sorry, I dont know. I'm not sure why you're getting this.

Maybe try updating your Hauppauge drivers. The problem seems to occur when trying to access the device filters.

[tgp]

Well, let me ask a couple of specific questions, which may illuminate something else...

I have a PVR350 and PVR150 loaded into this system. The PVR350 software drivers are all that I've ever loaded, since that was the first board into the system. Later on (2-3 months later) when the 150 showed up, it was recognized by the system automatically, but GBPVR only saw it as a 250.

It seemed to operate fine under 99.12 and 1.0.8 in this manner, for a couple of months. I never saw a need to change it.

I did see something similar (filter issues) to this in late Oct/early Nov, where the findfilter couldn't get it for device #2
http://forums.nextpvr.com/showthread.php?t=30715

Then I tried drivers from Hauppauge 's website, loaded them in, but couldn't get a successful recording, out of either WinTV or GBPVR. I backed out all Hauppauge and GBPVR software, reinstalled as if new system, drivers came off the CD, again only the 350 drivers, the 150 never asked for anything. Worked ok for about a week, until I started this thread (Nov15), since the behaviour was slightly different.

- Is it possible to have 2 different boards running the same drivers?
- Is GBPVR seeing the 150 as a 250 anything to worry about
- loading the latest drivers from the website seemed to not help, since nothing would record

can you (or anyone) point me to a link for the latest drivers, maybe my googing last November got me to drivers that were just broken, and since I backout at that point...

Remember, for this system, now, I just reimaged it over Christmas, it has a fresh copy of XPSP2, the Hauppage drivers from the 350 CD, and 1.1.5 GBPVR - that's it

Tom

[sub]

I'm not expert on Hauppauge PVR150 vs 350 drivers, so cant answer your questions on that. You can usually get the most recent Hauppauge drivers from http://www.shspvr.com/smf.

[tgp]

Yesterday I put a used eBay PVR-500 MCE into my GBPVR system. I will probably put the 350 and the 150 up for sale on eBay, but for now, I'll confirm in about a week or two, if I'm still having any errors with the recording service.

I removed the cards, their corresponding drivers and other Hauppauge software and then installed the PVR500 and it's drivers. Only config changes, EPG, for GBPVR...

Here's hoping for the best, but I'll let you know.

[tgp]

yesterday, Jan 19, 1900 hrs, (about 2 days of running) recording service stopped again - again complaining about the "memory error" - in this case, when my son tried to do a live recording from an MVP

Code:

2008-01-19 19:00:06.015    VERBOSE    [7]    Starting LiveTV for captureSource: 3 channel oid: 67  filename:
2008-01-19 19:00:06.015    VERBOSE    [7]    getValue cached value: /settings/LiveTVDirectory : F:\Recordings\LiveTV
2008-01-19 19:00:06.171    VERBOSE    [7]    Temporary live TV filename: F:\Recordings\LiveTV\Resident Evil_3_20080119_19002100.mpg
2008-01-19 19:00:06.171    VERBOSE    [7]    DirectRecordingSource about to start recording  oid:3 channel:79
2008-01-19 19:00:06.750    ERROR    [7]    Error starting live tv recording: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
2008-01-19 19:00:15.953    VERBOSE    [7]    Starting LiveTV for captureSource: 3 channel oid: 67  filename:
2008-01-19 19:00:15.953    VERBOSE    [7]    getValue cached value: /settings/LiveTVDirectory : F:\Recordings\LiveTV
2008-01-19 19:00:15.953    VERBOSE    [7]    Getting current programme from cache
2008-01-19 19:00:15.953    VERBOSE    [7]    Temporary live TV filename: F:\Recordings\LiveTV\Resident Evil_3_20080119_19002100.mpg
2008-01-19 19:00:15.953    VERBOSE    [7]    DirectRecordingSource about to start recording  oid:3 channel:79
2008-01-19 19:00:15.953    VERBOSE    [7]    Stopping recording oid:3
2008-01-19 19:00:16.484    ERROR    [7]    Error starting live tv recording: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
2008-01-19 19:05:52.234    VERBOSE    [10]    Checking if GB-PVR can remove: F:\Recordings\LiveTV\Psych_3_20080119_18001900.mpg
2008-01-19 19:05:52.515    VERBOSE    [10]    LiveTV file removed: F:\Recordings\LiveTV\Psych_3_20080119_18001900.mpg
2008-01-19 19:07:48.625    VERBOSE    [7]    Starting LiveTV for captureSource: 3 channel oid: 67  filename:
2008-01-19 19:07:48.625    VERBOSE    [7]    getValue cached value: /settings/LiveTVDirectory : F:\Recordings\LiveTV
2008-01-19 19:07:48.625    VERBOSE    [7]    Getting current programme from cache
2008-01-19 19:07:48.625    VERBOSE    [7]    Temporary live TV filename: F:\Recordings\LiveTV\Resident Evil_3_20080119_19002100.mpg
2008-01-19 19:07:48.625    VERBOSE    [7]    DirectRecordingSource about to start recording  oid:3 channel:79
2008-01-19 19:07:48.625    VERBOSE    [7]    Stopping recording oid:3

This is with the 500 tuners installed and the other boards/drivers removed.

Sorry, I forgot to do the filtercheck log, but in this case, I don't think it's the same error. The Jan 4 error was also a protected memory error msg... Two different things going on?

This is extremely frustrating.

[tgp]

another "memory" exception

2008-01-21 03:43:23.846 ERROR [7] Error starting live tv recording: Attempted to read or write protected memory.

as noted this was for live tv, but then at 04:00 was a scheduled recording, and it went into the "FindFilter" repeating loop

SlimmPVR eventually got in the act and tried to restart the recording service, so I don't know if it was successful (thus messing up the filterlog) but it's in the attachment anyway.

Probably the root cause is the original error 17 minutes prior?

I have another PC like this, I could probably swap disks and move the tuner cards, that would eliminate or prove as a cause any true memory issue, since it would be using different memory (and proc)... Is this worth doing?