TROUBLESHOOTING


Domino OS/2 server crashes
If an OS/2 server crashes, a message resembling the following appears:
Crashed network drivers or an OS/2 problem may cause this error. Record the addresses and report them to your network administrator. Then restart the server.

Codes that display when an OS/2 server crashes
When an OS/2 server crashes, the console displays an error code. Record the code.
CodeMeaningCause
0 Divide errorThe software is bad.
1.00Debug exceptionsThe software is bad. Record all addresses.
2.00NMI interruptStands for non­maskable interrupt. The software is bad. Record all addresses.
3.00BreakpointThere is a software problem. Record all addresses.
4.00OverflowThe software is bad. Record all addresses.
5.00Bound range exceededThere is a software problem. Record all addresses.
6.00Invalid opcodeThere is a software problem. Record all addresses.
7.00Coprocessor not availableThe software is expecting a math coprocessor, and one isn't installed.
8.00Double faultTwo traps occurred at the same time. Record all addresses.
9.00Coprocessor segment overrunThere is a software problem. Record all addresses.
A/10Invalid task state segmentThere is a software problem. Record all addresses.
B/11Segment not presentThere is a software problem. Record

all addresses.

C/12Stack exceptionThere is a software problem. Ignore this code if it follows a code D/13.
D/13General protectionThere is a software problem or a corrupted database.
F/15Coprocessor errorThere is a bad coprocessor chip.
See also