NetServer LH 3 & Smart Array 3200 NMI: Memory Parity Error

[Samuel Cortez_1]

I've installed w2003 server on a netserver lh3.
S.O. is installed in a RAID1 volume attached to the NetRaid controller (C:), and i have 1 storage unit attached to the Smart array 3200 controller, which have 2 volumes (D: y E:) The problem is when i copy and paste or move files from any volume on the storage to volume C: or to the other volume in the storage.
the server stops responding and display a blue screen with the following message:

*** Hardware Malfunction
Call your hardware vendor for support
*** The system has halted ***
NMI: Parity Check / Memory Parity Error


Firmware, Drivers, BIOS, ACU are up to date.
From C: to D: or E: no problems, only from D: to C: or From E: to C:
I also have tried remplacing memory, removing other devices and nothing

Any Suggestions???

Best regards.

[Greg Carlson]

Samuel,

Normally memory is the cause of NMI parity errors. Third party memory in netservers caused this error a lot!
Install ITT (instant top tools and check for single and or multiple bit errors)
http://tinyurl.com/5f56b (Link for ITT)

Ciao,
Greg

[Samuel Cortez_1]

The server has 3 128MB compaq DIMM's, and I´ve tested many utilities and diagnostic tools without errors or alarms.

I would like to know if there is a way to configure the smart array 3200 other than Array Configuration Utility (ACU), i mean by BIOS?

I Know it is possible in ProLiant Servers by pressing Ctrl+A at booting, but i don't know how to configure on a NetServer L

[Greg Carlson]

Samuel,
Try to run with the standard memory that originally shipped with the LH 3. Also the SAC 3200 was obviously never tested or supported in the LH 3. The Netraid utility is accessed by Ctrl-M, the SAC is accessed by its own keyboard short cut, I think its ctrl-9.

Ciao,
Greg

[e4services]

My take would be to blame the 3200 or Windows. A Windows drive cache or 3200 cache memory or the timeing beteen the 2. See if windows is running write caching on the "C:", that would explain why only when writing to "C:".
Or just plain drive disfunctionality on one of those 2 old controllers.