Scenario:
NetWare 6.5 SP6
ZfD 7.0.1 SP1 (HotPatch 2)
DTS.NLM v3.01.05 (16 Nov 2006)

Issue:
Servers running ZfD 7.0.1 imaging keeps abending after applying ZfD 7.0.1 SP1.
HotPatch 2 does not correct the problem.
Average time between abends are some 2-5 days.
Abending happens regardless of whether imaging goes on or not,
on both my imaging servers, one HP Proliant DL380 G2, and one HP Proliant BL20 blade.

Details:
After an abend, the abend.log always states the same:

************************
Novell Open Enterprise Server, NetWare 6.5
PVER: 6.50.06

Server SKOLE-NWS2 halted Friday, 30 March 2007 9.54.20,648
Abend 1 on P00: Server-5.70.06: Page Fault Processor Exception (Error code 00000000)

Registers:
CS = 0008 DS = 0068 ES = 0068 FS = 0068 GS = 007B SS = 0068
EAX = 74A26C60 EBX = 00000000 ECX = 74B463C0 EDX = 00000001
ESI = 00200246 EDI = 74A26C60 EBP = 74CC65A0 ESP = A9FE7D4C
EIP = 00000001 FLAGS = 00210002
Address (0x00000001) exceeds valid memory limit
EIP in UNKNOWN memory area
Access Location: 0x00000001

The violation occurred while processing the following instruction:



Running process: NWTS 1027 Process
Thread Owned by NLM: DTS.NLM
Stack pointer: A9FE5C5C
OS Stack limit: A9FD8720
CPU 0 (Thread 73F39480) is in a NO SLEEP state
Scheduling priority: 67371008
Wait state: 5050190 Blocked on a kernel CV
Stack: 8CA0AC33 (WS2_32.NLM|WSPSessnClose+187)
--74B463C0 ?
-8CA3812C (WS2_32.NLM|map_functions+70)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--74CC6500 ?
--A9FE7DA8 ?
--74CC65A0 ?
--74B46360 ?
8CA05304 (WS2_32.NLM|WSPCloseSocket+14C)
--74B46360 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--74B46384 ?
--00200246 ?
--A9FE7DE8 ?
--A9FE867C ?
--000000E7 (LOADER.NLM|KernelAddressSpace+E7)
--0000002B (LOADER.NLM|KernelAddressSpace+2B)
8CA111AB (WS2_32.NLM|WS2_32_closesocket+13)
--000000E7 (LOADER.NLM|KernelAddressSpace+E7)
--A9FE7DA8 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--A9FE867C ?
--7CA97720 ?
--0000002B (LOADER.NLM|KernelAddressSpace+2B)
998E2EE0 (DTS.NLM|?SendDataPacket_CRealRpc_v1__QAE_NPAUsock addr_in__HPAD_Z+B0)
--000000E7 (LOADER.NLM|KernelAddressSpace+E7)
--7CB24C1F ?
--000000E7 (LOADER.NLM|KernelAddressSpace+E7)
--00CCCCCC ?
--0000002C (LOADER.NLM|KernelAddressSpace+2C)
--CCCCCCCC ?
--CCCCCCCC ?
--CCCCCCCC ?
--CCCCCCCC ?
--CCCCCCCC ?
--A9FE7DC0 ?
--A9FE8684 ?
998E3AB0 (DTS.NLM|?Process_RPCCall_CRealRpc_v1__QAE_NAAUSPo rtPacket__AAUSDeviceInfo___Z+6C0)
--8FAB66A0 ?
--0000002C (LOADER.NLM|KernelAddressSpace+2C)
--7CBA3920 ?
--7CB24C1F ?
--CCCCCCCC ?
--CCCCCCCC ?
--CCCCCCCC ?
-8CA3EA00 (WS2_32.NLM|szDottedIpAddr+0)
--CCCCCCCC ?
--CCCCCCCC ?
--CCCCCCCC ?
-8CA3EA00 (WS2_32.NLM|szDottedIpAddr+0)
--CCCCCCCC ?
--CCCCCCCC ?
--CCCCCCCC ?
--CCCCCCCC ?
--CCCCCCCC ?
-8CA3EA00 (WS2_32.NLM|szDottedIpAddr+0)
--00CCCCCC ?
--B506060A ?
--CCCCCCCC ?
--CCCCCCCC ?
--03CCCCCC ?
--00000344 (LOADER.NLM|KernelAddressSpace+344)
--8FAB66B0 ?
--CCCCCCCC ?
--CCCCCCCC ?
--CCCCCCCC ?
--CCCCCCCC ?
--CCCCCCCC ?
--A9FE7DFC ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--0009E7A6 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)

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


Ideas anyone?

- Erik