ButterworthHighpassFilter "Attempted to read or write protected memory"

[fjm1]

I have an application that runs 24x7 measuring and analyzing data once every minute.  Once every couple of days, I receive the following error:

"Attempted to read or write protected memory. This is often an indication that other memory is corrupt."

Only that measurement is effected and the application keeps functioning normally.  After adding debug statements that write to a log file I have narrowed down the error to the following line:

dblY = newFilter.FilterData(dblX)

where:

Dim newFilter As New Analysis.Dsp.Filters.ButterworthHighpassFilter(2, dblSampleFreq, dblCutoff)

Using the same dataset I am not able to reproduce this problem.  Is this potentially a memory  problem in the Analysis library?

I am using VB.Net 2008 and Measurement Studio's v8.6.0.189 with Alanysis.Enterprise v8.6.35.189.

Thanks,

Frank

[Michael_W.]

Hi Frank,

Please see this other discussion forum post as it sounds like it may be the same issue.

Cheers,

[fjm1]

I saw that thread.  It was posted in 2008, I thought it would not be relevant since it was related to software/firmware versions.

[Michael_W.]

 Hi Frank,

What operating system are you using?  If you haven't already you should try disabling DEP as a workaround because that fixed the issue in the other post?  Also, the problem in the other post seemed to be isolated to only certain machines.  Would it be possible to try on another machine and see if the behavior is reproduced?

Cheers, 

[fjm1]

We are running on Windows XP.  I will start with disabling DEP.  It does not happen often so it will take a week of running to feel confident it fixed the problem.

Thanks,

Frank

[fjm1]

DEP was disabled and the error still occurred after a week of running.

[Michael_W.]

Hi fjm1,

I'm sorry to hear that you're still seeing the problem.  To really dive into the cause of the error, we will need to be able to reproduce the error on our end.  Would it be possible for you to create a simple version of your code, preferably all in software, that still exhibits the issue? Please post back if and when you've uploaded the code.

Message Edited by Michael_W. on 05-06-2010 03:18 PM