| Problem | Solution |
| Power problem | If no lights are on either on the computer or monitor, check your power outlet. Toggle the power switch on both computer and monitor. If power light on the monitor is OK, but lights on the computer are all off, most likely power supply is defective. |
| Floppy problem | If you have an 'A" floppy 3 1/2", and can not access it, then you either have (a) a defective floppy drive, (b) a defective floppy drive cable, or (c) CMOS setup is incorrect. Also, do not rule out the possibility of a defective diskette. |
| Hard Drive problem | Does your computer try to boot only from the floppy drive, i.e. the A drive light stays on? This means your computer cannot access the hard drive. Caused by corrupted "boot track" on the hard drive. Try putting a bootable diskette in the A floppy drive, and reboot your computer. When you get the A> prompt, try entering C: which should give you the "C" prompt. If you get the "C:" prompt try typing "dir" (return) and you get a directory listing of files on the hard drive. you probably just have a corrupted "boot track". If you get a message "invalid drive specification" your hard drive is probably dead. |
| Memory problem | Memory problems are relatively rare. Are you getting a count up during your memory test on power up? Does it count to the maximum you know you have in your machine - a number like "1024K" or "4096K" that you are used to seeing? If there has been a recent change in this number, then you do indeed have defective memory. Note that some so-called memory problems are caused by software demanding more memory than is available in your machine. Are you running a new program? Some memory problems are caused by improper CMOS settings; others occur with certain software because "CONFIG.SYS" file used on bootup is incorrect. |
| CMOS problem | Do your CMOS settings change when you turn power off? If so, you have a defective backup battery on your motherboard. Some machines have rechargeable Ni Cad batteries, which will rejuvenate if the machine is left on for 24 hours or so. Many still have Lithium batteries which need to be changed at intervals of 3 years or so. |
| Problems after booting | Pc Freezes: Check CPU fan, case fan and power box fan, make sure all are working and clean off dust. Check hard drive, CPU, power supply for over heating. Some video cards may also heat up and create excessive heat inside the case. Make sure that the case is kept cool, by maintaining good air flow.
|
| Pc Restarts while in use |
|
| Voltage problem or overheated components | If the computer is actually functioning and the computer beeps continuously, then there is a problem with a voltage on the power supply being incorrect or the CPU overheating. Go into the BIOS and check CPU temperature, fan speed and voltages |
| Unreliable USB Ports |
|
| Possessed PC |
|
| Printer Goes Clueless |
|
| Monitor is blank. |
|
| Monitor light lit but monitor is blank. | Check the following:
|
| The monitor is blank, but there are no lights on the keyboard. | Check all switches, circuit breakers and cables. Computer power cables sometimes look like they’re plugged in, but need to be pushed in harder to make contact. Push all the power cables into the equipment to make sure they are seated firmly. |
| A blue screen with any of these words:fatal exception, invalid, overflow, insufficient memory. | You need to reboot the computer.You will lose all information typed in since the most recent save. If there is a reset button on the computer box, push it.Otherwise, push and hold down the CTRL and ALT keys. WHile holding them down, gently tap the DELETE key once. If the mouse works, click on Shut Down. Otherwise, tap the S key while holding down the ALT key. This will turn off the computer. Once it is off, count to ten and turn it back on again. |
| Keyboard error - press F1 to continue. | Your keyboard is unplugged, defective, or the plug is loose. Make sure it is firmly plugged in. Hit the F1 key. If it still does not respond, reboot the computer by hitting the reset button (if there is one) or else turn the power off to the computer. Wiggle all the keyboard connectors, count to ten and turn it back on. If this happens repeatedly, the keyboard should be replaced. If the comptuer boots normally, you're done. |
| Your computer was improperly shut down. Press any key to run a Scan Disk. | Press any key. The computer will attempt to correct the errors caused by improper shut down. Next time, please turn the computer off using the Shut Down command. |
| Mouse problems. |
|
Definitions and Solutions for BIOS Error Beeps and Messages Codes
Source: iSAVE
AMIBIOS
AMIBIOS Audio Beep Erros
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
2 beeps
Parity Circuit Failure
3 beeps
Base 64K RAM failure
4 beeps
System Timer Failure
Send System Board in for Repair
5 beeps
Processor Failure
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.
7 beeps
Virtual Mode Exception Error
Send System Board in for Repair
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.
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).
10 beeps
CMOS Shutdown Register Read/Write Error
Send System Board in for Repair
1 long 2 short
Video failure
Reseat the video board - replace if board is determined to be faulty.
1 long 3 short
Video failure
1 long
POST
No Errors
AMIBIOS Error Messages/Codes
Error Messages
Problem
Solution
CH-2 Timer Error
Non fatal. Could be caused by a peripheral.
INTR #1 Error
Interrupt Channel 1 has failed the POST test
Check system boards for IRQs 0-7.
INTR #2 Error
Interrupt Channel 2 has failed the POST test
Check system boards for IRQs 8-15.
CMOS Battery State Low
Replace battery.
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.
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.
CMOS System Options Not Set
CMOS values are either corrupt or do not exist.
Run Setup.
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.
Keyboard is locked ... Unlock it
Unlock the keyboard.
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.
AWARD
AWARD Audio Beep
Number of Beeps
Description of Problem
Solutions
1 long, 2 short
Video adapter error
Either video adapter is bad or is not seated properly. Also, check to ensure the monitor cable is connected properly.
Repeating (endless loop)
Memory error
Check for improperly seated or missing memory.
1 long, 3 short
No video card or bad video RAM
Reseat or replace the video card.
High frequency beeps while running
Overheated CPU
Check the CPU fan for proper operation. Check the case for proper air flow.
Repeating High/Low
Either the CPU is not seated properly or damaged. May also be due to excess heat.
Check the CPU fan or BIOS settings for proper fan speed.
AWARD Error Messages/Codes
Error Messages
Problem
Solution
CMOS BATTERY HAS FAILED
CMOS battery is no longer functional.
Replace battery.
CMOS CHECKSUM ERROR
Checksum of CMOS is incorrect. This can indicate that CMOS has become corrupt. A weak battery may have caused this error.
Check battery and replace it if necessary.
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.
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.
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.
DISPLAY TYPE HAS CHANGED SINCE LAST BOOT
Since you last shut the system down, the display had been changed.
Run Setup and reconfigure display if possible.
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.
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.
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.
ERROR ENCOUNTERED INITIALIZING HARD DRIVE
The hard drive cannot be initialized.
Be sure the adapter/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.
ERROR INITIALIZING HARD DRIVE CONTROLLER
Cannot initialize 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.
FLOPPY DISK CONTROLLER ERROR OR NO CONTROLLER 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.
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 that allows you to run the EISA Configuration Utility.
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.
Memory parity Error at XXXX
Indicates a memory parity error at XXXX location.
Same as Above.
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.
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).
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.
OFFENDING SEGMENT:
Same as above.
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.
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.
RAM PARITY ERROR - CHECKING FOR SEGMENT
Indicates a parity error in Random Access Memory.
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.
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.
Wrong Board in Slot
The board ID does not match the ID stored in the EISA non-volatile memory.
Run the EISA Configuration Utility.
PHOENIX
PHOENIX Bios Beep Codes
Phoenix beep codes are the most detailed about. They use a system of 4 beeps each separated by a small pause i.e. 1 pause 2 pause 1 pause 1 pause (1-2-1-1), you may need to reboot the pc a few times in order to count all the beeps. To find out more information on Phoenix beep codes you can go here.
Beeps Codes
Description What to Check
1-1-1-3
Verify Real Mode.
1-1-2-1
Get CPU type.
1-1-2-3
Initialize system hardware.
1-1-3-1
Initialize chipset registers with initial POST values.
1-1-3-2
Set in POST flag.
1-1-3-3
Initialize CPU registers.
1-1-4-1
Initialize cache to initial POST values.
1-1-4-3
Initialize I/O.
1-2-1-1
Initialize Power Management.
1-2-1-3
Jump to UserPatch0.
1-2-2-1
Initialize keyboard controller.
1-2-2-3
BIOS ROM checksum.
1-2-3-1
8254 timer initialization.
1-2-3-3
8237 DMA controller initialization.
1-2-4-1
Reset Programmable Interrupt Controller.
1-3-1-1
Test DRAM refresh.
1-3-1-3
Test 8742 Keyboard Controller.
1-3-2-1
Set ES segment to register to 4 GB.
1-3-3-1
28 Autosize DRAM.
1-3-3-3
Clear 512K base RAM.
1-3-4-1
Test 512 base address lines.
1-4-1-3
Test CPU bus-clock frequency.
1-4-2-4
Reinitialize the chipset.
1-4-3-1
Shadow system BIOS ROM.
1-4-3-2
Reinitialize the cache.
1-4-3-3
Autosize cache.
1-4-4-1
Configure advanced chipset registers.
1-4-4-2
Load alternate registers with CMOS values.
2-1-1-1
Set Initial CPU speed.
2-1-1-3
Initialize interrupt vectors.
2-1-2-1
Initialize BIOS interrupts.
2-1-2-3
Check ROM copyright notice.
2-1-2-4
Initialize manager for PCI Options ROMs.
2-1-3-1
Check video configuration against CMOS.
2-1-3-2
Initialize PCI bus and devices.
2-1-3-3
Initialize all video adapters in system.
2-1-4-1
Shadow video BIOS ROM.
2-1-4-3
Display copyright notice.
2-2-1-1
Display CPU type and speed.
2-2-1-3
Test keyboard.
2-2-2-1
Set key click if enabled.
2-2-2-3
56 Enable keyboard.
2-2-3-1
Test for unexpected interrupts.
2-2-3-3
Display prompt "Press F2 to enter SETUP".
2-2-4-1
Test RAM between 512 and 640k.
2-3-1-1
Test expanded memory.
2-3-1-3
Test extended memory address lines.
2-3-2-1
Jump to UserPatch1.
2-3-2-3
Configure advanced cache registers.
2-3-3-1
Enable external and CPU caches.
2-3-3-3
Display external cache size.
2-3-4-1
Display shadow message.
2-3-4-3
Display non-disposable segments.
2-4-1-1
Display error messages.
2-4-1-3
Check for configuration errors.
2-4-2-1
Test real-time clock.
2-4-2-3
Check for keyboard errors
2-4-4-1
Set up hardware interrupts vectors.
2-4-4-3
Test coprocessor if present.
3-1-1-1
Disable onboard I/O ports.
3-1-1-3
Detect and install external RS232 ports.
3-1-2-1
Detect and install external parallel ports.
3-1-2-3
Re-initialize onboard I/O ports.
3-1-3-1
Initialize BIOS Data Area.
3-1-3-3
Initialize Extended BIOS Data Area.
3-1-4-1
Initialize floppy controller.
3-2-1-1
Initialize hard-disk controller.
3-2-1-2
Initialize local-bus hard-disk controller.
3-2-1-3
Jump to UserPatch2.
3-2-2-1
Disable A20 address line.
3-2-2-3
Clear huge ES segment register.
3-2-3-1
Search for option ROMs.
3-2-3-3
Shadow option ROMs.
3-2-4-1
Set up Power Management.
3-2-4-3
Enable hardware interrupts.
3-3-1-1
Set time of day.
3-3-1-3
Check key lock.
3-3-3-1
Erase F2 prompt.
3-3-3-3
Scan for F2 key stroke.
3-3-4-1
Enter SETUP.
3-3-4-3
Clear in-POST flag.
3-4-1-1
Check for errors
3-4-1-3
POST done--prepare to boot operating system.
3-4-2-1
One beep.
3-4-2-3
Check password (optional).
3-4-3-1
Clear global descriptor table.
3-4-4-1
Clear parity checkers.
3-4-4-3
Clear screen (optional).
3-4-4-4
Check virus and backup reminders.
4-1-1-1
Try to boot with INT 19.
4-2-1-1
Interrupt handler error.
4-2-1-3
Unknown interrupt error.
4-2-2-1
Pending interrupt error.
4-2-2-3
Initialize option ROM error.
4-2-3-1
Shutdown error.
4-2-3-3
Extended Block Move.
4-2-4-1
Shutdown 10 error.
4-3-1-3
Initialize the chipset.
4-3-1-4
Initialize refresh counter.
4-3-2-1
Check for Forced Flash.
4-3-2-2
Check HW status of ROM.
4-3-2-3
BIOS ROM is OK.
4-3-2-4
Do a complete RAM test.
4-3-3-1
Do OEM initialization.
4-3-3-2
Initialize interrupt controller.
4-3-3-3
Read in bootstrap code.
4-3-3-4
Initialize all vectors.
4-3-4-1
Boot the Flash program.
4-3-4-2
Initialize the boot device.
4-3-4-3
Boot code was read OK.
MS DOS ERRORS
Abort, Retry, Fail?
Usually you will get this error message if you are trying to read a disk that is not readable of if no disk is in there
Access denied
Usually meaning the file has an attribute on it *TIP* if you need to delete the file just deltree FILE
Bad command or file name
Usually this is when you miss type a command or if DOS does not know the command.
Bad or missing command interpreter
DOS cannot locate the Command.com a important file that holds all of DOS's needed information, you will need to recopy it also there is a chance you could possible have a Virus
Divide overflow
Program has attempted to divide something by 0.
Drive not ready error
Disk in the drive is not readable, such as a disk not being in the disk drive.
Duplicate file name or file not found
When attempting to rename a file the file does not exist or there is already a file with that name.
File cannot be copied onto itself
An attempt to copy a file could not be completed because the file already exists or same source and destination.
File creation error
Directory could be full because of the DOS limitation of files in one directory the file could also already exist or the file was not copied correctly
File not found
Meaning that in the directory that you searched does not have that certain file or there are no files in the directory.
General Failure
Something bad has occurred and DOS not know what to say so it just gives you this error if this is giving when try reading the Hard drive you may need to format the hard drive or it possible even could be bad - Usually meaning the file has an attribute on it *TIP* if you need to delete the file just deltree FILE
Insufficient disk space
Disk is full or if you are trying to copy a file to a disk the file is too big to fit on the disk.
Internal stack overflow
DOS's internal storage areas are full if you need to go into your config.sys and increase the STACKS=0,0
Invalid directory
Directory is invalid or does not exist in the directory you are currently in.
Invalid drive specification
Drive does not exist on the computer or cannot be found.
Invalid file name or file not found
DOS cannot find the file specified in the current directory or the file has a invalid character in it.
Invalid media, track 0 bad or unusable
Format command cannot format the specified disk or the disk capacity is invalid, or bad disk.
Invalid number of parameters
When the command was typed something was left out that DOS needed by the command, mistyped the command. or put a space where one was not needed.
Invalid parameter
Typed a command correctly but specified the incorrect parameter such as format /z
Invalid Switch
The wrong slash was typed such as cd/ when it is supposed to be cd.
Non-System disk or disk error
When booting up the computer this error will usually occur when there is a floppy disk in the computer that is not bootable if there is no disk inside the computer this could be an indication of a unrecognized hard drive, un formatted hard drive, or hard drive with missing system files.
Not ready, reading drive X
Attempted to read a disk that is not readable or there is no disk in that drive.
Write fault error
Tried to reroute text to a device that is not connected or is not valid or not hooked up.
Write protect
Tried to write to a disk that is write protected.
Create a free website at Webs.com