| Symptom / Error | FRU / Action |
0001 01XX
Interrupt failure.
Possibly a bad battery or processor |
1. Run Advanced Diagnostics
2. 486DX33 Upgrade (70/80) |
0001 02XX
ROM checksum or timer error.
Possibly a bad battery or processor |
1. Run Advanced Diagnostics
2. 486DX33 Upgrade (70/80) |
(If the battery was removed while replacing the 80386 processor in a model 70, with a 486DX33 Processor Upgrade (FRU Number 92F0436), remove the 486DX33 processor and install the 80386 processor, then install the battery.
Configure the system and re-install the 486DX33 processor without removing the battery.) |
|
0001 0300
Checksum or timer error.
If it is a 20 MHz board, and the processor is not a 487SX, the jumper must be in positions 2 and 3
(487SX is indicated on the processor) |
1. Processor Board (90/95)
2. System Board |
0001 02XX
0001 03XX
0001 04XX
0001 07XX |
1. System Board
2. Processor Board |
0001 05XX
Command not accepted |
Information only |
0001 06XX
Converting logic test failure |
1. Run Advanced Diagnostics |
0001 07XX / 0001 08XX
0001 09XX
Interrupt or memory failure |
1. System Board Memory
2. System Board
3. Processor Board (90/95)
4. Any Adapter
5. Bus Adapter |
0001 0XXX
any other not listed |
1. System Board |
0001 10XX
Check Memory
(For Model 56 / 57 & 90 / 95, also
see 000201XY for socket location list) |
1. Memory Module Kit
2. System Board |
0001 11XX
I/O channel check |
1. Adapter Memory
2. Expansion Adapter
3. System Board |
0001 12XX / 0001 13XX
Possible MC-timeout error
Often caused by a card with defective MCA bus interface or too slow responding card. |
1. System Board
2. Processor Board (90/95)
3. Any Adapter |
0001 14XX
ROM error |
1. Any Adapter
2. Bus Adapter |
0001 15XX
80386 protected mode failure, or BIOS
checksum error |
1. System Board
2. 486DX33 Upgrade (70/80) |
0001 16XX
Possible read/write problem |
1. Run Advanced Diagnostics
2. 486DX33 Upgrade (70/80) |
0001 18XX
Previously detected error.
Run Advanced Diagnostics |
1. System Board Memory
2. Processor Board (90/95) |
0001 19XX
2.88MB diskette drive is
installed but not supported. |
1. Run Automatic Configuration
2. System Board |
0001 1XXX
not listed above |
1. System Board |
0001 20XX
Possible Processor self test failure
(90/95) |
1. System Board Processor Cache
2. Processor Board (90/95) |
0001 21XX
A problem was detected during
memory remapping (256KB ROM Error) |
Information only |
0001 22XX
POST found a hardware error |
1. Run Advanced Diagnostics |
0001 2201 / 0001 2202
0001 2203 / 0001 2204
0001 2205 / 0001 2206
0001 2207 / 0001 2208
Data error, Possible system board failure |
1. Run Advanced Diagnostics |
| 0001 29XX |
1. Run Advanced Diagnostics
2. Cache Kit
3. System Board |
0001 30XX
POST could not start the operating system. Operating system loaded ?
Is the boot drive in the selectable drive sequence ? |
1. Check Drive Sequence |
0001 3001
Security system is being used, but the computer is not totally secured because there is a diskette drive in the startup sequence |
1. Delete diskette drive from the startup sequence if so desired. |
0001 3002
Drive startup sequence is corrupt
or invalid |
1. Run Automatic Configuration, then reset the selectable drive startup sequence. If the problem still exists, replace the system board |
0001 3003
EEPROM could not be read |
1. Run Automatic Configuration
If the problem still exits, replace the system board. |
| 0001 31XX |
1. System Board |
0001 32XX
DMA extended registers error |
1. Run Advanced Diagnostics |
0001 33XX
DMA verify function error. Logic failed |
1. Run Advanced Diagnostics |
0001 34XX
DMA arbitration logic error |
1. Run Advanced Diagnostics |
| 0001 4905 |
1. System Board
2. Processor Board |
0001 4908 / 0001 4909
Before replacing any FRUs, see 'Cover Lock and Tamper-Evident Switches' |
1. System Board
2. Tamper Evident Switches
3. Keylock Assembly |
0001 52XX
Real time clock error.
This is not always a hardware failure. See also 'Real-Time Clock Problems' |
1. Run Advanced Diagnostics |
0001 56XX
Security error.
The covers were removed without using the key. The tamper evident switch was tripped. |
1. Start the system from the Reference diskette (or server image) and reconfigure the system.
2. Security Switch Assembly
3. System Board |
