Latest PsiParser.ax and Data Execution Prevention errors

[kayfam]

sub,
Not to keep hounding you about this but I'm still experiencing DEP problems even with the latest patches from the survival guide. I try to initiate a QAM scan and it crashes the config.exe each and every single time with a DEP error. Everything else seems to be fine such as recording, watching live TV, I can even preview already scanned channels in the config, but try to initiate a scan and *crash*. Swapping in place the old PsiParser and I can scan without issue minus some channels that keep coming up missing.
At this point after looking at all sides of the issue I think the problem actually resides in the config.exe itself. You did mention something about changing some of the logic involved with the latest patches and my guess something is occuring that the config.exe is not able to compensate for. Logs are useless as everything looks normal up to the point of the crash and the windows dump shows nothing that makes sense to me. I can provide you with a copy of it will be of any help, just say the word.

[sub]

Sorry, I dont have any fix for you yet. I had two guys testing patches and producing logs all weekend to try to to get to the bottom of it, but we didnt find the cause yet. I got busy with with work, so had to push it aside for a bit. I'm hoping to get back to it over the next coupld of days.

Out of curiosity, what capture card do you have?

[kayfam]

Hauppauge HVR-1800

[sub]

I was pretty sure you were going to say either a 1800 or 1600. The problem seems to be related to the garbage these device's tuner can deliver immediately after tuning to a new channel. Something about the new code is less tolerant of this garbage.

I just wish I could reproduce the problem here....

[Bobins]

Sub,

I often get this too on scanning (with the last patch) and Im using a Pinnacle card although it's not a big problem as I haven't needed to scan very often.

Just frustrating when it's nearly at the end of the scan and bombs out so you have to start again

[sub]

I'm looking into it.

[soccerdad]

I have seen this problem as well but did not relate it to the psiparser but I know it started when I was working on the .ts stuff. I too have an HVR-1800. Note that I am NOT scanning when this happens. My symptoms don't show up consistently. Just sometimes I can't change a channel or things quit working right so I close and try to reboot. Instead of rebooting I get a DEP error. I also have noticed that the tray icon does not always turn green when watching a channel. Usually it does, but not always like it used to. Perhaps a clue? Or totally unrelated. I will try to keep track of what I was doing next time I see it.

[sub]

I'm not sure it'll fix the problem, but give this patch a go and let me know if it helps.

[kayfam]

Almost there sub, but a few issues with this patch. While it completes a scan it's misidentifying the video/audio type in the stream on some channels. For example

Code:

T:99,0,0~P:1~V:3774~VTYPE:H264~A:69~PMT:71~PCR:72~N:>99.1  * (000(AC3)) or T:97,0,0~P:70~V:5009~A:4002~PMT:5008~PCR:5009~N:>97.70  Unknown9 (000(AAC))

when they should be

Code:

T:99,0,0~P:1~V:72~A:69~PMT:71~PCR:72~N:>99.1  * (000(AC3)) or T:97,0,0~P:70~V:5009~A:5010~PMT:5008~PCR:5009~N:>97.70  Unknown9 (000(AC3))

Any attempt to tune any such channel results in either a black screen and or lockup of the GUI and crash back to desktop for obvious reasons. Attached are the logs from the last scanning session.

[sub]

Can you make a 100MB 'full ts' recording available, so I cant check it here?

I wouldnt have expected anything changed in PsiParser.ax in recent days to effect the PIDs identified during a scan.