LabVIEW Crash

[B. Farhi]

Okay - here's a riddle.

My organization is running an extrememly complex LabVIEW program, and we're
having a recurring problem. The program will work fine for weeks or even
months at a time, but will then freeze requiring a hard reboot. We are ruinning
version 5.0.1 on a PII2333 (128MB) that has Win 95 4.00.95 B. We have the
system acquiring data from an HP 3497A, an SC-2070, and a couple of analog
output boards.

I remember from a LabVIEW course I once took that there may be a problem
using the Tick Count VI, since the value of the millisecond timer wraps
from 232-1 to 0. But whatever is causing this is crashing the whole PC, and
I'm uncertain as to whether a wrapping Tick Count would do that. Another
theory we had was that perhaps some c
ommunication error is occuring. I know
there's a lot of information I'm leaving out, but given all of this, does
anyone have any ideas as to what might be causing this problem?

Thanks for your help.


Brian Farhi

[charles adams]

Is there any consistency with what point the program crashes? If there isn't
then it may not be a labview problem at all. It seems as though your program
is working fine if it will run for months without having to be rebooted.
What kind of error is windows giving you? Could it be a windows problem
rather then a labview problem? You might also consider reinstalling Labview
and/or Windows or trying your program on another computer.
Also are there any other programs running on this machine other then the
Labview program, or is this a LabVIEW dedicated machine? Good luck finding
the bug, and let me know if I can be of any help!

Charley
Charles.r.adams@jpl.nasa.gov


B. Farhi" wrote in message
news:38bc217a@newsgroups.ni.com...
>
> Okay - here's a
riddle.
>
> My organization is running an extrememly complex LabVIEW program, and
we're
> having a recurring problem. The program will work fine for weeks or even
> months at a time, but will then freeze requiring a hard reboot. We are
ruinning
> version 5.0.1 on a PII2333 (128MB) that has Win 95 4.00.95 B. We have the
> system acquiring data from an HP 3497A, an SC-2070, and a couple of analog
> output boards.
>
> I remember from a LabVIEW course I once took that there may be a problem
> using the Tick Count VI, since the value of the millisecond timer wraps
> from 232-1 to 0. But whatever is causing this is crashing the whole PC,
and
> I'm uncertain as to whether a wrapping Tick Count would do that. Another
> theory we had was that perhaps some communication error is occuring. I
know
> there's a lot of information I'm leaving out, but given all of this, does
> anyone have any ideas as to what might be causing this problem?
>
> Thanks for your help.
>
>
> Brian Farhi
>

[Chris]

One of the undocumented "features" of Windows 95
is a memory leak. On large scale applications
that allocate and release memory, a little bit of
the memory will not be released. Over the course
of time the thing will eat all the available
memory and then crash. Get a Windows resource
indicator and watch the memory usage.

I have run into this problem with 3D CAD
applications that use LARGE amounts of memory and
I would have to reboot once or twice a day to
resolve the problem.

The only real solution (other than occasionally
rebooting) is to switch to Windows NT.

On 29 Feb 2000 13:43:54 -0600, "B. Farhi"
wrote:

>
>Okay - here's a riddle.
>
>My organization is running an extrememly complex LabVIEW program, and we're
>having a recurring problem. The
program will work fine for weeks or even
>months at a time, but will then freeze requiring a hard reboot. We are ruinning
>version 5.0.1 on a PII2333 (128MB) that has Win 95 4.00.95 B. We have the
>system acquiring data from an HP 3497A, an SC-2070, and a couple of analog
>output boards.
>
>I remember from a LabVIEW course I once took that there may be a problem
>using the Tick Count VI, since the value of the millisecond timer wraps
>from 232-1 to 0. But whatever is causing this is crashing the whole PC, and
>I'm uncertain as to whether a wrapping Tick Count would do that. Another
>theory we had was that perhaps some communication error is occuring. I know
>there's a lot of information I'm leaving out, but given all of this, does
>anyone have any ideas as to what might be causing this problem?
>
>Thanks for your help.
>
>
>Brian Farhi

[ej]

Windows 95 has a known bug that causes it to crash every 2^32
milliseconds (appx 50 days). This problem has to do with the operating
system. If this is your problem, I believe that Microsoft has a fix
for it on their site.

ej

In article <38bc217a@newsgroups.ni.com>,
"B. Farhi" wrote:
>
> Okay - here's a riddle.
>
> My organization is running an extrememly complex LabVIEW program, and
we're
> having a recurring problem. The program will work fine for weeks or
even
> months at a time, but will then freeze requiring a hard reboot. We
are ruinning
> version 5.0.1 on a PII2333 (128MB) that has Win 95 4.00.95 B. We have
the
> system acquiring data from an HP 3497A, an SC-2070, and a couple of
analog
> output boards.
>
> I remember from a LabVIEW course I on
ce took that there may be a
problem
> using the Tick Count VI, since the value of the millisecond timer
wraps
> from 232-1 to 0. But whatever is causing this is crashing the whole
PC, and
> I'm uncertain as to whether a wrapping Tick Count would do that.
Another
> theory we had was that perhaps some communication error is occuring.
I know
> there's a lot of information I'm leaving out, but given all of this,
does
> anyone have any ideas as to what might be causing this problem?
>
> Thanks for your help.
>
> Brian Farhi
>
>


Sent via Deja.com http://www.deja.com/
Before you buy.

[Markhl]

ej wrote:
>
> Windows 95 has a known bug that causes it to crash every 2^32
> milliseconds (appx 50 days). This problem has to do with the operating
> system. If this is your problem, I believe that Microsoft has a fix
> for it on their site.

At http://support.microsoft.com/support/kb/articles/q216/6/41.asp .

Best, Mark