ABEND in NDPS v3.00b

[sven....@wilm.ppdi.com]

I received, and continue to receive the following ABENDs:

Server WIL-SERV halted Monday, January 26, 2004 10:54:04 am
Abend 1 on P00: Server-5.00k: Page Fault Processor Exception (Error code
00000000)

Registers:
CS = 0008 DS = 0010 ES = 0010 FS = 0010 GS = 0010 SS = 0010
EAX = 0E345559 EBX = 0FD041DC ECX = 4EBA5A70 EDX = 0E345520
ESI = C7BA5000 EDI = 0E345520 EBP = C7862904 ESP = C78628E4
EIP = D5240358 FLAGS = 00010202
D5240358 8A06 MOV AL,[ESI]=?
EIP in LIBC.NLM at code start +00042358h
Access Location: 0xC7BA5000

The violation occurred while processing the following instruction:
D5240358 8A06 MOV AL,[ESI]
D524035A 8803 MOV [EBX],AL
D524035C 46 INC ESI
D524035D 43 INC EBX
D524035E 49 DEC ECX
D524035F 85C9 TEST ECX,ECX
D5240361 75F5 JNZ D5240358
D5240363 EB16 JMP D524037B
D5240365 01CE ADD ESI,ECX
D5240367 01CB ADD EBX,ECX

Running process: NDPSM 339340 Process
Created by: NetWare Application
Thread Owned by NLM: NDPSM.NLM
Stack pointer: C7862764
OS Stack limit: C785EBC0
Scheduling priority: 67371008
Wait state: 5050100 (Delayed)
Stack: --C71B6500 ?
--5056472C ?
D157F0FC (DPRPCNLM.NLM|ndps_svc_getrpccaller+D3C)
--0E345520 ?
--C61E6344 ?
--5056472C ?
--00000000 ?
--C71B6500 ?
--C7862920 ?
D157F666 (DPRPCNLM.NLM|ndps_xdr_opaque+46)
--C71B6500 ?
--0E345520 ?
--5056472C ?
--C71B6500 ?
--5E8AA164 ?
--C7862950 ?
D157F7E1 (DPRPCNLM.NLM|ndps_xdr_bytes+D1)
--C71B6500 ?
--0E345520 ?
--5056472C ?
00056911 (LOADER.EXE|GetRealModeInterruptMask+1F3B)
--5056472C ?
--13FBC078 ?
--00000001 ?
--00000000 ?
--00000001 ?
--C71B6500 ?
--C78629A8 ?
D121B2A6 ?
--C71B6500 ?
--5E8AA164 ?
--5E8AA160 ?
--FFFFFFFF ?
--5E8AA160 ?
D121CFD9 ?
--C71B6500 ?
--5E8AA160 ?
--00000001 ?
--5E8AA160 ?
D157FC6F (DPRPCNLM.NLM|ndps_xdr_array+CF)
--C71B6500 ?
--5E8AA160 ?
D157FAEF (DPRPCNLM.NLM|ndps_xdr_pointer+5F)
--38582C20 ?
--C7862A30 ?
--0000001C ?
--C7862AD8 ?
--C71B6500 ?
--C7862A38 ?
--C7862A00 ?
D121E778 (NDPSM.NLM|nwdp_printprogram_a+78F)
--C71B6500 ?
--C7862A38 ?
--C7862A34 ?
--FFFFFFFF ?
--00000014 ?
D121CFC8 ?
--C7862A18 ?
--C71B6500 ?
D121E850 (NDPSM.NLM|nwdp_printprogram_a+867)
--C71B6500 ?
--C7862A1C ?
D121E897 (NDPSM.NLM|nwdp_printprogram_a+8AE)
--C71B6500 ?
D121E892 (NDPSM.NLM|nwdp_printprogram_a+8A9)
--C71B6500 ?
--C7862A18 ?
D121E86D (NDPSM.NLM|nwdp_printprogram_a+884)
D157DB81 (DPRPCNLM.NLM|ndps_svc_getargs+11)
--C71B6500 ?
--C7862A14 ?
--C7862B4C ?
D121DADA ?
--C7862AD8 ?
D121E86D (NDPSM.NLM|nwdp_printprogram_a+884)
--C7862A14 ?
--D0E5EE50 ?
--00000000 ?
--00000016 ?
--C8DF24A0 ?
--00000000 ?
--00000001 ?
--C8DF24C0 ?
--C71B6780 ?
--38582C20 ?
--5E8AA160 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--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 NDPSM.NLM.

The OS is NW5.1 SP4, other than possibly patching just NDPS, our corporate
environment does not allow for patching the entire OS just yet. So is
there an NDPS patch that would take care of this problem?
Thanks,
Sven

[Andrew C Taubman]

No. Your only answer will be to apply the current SP, SP6, which contains
the fixed NDPSM code. If your corporate policies prevent you from fixing
your servers, they are hindrances and need to be changed.
--
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.