'Memory full', problem at loop tunnel.

[PHJOHNSON]

On running a previously functional VI on a new computer, I receive the error message: 'Memory is full. "filename" was stopped at loop tunnel "location"'. I can rectify the problem at individual tunnels, but the error merely cycles through each of them in turn. The computer memory is almost empty.

[Al_S]

What version(s) of LabView are on the new and old machines?
What OS(s) are on the new and old machines?
How much RAM is the in the new and old machines?
How much free disk space is on the new and old machines?
What virtual memory settings are on the new and old machines?
What is the VI doing?
What type and size of data is at the tunnel?
How do you "rectify the problem at individual tunnels"?
How do you know that "The computer memory is almost empty."?
What's wrong with answering a question with a question?

[PHJOHNSON]

It's LabView 5.1,
Both are using Windows,
128MB RAM on both,
28GB available on the new machine, 28.6GB on the old,
Automatic virtual memory on both,
The VI is sending a pulse to drive a stepper motor and recording data from a lock-in amp,
the tunnel connects a number (multiply) to an array,
I have rectified the tunnel problem as recommended in the manual by deleting and recreating them,
We've checked the computer memory, and it is a fairly new machine,
Nothing! Any help gratefully received!

[Al_S]

What version of Windows are you running on the old and new machine?
What is the size of the array?
Is the VI running on a loop?
If it's in a loop, on what iteration do you get the error message? Does it run for awhile before you get the error or is the error on the first iteration?
Have you tried Profile VIs, selecting Profile Memory Usage?

[PHJOHNSON]

Many thanks for your swift response: I suspect it's 95 or 98 on both, but I'll have to check- won't know until Monday, sorry,
The array is 2 or 3 depending on which data are required,
The error is encountered on the first iteration every time- previously I have been running up to 400 without difficulty.
I have not tried PVIs- I'm afraid that I am unfamiliar with the term- as you may have realised I am fairly inexperienced with computers, and am having to pick this up as I go along.
Many thanks again.

[PHJOHNSON]

I apologise for having wasted your time- I have solved the problem by removing some very stupid and obvious mistakes which resulted in a division by 0. Thanks anyway!