Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!mit-eddie!uw-beaver!zephyr.ens.tek.com!tektronix!nosun!qiclab!techbook!kenh
From: kenh@techbook.com (Ken Haynes)
Newsgroups: comp.dcom.lans
Subject: Re: NOVELL - Abend: NMI interrupt (memory parity error).
Keywords: error, NMI, diags_unsuccessful, help/suggestions_needed
Message-ID: <1990Nov7.140157.9904@techbook.com>
Date: 7 Nov 90 14:01:57 GMT
References: <1990Nov6.155258.8676@cs.odu.edu>
Distribution: usa
Organization: TECHbooks of Beaverton Oregon - Public Access Unix
Lines: 20

In article <1990Nov6.155258.8676@cs.odu.edu> perry@cs.odu.edu (Perry Lovill) writes:
>
>Our file server has been crashing with the above error message serveral
>times a day for the last week-and-a-half; and I am now at a complete loss
>(short of replacing the entire File Server) as to how to solve the problem.

Instead of just reseating the chips, have you tried to replace them?  "other"
hardware going flakey can also cause an NMI interrupt, check the disk drives
and LAN card if you have diagnostics for them.  Are there devices on the 
LPT and COM ports?  If not, can they be disabled?  When you performed your
netgen did you tell the linker there were LPT and COM ports in the system?
Have you added any new protocols to the wire lately?  Can your vendor help
in any way?

KEN
-- 
******************************************************************************
Network Support Services:

UUCP: {nosun, sequent, tessi} kenh@techbook