ABEND LOG for SCRSAVER.NLM issue! - TechRepublic
General discussion
April 15, 2003 at 12:19 AM
tdkline

ABEND LOG for SCRSAVER.NLM issue!

by tdkline . Updated 22 years, 11 months ago

Server MARTBURG2 halted Saturday, April 5, 2003 10:32:37.397 am
Abend 1 on P00: Server-5.60c: Page Fault Processor Exception (Error code 00000000)
Registers:
CS = 0008 DS = 0010 ES = 0010 FS = 0010 GS = 005B SS = 0010
EAX = 00000000 EBX= C0AC5D40 ECX = 000029E9 EDX = D004E09C
ESI = 00000000 EDI = FC119DC9 EBP = D0E12680 ESP = D0DE9504
EIP = B5DAC0E0 FLAGS = 00010082
Address (0xB5DAC0E0) exceeds valid memory limit
EIP in UNKNOWN memory area
Access Location: 0xB5DAC0E0

The violation occurred while processing the following instruction:
Running process: Interrupt service routine (nested count 2)
Interrupted process: Console Command Process
Thread Owned by NLM: SERVER.NLM
Stack pointer: D0DE9638
OS Stack limit: D0DE2040
CPU 0 (Thread D0E124C0) is in a NO SLEEP state
Scheduling priority: 67371008
Wait state: 3030070 Yielded CPU
Stack: FC08BE7C (SERVER.NLM|EventReport+27C)
–D004E09C ?
–00000000 ?
–C0AC5D40 ? FC119DC9 (SERVER.NLM|KeyboardEventHandler+11)
–000029E9 ?
-00134AA0 (LOADER.EXE|activeScreen+3E84)
FC09DD54 (SERVER.NLM|GetNLMNames+48)
–D0DE9540 ?
–00000000 ?
-D41F9577 (POLIMGR.NLM|PMmajor+782)
D41EFD3E -00134AA0 (LOADER.EXE|activeScreen+3E84)
Additional Information:
The hardware detected a problem while executing an interrupt service routine. The code being executed is owned by SERVER.NLM. It may be thesource of the problem or there may have been a memory corruption.

This discussion is locked

All Comments