Mitsubishi Electric - Computing for a Connected World Insight CD Home Page

Product Identification
Product Timeline
Desktop Systems
Server Systems
Add-in Cards
Sorage Devices
Search Insight
E-Mail us
Insight Service
Year 2000
Other Mitsubishi Sites
Site Disclaimer

FT4200 Diagnostic Codes Reference Guide (Rel 1.8.8)

This document lists the diagnostic codes that your server can produce. Some of these codes indicate errors or malfunctions; others are simply way-markers that indicate normal progress. The codes can appear in the server’s front panel LCD display or on the screen in the System Management Application software.


Some codes described in this guide will seem obscure to less experienced users, particularly those codes which appear on the Front Panel LCD. If you cannot understand the meaning of a code, ask an authorised engineer for help.

Codes that appear on the Front Panel LCD

When you press the Power On button from Standby mode, the server initiates several phases in the boot process. During these phases the system performs the following operations:

Checks the Diagnostic Processor.

Checks the System Management Controller (SMC).

Checks the BIOS, which executes the Power On Self Test (POST).

Loads the Operating System.

Attaches the Device Driver and associated clients.


There is a set of diagnostic codes, expressed as hexadecimal numbers, associated with each phase. If your server fails to complete any of these phases, the system will halt and one of the codes will flash on and off on the front panel LCD display. The code represents the point at which the power-on sequence came to a stop and may indicate what element of the system could be at fault.

 The appearance of some codes may require an engineer to deal with the problem. In this case, be sure to do the following:

1. Note down the code to help the engineer diagnose the fault.

2. Clear the LCD (and silence the alarm if it is sounding) by using the key to turn the front drive bay door lock to the Unlock position (door closed). If it is already in the Unlock position, turn it to Lock and then to Unlock again.

Note Power On
Press this button to switch the system on from Standby Mode. The Power LED will light up and the system will initiate its boot sequence. Diagnostic codes, expressed as hexadecimal numbers, will appear as a matter of course on the LCD screen on the Front Panel. What happens after this depends on how your Shogun has been configured, i.e. which operating system or other software may be installed

Power Failure Codes

The LCD will display these codes if the mains electricity supply fails. These codes, shown in brackets below, represent three power failure modes. In each mode, the power supply battery pack powers the system. Each code uses a countdown timer, indicated by nnn, to indicate the number of seconds before its mode expires and the next mode begins. If the countdown begins at 1000 or greater, the LCD will display 999 and hold until the countdown actually reaches 999. The LCD will display the progress of the countdown from then on.

Brownout (A.nnn) This mode indicates a temporary reduction or even absence of the AC electric power. If it turns out that full power is not restored after approximately five seconds, Brownout will change to Battery Mode. If the battery charge is already low and power consumption is high, the system may skip Battery Mode altogether and jump to Power Fail mode. On the other hand, if power is fully restored before the countdown reaches zero, system function will return to normal and the batteries will recharge.

Battery Mode (b.nnn) This mode results because power has not been restored in Brownout Mode. The system warns users to save their work, terminate their applications and log off the network. System shutdown is initiated in this mode. If power is fully restored before the countdown reaches zero, the system will return to normal function and recharge the batteries; otherwise Power Fail mode begins.

Power Fail (F.nnn) In this mode, power has not yet been restored; system shutdown should be in progress to prevent deep battery discharge. Shutdown continues even if power should be restored at this late stage.

Under normal conditions, the server deals with the power failure itself by means of the Event Manager and, when necessary, initiates system shutdown. You will probably only see the Power Fail code on the LCD if the brownout lasts that long. However, if a brownout occurs and persists when the Event Manager is not loaded, then the LCD will display each of the codes described above. Under these conditions the system is not able to initiate system shutdown. You, or some other person who is local to the server, will need to do it yourself while the system is in Battery Mode. The precise steps you need to take to shut down the system, after instructing network users to close their applications and log off, will depend on the operating system you are using. When the operating system is at the point where it is safe to switch the machine to Standby, press and hold the Standby (see note below) button on the front panel until the system switches off (see Chapter 2, Operating Your System, in the Owner’s Handbook for more information about switching off).

After you have instructed all network users to close their applications down and log off the network, hold this button down for a specific period of time before the system initiates a shutdown sequence to Standby Mode. The system will display the code 1200 on the LCD and sound a tone.
Continue to hold down the STANDBY button until the tone stops, at which time the shutdown sequence begins. In Standby Mode, the mains electricity supply keeps the battery pack fully charged, but there is no DC power supplied to the system.
Press STANDBY and CONTROL simultaneously to cancel the current shutdown sequence.
Special Button Functions

System Management Controller (SMC) Error Codes

This section contains SMC error codes. These codes fall into two groups, the range 0F01-0F0F and the range 0F10-0F4F.


These are initialisation codes for the SMC which will only appear immediately after power-up. If the system stops and the LCD flashes one of these codes, it means that there is a serious hardware problem with the SMC board and it probably needs replacing. The following table defines these codes:


Error Code Error Factor
0F01 80C186EB internal H/W (general purpose register) error
0F02 80C186EB internal H/W (flag register) error
0F03 80C186EB internal H/W (timer) error
0F04 SC’s SRAM write/read test error
0F05 SC’s EPROM checksum error
0F06 SC’s FLASH checksum error
0F07 Copy from FLASH to SRAM failed
0F08 Copy from EPROM to SRAM failed
0F09 RTC’s RAM write/read test error
0F0A A/D converter’s busy bit error
0F0B SC’s FLASH is not programmed
0F0D UART1 internal loop test failed
0F0E UART2 internal loop test failed
0F0F UART1 and UART2 internal loop test both failed



These codes indicate various other errors and could appear on the LCD at any point. The following list defines the codes and indicates what action you should take if these errors occur. If an error persists and efforts to solve the problem prove ineffective, you should contact a service engineer.

0F10 Power On Error - This code appears when the firmware does not detect a power-on signal from the Power button within one second. Possible faulty items are the motherboard, the SMC board, the SMIC or the cabling between them. Try pressing the Power button again.

0F11 Power Off Error - Appears when the system will not shut down after pressing the Standby button on the front panel. Possible faulty items are the main circuit board, the SMC board or the cable between them. If it is absolutely necessary to shut down the server, you can switch the circuit breaker switch on the rear panel to the Off position and unplug the mains lead. Only do this, however, as a last resort.

0F12 SMC Watchdog Timer over-flow error - Indicates a faulty SMC board or the SMC firmware. If this code appears, first try resetting the SMC by doing the following:

1. Unlock the removable drive bay door to deactivate the security alarm (see chapter 2 in the Owner’s Handbook).

2. Press the Control, Standby and Reset buttons simultaneously. This action displays "8888" on the LCD.

3. Press Standby and Reset simultaneously. This clears the LCD and resets the SMC. If the error code persists, contact a service engineer.

0F13 Too many time-out errors - Indicates faulty SMC board. Try resetting the SMC using the same procedure as for 0F12.

0F15 Invalid interrupt - Indicates a fault in either the SMC board or firmware.

0F20 Diagnostic Processor communication error - Indicates an error in the diagnostic processor on the System Management Interface Card (SMIC), the power distribution board or the cable between them.

0F30 SMC port retry-error occurred - Indicates an error in the SMC board, the SMIC board, the motherboard power distribution board, the cable between them, firmware or the setting of the SMC (or FPSC) variables. First check the settings of the FPSCResponseTimeOut and FPSCReceiptTimeOut variables in the System Management Application (SMA).

0F31 SMC port Response time-out occurred - Same as for 0F30.

0F32 SMC port Transmit time-out occurred - Indicates faulty SMC board or firmware.

0F40 Modem port retry-over occurred - Indicates a faulty modem, modem cable, telephone line, SMC board, settings of SMC (or FPSC) variables in the SMA. You should check the following items first:

1. The modem is connected correctly.

2. The modem is switched on.

3. The modem is connected to the telephone line correctly.

4. The modem works correctly. To double-check this, connect a different modem that you know is in working order.

5. The serial port settings for the modem (e.g. baud rate) are correct.

6. Settings of the MODEMResponseTimeOut and MODEMReceiptTimeOut variables, in the SMA, are correct.

0F41 MODEM port Response time-out - Same as 0F40.

0F42 MODEM port Transmit time-out - Same as 0F40.

0F4D MODEM AT command result code time-out occurred - Indicates faulty modem, modem cable, SMC board or SMC (FPSC) variable settings. You should check the following items first:

1. The modem is connected correctly.

2. The modem is switched on.

3. The modem connection to the telephone is in order.

4. The modem functions properly. To double-check this, connect a different modem that you know is in working order.

5. The serial port settings for the modem (e.g. baud rate) are correct.

6. The settings of the ModemATOriginal, ModemATCommands and MODEMPortBaudRate variables, in the SMA, are correct.

0F4E MODEM AT command failed - Same as 0F4D.

0F4F MODEM AT command unexpected result code is received - Same as 0F4D.

Note Control Standby & Reset
Special Button Functions
Pressing Standby, Control and Reset simultaneously while the front drive bay door is unlocked switches the system into a mode in which these three buttons have special functions. The LCD displays 8888 to indicate this mode.
STANDBY or RESET - Pressing one of these buttons initiates a memory dump to the central processing unit by activating and then deactivating the Non-Maskable Interrupt (NMI) signal via the diagnostic processor. You can then use the appropriate function of the network operating system to examine the contents of the dump.
CONTROL - Pressing this button initialises the modem, which is connected to the SMC serial port on the backplane of the Shogun. If the modem initialisation is successful, the LCD displays the code 0000. If the initialisation is unsuccessful, the LCD displays 0F4D or 0F4E.
STANDBY + RESET - Pressing these buttons simultaneously clears the LCD and then releasing them executes an independent Front Panel System Controller (FPSC) reset. This would only be necessary if a major problem or error had occurred in the system.
If you do not press any buttons for ten seconds, the system returns to normal mode.

Progress Control (NextBootStage) Codes

A single SMC (FPSC) variable, NextBootStage, records the progress of all phases of the boot process. These phases are:

Power-On Self Test (POST), executed by the BIOS.

SMC Device Driver Attachment (i.e. initialisation).

SMC Client Loading.

The SMC Last Client sends a message to the SMC that it has loaded.

The NextBootStage variable can take values in the range 1000-FFFF. The most significant digits of this variable (i.e. the first three) are progress codes and are allocated as follows:

100-1FF Diagnostic Processor and SMC

200-2FF Motherboard BIOS

300-3FF System Management Interface Card (SMIC) BIOS

400-7FF Unallocated

800-8FF Device Driver

900-EFF Unallocated

F00-FFF Last Client

The least significant digit (i.e. the fourth) indicates whether there is an error condition, according to the following scheme:

0 No error

F Used by SMC to indicate an error

 The following codes have special meaning to the SMC:

 0001 is issued, accompanied by an alarm, under the following circumstances:

The nickel-cadmium battery on the SMC board has fully discharged. This will happen if the server is disconnected from the mains electricity for at least one month.

The SMC firmware which controls the Front Panel is updated.

A fatal error occurs on the SMC and the SMC executes a self-reset. This means that any changes you have made to the configuration settings within the SMA have been lost. Use the SMA to restore these settings (see the SMA User’s Guide and the SMA’s own on-line help system).

2000 must be issued by the BIOS when it starts execution before configuration testing has taken place.

7FF0 is the POST completion code. It is sent by the BIOS when the POST completes successfully. When the code is received, the POST watchdogs are disabled.

8FE0 is the code sent by the SMC Device Driver to indicate that it will be absent.

8FF0 is the code sent by the SMC Device Driver to indicate that it has initialised successfully.

FFE0 is the code sent by the SMC Last Client to indicate that all clients will be unloaded. The Trap generator is disabled.

FFF0 is the code sent by the SMC Last Client to indicate that all clients are now loaded. The Trap generator is enabled.

SMC-specific codes and NextBootStage codes

Code Meaning Source
0000 Reset or Shutdown has been cancelled by S/W. Device drivers or clients
1000 Reset is issued to Diag-Processor SMC
100F POST has not started its execution. (SMC detected time-out) SMC
1200 Shutdown_request is issued to S/W SMC
1400 Normal Reset_request issued to S/W SMC
1600 NMI request is issued to Diag-processor SMC
1800 Dump (INIT) request is issued to Diag-processor SMC
1FFF System dead is reported by Diagnostic processor Diagnostic processor
2000 POST has started its execution POST
2001-2FFF POST indicates the number or error of test being executed POST
7FF0 POST completes its execution POST
8000-FFFF These codes are issued by device driver or clients Device driver or client
8FE0 Device driver is detached Device driver
8FF0 Device driver is attached Device driver
FFE0 Clients are detached Last Client
0000 Clients are attached.

This code also appears when a Reset or Shutdown has been cancelled by S/W.

Last Client

Device drivers or clients


POST beep codes

Certain tests are performed before the video subsystem is initialised, thus requiring the codes speaker to emit beep codes in the case of a failure. The following table describes the various and their meaning.


Diagnostic code

Number of beeps



1 - 1 - 3

CMOS write/read test failure


1 - 1 - 4

BIOS ROM checksum failure


1 - 2 - 1

Programmable Interval Timer test failure


1 - 2 - 2

DMA initialisation failure


1 - 2 - 3

DMA page register read/write test failure


1 - 2 - 4

RAM refresh verification failure


1 - 3 - 1

First 64K RAM test failure


1 - 3 - 2

First 64K RAM parity test failure


1 - 3 - 3

Slave DMA register test failure


1 - 3 - 4

Master DMA register test failure


1 - 4 - 1

Master interrupt mask register test failure


1 - 4 - 2

Slave interrupt mask register test failure


1 - 4 - 4

Keyboard controller test failure


2 - 2 - 2

Search for video ROM test failure


2 - 2 - 3

Screen believed inoperable


2 - 2 - 4

Timer tick interrupt test failure


2 - 3 - 1

Interval timer channel 2 test failure


2 - 3 - 3

Time-of-day clock test failure


2 - 4 - 3

CMOS memory size against actual compare failure


2 - 4 - 4

Memory size mismatch occurred


Other BEEP Codes

There are a few other codes that occur, but please note that some are system beeps that will be heard during normal operation.

No beeps. If no beeps are heard at all the speaker may be disconnected or there may be a speaker cicuitry fault.

One short beep. Marks the completion of POST and no functional errors found. You will also get a single beep if you press an invalid key for a power-on password.

Two short beeps. Indicates and draws your attention to an error during POST. This should be accompanied by an error code from the table below.

Three short beeps. System memory error, normally accompanied by code 201, but beeps are used when the video cannot display the code.

Continuous beep. Could indicate a serious failure of the system motherboard, or a failure of the speaker circuitry.

Repeating short beeps. Usually indicative of a keyboard key stuck down, may be due to the keyboard interface failing.

One Long and one short beep. POST has detected an error on the video adapter in the system. There may well be no display on the screen.

One long and two short beeps. This means that either the video subsystem is faulty or that a video I/O adapter ROM is not readable.

Two long and two short beeps. The video subsystem cannot be supported by the main system POST. This can occur when the video subsystem is replaced or changed on site.

POST codes




Default config in use (last 3 boots failed)


Timer tick interrupt failure


Timer 2 test failure


Diskette controller failure


System board memory parity error


I/O Channel card error


Option ROM checksum failure


Unexpected hardware type 2 interrupt occurred


Internal cache error


Real time clock failure


Real time clock battery failure


CMOS RAM checksum failure


Invalid configuration inforamtion


Time of day not set


Memory size does not match




System tampered, covers removed


Bad administrator password checksum


System tampered


EEPROM is not functional


Administrator password is needed


Bad power-on password checksum


Corrupted boot sequence


Hardware problem


Excessive password attempts


Memory error


Internal cache error


DRAM parity configuration


Keyboard/keyboard controller failure


Diskette drive failure


Diskette unlocked problem


Diskette drive configuration


Coprocessor configuration


Parallel port configuration


Serial port configuration


Fixed disk configuration


Fixed disk 0 failure


Fixed disk 1 failure


Fixed disk 2 failure


Fixed disk 3 failure


PCI - no more IRQ available


PCI - no more room for option ROM


PCI - no more I/O space available


PCI - no more memory (above 1MB) available


PCI - no more memory (below 1MB) available


PCI - checksum error or 0 size Option ROM


No bootable device


Display adapter failed, using alternate


Video memory configuration error


CD-ROM configuration error


Pointer device has been removed


Codes Generated by the SMIC BIOS

The following table contains codes that the System Management Interface Card (SMIC) BIOS generates during POST. The codes, which can appear on the LCD or within the System Management Application, define the start and end points of each action. The appearance of one of these codes does not indicate an error unless it flashes.


Start Definition End
3100 Boot control decision logic 3900
3110 Console redirect decision logic 3910
3200 Initialise FPSC communications 3A00
3210 Write inventory information 3A10
3220 Enable / Disable CPUs 3A20
3230 Fatal error handler 3A30
3240 Write inventory information 3A40
3300 Console redirection 3B00
3510 Ethernet card node address reporting 3D10
3520 Time synchronisation 3D20
3530 Non-fatal POST errors reporting 3D30
3540 Security 3D40
3700 Flash Disk initialisation 3F00
3710 Flash Disk boot 3F10
3720 Flash Disk self-test 3F20


Codes that appear in the SMA

POST error codes and messages

The BIOS indicates errors by writing an error code to the PS/2 standard logging area in the Extended BIOS Data Area, and by displaying a message on the screen, which is preceded by the POST Error Code. The error code will also be logged to the Critical Event Logging area. The following codes will appear inside the System Management Application (SMA) and not on the front panel LCD.


Code Error Message
0002 Primary Boot Device Not Found
0010 Cache Memory Failure, Do Not Enable Cache
0015 Primary Output Device Not Found
0016 Primary Input device Not Found
0041 EISA ID Mismatch for Slot
0043 EISA Invalid configuration for Slot
0044 EISA config NOT ASSURED!
0045 EISA Expansion Board Not Ready in Slot
0047 EISA CMOS Configuration Not Set
0048 EISA CMOS Checksum Failure
0049 EISA NVRAM Invalid
0060 Keyboard Is Locked ... Please Unlock It
0070 CMOS Time & Date Not Set
0080 Option ROM has bad checksum
0083 Shadow of PCI ROM Failed
0084 Shadow of EISA ROM Failed
0085 Shadow of ISA ROM Failed
0131 Floppy Drive A:
0132 Floppy Drive B:
0135 Floppy Disk Controller Failure
0140 Shadow of System BIOS Failed
0170 Disabled CPU slot #
0171 CPU Failure - Slot 1, CPU #1
0172 CPU Failure - Slot 1, CPU #2
0173 CPU Failure - Slot 2, CPU #1
0174 CPU Failure - Slot 2, CPU #2
0171 Previous CPU Failure - Slot 1, CPU #1
0172 Previous CPU Failure - Slot 1, CPU #2
0173 Previous CPU Failure - Slot 2, CPU #1
0174 Previous CPU Failure - Slot 2, CPU #2
0175 CPU modules are incompatible
0180 Attempting to boot with failed CPU
0191 CMOS Battery Failed
0195 CMOS System Options Not Set
0198 CMOS Checksum Invalid
0289 System Memory Size Mismatch
0295 Address Line Short Detected
0297 Memory Size Decreased
0299 ECC ErrorCorrection Failure
0301 ECC Single bit correction failed, Correction disabled
0302 ECC Double Bit Error
0310 ECC Address Failure, Partition #
0370 Keyboard Controller Error
0373 Keyboard Stuck Key Detected
0375 Keyboard and Mouse Swapped
0380 ECC SIMM failure, Board in slot 1 SIMM #
0392 ECC SIMM failure, Board in slot 2 SIMM #
0430 Timer Channel 2 Failure
0440 Gate-A20 Failure
0441 Unexpected Interrupt in Protected Mode
0445 Master Interrupt Controller Error
0446 Slave Interrupt Controller Error
0450 Master DMA Controller Error
0451 Slave DMA Controller Error
0452 DMA Controller Error
0460 Fail-safe Timer NMI Failure
0461 Software Port NMI Failure
0465 Bus Timeout NMI in Slot
0467 Expansion Board NMI in slot
0501 PCI System Error
0510 PCI Parity Error
0710 System Board Device Resource Conflict
0711 Static Device Resource Conflict
0800 PCI I/O Port Conflict
0801 PCI Memory Conflict
0802 PCI IRQ Conflict
0803 PCI Error Log is Full
0810 Floppy Disk Controller Resource Conflict
0811 Primary IDE Controller Resource Conflict
0812 Secondary IDE Controller Resource Conflict
0815 Parallel Port Resource Conflict
0816 Serial Port 1 Resource Conflict
0817 Serial Port 1 Resource Conflict
0820 Expansion Board Disabled in Slot
0900 NVRAM Checksum Error, NVRAM Cleared
0903 NVRAM Data Invalid, NVRAM Cleared
0905 NVRAM Cleared By Jumper
0982 I/O Expansion Board NMI in Slot
0984 Expansion Board Disabled in Slot
0985 Fail-safe Timer NMI
0986 System Reset Caused by Watchdog Timer
0987 Bus Timeout NMI in Slot



Computing for a Connected World