I am not a Netware expert, so it's difficult for me to diagnose.

I recently started a new job, and inherited a Netware 6.5 server, running BackupExec 9.1 that has some hardware issues. It runs on an HP Proliant350 G4.

The server started having issues over 6 months ago, and even though it absolutely business critical, apparently nobody thought it would be a good idea to actually fix it.
So the problems have been getting progressively worse, from abending occasionally during backups (with an NMI error), to abending every other day during the backup.

I'll attach the abend log at the end.

The abend log had a line about possible bad memory, so I replaced the memory yesterday. Matters actually got worse. Now instead of restarting, it freezes completely with the Health light turning red, and fault leds next to the new memory strips going amber. (Even though the memory is new and is the right part number, and tests successfully at boot)

If I disable the backups, the system doesn't fail. But that is obviously not acceptable.

I opened a case at HP to see if they could help.
I was wondering if anyone here would have any ideas...

Log:
Novell Open Enterprise Server, NetWare 6.5
PVER: 6.50.07

Server LIVE halted Monday, July 26, 2010 6:46:41.320 pm
Abend 1 on P00: Server-5.70.07: NMI (Uncorrectable memory error) Processor Exception (Error code 000000B0)

Registers:
CS = 0008 DS = 0010 ES = 0010 FS = 0010 GS = 0023 SS = 0010
EAX = 8A149A90 EBX = 91E01380 ECX = 00001A34 EDX = 00001070
ESI = 8A152140 EDI = A1522830 EBP = 00000000 ESP = 9A793D7C
EIP = 00362AAD FLAGS = 00010206
00362AAD F3A5 REP MOVSD
EIP in SERVER.NLM at code start +0016240Dh

The violation occurred while processing the following instruction:
00362AAD F3A5 REP MOVSD
00362AAF 2403 AND AL, 03
00362AB1 8AC8 MOV CL, AL
00362AB3 F3A4 REP MOVSB
00362AB5 5F POP EDI
00362AB6 5E POP ESI
00362AB7 C3 RET
SERVER.NLM|CMovW:
00362AB8 56 PUSH ESI
00362AB9 57 PUSH EDI
00362ABA 8B74240C MOV ESI, [ESP+0C]



Running process: VxNDMP_9939d3c0 Process
Thread Owned by NLM: NDMPD.NLM
Stack pointer: 9A793CEC
OS Stack limit: 9A784660
Scheduling priority: 67371008
Wait state: 5050100 Delayed
Stack: --00001070 (LOADER.NLM|KernelAddressSpace+1070)
--0000EF90 (LOADER.NLM|KernelAddressSpace+EF90)
99465533 (NDMPD.NLM|BE_NDMPD_CheckUnloadOK+E76F)
--8A149A80 ?
--A151A170 ?
--0000EF90 (LOADER.NLM|KernelAddressSpace+EF90)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--9A793DFC ?
9947B7D8 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--0000FFEA (LOADER.NLM|KernelAddressSpace+FFEA)
--0000FFEA (LOADER.NLM|KernelAddressSpace+FFEA)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--9A793DDC ?
--0000FFEA (LOADER.NLM|KernelAddressSpace+FFEA)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--FFFF0016 ?
--0000FFE9 (LOADER.NLM|KernelAddressSpace+FFE9)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--8A147280 ?
--00010000 (LOADER.NLM|KernelAddressSpace+10000)
--8A149A80 ?
--91E01380 ?
99488A12 ?
--91E01380 ?
--8A149A80 ?
--00010000 (LOADER.NLM|KernelAddressSpace+10000)
--9A793E04 ?
9947D4ED ?
--91E01380 ?
--8A149A80 ?
--00010000 (LOADER.NLM|KernelAddressSpace+10000)
--0000FFE9 (LOADER.NLM|KernelAddressSpace+FFE9)
--FFFF0016 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--0000FFEA (LOADER.NLM|KernelAddressSpace+FFEA)
--9A7943E0 ?
--0000FFEA (LOADER.NLM|KernelAddressSpace+FFEA)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--8A147280 ?
9949F98C ?
--9A7943E0 ?
--8A147280 ?
--95B604E4 ?
--95B604E4 ?
--00000004 (LOADER.NLM|KernelAddressSpace+4)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--9A793ED0 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--95B604E4 ?
--9A793ED4 ?
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--9A793E98 ?
--95B604E4 ?
--00000004 (LOADER.NLM|KernelAddressSpace+4)
--9A793ED0 ?
95A62361 (SMSUT.NLM|NWSMPutFirstName+60)
--95AA4E06 ?
--00000004 (LOADER.NLM|KernelAddressSpace+4)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--9A793ED0 ?
--9A793ED4 ?
--00000004 (LOADER.NLM|KernelAddressSpace+4)
--95B604E4 ?
--9A793EB8 ?
0022030F (SERVER.NLM|kGetThreadStackInfo+37)
--980090E0 ?
--9A793EB4 ?
--9A793EB8 ?
--9A793EE8 ?
--9A793EA4 ?
--9A793EC8 ?
--00000005 (LOADER.NLM|KernelAddressSpace+5)
--95AA4BE4 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
90296D1F (THREADS.NLM|free+F)
--95A53180 ?
95A677C5 (SMSUT.NLM|NWSMFreeString+1C19)
--95A53180 ?
--95AA4BE4 ?
--9A793EE8 ?
--00000005 (LOADER.NLM|KernelAddressSpace+5)
--95AA4BE4 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
95A621EB (SMSUT.NLM|NWSMCloseName+63)
--95A53180 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--9A793F1C ?
95BC6A2F (TSAFS.NLM|internTsaKSpinLock+F)
--95B60304 ?
--9665F1E0 ?
95BC6A70 (TSAFS.NLM|tsaKSpinUnlock+20)
--95B60304 ?
--9A793F70 ?
95BC1654 (TSAFS.NLM|JOB_QueueScannedDataSet+1E4)
--9665F24C ?

Additional Information:
There may be some bad memory either on an adapter card or on the motherboard. If the problem continues, try replacing the main system memory or adapter cards to prevent future parity errors.

Loaded Modules:
NWNATIVE.NLM Native Method Implementations for Java Beans