| Motherboard troubleshooting |
| |
A.)GENERAL TESTING TIPS.
Before you begin, download a few of our Diagnostic Software Tools to pinpoint possible problem areas in your PC. Ideally, troubleshooting is best accomplished with duplicate parts from a used computer enabling "test" swapping of peripheral devices/cards/chips/cables. In general, it is best to troubleshoot on systems that have been leaned-out. Remove unnecessary peripherals (soundcard, modem, harddisk, etc.) to check the unworking device in as much isolation as possible. Also, when swapping devices, don't forget the power supply. Power incompetency (watts and volts) can cause intermittent problems at all levels, but especially with UARTS and HD's.
Inspect the motherboard for loose components. A loose or missing CPU, BIOS chip, Crystal Oscillator, or Chipset chip will cause the motherboard not to function. Also check for loose or missing jumper caps, missing or loose memory chips (cache and SIMM's or DIMM's). To possibly save you hours of frustration i'll mention this here, check the BIOS Setup settings. 60% of the time this is the cause of many system failures. A quick fix is to restore the BIOS Defaults. Next, eliminate the possibility of interference by a bad or improperly set up I/O card by removing all cards except the video adapter. The system should at least power up and wait for a drive time-out. Insert the cards back into the system one at a time until the problem happens again. When the system does nothing, the problem will be with the last expansion card that was put in.
Did you recently 'flash' your computers BIOS, and needed to change a jumper to do so? Perhaps you left the jumper in the 'flash' position which could cause the CMOS to be erased.
If you require the CMOS Reset and don't have the proper jumper settings try these methods: Our Help Desk receives so many requests on Clearing BIOS/CMOS Passwords that we've put together a standard text outlining the various solutions.
Switching power supplies (the most common used PC's), cannot be adequately field-tested with V/OHM meters. Remember: for most switching power supplies to work, a FLOPPY and at least 1 meg of memory must be present on the motherboard. If the necessary components are present on the motherboard and there is no power:
1) check the power cable to the wall and that the wall socket is working. (You'd be surprised!)
2) swap power supply with one that is known to work.
3) if the system still doesn't work, check for fuses on the motherboard. If there are none, you must replace the motherboard.
2) swap power supply with one that is known to work.
3) if the system still doesn't work, check for fuses on the motherboard. If there are none, you must replace the motherboard.
Peripherals are any devices that are connected to the motherboard, including I/O boards, RS232/UART devices (including mice and modems), floppies and fixed-disks, video cards, etc. On modern boards, many peripherals are integrated into the motherboard, meaning, if one peripheral fails, effectually the motherboard has to be replaced.* On older boards, peripherals were added via daughter boards.
*some MB CMOS's allow for disabling on-board devices, which may be an option for not replacing the motherboard -- though, in practicality, some peripheral boards can cost as much, if not more, than the motherboard. Also, failure of on-board devices may signal a cascading failure to other components.
1. New peripheral?
1. New peripheral?
a) Check the MB BIOS documentation/setup to ensure that the BIOS supports the device and that the MB is correctly configured for the device.
(Note>> when in doubt, reset CMOS to DEFAULT VALUES. These are ) (optimized for the most generalized settings that avoid some of) (the conflicts that result from improper 'tweaking'. )
b) Check cable attachments & orientation (don't just look, reattach!)
c) If that doesn't work, double-check jumper/PnP (including software and/or MB BIOS set) settings on the device.
d) If that doesn't work, try another peripheral of same brand & model that is known to work.
e) If the swap peripheral works, the original peripheral is most likely the problem. (You can verify this by testing the non-working peripheral on a test MB of the same make & bios.)
f) If the swap periphal doesn't on the MB, verify the functionality of the first peripheral on a test machine. If the first peripheral works on another machine AND IF the set-up of the motherboard BIOS is verified AND IF all potentially conflicting peripherals have been removed OR verified to not be in conflict, the motherboard is suspect. (However, see #D below.)
g) At this point, recheck MB or BIOS documentation to see if there are known bugs with the peripheral AND to verify any MB or peripheral jumper settings that are necessary for the particular peripheral to work. Also, try a different peripheral of the same kind but a different make to see if it works. If it does not, swap the motherboard. (However, see #D below.)
(Note>> when in doubt, reset CMOS to DEFAULT VALUES. These are ) (optimized for the most generalized settings that avoid some of) (the conflicts that result from improper 'tweaking'. )
b) Check cable attachments & orientation (don't just look, reattach!)
c) If that doesn't work, double-check jumper/PnP (including software and/or MB BIOS set) settings on the device.
d) If that doesn't work, try another peripheral of same brand & model that is known to work.
e) If the swap peripheral works, the original peripheral is most likely the problem. (You can verify this by testing the non-working peripheral on a test MB of the same make & bios.)
f) If the swap periphal doesn't on the MB, verify the functionality of the first peripheral on a test machine. If the first peripheral works on another machine AND IF the set-up of the motherboard BIOS is verified AND IF all potentially conflicting peripherals have been removed OR verified to not be in conflict, the motherboard is suspect. (However, see #D below.)
g) At this point, recheck MB or BIOS documentation to see if there are known bugs with the peripheral AND to verify any MB or peripheral jumper settings that are necessary for the particular peripheral to work. Also, try a different peripheral of the same kind but a different make to see if it works. If it does not, swap the motherboard. (However, see #D below.)
2. Peripheral that worked before?
a) If the hood has been opened (or even if it has not), check the orientation and/or seating of the cables. Cables sometimes 'shake' loose or are accidentally pulled out by end-users, who then misalign or do not reattach them.
b) If that doesn't work, try the peripheral in another machine of the same make & bios that is known to work. If the peripheral still doesn't work, the peripheral is most likely the problem. (This can be verified by swapping-in a working peripheral of the same make and model AND that is configured the same as the one that is not working. If it works, then the first peripheral is the problem.)
c) If the peripheral works on another machine, double-check other peripherals and/or potential conflicts on the MB, including the power supply. If none can be found, suspect the MB.
d) At this point, recheck MB or BIOS documentation to see if there are known bugs with the peripheral AND to verify any jumper settings that might be necessary for the particular peripheral. Also, try another peripheral of the same kind but a different make to see if it works. If not, swap the motherboard!
b) If that doesn't work, try the peripheral in another machine of the same make & bios that is known to work. If the peripheral still doesn't work, the peripheral is most likely the problem. (This can be verified by swapping-in a working peripheral of the same make and model AND that is configured the same as the one that is not working. If it works, then the first peripheral is the problem.)
c) If the peripheral works on another machine, double-check other peripherals and/or potential conflicts on the MB, including the power supply. If none can be found, suspect the MB.
d) At this point, recheck MB or BIOS documentation to see if there are known bugs with the peripheral AND to verify any jumper settings that might be necessary for the particular peripheral. Also, try another peripheral of the same kind but a different make to see if it works. If not, swap the motherboard!
1. CLOCK that won't keep correct time. >>Be sure to check/change the battery.
2. CMOS that won't hold configuration information. >>Again, check/change the battery.
Note about batteries and CMOS: in theory, CMOS should retain configuration information even if the system battery is removed or dies. In practice, some systems rely on the battery to hold this information. On these systems, a machine that is not powered-up for a week or two may report improper BIOS configuration. To check this kind of system, change the battery, power-up and run the system for several hours. If the CMOS is working, the information should be retained with the system off for more than 24 hours.
1. If the motherboard cannot configure to a particular peripheral, don't automatically assume a bad motherboard, even if the peripheral checks out on another machine -- especially if the other machine has a different BIOS revision. Check with the board manufacturer to see if a BIOS upgrade is available. Many BIOS upgrades can be made right on the MB with a FLASH RAM program provided by the board maker. See our BIOS page for more information.
More than 70% of all computer problems are related to cabling and connections. Ensure all cables are connected and connected firmly. IDE and floppy ribbon cables and power cables can often go loose. Ensure microprocessor, memory modules, and adapters such as video card are inserted correctly and didn't "pop-up" due to vibration.
System has no power at all. Power light does not illuminate, fan inside the power supply does not turn on, and indicator light on keyboard does not turn on.
| PROBABLE CAUSE | DIAGNOSIS | SOLUTION |
| Power cable is unplugged. | Visually inspect power cable. | Make sure power cable is securely plugged in. |
| Defective power cable. | Visual inspection, try another cable. | Replace cable. |
| Power supply failure. | Power cable and wall socket are OK, but system is still dead. | Contact technical support |
| Faulty wall outlet;circuit breaker or fuse blown. | Plug device into socket know to work and test. | Use different socket, repair outlet, reset circuit breaker or replace fuse. |
System inoperative. Keyboard lights are on, power indicator lights are lit, and hard drive is spinning.
| PROBABLE CAUSE | DIAGNOSIS | SOLUTION |
| Expansion card is partially dislodged from expansion slot on the motherboard. | Turn off computer. Take cover off system unit. Check all expansion cards to ensure they are securely seated in slots. | Using even pressure on both ends of the expansion card, press down firmly on expansion card. |
| Defective floppy disk drive or tape drive. | Turn system off. Disconnect the cables from one of the floppy drives. Turn on the system, check to see if the keyboard operates normally. Repeat until you have located defective unit. | Contact Technical Support. |
| Defective expansion card. | Turn computer off. Remove an expansion card. | Make sure expansion card is secure in expansion socket. |
System does not boot from hard disk drive, can be booted from floppy disk drive.
| PROBABLE CAUSE | DIAGNOSIS | SOLUTION |
| Connector between hard drive and system board unplugged. | When attempting to run the FDISK utility described in the HARD DISK section of this manual you get a message, INVALID DRIVE SPECIFICATION. | Check cable running form disk to disk controller on the board. Make sure both ends are securely plugged in; check the drive type in the Standard CMOS Setup (in your motherboard manual). |
| Damaged Hard Disk or Disk Controller. | Format hard disk; if unable to do so, the hard disk may be defective. | Contact Technical Support. |
| Hard Disk directory or FAT is scrambled. | Run the FDISK program, format the hard drive(See HARD DRIVE section of manual). Copy your backup data back onto hard drive. | Backing up the hard drive is extremely important. All Hard Disks are capable of breaking down at any time. |
System only boots from Floppy Disk. Hard Disk can be read and applications can be used, but booting from Hard Disk is impossible.
| PROBABLE CAUSE | DIAGNOSIS | SOLUTION |
| Hard Disk boot program has been destroyed. | A number of causes could be behind this. | Back up data and applications files. Reformat the Hard Drive as described in the Hard Drive section of this manual. Re-install applications and data using backup disks. |
Error message reading "SECTOR NOT FOUND" or other error messages indication certain data is not allowed to be retrieved.
| PROBABLE CAUSE | DIAGNOSIS | SOLUTION |
| A number of causes could be behind this. | Use a file by file backup instead of an image backup to backup the Hard Disk. | Back up any salvageable data. Then do a low level format, partition, and high level format of the hard drive( see Hard Disk section of your manual for instructions). Re-install all saved data when completed. |
Disk formatted on IBM PS/2 will not operate with this system.
| PROBABLE CAUSE | DIAGNOSIS | SOLUTION |
| The IBM PS/2 uses a different format than other computers. | IBM PS/2 disk format will not work in an AT type computer. | Format disk in the AT type computer insert disk into the IBM PS/2 and copy the files you wish. |
After install an expansion card (network card, tape drive card, etc.) the system no longer works properly.
| PROBABLE CAUSE | DIAGNOSIS | SOLUTION |
| No power to monitor. | All or part of the system may be inoperable. The new card may work but a mouse or COM port may not work. | Change the interrupt or RAM address on the new expansion card. See the documentation that came with the new card in order to change pin settings. many expansion devices come with proprietary software that will assist you in doing this. |
Screen message says "Invalid Configuration" or "CMOS Failure."
| PROBABLE CAUSE | DIAGNOSIS | SOLUTION |
| Incorrect information entered into the configuration (setup) program. | Check the configuration program. Replace any incorrect information. | Review system's equipment. Make sure correct information is in setup. |
Screen is blank.
| PROBABLE CAUSE | DIAGNOSIS | SOLUTION |
| No power to monitor. | | Check the power connectors to monitor and to system. Make sure monitor is connected to display card, change I/O address on network card if applicable. |
| Monitor not connected to computer. | | See instructions above. |
| Network card I/O address conflict. | | See instructions above. |
System does not boot from hard disk drive, can be booted from floppy disk drive.
| PROBABLE CAUSE | DIAGNOSIS | SOLUTION |
| Connector between hard drive and system board unplugged. | When attempting to run the FDISK utility described in the HARD DISK section of this manual you get a message, INVALID DRIVE SPECIFICATION. | Check cable running form disk to disk controller on the board. Make sure both ends are securely plugged in; check the drive type in the Standard CMOS Setup (in your |
Problem
| PROBABLE CAUSE | DIAGNOSIS | SOLUTION |
| Memory problem, display card jumpers not set correctly. | | Reboot computer. Re-install memory, make sure that all memory modules are installed in correct sockets. Check jumper and switch settings on display card. See display card section for information of settings. |
| Computer virus. | | Use anti-virus programs (McAfee/PC-cillin, E-port, etc) to detect and clean viruses. |
Screen goes blank periodically.
| PROBABLE CAUSE | DIAGNOSIS | SOLUTION |
| Screen saver is enabled. | | Disable screen saver. |
Keyboard failure.
| PROBABLE CAUSE | DIAGNOSIS | SOLUTION |
| Keyboard is disconnected. | | Reconnect keyboard. Check keys again, if no improvement, replace keyboard. |
No color on screen.
| PROBABLE CAUSE | DIAGNOSIS | SOLUTION |
| Faulty Monitor. | | If possible, connect monitor to another system. If no color, replace monitor. |
| CMOS incorrectly set up. | | Call technical support. |
Floppy drive lights stays on.
| PROBABLE CAUSE | DIAGNOSIS | SOLUTION |
| Floppy Drive cable not connected correctly. | | Reconnect floppy cable making sure PIN1 on the Floppy Drive corresponds with PIN1 on floppy cable connector. |
Error reading drive A:
| PROBABLE CAUSE | DIAGNOSIS | SOLUTION |
| Bad floppy disk. | | Try new floppy disk. |
| Floppy disk not formatted | | Format floppy disk(type ENTER) |
C: drive failure.
| PROBABLE CAUSE | DIAGNOSIS | SOLUTION |
| SETUP program does not have correct information. | | Boot from drive A: using DOS system disk. Input correct information to SETUP program. |
| Hard Drive cable not connected properly. | | Check Hard drive cable. |
Cannot boot system after installing second hard drive.
| PROBABLE CAUSE | DIAGNOSIS | SOLUTION |
| Master/Slave jumpers not set correctly. | | Set master /Slave jumpers correctly. |
| Hard Drives not compatible / different manufacturers. | | Run SETUP program and select correct drive types. Call drive manufactures for compatibility with other drives. |
Missing operating system on hard drive.
| PROBABLE CAUSE | DIAGNOSIS | SOLUTION |
| CMOS setup has been changed. | | Run setup and select correct drive type. |
Certain keys do not function.
| PROBABLE CAUSE | DIAGNOSIS | SOLUTION |
| Keys jammed or defective. | | Replace keyboard. |
Keyboard is locked, no keys function.
| PROBABLE CAUSE | DIAGNOSIS | SOLUTION |
| Keyboard is locked. | | Unlock keyboard |
