LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

hardware error and system crash when dual core option ON

Hi,

running a large LabView application (LV 7.1) we thought that it would be reasonable to use a computer with a dual core  processor (pentium D). The program performance indeed increases a lot when dual core option turned on.  Unfortunately the system is always crashing completely unexpectable quite badly indicating the following code:
Hardware error detected
NMI memory parity check

Does anybody know what the problem might be?
We are using the PXI 6259 and PXI 6122 board

Thanks really a lot for any suggestions.


0 Kudos
Message 1 of 5
(3,291 Views)

"NMI memory parity check"

sounds like a hardware error. Try re-seating your memory and I/O devices.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 2 of 5
(3,289 Views)
Hi Ben,

thanks a lot for your quick answer!

What exactly do I need to do for re-seating memory and devices? I should also emphasize that the crash occurs regardless whether a AO, DIO operation is taking place or not.

Thanks in advance for any help or suggestions!
0 Kudos
Message 3 of 5
(3,270 Views)

Hi,

Could you please describe your system more in detail?

Which ni boards are you using and which driver versions and so on?

 

Thanks in advance!

Regards,

Evrem 

0 Kudos
Message 4 of 5
(3,246 Views)
Hi Evrem,

we are using a PXI system with PXI 6259 board for AO and digital input at sample clock rates up to 500 kHz for each channel (AO and DI running at the same rate, the AO sample clock being the sample clock source for the DI operation).  I should also mention that after a certain number of analog output updates new values are written to the output buffer (without stopping the running task) in order to  allow  fast  corrections of the outputted voltages.

However, we solved the problem sort of: With dual core option turned on we set the affinity of LabView at the windows task manager to only one CPU. The other CPU is free for other applications. Without changing the CPU affinity LV our program leads to a CPU load of 55 - 60 % (for the two CPUs altogether). What might now lead to a system crash is that one CPU tries to read out memory that hasn't been generated yet by the other CPU.

Thanks for any help or suggestions!

P.S.: we are using LV 7.1


0 Kudos
Message 5 of 5
(3,242 Views)