Recording Service crashing

[audiolab]

I have just recently purchased a WinTV-PVR150 card and have been trying for over a week to get GBPVR working with it.
I have changed PCI slot locations for the card, installed the newest drivers from the Hauppauge website, tried multiple installs, and I have finally tried only installing the PVR150 drivers, MPEG decoder and IR software (no WinTV) to see if there is some conflict with GBPVR.
My main problem is that even though GBPVR installs with no problem, the IR blaster and IR control work fine, and I can select channels through my satellite box and watch tv on my PC, every time I try recording I get the "Application has generated an exception that could not be handled" error that I have read about others on this forum experiencing. What's even worse is that when this error happens, at times it causes the IR hardware/software to crash and stop functioning. The only solution at that point is to go through the Hauppauge IR blaster setup software again and re-boot the machine. Even though the error occurs, GBPVR does record the program, at least until I reboot the PC. So, the card seems to be functioning properly and playback works fine too.
This is on a new PC with very little installed on it:

P4 HT 2.8GHz, 800MHz FSB
512meg DDR2 ram
Windows XP home (not MCE) SP2
XGI Volari V3XT video card

I don't see any error flags in the recording service logs, but I can post them if that would help.
Are there any obvious things that I can check?
This software looks REALLY great, I just wish it would work on my system!

Thanks for your help!

Andrew

[sub]

Can you zip and attach your GBPVRRecordingService.exe.log and GBPVRRecordingService.exe-native.log?

[audiolab]

Here you go:

[sub]

There is nothing obvious in the logs, but there was a group of PVR150 owners that had this same crash recently. They resolved the issue by upgrading to a newer version of the drivers, which can be found at http://www.shspvr.com/smf

[audiolab]

Hmmm...I am running the latest drivers from the Hauppauge website.
2.0.35.23258

Are others maybe using a beta version driver to solve this issue?

Thanks for your help!

Andrew

[sub]

Yes, there are newer drivers at the website I mentioned. I dont think the necessarily had to be newer drivers. I think this problem was probably just caused by a specific version of the drivers. You may also find older ones correct it.

Maybe try 2.0.35.23297 from http://www.shspvr.com/smf/index.php?topic=9008.0

[audiolab]

Will do.
I'll let you know how it turns out.
Thanks!