Can anyone lend a hand on this abend?

Thanks,
John

Novell Open Enterprise Server, NetWare 6.5
PVER: 6.50.07

Server ********* halted Sunday, May 10, 2009 3:59:30.795 am
Abend 1 on P00: Server-5.70.07: Page Fault Processor Exception (Error code 00000000)

Registers:
CS = 0008 DS = 0010 ES = 0010 FS = 0023 GS = 0023 SS = 0010
EAX = 00000010 EBX = A6923108 ECX = 445D1200 EDX = 8F49100E
ESI = A6922B40 EDI = 8F49100E EBP = 445D1200 ESP = A6922A90
EIP = 8F412828 FLAGS = 00010286
8F412828 668B0A MOV CX, [EDX]=?
EIP in WS2_32.NLM at code start +00012828h
Access Location: 0x8F49100E

The violation occurred while processing the following instruction:
8F412828 668B0A MOV CX, [EDX]
8F41282B 6683F906 CMP CX, 0006
8F41282F 0F85F3000000 JNZ 8F412928
8F412835 83F80E CMP EAX, 0000000E
8F412838 0F82D0000000 JB 8F41290E
8F41283E BFBC88438F MOV EDI, 8F4388BC
8F412843 B9FFFFFFFF MOV ECX, FFFFFFFF
8F412848 33C0 XOR EAX, EAX
8F41284A F2AE REPNE SCASB
8F41284C B8FEFFFFFF MOV EAX, FFFFFFFE



Running process: NLSLRUP HK Process
Thread Owned by NLM: NLSLRUP.NLM
Stack pointer: A6922888
OS Stack limit: A691F1C0
Scheduling priority: 67371008
Wait state: 5050030 Blocked on Semaphore
Stack: 89A06EFC (UNICODE.NLM|unicode_to_byte+7C)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--A6922AB4 ?
--A6922AB8 ?
--A6922AB0 ?
--00000010 (LOADER.NLM|KernelAddressSpace+10)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--445D1220 ?
--A692301C ?
--00000010 (LOADER.NLM|KernelAddressSpace+10)
--8F6FF000 ?
--00000010 (LOADER.NLM|KernelAddressSpace+10)
--A692300C ?
--445D1200 ?
89A0AAC6 (LOCNLM32.NLM|NWUXUnicodeToUntermByte+C6)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--445D1200 ?
--A692300C ?
--FFFFFFFF ?
--00000010 (LOADER.NLM|KernelAddressSpace+10)
--A6922AF0 ?
--A6922AF4 ?
--A6922AF8 ?
--00000010 (LOADER.NLM|KernelAddressSpace+10)
--00000010 (LOADER.NLM|KernelAddressSpace+10)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--A692300C ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--445D1200 ?
--A692300C ?
--445D1200 ?
--A692300C ?
--445D1200 ?
--8F49100E ?
--00000010 (LOADER.NLM|KernelAddressSpace+10)
--A6922B6C ?
8F42B5C4 (WS2_32.NLM|WSAAddressToStringW+28)
--8F49100E ?
--00000010 (LOADER.NLM|KernelAddressSpace+10)
--A6922B6C ?
--445D1200 ?
--A6923108 ?
--A6922B40 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--445D1200 ?
--8F49100E ?
--00000010 (LOADER.NLM|KernelAddressSpace+10)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
8F42B4F1 (WS2_32.NLM|WSAAddressToStringA+E1)
--8F49100E ?
--00000010 (LOADER.NLM|KernelAddressSpace+10)
--A6922B6C ?
--445D1200 ?
--A6923108 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
-91F77590 (NLSMETER.NLM|(Data Start)+5590)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--00000020 (LOADER.NLM|KernelAddressSpace+20)
--A6922D18 ?
--8F48822C ?
91ABB67E (BTRIEVE.NLM|btrvID+26)
--0000000F (LOADER.NLM|KernelAddressSpace+F)
-91F775A0 (NLSMETER.NLM|(Data Start)+55A0)
--A6922BC4 ?
--A6922D9C ?
--A6922D54 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
-91F77590 (NLSMETER.NLM|(Data Start)+5590)
91F6B3DE (NLSMETER.NLM|ProdAudGetNextTranAddrRecord+C77)
--0000000F (LOADER.NLM|KernelAddressSpace+F)
-91F775A0 (NLSMETER.NLM|(Data Start)+55A0)
--A6922BC4 ?
--A6922D9C ?
--A6922D54 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
-91F77590 (NLSMETER.NLM|(Data Start)+5590)
--10000030 ?
--00740001 ?
--12010000 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
00300001 (SERVER.NLM|InitializeSetParametersFromRegistry+20 5)
--00740100 ?
--000B0000 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--02010000 ?
--00008000 (LOADER.NLM|KernelAddressSpace+8000)
--00000007 (LOADER.NLM|KernelAddressSpace+7)
--00000007 (LOADER.NLM|KernelAddressSpace+7)
--828B3740 ?
00321423 (SERVER.NLM|xxAllocateSlab+48F)
--828B3740 ?
--AD365000 ?
--919A3F98 ?
--919A3DC0 ?
--00001220 (LOADER.NLM|KernelAddressSpace+1220)
--00008000 (LOADER.NLM|KernelAddressSpace+8000)

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