Yes, I know. I should be on a later support pack. There are reasons why I
haven't moved up yet. The server has been running wonderfully on SP2 for
several months.

First indication of trouble: NRM showed condition yellow. The problem was
identified as low cache buffers. Since it wasn't immediately apparent as
to what was causing the problem, I decided to reboot and keep an eye on
the situation while I researched it. Restarted; no problem for 2 days.
Then at 3 am this morning, it abended (see log below). It was apparently
able to restart because it abended again 27 minutes later. It was
thoroughly hung when I arrived to check it. Restarted. Seemed okay for
about 30 minutes. I was using NRM to check the condition - it was green -
when it abended again. Restarted. Ran for 4 hours. Abended again. Tried
to restart; abended during restart. Ran complete hardware diagnostics. No
problem found.

Each abend was different. The log of the first one is included below. I
can't recall making any changes to the server since I applied SP2 several
months ago, certainly not within the past few weeks.

Thanks in advance for any and all help you can give me!

************************************************** *******

Server GEOLOGY halted Wednesday, October 5, 2005 3:05:00.039 am
Abend 1 on P00: Server-5.70.02: Page Fault Processor Exception (Error
code 00000000)

Registers:
CS = 0060 DS = 007B ES = 007B FS = 007B GS = 007B SS = 0068
EAX = 00000000 EBX = 559E11D5 ECX = 019BE7C4 EDX = 559E11D5
ESI = A49AA4E4 EDI = A8A532C4 EBP = A8A531E8 ESP = A8A531E8
EIP = 8413EEF6 FLAGS = 00010246
8413EEF6 668B02 MOV AX, [EDX]=?
EIP in DS.NLM at code start +00198EF6h
Access Location: 0x559E11D5

The violation occurred while processing the following instruction:
8413EEF6 668B02 MOV AX, [EDX]
8413EEF9 89EC MOV ESP, EBP
8413EEFB 5D POP EBP
8413EEFC C3 RET
8413EEFD 90 NOP
DS.NLM|getDataType$FlmDefaultRec:
8413EEFE 55 PUSH EBP
8413EEFF 89E5 MOV EBP, ESP
8413EF01 8B450C MOV EAX, [EBP+0C]
8413EF04 8A4003 MOV AL, [EAX+03]
8413EF07 240F AND AL, 0F



Running process: NTREND.NLM 6 Process
Thread Owned by NLM: NTREND.NLM
Stack pointer: A8A52D58
OS Stack limit: A8A50160
Scheduling priority: 67371008
Wait state: 3030070 Yielded CPU
Stack: --A8A5329C ?
841A8450 (DS.NLM|flmCurGetAtomFromRec+69)
--019BE7C4 ?
--559E11D5 ?
--0000000B ?
--0000010D ?
--00000031 ?
--00000040 ?
--00000056 ?
--A877DAE4 ?
--00000002 ?
--A8A532D4 ?
841A865A (DS.NLM|flmCurGetAtomFromRec+273)
--019BF604 ?
--A8A532D4 ?
-0043E27C (SERVER.NLM|xAllocSizeTable+1F8)
--019BF604 ?
--019BF6B8 ?
--00007D6C ?
--0000001D ?
--00690042 (CE100B.LAN|CE100BDmiLink+92CE)
-0064006E (XIM.XLM|(Data Start)+306E)
--00720065 ?
--00200079 ?
--00790054 ?
-00650070 (XSUP.NLM|(Data Start)+F070)
--00000000 ?
--0000004E ?
--00000000 ?
--A8A8A024 ?
--A8A8A034 ?
--00000000 ?
--A877DBD8 ?
--A8A5328C ?
8412F986 (DS.NLM|GedPoolReset+76)
--A877DBD8 ?
--559E11D5 ?
--A8A8A024 ?
--AAC95654 ?
--00000001 ?
--00000000 ?
--AAC9567C ?
--A49AA4E4 ?
--A8A532C4 ?
--A8A532EC ?
--A8A5337C ?
841A909F (DS.NLM|flmCurEvalCompareOp+225)
--A49AA4E4 ?
--A49AA5D8 ?
--AAC95654 ?
--019BE7C4 ?
--00000002 ?
--00000001 ?
--A8A532C4 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000002 ?
--00000040 ?
--00000000 ?
--00000190 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00004444 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000550 ?
--A8A5332C ?
--A5495B60 ?
--AAC9579C ?
--00000000 ?
--00000001 ?
--00000000 ?
--00000000 ?
--A8A53350 ?
--019BF604 ?
--00000000 ?
--00000000 ?
83FAB81F (DS.NLM|DMFree+10)
--00000000 ?
--00000000 ?
--A49AA5D8 ?
--00000000 ?
--A8A532C4 ?
--00000000 ?
--00000002 ?
--00000019 ?
--AAC95634 ?
--AAC95684 ?
--AAC956EC ?

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