Troubleshooting Specific PC Symptoms
Modem
Troubleshooting
Troubleshooting
Specific PC Symptoms Troubleshooting
BIOS and Startup problems Troubleshooting
client for Netware Networks
Troubleshooting
Communications Troubleshooting
Device Configuration Troubleshooting
Disk Corruption Troubleshooting
Drivers Troubleshooting
Windows95 Start-up Troubleshooting
Applications Troubleshooting
Missing File Systems Troubleshooting
SCSI Device Problems Troubleshooting
Setup Errors Troubleshooting
Specific Startup Errors Troubleshooting
Floppy Disk Systems
Troubleshooting
CPU's Shareware
Utilities BIOS
and Beep Codes CDROMS
Conflict
Troubleshooting Troubleshooting
CMOS
| So you're having trouble with your computer,
here you can solve your problems by simply clicking on your symptom from
this handy Symptom list and the appropriate solution will pop-up.
Disclaimer. Use these diagnostic and repair routines at your own risk. A Gathering Place or NW Computer jbstone@usa.net will assume no responsibility for damage or injury incurred from using these methods. Symptom:
Start up problems
8. System boots up but "ROM error" appears on the
monitor. Symptom 1. System does nothing, no lights, fan or power. Make sure that the system is plugged in. If you are familiar with voltage testing procedures, test the AC voltage at the end of the cord that plugs into the computer make sure that it is between 110v and 120v but use extreme caution! Serious injury or damage can result from improper test procedures. Protect yourself from accidental electrocution. If the AC input level is acceptable then remove the case from the computer and carefully check that the power connections from the supply to the motherboard and drives are all tightly connected and not broken. Next disconnect the power lead from one of the floppy drives. Set your multimeter for D.C. voltage readings. Place the ground lead on pin 2 of the connector and the positive lead on pin 1. Power up the unit and read the voltage, it should be 12 v + next place the ground lead on pin 3 of the same connector and the positive lead on pin 4, the reading should be 5v + If these voltages are low or missing replace the power supply. If they are present at their normal value, move on and turn off the unit, then disconnect the power connector to the motherboard. There should be a legend on the actual supply stating the output voltages for each of the leads, if not then locate the black lead at the connector and connect your negative probe there. You should be able to read either 12v or 5v at each of the other leads. If any of these readings are low, replace the supply. Symptom 2. Light on the front panel comes on but no display. Check to make sure that your monitor is plugged in and working properly, it should have an indicator light that is lit. If possible check the monitor on another computer. Make sure that the data cable that plugs into the back of the computer is intact and not cut or broken. Inspect the connector and make sure the pins are straight and undamaged and all the same height and not pushed in. Make sure the video card is in the slot firmly and that the retaining screw is firmly in place. Make sure the female connector on the board is free of debris, corrosion and obstruction and is mounted firmly on the card. If the reset light remains brightly lit, there may be a problem with the power supply, the computer is waiting for a "power good" signal to continue the boot sequence, check the power supply (see symptom1) If there is still no video, replace the video card and try again. Symptom 3. System lights and video come on, but system hangs at POST and won't boot to windows. This can be a symptom of numerous problems which need to be broken down by category.
a. Are there a series of beep codes? (See 'Troubleshooting Beep Codes' in
the Troubleshooting section of this department.)
One of the most common causes of hang up at the start sequence (POST) is
an incorrect CMOS setting. The CMOS is the set of start up instructions that
tell your computer what hardware and accessories are installed and how to
deal with them. These instructions are kept in the CMOS's memory by using
a small back-up battery, If for any reason this battery loses voltage or
just gets old and fails, then the system configuration will be lost and the
system will hang at the post. Replace the battery and reset your drives and
system data. If you are not familiar with CMOS operation you should not attempt
modifications to the setup. Symptom 4. System boots O.K. then hangs and the message "Can't find boot record" appears.
This particular error code usually indicates a problem with the Harddrive.
After the initial POST, the system asks for instructions from the harddrive
to continue the boot process, and if there is a problem communicating with
the drive, or if the (System) instructions are missing this message will
appear. Symptom 5. System turns on, but there is no harddrive activity (light stays off.) If this problem begins suddenly and nothing new has been added or no new software has been recently installed, then turn off the system and turn it back on, and listen very carefully to the case, you should be able to hear the harddrive clicking rapidly inside. If no sound is present and no harddrive light comes on, then first check the CMOS configuration and make sure that the drive is configured correctly. If you are not familiar with CMOS operation, do NOT attempt this procedure. First reboot the computer and press the DEL key until the CMOS program comes up. Look for: Standard setup or Drive configuration it may be listed under this or a similar title, the proper section will list the harddrive, floppys, and the CD-ROM in the same section. After the setup parameters are located check that the listing is the same as your harddrive. If you arent sure what size of drive you have then open the case and look at the label, many drives have the size and configuration information listed on a label on the drives case. If not then read the model number and manufacturer name and call a computer repair shop who has a reference guide (most shops do) or see your local librarys reference section. Determine if the drive is the same as the one installed in the CMOS, if your drive is a newer one, larger than 2 Gigs, your user setting may be set at AUTO in which case a Dynamic overlay program may be controlling the drive. (this is a program which fools the system BIOS into letting it run larger harddrives) This overlay program should pop up at the initial start up, and say something about managing the BIOS (like: EZ BIOS is managing harddrive controller 1 etc) If you already know which dynamic overlay program you are using, check it to make sure it is functioning correctly. It may need to be reinstalled. If the drive is functioning correctly but still wont boot the system files, try running SCANDISK from the DOS prompt or some other disk utility program, there may be damaged files which are preventing access. Symptom 6. The system boots up but an incorrect Memory Size or Parity Error appears on the monitor.
This is a common error code when the user has recently added additional RAM
memory to the system or a memory IC has failed. These are the (normally)
72 pin plugin chips that determine your systems RAM. (note, you must
use static protection when working with SIMMs or other memory ICs.
Ground your skin to the chassis of the computer by any means necessary.)
( I use an alligator clip jumper wire to my metal watch band, and the other
end to the metal of the power supply chassis.) You might see any one of the following general RAM errors a. Memory address line failure at XXXX, read YYYY, expecting ZZZZ b. Memory data line failure at XXXX, read YYYY, expecting ZZZZ c. Memory high address failure at XXXX, read YYYY, expecting ZZZZ d. Memory logic failure at XXXX, read YYYY, expecting ZZZZ e. Memory odd/even logic failure at XXXX, read YYYY, expecting ZZZZ f. Memory parity failure at XXXX, read YYYY, expecting ZZZZ g. Memory read/write failure at XXXX, read YYYY, expecting ZZZZ Each of the errors shown are general RAM error messages indicating a problem in base or extended/expanded RAM. The code XXXX is the failure segment ad-dress-an offset address might be included. The word YYYY is what was read back from the address, and ZZZZ is the word that was expected. The difference between these read and expected words is what precipitated the error. In general, these errors indicate that at least one base RAM IC or at least one SIMM has failed. A trial-and-error approach is usually the least expensive route in finding the problem. First, reseat each SIMM and retest the system to be sure that each SIMM is inserted and secured properly. Rotate a known-good SIMM through each occupied SIMM socket in sequence. If the error disappears when the known-good SIMM is in a slot, the old SIMM that had been displaced 'is probably faulty. You can go on to use specialized SIMM troubleshooting equipment to identify the defective IC, but such equipment is rather expensive unless you intend to repair a large volume of SIMMs to the IC level. If the problem remains unchanged even though every SIMM has been checked, the error is probably in the motherboard RAM or RAM support circuitry. Run a thorough system diagnostic if possible, and check for failures in other areas of the motherboard that affect memory (such as the interrupt controller, cache controller, DMA controller, or memory management chips. If the problem prohibits a software diagnostic, use a POST board and try identifying any hexadecimal error code. If a support IC is identified, you can replace the defective IC, or replace the motherboard outright. If RAM continues to be the problem, try replacing the motherboard RAM (or replace the entire motherboard), and retest the system. Symptom 8. System boots up but ROM ERROR is all that appears on the screen. This is the error code that usually indicates that there are no system files on the harddrive, (COMMAND.COM, I/O SYS, MS-DOS.SYS) the computer scans the drive looking for further bootup instructions and when it dosent find them it brings up this error. This sometimes happens when you format a drive and forget to add the /s command, after the format command. Try reformatting the drive with the command: format c:\ /s Symptom 9. You hear a series of Beeps but no error code is displayed. Any beep code other than just the short beep at the post indicates a serious problem. See the Troubleshooting beep codes article in this section. Symptom 10. The system start up sequence (POST) hangs up on some code. Your system BIOS (Basic Input Output System) has a problem. POST codes vary widely for different BIOS manufacturers first you need to determine what type of BIOS is installed in your computer. In order to do this you must open the case and look at the IC chips installed on the motherboard the traditional BIOS chip is a 28 pin (per side) dual in line IC, mounted in a socket which allows it to be removed and replaced. This chip may have a small square or round window in the middle and should have a sticker on the top which tells exactly what type of BIOS chip it is and the manufacturer . Armed with this information, go the BIOS section of this website and look under BIOS manufacturers and see if you can match the chip to the manfacturer on the list. Since there are so many types it should be quicker and easier to contact the manufacturers website and look up the appropriate beep code. The problem with codes of this type though. Is that they usually arent specific to the actual problem as to why the BIOS failed. Standard procedure dictates that you first determine if any changes in the setup or the system have been made, if in fact, there have been recent changes to some internal system or setup programs (like CMOS) then look there first. If the problem persists replace the BIOS and try again. |
Modem
Troubleshooting
Troubleshooting
Specific PC Symptoms Troubleshooting
BIOS and Startup problems Troubleshooting
client for Netware Networks
Troubleshooting
Communications Troubleshooting
Device Configuration Troubleshooting
Disk Corruption Troubleshooting
Drivers Troubleshooting
Windows95 Start-up Troubleshooting
Applications Troubleshooting
Missing File Systems Troubleshooting
SCSI Device Problems Troubleshooting
Setup Errors Troubleshooting
Specific Startup Errors Troubleshooting
Floppy Disk Systems
Troubleshooting
CPU's Shareware
Utilities BIOS
and Beep Codes CDROMS
Conflict
Troubleshooting Troubleshooting
CMOS