ClassLan

Notes - 25/05/2006 Hardware Troubleshooting

Hardware Troubleshooting

Intellectual Resources FAQs

Knowledge Bases (Microsoft TechNet)

Support Forums

Bug Lists

10 Trouble Shooting Steps

Define The Problem Can you see the problem?

How often does it happen?

Has any new software been installed?

Have any changes been made to the PC recently?

Check The Simple Stuff First Is it plugged in?

Is it turned on?

Is the system ready?

Reseat chips and cables?

Check If It is User Error EEOC Error (Equipment Exceeds Operator Capability)

Reboot The Computer

Determine If The Problem Is Hardware Or Software Related

If The Problem Is Hardware Related, Determine Which Component Is Failing

If The Problem Is Software Related, Try SAFEMODE

F5, F8 during boot

Hold down ’SHIFT’ during boot and drivers will not be loaded

Check Service Information Sources

If It Ain’t Broke… If the change that you make doesn’t work, change back

Ask For Help

Software Troubleshooting

Boot Clean Boot without software drivers (SAFEMODE)

Check OS for Error Messages

Uninstall/Reinstall the application that’s having problems

Look for ways to Repeat the Problem

Install Latest Patches

Check the Internet

Compare and Isolate

NOTE: Windows2000 uses ‘Intellimirror’ and its associated tools to maintain applications – replacing missing files, updating INI or Registry files, or doing a complete installation automatically

Main files used in DOS

IO.SYS First file that loads - Input Output of the system – loads basic drivers - IDE, video, etc

MSDOS.SYS DOS OS – controls file transfer and handling

COMMAND.COM Command interface, gives prompt: C:/>

CONFIG.SYS System Configuration – loads advanced device drivers

AUTOEXEC.BAT Auto runs programmes

MSCDEX.EXE Is the CD-ROM programme. It creates a ramdrive and loads the CD-ROM drivers

IO.SYS, MSDOS.SYS, COMMAND.COM is required

COMFIG.SYS, AUTOEXEC.BAT is extra files

REM Statements ‘rem’ is short for Remark. Used in DOS commands

where you want to stop a command from being initiated

System Resources Available memory should be at about 80% for optimal performance

GPF General Protection Faults

AKA Memory Leaks

The Registry

You can view the Registry by using REGEDIT.EXE or REGEDIT32.EXE (preferred)

POST Routines

1. The Processor is tested

2. The ROMs are checked

3. The DMA controller is tested

4. The Interrupt controller is checked

5. The system timing chip is tested

6. The BASIC ROMS are tested (if they exist)

7. The video card is checked

8. Expansion boards are initialized

9. RAM is counted and tested

10. The Keyboard is tested

11. The cassette interface is tested

12. The floppy drives are tested

13. Resources are checked and the PC is booted

Common POST Beep Codes

Continuous Beeps Power supply is bad, not plugged into the motherboard correctly or the keyboard is stuck

One Long Beep, Two Short Beeps Video Card Failure

Common POST Error Codes

1** Any number beginning with 1 indicates a system board problem

161 CMOS battery failure

164 Memory size error. Always happens when RAM has been added

2** 2** indicates a memory-related problem

201 Memory test failed, One or more RAM chip found to be bad

3** 3** indicates a problem with the keyboard

301 Keyboard error.

4** Monochrome video problems

5** Colour video problems

6** Floppy disk system problems

601 Floppy error – adapter or driver failure, cable problems

17** Hard disk problems.

1780 Drive 0 (C:) has failed

1781 Drive 1 (D:) has failed

posted by ClassLan @ 4:23 PM