GBPVRRecordingS error after reinstalled PVR-150 driver.

[EdCepse]

It worked like a charm until I reinstalled the PVR-150 driver--because I found a new one came out. The time I reinstalled the driver, timed recording with GBPVR would give me this error message: "Application has generated an exception that could not be handled. Process id = 0x334(820), Thread id = 0x2b0 (688). " If I don't click "OK" to terminate the application (GBPVRRecordingService.exe) it would keep recording without stopping.

I tried to reinstall GBPVR, or uninstall both PVR-150 and GBPVR and reinstall them, but the problem was still there. Please suggest what I should do. I am attaching the screen of the error message. Thank you sooo much!

My computer:
Win2K
P4 2.8G
PVR-150
1G Mem

[jridley]

I'm having the same problem. I installed on an existing Windows setup, but the main app locked whenever I tried to watch a video as it was being recorded. So I started from scratch, reinstalled everything, using the latest drivers. Watching live TV works OK but I get this error when a scheduled recording is trying to start. Any ideas?

[betlit]

could both of you reproduce the problem and zip & post the log-files here?

[wtg]

This error happens with certain versions of the 150 drivers... there are other threads about it. When it was happening to me, it only occurred with the composite inputs - I could record off coax fine. Others experienced the problem on both inputs.

You don't mention what drivers you've installed, but try reinstalling your old version andsee if the problem goes away. Personally, I like the 23035 version as it doesn't have the mpg timeline problems all the current releases have that I've tried, though others have said the 23083 works well too.

[jridley]

Last night I reverted my boot drive to a clean Win install, then reinstalled using the CD the 150 shipped with over a year ago. Got the same thing which is confusing since it was working before. Could be some other interaction.
I don't have the problem anymore since I reverted the boot drive to a previously working configuration. It's not a clean install but it's working so I'll stick with it. If I hit further problems I may revisit this issue and be able to send logs.