Environment: AS 2000 SP3 (Standard) on Win2K SP3

We have a server running over 70 AS databases with an average of about 4
cubes in each. What we have found recently is that when the virtual memory
consumption for AS goes over about 1.6Gb, MDX queries start returning
incorrect values. Interestingly, the values that are wrong are only a very
small percentage of all results returned and they differ from the correct
results by only a small margin.

By restarting AS, the problems go away (for a while at least). Note that
this is on a production server, and no cube processing is done there.

Anyone seen anything like this before?

TerryF