![[Company Logo Image]](http://www.jmgrossconsulting.com/_borders/JMGC%20-%20White.jpg)
J M Gross Consulting
On this Page:
Web Server
Error Messages
Bios
Error Beeps & Messages/Codes
DOS Error Messages
This page
provides help with deciphering error codes, messages and beeps that you may come
across on your computer.
Listed on this page are Web Server
Error Messages, Bios
Error Beeps & Messages/Codes (AMI
BIOS, AWARD
BIOS) and DOS Error Messages. Find the
error message on your computer, in one of the tables below, and click on it to
see the definition and/or solution to the issue.
WARNING!!!
Making changes to your system's BIOS could render your system unstable, or could
cause it to work improperly, or not at all. Be careful when making ANY changes
to the BIOS.
Web Server Error Messages
BIOS Error Beeps and
Messages/Codes
| 1 beep | 2 beeps | 3 beeps | 4 beeps |
| 5 beeps | 6 beeps | 7 beeps | 8 beeps |
| 9 beeps | 10 beeps | 1 long 2 short | 1 long 3 short |
| 1 long | [ Top of Page ] | [ Top of Page ] | [ Top of Page ] |
AMI
BIOS - Error Messages/Codes
Award BIOS ISA/EISA
v4.5x - Audio Beep Errors
Award BIOS ISA/EISA v4.5x -
Error Messages/Codes
Web Server Error Messages
400 Bad File Request - Usually means the syntax used in the URL is incorrect (e.g., uppercase letter should be lowercase letter; wrong punctuation marks).
This error message indicates that the server can't figure out the URL (Uniform Resource Locator) you requested. The problem often occurs because of incorrect URL syntax. If you typed the URL, check it for incorrect uppercase or lowercase letters, colons, and slashes. Try to type the URL again. If you still get an error, try to backtrack the URL to the directory the document resides in. If the error message persists, there may be a problem with the document. Your only recourse is to contact the site's administrator.
401 Unauthorized - Server is looking for some encryption key from the client and is not getting it. Also, wrong password may have been entered. Try it again, paying close attention to case sensitivity.
401 errors usually occur when an Internet site is protected and the server didn't receive the correct encryption ID or password for entry. If you're registered with the site, you can try your password again if you have the opportunity. As with URLs, passwords are often case-sensitive, so type the password carefully. You can also get this error from servers that deny access from certain domain types, for example, domain names ending in edu.
403 Forbidden/Access Denied - Similar to 401; special permission needed to access the site -- a password and/or username if it is a registration issue. Other times you may not have the proper permissions set up on the server or the site's administrator just doesn't want you to be able to access the site.
401 errors usually occur when a server denies access because of your domain, because of security restrictions, or because you don't have a password. These errors also occur when you haven't signed up with a site that requires registration. You can try to register with the site or try your password again. You can also attempt to contact the site's administrator for a password.
404 File Not Found - Server cannot find the file you requested. File has either been moved or deleted, or you entered the wrong URL or document name. Look at the URL. If a word looks misspelled, then correct it and try it again. If that doesn't work backtrack by deleting information between each backslash, until you come to a page on that site that isn't a 404. From there you may be able to find the page you're looking for.
The 404 error often appears as Not Found or simply File Not Found. These errors are very common and occur when the host server can't find the specific HTML (Hypertext Markup Language) document you requested. 404 errors usually stem from a document name change or a document deletion. They can also take place when you've made a syntax error in the document name. Your best bet is to assume you made a mistake when you typed the URL. Backtrack by deleting the portion of the URL that follows the last slash. Then re-access the URL and look for it in the directory you'll receive.
408 Request Timeout - Client stopped the request before the server finished retrieving it. A user will either hit the stop button, close the browser, or click on a link before the page loads. Usually occurs when servers are slow or file sizes are large.
500 Internal Error - Couldn't retrieve the HTML document because of server-configuration problems. Contact site administrator.
501 Not Implemented - Web server doesn't support a requested feature.
502 Service Temporarily Overloaded - Server congestion; too many connections; high traffic. Keep trying until the page loads.
This error indicates that the server is experiencing high-traffic load and can't process the request. You can often access the site by trying to load the site again. If the error persists, you may want to try at a later time.
503 Service Unavailable - Server busy, site may have moved ,or you lost your dial-up Internet connection.
This error occurs when your access provider, gateway, or system is down or busy. Your only hope is to wait a minute or two and try again.
Connection Refused by Host - Either you do not have permission to access the site or your password is incorrect.
File Contains No Data - Page is there but is not showing anything. Error occurs in the document. Attributed to bad table formatting, or stripped header information.
When you get this error, it means that you've accessed the right Web site, but the file you requested is empty. There's a possibility that the site administrator is updating the site, in which case you can try to access the document again later. You can also try to bypass this problem by retyping the URL with :80 before the last slash.
Bad File Request - Browser may not support the form or other coding you're trying to access.
This error messages indicates a problem with HTML coding at the site. The problem may be that your web browser doesn't support the form you're trying to access. You can try to bypass this problem by E-mailing the Web site administrator for help.
Failed DNS Lookup - The Domain Name Server can't translate your domain request into a valid Internet address. Server may be busy or down, or incorrect URL was entered.
This error indicates that the Domain Name System (DNS) can't translate the URL to a valid Internet address. This DNS error message occurs in several situations. The server that you're trying to connect to may be overloaded with traffic or temporarily down. If the server is just busy, you can sometimes get through by trying to access the site again. If the server is temporarily down or offline, there's nothing you can do except try again later. Unfortunately, there's no way for you to tell whether a server is down or just busy. You could have also incorrectly typed the URL.
If you're accessing the Internet via a modem and you get a DNS error for each Web site you try to access, chances are there's something wrong with your connection. Try re-launching Navigator and your required communication software. If the problem persists, contact your Internet service provider (ISP).
Host Unavailable - Host server down. Hit reload or go to the site later.
This error usually occurs when the host server is down. You can try to access the site again by clicking the Reload button on Navigator's toolbar.
Unable to Locate Host or Host Unknown - Host server is down, Internet connection is lost, or URL typed incorrectly.
These errors often occur for one of three reasons: the host server is down, you lost your Internet connection, or you incorrectly typed the URL. Try clicking the Reload button first. If this doesn't work, look at the URL again. If you still get the error message, check your Internet connection.
Network Connection Refused by the Server - The Web server is busy.
These errors most often indicate that the server is too busy to handle more traffic. You can try the site again by clicking the Reload button, or wait until a later time.
NNTP server error - An NNTP server error appears when you try to log on to a USENET newsgroup and can't gain access.
This error signals several possible problems. As is often the problem, the host server may be down, or you may have incorrectly typed the URL. It's also possible that the newsgroup you chose isn't available through your ISP, in which case you won't be able to access the newsgroup unless you contact your ISP and get it to add the newsgroup. Another possible problem is that you may have incorrectly entered your newsgroup preferences.
Permission denied - This message occurs when you're trying to upload a file to an FTP site.
The message indicates that the site's administrator won't allow the upload, the site is too busy, or that you've used the wrong syntax in the URL. Look at the URL syntax first and type it again. If the error message reappears, you should try again later. If the problem persists, you can try to E-mail the site's Webmaster for help.
You can't log on as an anonymous user - This error message appears when you try to access certain FTP sites.
It indicates that the site allows access only to registered members, or that the site allows access to only a limited number of non-members, in which case the site is simply busy. You can try to access the site again later, or if you're a registered member, try entering your user ID and password manually using an FTP software package.
BIOS Error Beeps and Messages/Codes
AMI BIOS - Audio Beep Errors
| Number of Beeps | Description of Problem | Solution |
| 1 beep | DRAM refresh failure | Try re-seating the memory first. If the error still occurs, replace the memory with known good chips. [ Top of Page ] |
| 2 beeps | Parity Circuit Failure | [ Top of Page ] |
| 3 beeps | Base 64K RAM failure | [ Top of Page ] |
| 4 beeps | System Timer Failure | Send System Board in for Repair. [ Top of Page ] |
| 5 beeps | Processor Failure | [ Top of Page ] |
| 6 beeps | Keyboard Controller / Gate A20 Failure | 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. [ Top of Page ] |
| 7 beeps | Virtual Mode Exception Error | Send System Board in for Repair. [ Top of Page ] |
| 8 beeps | Display Memory Read/Write Failure | 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. [ Top of Page ] |
| 9 beeps | ROM BIOS Checksum Failure | 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). [ Top of Page ] |
| 10 beeps | CMOS Shutdown Register Read/Write Error | Send System Board in for Repair. [ Top of Page ] |
| 1 long 2 short | Video failure | Reseat the video board - replace if board is determined to be faulty. [ Top of Page ] |
| 1 long 3 short | Video failure | [ Top of Page ] |
| 1 long | POST passed. | No Errors. [ Top of Page ] |
AMI BIOS - Error Messages/Codes
| Error Message | Problem | Solution |
| CH-2 Timer Error | Non fatal. Could be caused by a peripheral. | [ Top of Page ] |
| INTR #1 Error | Interrupt Channel 1 has failed the POST test | Check system boards for IRQs 0-7. [ Top of Page ] |
| INTR #2 Error | Interrupt Channel 2 has failed the POST test | Check system boards for IRQs 8-15. [ Top of Page ] |
| CMOS Battery State Low | Replace Internal battery. [ Top of Page ] | |
| CMOS Checksum Failure | 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. | Run the setup program again to correct the problem. [ Top of Page ] |
| CMOS Memory Size Mismatch | Usually caused when you add or remove memory from your system but could be caused by memory that has failed. | Run setup. [ Top of Page ] |
| CMOS System Optons Not Set | CMOS values are either corrupt or do not exist. | Run Setup. [ Top of Page ] |
| Display Switch Not Proper | Many motherboards have a jumper setting that allows you to specify whether you have a color or monochrome monitor. | Correct the switch position. [ Top of Page ] |
| Keyboard is locked ... Unlock it | Unlock the keyboard. [ Top of Page ] | |
| Keyboard Error | There is a problem with the keyboard | 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. [ Top of Page ] |
| K/B Interface Error | There is a problem with the keyboard connector on the motherboard. | [ Top of Page ] |
| FDD Controller Failure | The BIOS cannot communicate with the floppy drive controller. | The floppy may be disabled, also check that the cable is not loose. [ Top of Page ] |
| HDD Controller Failure | The BIOS cannot communicate with the hard disks. | The hard disk may be disabled, also check that the cable is not loose. [ Top of Page ] |
| C: Drive Error | The system cannot get a response from drive C. | The hard disk type is most likely set incorrectly, or the disk may not be formatted or connected properly. [ Top of Page ] |
| D: Drive Error | Same as above except for drive D. | Same as above. [ Top of Page ] |
| C: Drive Failure | The drive was detected but failed. More serious than error. | [ Top of Page ] |
| D: Drive Failure | Same as above. | [ Top of Page ] |
| CMOS Time and Date Not Set | Run Setup [ Top of Page ] | |
| Cache Memory Bad, do Not Enable Cache! | Cache may indeed be bad, if so replace. May simply need re-seating. [ Top of Page ] | |
| 8042 Gate-A20 Error! | The Gate-A20 portion of the keyboard controller has failed. | Replace the keyboard chip (8042) [ Top of Page ] |
| Address Line Short | There is a problem with the memory address decoding circuitry. | Try rebooting, (turn the system off and then on 10 seconds later). The problem may correct itself. [ Top of Page ] |
| DMA #1 Error | There is an error in the first DMA channel on the motherboard | Could be caused by a peripheral device. [ Top of Page ] |
| DMA Error | There is an error within the DMA controller on the motherboard. | [ Top of Page ] |
| No ROM Basic | There is nothing to boot from. (i.e.- the system cannot find an operating system). | Be certain that a bootable disk is defined in the system setup. [ Top of Page ] |
| Diskette Boot Failure | The diskette in the specified boot-up drive is corrupt. | [ Top of Page ] |
| Invalid Boot Diskette | Same as above, but the disk is readable. | [ Top of Page ] |
| On Board Parity Error | 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). | Possibly correctable with software from the motherboard manufacturer. (also do a Virus Check - some viruses cause parity errors). [ Top of Page ] |
| Off Board Parity Error | There is a parity error with memory installed in an expansion slot at address XXXX (hex) | Same as above. [ Top of Page ] |
| Parity Error | There is a parity error with memory somewhere in the system. | Same as above. [ Top of Page ] |
| Memory Parity Error at XXXX | Memory has failed. If it cannot be determined, it is displayed as XXXX, if not, as ???? | Same as above. [ Top of Page ] |
| I/O Card Parity Error at XXXX | Same as above. | Same as above. [ Top of Page ] |
| DMA Bus Time-out | A device has driven the bus signal for more than 7.8 microseconds. | Troubleshoot all system boards. (remove them and try to isolate the failure) [ Top of Page ] |
| Memory mismatch, run Setup | Disable Memory Relocation if possible. [ Top of Page ] | |
| EISA CMOS Checksum Failure | The checksom for EISA CMOS is bad, or the battery is bad. | [ Top of Page ] |
| EISA CMOS Inoperational | A read/write failure occured in extended CMOS RAM. | The battery may be bad. [ Top of Page ] |
| Expansion Board not ready at Slot X | AMI BIOS cannot find the expansion board in X slot. | Verify that the board is in the correct slot and is seated properly. [ Top of Page ] |
| Fail-Safe Timer NMI Inoperational | Devices that depend on the fail-safe NMI timer are not operating correctly. | [ Top of Page ] |
| ID information mismatch for Slot X | The ID of the EISA expansion board in slot X does not match the ID in CMOS RAM. | [ Top of Page ] |
| Invalid Configuration Information for Slot X | The configuration information for EISA board X is not correct. | Run the ECU. [ Top of Page ] |
| Software Port NMI Inoperational | The software port NMI is not working. | [ Top of Page ] |
| BUS Timeout NMI at Slot X | There was a bus timeout NMI at Slot X. | [ Top of Page ] |
| (E)nable (D)isable Expansion Board? | Type E to enable the board that had an NMI or D to disable it. [ Top of Page ] | |
| Expansion Board disabled at Slot X | The expansion board NMI was generated from slot X. | [ Top of Page ] |
| Fail-Safe Timer NMI | A fail-safe timer NMI has been generated. | [ Top of Page ] |
| Software Port NMI | A software port NMI has been generated. | [ Top of Page ] |
Award BIOS ISA/EISA v4.5x - Audio Beep Errors
| Number of Beeps | Description of Problem | Solution |
| 1 long, 2 short | Video error | Reseat the video card - replacement may be necessary if it is faulty. [ Top of Page ] |
Award BIOS ISA/EISA v4.5x - Error
Messages/Codes
| Error Message | Problem | Solution |
| CMOS BATTERY HAS FAILED | CMOS battery is no longer functional. | Replace battery. [ Top of Page ] |
| CMOS CHECKSUM ERROR | Checksum of CMOS is incorrect. This can indicate that CMOS has become corrupt. This error may have been caused by a weak battery. | [ Top of Page ] |
| DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER | No boot device was found. This could mean that either a boot drive was not detected or the drive does not contain proper system boot files. | Insert a system disk into Drive A: and press Enter. If you assumed the system would boot from the hard drive make sure the controller is inserted correctly and all cables are properly attached. Also be sure the disk is formatted as a boot device. Then reboot the system. [ Top of Page ] |
| DISKETTE DRIVES OR TYPES MISMATCH ERROR - RUN SETUP | Type of diskette drive installed in the system is different from the CMOS definition. | Run Setup and enter the drive type correctly. [ Top of Page ] |
| DISPLAY SWITCH IS SET INCORRECTLY | Many motherboards have a jumper or switch that allows you to specify whether you have a monochrome or color video board. | Check the jumper or switch and correct it's position. [ Top of Page ] |
| DISPLAY TYPE HAS CHANGED SINCE LAST BOOT | Since you last shut the system down, the display has been changed. | Run Setup and reconfigure display if possible. [ Top of Page ] |
| EISA Configuration Checksum Error | The EISA non-volatile RAM checksum is incorrect or cannot correctly read the EISA slot. | Run the EISA Configuration Utility. Either the EISA non-volatile memory has become corrupt or the slot has been configured incorrectly. Also make sure the card is installed firmly in the slot. When this error appears, the system will boot in ISA mode, which allows you to run the EISA Configuration Utility. [ Top of Page ] |
| EISA Configuration is Not Complete | The slot configuration information stored in the EISA non-volatile memory is incomplete. When this error appears, the system will boot in ISA mode, which allows you to run the EISA Configuration Utility. | Run the EISA Configuration Utility. [ Top of Page ] |
| ERROR ENCOUNTERED INITIALIZING HARD DRIVE | The hard drive cannot be initialized. | Be sure the adaptor/controller is installed correctly and that all cables are correctly and firmly attached. Also make sure the correct hard drive type is selected in Setup. [ Top of Page ] |
| ERROR INITIALIZING HARD DRIVE CONTROLLER | Cannot initiallize the controller card. | Make sure the card is correctly and firmly seated in the system board. Be sure the correct hard drive type is selected in Setup. Also check to see if any jumpers need to be set on the hard drive. [ Top of Page ] |
| FLOPPY DISK CNTRLR ERROR OR NO CNTRLR PRESENT | Cannot find or initialize the floppy drive controller. | Make certain the controller is installed correctly and firmly. If there are no floppy drives installed, be sure the Diskette Drive selection in Setup is set to NONE. [ Top of Page ] |
| Invalid EISA Configuration | The non-volatile memory containing EISA configuration information was programmed incorrectly or has become corrupt. | Re-run EISA Configuration Utility to correctly program the memory. When this error occurs, the system will boot in ISA mode which allows you to run the EISA Configuration Utility. [ Top of Page ] |
| KEYBOARD ERROR OR NO KEYBOARD PRESENT | Cannot initialize the keyboard. | Make sure the keyboard is attached correctly and that no keys are stuck or are being pressed during the boot. If you are purposely configuring the system without the keyboard, set the error halt condition in Setup to HALT ON ALL, BUT KEYBOARD. This will cause the BIOS to ignore the missing keyboard and continue the boot. [ Top of Page ] |
| Memory Address Error at XXXX | Indicates a memory address error at XXXX location. | Use the location along with the memory map for your system to find and replace the bad memory chips. [ Top of Page ] |
| Memory parity Error at XXXX | Indicates a memory parity error at XXXX location. | Same as Above. [ Top of Page ] |
| MEMORY SIZE HAS CHANGED SINCE LAST BOOT | Memory has been added or removed since the last boot. | In EISA mode, use the EISA Configuration Utility to reconfigure the memory configuration. In ISA mode, enter Setup and enter the new memory size in the memory fields if possible. [ Top of Page ] |
| Memory Verify Error at XXXX | Indicates an error verifying a value already written to memory. | Use the location along with your system's memory map to locate the bad chip(s). [ Top of Page ] |
| OFFENDING ADDRESS NOT FOUND | This message is used in conjunction with the I/O CHANNEL CHECK and RAM PARITY ERROR messages when the segment that has caused the problem cannot be isolated. | [ Top of Page ] |
| OFFENDING SEGMENT: | Same as above. | [ Top of Page ] |
| PRESS A KEY TO REBOOT | This message is displayed at the bottom of the screen when an error occurs that requires you to reboot. | Press any key to reboot the system. [ Top of Page ] |
| PRESS F1 TO DISABLE NMI, F2 TO REBOOT | When BIOS detects a Non-maskable Interrupt condition during boot, this will allow you to disable the NMI and continue to boot, or you can reboot the system with the NMI enabled. | [ Top of Page ] |
| RAM PARITY ERROR - CHECKING FOR SEGMENT | Indicates a parity error in Random Access Memory. | [ Top of Page ] |
| Should Be Empty But EISA Board Found | A valid board ID was found in a slot that was configured as having no board ID. | Run the EISA Configuration Utility. [ Top of Page ] |
| Should Have EISA Board But Not Found | The board installed is not responding to the ID request, or no board ID has been found in the indicated slot. | Run the EISA Configuration Utility. [ Top of Page ] |
| Slot Not Empty | A slot designated as empty by the EISA Configuration Utility actually contains a board. | Run the EISA Configuration Utility. [ Top of Page ] |
| SYSTEM HALTED, (CTRL-ALT-DEL) TO REBOOT ... | Indicates the present boot attempt has been aborted and the system must be rebooted. | Press and hold down the CTRL and ALT keys and press the DEL key simultaneously. [ Top of Page ] |
| Wrong Board in Slot | The board ID does not match the ID stored in the EISA non-volatile memory. | Run the EISA Configuration Utility. [ Top of Page ] |
DOS Error Messages
8042 GATE-A20 ERROR - Usually caused by a bad keyboard. Try a different one.
8087 NMI AT XXXX.XXXX. TYPE (S)HUT OFF NMI, (R)EBOOT, OTHER KEYS TO CONTINUE - Your math coprocessor has generated a Non-maskable interrupt. Have your math coprocessor tested. If it has failed, replace it.
ACCESS DENIED - Your have tried to perform a write function to a read-only file. If using a floppy, make sure the disk is not write-protected. If you really want to delete the file, you can change it be a regular file, then delete it. In Windows 95, right click the file, choose Properties, then un-check the "Read-Only" box. In DOS, use the ATTRIB command.
ALLOCATION ERROR, SIZE ADJUSTED - CHKDSK is telling you that the physical size and the allocated size of a file do not match. It is not a big deal, but if this error is gotten often, backup your hard drive, because this is sign of a coming failure.
ATTEMPTED WRITE-PROTECT VIOLATION - You tried to format a write-protected floppy diskette.
BAD DMA PORT = XX - Your DMA controller chip on the motherboard has failed the POST. You will likely have to replace your motherboard.
BAD OR MISSING COMMAND INTERPRETER - More than likely, you are trying to boot from a disk that is missing COMMAND.COM. If this is a hard disk, replace this file into the root directory.
BAD PARTITION TABLE - Try reperforming FDISK on this drive. After this, if you still get this error, try low-level formatting the drive. Another possibility is that you have picked up a computer virus which has damaged the partition table. Try running anti-virus software.
BUS TIMEOUT NMI AT SLOT X - There is a error with your EISA bus. Make sure the card in slot X is configured correctly. If this doesn't do it, call the manufacturer of the card. If all else fails, there is a possibility of a faulty motherboard.
C: DRIVE ERROR - Your C: drive is not properly configured in the CMOS. Run setup and reconfigure.
C: DRIVE FAILURE - This is a time out message saying the computer has gotten no response from the hard drive. There is a possibility your hard drive has crashed, but first check to be sure the drive is receiving power from the power supply and that the data cable is attached correctly.
CACHE MEMORY BAD, DO NOT ENABLE CACHE! - The cache memory chips on your motherboard are malfunctioning. Locate and reseat them. You may have to replace the cache.
CH-2 TIMER ERROR - The timer chip on your motherboard is not working. Replace the motherboard.
CMOS BATTERY STATE LOW - Replace the CMOS battery.
CMOS CHECKSUM FAILURE - The checksum error correcting has detected corruption in your CMOS data. Replace your CMOS battery and re-run setup. If the problem persists, the CMOs chip is probably bad, and you'll have to replace the motherboard.
CMOS DISPLAY TYPE MISMATCH - Your CMOs says you have a monochrome video card installed. Correct this information in setup.
COM PORT DOES NOT EXIST - You are trying to use a COM port that does not exist. Run a diagnostic utility and see if the computer recognizes the COM port you are trying to use.
DATA ERROR READING DRIVE X: - Usually caused by the slow misalignment of disk drives over time. Use a disk fixing utility to realign the disk's data.
DISK BAD - A rather general error meaning some thing related to your hard drive is not working anymore. First, check to be sure all of your data cables are attached correctly. Listen and see if the hard drive platters are spinning. If necessary, unplug the drive and then re-plug it in in order to better differentiate the drive's sound from the rest of the system. If it is not spinning, try another power supply lead. If that doesn't help, your hard drive is probably shot.
DISK BOOT ERROR, REPLACE AND STRIKE ANY KEY WHEN READY - You are trying to boot of a disk that is not bootable. Make sure it is a valid system disk.
DISK CONFIGURATION ERROR - Usually caused by trying to use a newer technology drive on a system that is too old. Your BIOS does not recognize the code in the CMOS for this newer drive. This problem can be fixed by updating your BIOS, in most cases.
DISK DRIVE 0 SEEK FAILURE - Drive 0 and 1 refer to your a: and b: drive. Most often, if you get this error it is because your BIOS is looking for a drive that is not there. Check your setup and be sure that only the floppy drives located on your machine are activated.
DISK DRIVE RESET FAILED - The disk drive controller cannot reset. Trying turning the system off and back on again. If this doesn't fix anything, you'll probably have to replace the drive controller.
DISK BOOT FAILURE - Most likely, the boot disk in the A: drive is bad. Try another one.
DISK READ FAILURE - Many potential problems. Try another disk. Make sure the cables are correctly attached to the drive. If all this is ruled out, your floppy drive is probably bad.
DISPLAY SWITCH NOT SET PROPERLY - Some older 286-486 computers have a jumper on the motherboard that controls monochrome vs. color. Check to be sure that it is set correctly.
DMA ERROR - Your DMA chip has failed. You'll have to replace the motherboard.
DRIVE NOT READY - If this is a floppy drive, make sure the disk is inserted all the way. Try another disk. Make sure the floppy drive cable is not damaged. If this doesn't pinpoint the problem, you'll have to replace the floppy drive. You may have a bad sensor, so it can't sense a disk inside it.
EXPANSION BOARD NMI AT SLOT X - The board in slot X has produced a nonmaskable interupt error. Remove the card and inspect it for damage. Consult its manual or the manufacturer.
FAIL SAFE TIMER NMI - An EISA device has gone awry. It is taking up the entire bus. Try rebooting. If this doesn't help, try to narrow down which expansion card is producing the error by removing them one by one and rebooting. If none of the cards seem to be suspect, the problem may lie with the motherboard itself.
FDD CONTROLLER FAILURE - This often means your floppy drive controller has failed, or possibly the drive itself. If using an I/O card, make sure it is still seated fully in the bus. Check all cables. If the obvious is ruled out, buy a new controller.
FILE ALLOCATION TABLE BAD - There is a problem with the FAT. Try running a disk repair utility.
FIXED DISK CONFIGURATION ERROR, CONTROLLER FAILURE - See Hard Disk Configuration Error.
GATE A20 FAILURE - The computer has had to switch into protected mode in order to count its memory. First, try another keyboard. A bad keyboard can cause the controller to send misc. signals across the address line 20. If this doesn't help, then you'll have to replace the motherboard.
GENERAL FAILURE READING DRIVE X: - First, press I for ignore, then use a diagnostic utility to test the disk. If this doesn't help, press A for abort, then inspect all cables related to the drive producing the error. If it a floppy, try another diskette.
HARD DISK FAILURE - See C: DRIVE FAILURE above.
HARD DISK READ FAILURE - STRIKE F1 TO RETRY BOOT - First, check the hard drive cables. f this isn't the problem, press F1 and see if it reboots. If it does, run a diagnostic on the drive. If it doesn't reboot, boot the system off a system disk then switch to C:. If you get an Invalid Drive message, then the computer is getting no signal from the drive. Make sure the drive is properly set up in CMOS. Try rebooting again. If all else fails, try reformatting the drive. If this doesn't help, your drive or controller is crashed.
INFINITE RETRY ON PARALLEL PRINTER TIMEOUT, PRINTER DEVICE FAILURE - Makes sure your printer is turned on and on-line. If you have a device between the printer and the computer, such as a ZIP drive, make sure it is turned on, too.
INSUFFICIENT MEMORY - Your software is trying to use more memory than is physically installed in your system. Try adding more memory, or running a memory management program. See if you have any unnecessary programs running. Check your start up folder to see what starts on boot up.
INTERNAL CACHE TEST FAILED - Reboot and try again. If this doesn't help, your CPU cache is probably dead. You'll need a new processor.
INTR1 ERROR - Replace your motherboard. The interrupt controller is fried.
INVALID BOOT DISKETTE - Try another valid system disk.
KEYBOARD BAD - Your keyboard has failed the post. Make sure it is connected. If it is, replace the keyboard.
KEYBOARD CLOCK LINE FAILURE, STUCK KEY FAILURE - The keyboard is not responding to the controller's POST tests. Either the keyboard is bad of its cable is bad. Makes sure there are no stuck keys.
KEYBOARD ERROR - Your keyboard may be incompatible with the AMIBIOS in your system. You can try to get around this by setting the keyboard to "Not Installed" in setup in order to skip the keyboard POST.
MEMORY ADDRESS LINE FAILURE AT XXX:XXX, ... - Impossible to fix. Replace the motherboard.
MEMORY PARITY ERROR AT XXXX - One of your memory chips is bad. Locate and replace.
NO BOOT DEVICE AVAILABLE - Your system can't find anything to boot off of. It displays this error after searching for a Drive A: and a C: and finding nothing. Make sure your drive cables are in place. Make sure you have a valid system disk in Drive A:. If there is not supposed to be a disk in Drive A:, then the problem lies with your hard drive. Try hitting F1 to reboot. Then run a disk diagnostic utility. It is possible your boot segment is damaged or out of alignment.
NON-DOS DISK ERROR READING(WRITING) DRIVE X: - The computer can't find a boot track on the disk. Boot off a floppy then use SYS to recopy the system files over.
NON SYSTEM DISK OR DISK ERROR - You are trying to boot of a non-system disk. If it a floppy disk, then try another one, or simply remove the one you forgot to remove. If it a hard drive, you'll have to boot off a floppy then use SYS to recopy system files to the hard drive.
NO TIMER TICK INTERRUPT - Your timer chip can't get the interrupt controller to designate interrupt 0. Your motherboard will have to be replaced.
NOT READY READING DRIVE X: - Usually, the cause of this is that the drive door of your diskette drive is not closed all the way. If it is, then you may have a bad sensor in your disk drive.
POINTER DEVICE FAILURE - There is a problem with your pointer device attached to your PS/2 mouse port. Make sure it is properly connected to the computer. Try another device.
PROCESSING CANNOT CONTINUE - Happens when you run a DOS utility without enough memory. Add more RAM.
RAM BAD - Pretty self explanatory. Usually, one or more of your RAM chips is bad. Its best to bring your system on just the RAM to a shop and have them test for the bad chip. If no memory is bad, the problem could lie with your motherboard.
REAL TIME CLOCK FAILURE - Run setup again and reset the time. If the problem persists, try replacing the battery. If that doesn't do it, replace the power supply.
RESUME='F1' KEY - Some type or error has occurred, but hitting F1 allows you to continue.
XX=SCANCODE, CHECK KEYBOARD - The computer received a strand signal from the keyboard. It may be caused by a bad connector a maybe even a stuck key. Either fix the stuck key or try another keyboard.
TARGET DISK IS WRITE PROTECTED - Often seen when trying to do a DISKCOPY to a write protected floppy disk. If the disk is not write protected, then that part of your floppy drive that senses write protection may be broken. Best bet is to buy another diskette drive.
TRACK 0 BAD - DISK UNUSABLE - This error may be seen if trying to format a larger disk in a lower capacity floppy drive. It could also mean your disk is bad, in which case you just try another. If this is your hard drive, then you'll likely have to replace the hard drive.
UNLOCK SYSTEM UNIT KEYLOCK - You have locked the keyboard out by locking the keylock on the front of your computer. Unlock it then reboot.
Questions about a service or product?
Or email us at
webmaster@jmgrossconsulting.com
with questions or comments about this web site.
Copyright © 2005 J M Gross Consulting