Same problems. this abend happens randomly during the school year. it doesnt happen all summer long but, when hte kids come back then it starts up again.

>I have a netware 3 sp4 server


Actually it's NW6SP5 . You might try nwlib6b.exe as your abend is in LIBC
--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://support.novell.com/forums
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.


I have a netware 3 sp4 server which gets the following abend once every couple weeks. The server will then stop responding
completely. Any help would be great. Please let me know if you need any additional info.
thanks again!!


Server Temp halted Tuesday, March 22, 2005 8:40:54.335 am
Abend 1 on P00: Server-5.60.05: Page Fault Processor Exception (Error code 00000002)

Registers:
CS = 0008 DS = 0010 ES = 0010 FS = 0010 GS = 0010 SS = 0010
EAX = 000000FB EBX = FFFFFFFB ECX = 3FFFFADF EDX = 8C415170
ESI = 8C4165EC EDI = 8AA89FFD EBP = 8AA88B3C ESP = 8AA88B10
EIP = C8DF7138 FLAGS = 00010213
C8DF7138 F2A5 **REPNE*MOVSD
EIP in LIBC.NLM at code start +0008A138h
Access Location: 0x8AA8A000

The violation occurred while processing the following instruction:
C8DF7138 F2A5 **REPNE*MOVSD
C8DF713A 2403 AND AL,03
C8DF713C 8AC8 MOV CL,AL
C8DF713E F2A4 **REPNE*MOVSB
C8DF7140 8B44240C MOV EAX,[ESP+0C]
C8DF7144 5E POP ESI
C8DF7145 5F POP EDI
C8DF7146 C3 RET
LIBC.NLM|memcmp:
C8DF7147 57 PUSH EDI
C8DF7148 56 PUSH ESI

Running process: Server 00:20 Process
Thread Owned by NLM: SERVER.NLM
Stack pointer: 8AA89F80
OS Stack limit: 8AA82040
Scheduling priority: 67371008
Wait state: 50500F0 Waiting for work
Stack: --8C41516F ?
--8AA88B81 ?
839FDF2B ?
--8AA88B81 ?
--8C415170 ?
--FFFFFFFB (LOADER.EXE|KernelTempAliasesEnd+FFB)
--0000000F ?
--00000000 ?
--849130C8 ?
--00000004 ?
--00000002 ?
--8AA88F7C ?
839FD0F2 ?
--00007945 ?
--8C41516F ?
--00000001 ?
--00000002 ?
--8AA88B6C ?
--00000004 ?
--00000000 ?
--00000000 ?
--00000028 ?
--01000000 (UKBDSHIM.NLM|__NLM_BSS_End+1B54)
--314C4F56 ?
--53552F3A ?
--2F535245 ?
--534F564C ?
--53524554 ?
--736F4C2F ?
--696E6120 ?
--656C616D ?
--72672073 ?
--65646E61 ?
--65732073 ?
--646E6120 ?
--6E616261 ?
--6C657020 ?
--646E6165 ?
--6F6C206F ?
--6E612073 ?
--6C616D69 ?
--63207365 ?
--75716968 ?
--736F7469 ?
--646E6120 ?
--6E616261 ?
--72657020 ?
--6F646964 ?
--20792073 ?
--20736F6C ?
--61706170 ?
--69762073 ?
--7265696E ?
--79206E6F ?
--736F6C20 ?
--70617020 ?
--6C207361 ?
--64207365 ?
--72656A69 ?
--6C206E6F ?
--7020736F ?
--65726461 ?
--6F642073 ?
--2065646E ?
--61747365 ?
--7420206E ?
--736F646F ?
--736F6C20 ?
--72746F20 ?
--6320736F ?
--75716968 ?
--736F7469 ?
--6C207920 ?
--6320736F ?
--6C616261 ?
--20736F6C ?
--72657566 ?
--61206E6F ?
--61676120 ?
--72617272 ?
--75676120 ?
--65642061 ?
--6564206C ?
--72656973 ?
--65206F74 ?
--6E6F746E ?
--20736563 ?
--20736F6C ?
--61632033 ?
--6C6C6162 ?
--636F642E ?
--00000000 ?
--00000010 ?
--0000001C ?
--00000000 ?
--00000000 ?
--2F6D8CA3 ?
--000083D7 ?
--2F6D8CA3 ?
--00000000 ?

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