Network Computing is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Basic Hardware Problem Diagnostics: Page 3 of 5

These diagnostics let you determine the extent of the damage so you can gauge what it will cost you to repair or replace your equipment. Most organizations simply don't have the time or resources to do component-level repairs. In many cases, it's cheaper to replace equipment than to repair it, especially if the hardware is old.

Rolling Up Your Sleeves

Sometimes hardware doesn't fail completely. A specific function, like the loading mechanism on a tape drive or the fan on a PC, for example, won't work. It's difficult in these situations to discern whether the problem is with the configuration, the software or the hardware itself. Again, take a diagnostic approach. Reset the configuration to factory defaults and set it up from scratch.

If it's a PC or PC-based server that gets a software load, reload from scratch if possible, or load a backup of the software onto an identical machine to help you determine the problem. A software problem, for example, will manifest itself on the other machine as well. Make sure that cables are plugged firmly in and firmware (BIOS) settings are as they should be.

Memory-test software is a good first step, but not the definitive one. We've had machines in our Network Computing Real-World Labs® that run these supposedly comprehensive memory tests for days, and the machine still ends up needing a memory replacement. If you suspect memory failure after eliminating configuration and software problems from your list of suspects, reseat the memory and replace it wholesale. If you're still having problems, it's time to call in the professional service technicians or ditch the hardware.