Today, server netware 6.5 sp6 abended again.
Up to now, it abended 4 times this year, 1.26 3.22 5.4 and today.
Everytime occurred, the abend.log showed same messege:
"
Additional Information:
The CPU encountered a problem executing code in NCPIPX.NLM. The problem may be in that module or in data passed to that module by a process owned by SERVER.NLM.
"
I found an article "Server abending. NCPIPX.NLM top of stack."
I don't know whether it helps, i'll try it later.
10071071: Server abending. NCPIPX.NLM top of stack.

I'm a newbie to netware, this error almost drove me crazy. Here is part of the sys$log.err and abend.log
Thanks for your help.

sys$log.err
***********************************
8-23-2011 2:03:39 pm: SERVER-5.70-4631
Severity = 3 Locus = 18 Class = 6
WARNING! Server LXSZ_HQ experienced a critical error. The offending process was suspended or recovered. However, services hosted by this server may have been affected.

abend.log
***********************************
Novell Open Enterprise Server, NetWare 6.5
PVER: 6.50.06

Server LXSZ_HQ halted Tuesday, August 23, 2011 2:03:43.239 pm
Abend 2 on P00: Server-5.70.06: Page Fault Processor Exception (Error code 00000000)

Registers:
CS = 0008 DS = 0010 ES = 0010 FS = 0010 GS = 0010 SS = 0010
EAX = 00000000 EBX = 86F0ECE0 ECX = 00000000 EDX = 90AB41A0
ESI = 9153A280 EDI = 8604ED20 EBP = 86EEAC04 ESP = 86EEABBC
EIP = 8E321E19 FLAGS = 00010046
8E321E19 8B5F04 MOV EBX, [EDI+04]=?
EIP in NCPIPX.NLM at code start +00003E19h
Access Location: 0x8604ED24

The violation occurred while processing the following instruction:
8E321E19 8B5F04 MOV EBX, [EDI+04]
8E321E1C 807F1800 CMP [EDI+18], 00
8E321E20 0F850A020000 JNZ 8E322030
8E321E26 8B7708 MOV ESI, [EDI+08]
8E321E29 8B4318 MOV EAX, [EBX+18]
8E321E2C 85C0 TEST EAX, EAX
8E321E2E C6863A01000000 MOV [ESI+0000013A], 00
8E321E35 0F84AA010000 JZ 8E321FE5
8E321E3B C6467002 MOV [ESI+70], 02
8E321E3F 8B531C MOV EDX, [EBX+1C]

Running process: Server 5 Process
Thread Owned by NLM: SERVER.NLM
Stack pointer: 86EEAC84
OS Stack limit: 86EE3020
CPU 0 (Thread 87A21280) is in a NO SLEEP state
Scheduling priority: 67371008
Wait state: 5050090 Wait for interrupt
Stack: 870ADDD2 (LSL.NLM|LSLServiceEvents+72)
--9153A2C0 ?
90A6FDEA (MSM.NLM|CMSMServiceEvents+A)
--00000002 (LOADER.NLM|KernelAddressSpace+2)
--8FD303DC (ETHERTSM.NLM|CEtherTSMGetConfigInfo+5F2F)
--8FD349C0 (ETHERTSM.NLM|CEtherTSMGetConfigInfo+A513)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--86EEAC04 (IDECD.CDM|StringF+9A50)
90A8D779 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--8FD33E1C (ETHERTSM.NLM|CEtherTSMGetConfigInfo+996F)
--90AB41A0 ?
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--8FD33DDE (ETHERTSM.NLM|CEtherTSMGetConfigInfo+9931)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--8FD303DC (ETHERTSM.NLM|CEtherTSMGetConfigInfo+5F2F)
--0F1E0188 ?
--86EEAC44 (IDECD.CDM|StringF+9A90)
90A8D557 ?
--8FD303DC (ETHERTSM.NLM|CEtherTSMGetConfigInfo+5F2F)
--86EEAC38 (IDECD.CDM|StringF+9A84)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--00000003 (LOADER.NLM|KernelAddressSpace+3)
-870B97B0 (LSL.NLM|AdapterLockTable+40)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--0000001C (LOADER.NLM|KernelAddressSpace+1C)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
90A69CEE (MSM.NLM|MSMAESProcedure+1AE)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--0F1E0188 ?
--8FD313BC (ETHERTSM.NLM|CEtherTSMGetConfigInfo+6F0F)
90A70659 (MSM.NLM|CMSMValidateAuxDataBuffer+99)
--8FD303DC (ETHERTSM.NLM|CEtherTSMGetConfigInfo+5F2F)
--0F1E0188 ?
90A69CB2 (MSM.NLM|MSMAESProcedure+172)
--8FD303DC (ETHERTSM.NLM|CEtherTSMGetConfigInfo+5F2F)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--00000082 (LOADER.NLM|KernelAddressSpace+82)
870AC58A (LSL.NLM|LSLPollProcedure+4A)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--00010001 ?
003684BA (SERVER.NLM|DirectCallPollProcedures+A)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
0021108C (SERVER.NLM|CallRegisteredPollingRoutines+44)
--00010001 ?
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--00000046 (LOADER.NLM|KernelAddressSpace+46)
0022DA31 (SERVER.NLM|MpkSystemWork+61)
--00010001 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
00221AC6 (SERVER.NLM|SchedSwitch+31E)
--8F861000 ?
--22A51879 ?
--D01C829F ?
--00000046 (LOADER.NLM|KernelAddressSpace+46)
00218A02 (SERVER.NLM|RealCSleepUntilInterrupt+52)
--86EEAD00 (IDECD.CDM|StringF+9B4C)
--8848C040 ?
--0F1E0328 ?
00367D3F (SERVER.NLM|SleepUntilInterrupt+C)
--000007C6 (LOADER.NLM|KernelAddressSpace+7C6)
--000007C6 (LOADER.NLM|KernelAddressSpace+7C6)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--0000138D (LOADER.NLM|KernelAddressSpace+138D)
8E321B7B (NCPIPX.NLM|Case100+185)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--423798A0 ?
--60DBE4A8 ?
--000007C7 (LOADER.NLM|KernelAddressSpace+7C7)
--86EEAD00 (IDECD.CDM|StringF+9B4C)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--000002B3 (LOADER.NLM|KernelAddressSpace+2B3)
--00000514 (LOADER.NLM|KernelAddressSpace+514)
--87A21280 (IDEATA.HAM|ProceedToProcessInterrupt+36B0)
--86EEACE0 (IDECD.CDM|StringF+9B2C)
--91097D00 (NLSLSP.NLM|NLSGetInternalVersionInfo+9487)
--0000051C (LOADER.NLM|KernelAddressSpace+51C)
--000002B3 (LOADER.NLM|KernelAddressSpace+2B3)
8E321A6B (NCPIPX.NLM|Case100+75)
91090100 (NLSLSP.NLM|NLSGetInternalVersionInfo+1887)
8E31FBF7 (NCPIPX.NLM|FinishUpPacket+C6)
--870DE271 ?
-86324490 (NCPIPX.NLM|IPXReplyProceduresVector+0)
--870DE224 ?
--0000005A (LOADER.NLM|KernelAddressSpace+5A)
--86EEAD38 (IDECD.CDM|StringF+9B84)
--0000021A (LOADER.NLM|KernelAddressSpace+21A)
--7D058085 ?
--00000046 (LOADER.NLM|KernelAddressSpace+46)
00108EC6 (LOADER.NLM|kSpinUnlockRestore+26)
--00000046 (LOADER.NLM|KernelAddressSpace+46)
87A2965C (HPQCISS.HAM|(Code Start)+465C)

Additional Information:
The CPU encountered a problem executing code in NCPIPX.NLM. The problem may be in that module or in data passed to that module by a process owned by SERVER.NLM.