2007-08-16, 05:41 PM
Despite having installed the hotfix described in the survival guide I'm still getting more and more of these 'Attempted to read or write protected memory' errors:
2007-08-16 13:37:00.640 ERROR [5] Error starting recording: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at NativeUtilities.ConexantRecorder.StartRecording(String cardType, ConexantRecordSource recordingSource, Int32 qualitySetting, Int32 board, String filename, Int32 channel, Int32 countryCode, Int32 tuningType, Boolean useStreamingEngineIfAvailable, Boolean previewMode, Boolean fmRadioMode, Boolean fmRadioPreviewMode)
at GBPVR.Backend.Common.DirectRecordingSource.startRecording(IRecordingSourceConfiguration config, Int32 qualitySetting, String filename, ChannelTuning channelTuning, Int32 minutes, Boolean useStreamingEngineIfAvailable)
at GBPVR.RecordingService.x93f60a55016d55c4.xcba1f05fb5a46d5f()
I'm running AVG A/V so I think I'll disable that for a short while and see if it goes away - is anyone else running AVG?
Are there other reasons for this error?
I'm running 1.0.16 on XP.
Thanks in advance for any help.
2007-08-16 13:37:00.640 ERROR [5] Error starting recording: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at NativeUtilities.ConexantRecorder.StartRecording(String cardType, ConexantRecordSource recordingSource, Int32 qualitySetting, Int32 board, String filename, Int32 channel, Int32 countryCode, Int32 tuningType, Boolean useStreamingEngineIfAvailable, Boolean previewMode, Boolean fmRadioMode, Boolean fmRadioPreviewMode)
at GBPVR.Backend.Common.DirectRecordingSource.startRecording(IRecordingSourceConfiguration config, Int32 qualitySetting, String filename, ChannelTuning channelTuning, Int32 minutes, Boolean useStreamingEngineIfAvailable)
at GBPVR.RecordingService.x93f60a55016d55c4.xcba1f05fb5a46d5f()
I'm running AVG A/V so I think I'll disable that for a short while and see if it goes away - is anyone else running AVG?
Are there other reasons for this error?
I'm running 1.0.16 on XP.
Thanks in advance for any help.