2008-06-06, 03:24 AM
(This post was last modified: 2008-06-06, 03:47 AM by crlorentzen.)
Windows XP SP3
Hauppauge HVR-1800 fresh install of latest drivers
QAM channels
GBPVR 1.2.13 new install
I was scrolling through the QAM channel lineup using my mouse when the PVRX2 application just vanished. No error message, no Microsoft Report.
I then re-opened PVRX2 and proceeded to the live TV again and continued scrolling up and down through the QAM Channels. PVRX2 crashed again this time with the option to report to Microsoft.
Logs collected after restarting the GBPVR recording service. Includes the first and second event.
GBPVR configuration
Renderer: VMR9 Custom
MPEG 2 Video Codec InterVideo NonCSS Video Decoder also tried and had the same failure with MainConcept (HCW) MPEG-2 Video Decoder (I had selected MPEG Video Decoder, but directshow must have selected the other codec
All other codes system default.
Using Live Preview Mode
Using <BDASubmitTuningRequestTwiceOnLivePreview> true
I guess the next step would be to test with 1.2.9 and see if it shows the same issue, but I don't have the time tonight.
Hauppauge HVR-1800 fresh install of latest drivers
QAM channels
GBPVR 1.2.13 new install
I was scrolling through the QAM channel lineup using my mouse when the PVRX2 application just vanished. No error message, no Microsoft Report.
I then re-opened PVRX2 and proceeded to the live TV again and continued scrolling up and down through the QAM Channels. PVRX2 crashed again this time with the option to report to Microsoft.
Logs collected after restarting the GBPVR recording service. Includes the first and second event.
GBPVR configuration
Renderer: VMR9 Custom
MPEG 2 Video Codec InterVideo NonCSS Video Decoder also tried and had the same failure with MainConcept (HCW) MPEG-2 Video Decoder (I had selected MPEG Video Decoder, but directshow must have selected the other codec
All other codes system default.
Using Live Preview Mode
Using <BDASubmitTuningRequestTwiceOnLivePreview> true
I guess the next step would be to test with 1.2.9 and see if it shows the same issue, but I don't have the time tonight.