💾 Archived View for uscoffings.net › retro-computing › components › PC › BIOS › AMI-FAQ.html captured on 2022-06-04 at 00:12:56.
-=-=-=-=-=-=-
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>New Page 3</title>
<meta name="GENERATOR" content="Microsoft FrontPage 3.0">
</head>
<body>
<p><font size="+2">AMI BIOS</font> </p>
<p><font size="+1">Audio Beep Errors:</font> </p>
<table border="1">
<TBODY>
<tr>
<th>Number of Beeps</th>
<th>Description of Problem</th>
<th>Solution</th>
</tr>
<tr>
<td>1 beep</td>
<td>DRAM refresh failure</td>
<td>Try re-seating the memory first. If the error still occurs, replace the memory with
known good chips.</td>
</tr>
<tr>
<td>2 beeps</td>
<td>Parity Circuit Failure</td>
</tr>
<tr>
<td>3 beeps</td>
<td>Base 64K RAM failure</td>
</tr>
<tr>
<td>4 beeps</td>
<td>System Timer Failure</td>
<td>Send System Board in for Repair</td>
</tr>
<tr>
<td>5 beeps</td>
<td>Processor Failure</td>
</tr>
<tr>
<td>6 beeps</td>
<td>Keyboard Controller / Gate A20 Failure</td>
<td>Try re-seating the keyboard controller chip. If the error still occurs, replace the
keyboard chip. If the error persists, check parts of the system relating to the keyboard,
e.g. try another keyboard, check to see if the system has a keyboard fuse.</td>
</tr>
<tr>
<td>7 beeps</td>
<td>Virtual Mode Exception Error</td>
<td>Send System Board in for Repair</td>
</tr>
<tr>
<td>8 beeps</td>
<td>Display Memory Read/Write Failure</td>
<td>Indicates a memory error on the video adapter. Try re-seating the video card. If it
still beeps, try replacing the video card or the memory on the video card.</td>
</tr>
<tr>
<td>9 beeps</td>
<td>ROM BIOS Checksum Failure</td>
<td>Indicates faulty BIOS chip(s). It is not likely that this error can be corrected by
re-seating the chips. Consult the motherboard supplier or an AMI product distributor for
replacement part(s). </td>
</tr>
<tr>
<td>10 beeps</td>
<td>CMOS Shutdown Register Read/Write Error</td>
<td>Send System Board in for Repair</td>
</tr>
<tr>
<td>1 long 2 short</td>
<td>Video failure</td>
<td>Reseat the video board - replace if board is determined to be faulty. </td>
</tr>
<tr>
<td>1 long 3 short</td>
<td>Video failure</td>
</tr>
<tr>
<td>1 long</td>
<td>POST passed. </td>
<td>No Errors</td>
</tr>
</TBODY>
</table>
<p><font size="+1">Error Messages/Codes</font> </p>
<p> </p>
<table border="1">
<TBODY>
<tr>
<th>Error Message</th>
<th>Problem</th>
<th>Solution</th>
</tr>
<tr>
<td>CH-2 Timer Error</td>
<td>Non fatal. Could be caused by a peripheral.</td>
<td> </td>
</tr>
<tr>
<td>INTR #1 Error</td>
<td>Interrupt Channel 1 has failed the POST test</td>
<td>Check system boards for IRQs 0-7. </td>
</tr>
<tr>
<td>INTR #2 Error</td>
<td>Interrupt Channel 2 has failed the POST test</td>
<td>Check system boards for IRQs 8-15. </td>
</tr>
<tr>
<td>CMOS Battery State Low</td>
<td> </td>
<td>Replace battery. </td>
</tr>
<tr>
<td>CMOS Checksum Failure</td>
<td>A checksum is generated when CMOS values are saved for error checking on subsequent
startups. This error message will appear if the checksum is different from one boot-up to
the next. </td>
<td>Run the setup program again to correct the problem. </td>
</tr>
<tr>
<td>CMOS Memory Size Mismatch</td>
<td>Usually caused when you add or remove memory from your system but could be caused by
memory that has failed. </td>
<td>Run setup. </td>
</tr>
<tr>
<td>CMOS System Optons Not Set</td>
<td>CMOS values are either corrupt or do not exist. </td>
<td>Run Setup. </td>
</tr>
<tr>
<td>Display Switch Not Proper</td>
<td>Many motherboards have a jumper setting that allows you to specify whether you have a
color or monochrome monitor. </td>
<td>Correct the switch position. </td>
</tr>
<tr>
<td>Keyboard is locked ... Unlock it</td>
<td> </td>
<td>Unlock the keyboard. </td>
</tr>
<tr>
<td>Keyboard Error</td>
<td>There is a problem with the keyboard</td>
<td>Make sure your keyboard BIOS is compatible, that the keyboard is plugged in
completely, and that no keys are stuck. Or, change the BIOS keyboard setting to "Not
Installed" to skip the test. </td>
</tr>
<tr>
<td>K/B Interface Error</td>
<td>There is a problem with the keyboard connector on the motherboard. </td>
<td> </td>
</tr>
<tr>
<td>FDD Controller Failure </td>
<td>The BIOS cannot communicate with the floppy drive controller. </td>
<td>The floppy may be disabled, also check that the cable is not loose. </td>
</tr>
<tr>
<td>HDD Controller Failure </td>
<td>As above, but for hard disks. </td>
<td> </td>
</tr>
<tr>
<td>C: Drive Error</td>
<td>The system cannot get a response from drive C. </td>
<td>The hard disk type is most likely set incorrectly, or the disk may not be formatted or
connected properly. </td>
</tr>
<tr>
<td>D: Drive Error</td>
<td>Same as above except for drive D. </td>
<td>Same as above. </td>
</tr>
<tr>
<td>C: Drive Failure </td>
<td>The drive was detected but failed. More serious than error. </td>
<td> </td>
</tr>
<tr>
<td>D: Drive Failure</td>
<td>Same as above. </td>
<td> </td>
</tr>
<tr>
<td>CMOS Time and Date Not Set</td>
<td> </td>
<td>Run Setup</td>
</tr>
<tr>
<td>Cache Memory Bad, do Not Enable Cache! </td>
<td> </td>
<td>Cache may indeed be bad, if so replace. May simply need re-seating. </td>
</tr>
<tr>
<td>8042 Gate-A20 Error! </td>
<td>The Gate-A20 portion of the keyboard controller has failed. </td>
<td>Replace the keyboard chip (8042) </td>
</tr>
<tr>
<td>Address Line Short</td>
<td>There is a problem with the memory address decoding circuitry. </td>
<td>Try rebooting, (turn the system off and then on 10 seconds later). The problem may
correct itself. </td>
</tr>
<tr>
<td>DMA #1 Error</td>
<td>There is an error in the first DMA channel on the motherboard</td>
<td>Could be caused by a peripheral device. </td>
</tr>
<tr>
<td>DMA Error </td>
<td>There is an error within the DMA controller on the motherboard. </td>
<td> </td>
</tr>
<tr>
<td>No ROM Basic. </td>
<td>There is nothing to boot from. (i.e.- the system cannot find an operating system). </td>
<td>Be certain that a bootable disk is defined in the system setup. </td>
</tr>
<tr>
<td>Diskette Boot Failure </td>
<td>The diskette in the specified boot-up drive is corrupt. </td>
<td> </td>
</tr>
<tr>
<td>Invalid Boot Diskette </td>
<td>Same as above, but the disk is readable. </td>
<td> </td>
</tr>
<tr>
<td>On Board Parity Error </td>
<td>There is a parity error with memory on the motherboard at address XXXX (hex). (On
Board specifies that the memory is not on an expansion board, but rather is located on the
motherboard physically).</td>
<td>Possibly correctable with software from the motherboard manufacturer. (also do a Virus
Check - some viruses cause parity errors).</td>
</tr>
<tr>
<td>Off Board Parity Error </td>
<td>There is a parity error with memory installed in an expansion slot at address XXXX
(hex) </td>
<td>Same as above. </td>
</tr>
<tr>
<td>Parity Error</td>
<td>There is a parity error with memory somewhere in the system. </td>
<td>Same as above. </td>
</tr>
<tr>
<td>Memory Parity Error at XXXX</td>
<td>Memory has failed. If it cannot be determined, it is displayed as XXXX, if not, as
???? </td>
<td>Same as above. </td>
</tr>
<tr>
<td>I/O Card Parity Error at XXXX</td>
<td>Same as above. </td>
<td>Same as above. </td>
</tr>
<tr>
<td>DMA Bus Time-out</td>
<td>A device has driven the bus signal for more than 7.8 microseconds. </td>
<td>Troubleshoot all system boards. (remove them and try to isolate the failure) </td>
</tr>
<tr>
<td>Memory mismatch, run Setup</td>
<td> </td>
<td>Disable Memory Relocation if possible. </td>
</tr>
<tr>
<td>EISA CMOS Checksum Failure</td>
<td>The checksom for EISA CMOS is bad, or the battery is bad. </td>
<td> </td>
</tr>
<tr>
<td>EISA CMOS Inoperational</td>
<td>A read/write failure occured in extended CMOS RAM. </td>
<td>The battery may be bad. </td>
</tr>
<tr>
<td>Expansion Board not ready at Slot X</td>
<td>AMI BIOS cannot find the expansion board in X slot. </td>
<td>Verify that the board is in the correct slot and is seated properly. </td>
</tr>
<tr>
<td>Fail-Safe Timer NMI Inoperational</td>
<td>Devices that depend on the fail-safe NMI timer are not operating correctly. </td>
<td> </td>
</tr>
<tr>
<td>ID information mismatch for Slot X</td>
<td>The ID of the EISA expansion board in slot X does not match the ID in CMOS RAM. </td>
<td> </td>
</tr>
<tr>
<td>Invalid Configuration Information for Slot X</td>
<td>The configuration information for EISA board X is not correct. </td>
<td>Run the ECU. </td>
</tr>
<tr>
<td>Software Port NMI Inoperational</td>
<td>The software port NMI is not working. </td>
<td> </td>
</tr>
<tr>
<td>BUS Timeout NMI at Slot X</td>
<td>There was a bus timeout NMI at Slot X. </td>
<td> </td>
</tr>
<tr>
<td>(E)nable (D)isable Expansion Board? </td>
<td> </td>
<td>Type E to enable the board that had an NMI or D to disable it. </td>
</tr>
<tr>
<td>Expansion Board disabled at Slot X</td>
<td>The expansion board NMI was generated from slot X. </td>
</tr>
<tr>
<td>Fail-Safe Timer NMI </td>
<td>A fail-safe timer NMI has been generated. </td>
<td> </td>
</tr>
<tr>
<td>Software Port NMI</td>
<td>A software port NMI has been generated. </td>
<td> </td>
</tr>
</TBODY>
</table>
</body>
</html>