"NMI: Parity Check / Memory Parity Error" While using Eagle 730-E

[Yaron Glazer]

Hello Guys!

I switched to a new computer (Dell OptiPlex 780).

I moved my Eagle 730-E card from one computer to another and installed LabView 8.5.

After I got everything installed I tried running my VI just to find that the computer crashes with a BSOD and the "NMI: Parity Check / Memory Parity Error" message.

Do you want me to provide the VI that caused the crash?

Thanks a lot for your help!

Kind regards,

Yaron Glazer.

[Tom_W_[DE]]

Hi Yaron-

An NMI failure is almost certainly related to a hardware malfunction or issue of some kind.  I would encourage you to contact Eagle Technology for help in troubleshooting this error.

Hopefully this helps-

[Yaron Glazer]

It worked up until now on another computer so I guess the card is not the problem, I also tried changing the RAM sticks to dual channel (2X2GB instead of 1X4GB) and also tried upgrading BIOS, didn't work, can you recommend on any further steps ?

[Elizabeth_K.]

Yaron,

Searching on Google provides quite a bit of information regarding this error and its possible problems. On our site, the only information I could find was KB 20N8H9LJ What Do I Do if I Receive a Memory Parity Error, Followed by a General Protection Fault? and this discussion forum with no resolution.

From Google, it seems like a hardware issue. Are you able to boot back up from the blue screen? Does anything else cause the blue screen? Does the BSOD always happen when you run that VI?

Regards,

Elizabeth K. 

National Instruments | Applications Engineer | www.ni.com/support 

[Tom_W_[DE]]

Elizabeth offers some good questions to consider, but I would also reiterate my suggestion to contact the manufacturer of your card.  It doesn't necessarily mean that the card is "broken" when you receive this error,  but you might be experiencing incompatibility problems with your new system.  The hardware manufacturer is in the best position to help you confirm whether this is the case, and, if so, to help with troubleshooting.