Why, What for…
I often run into quick guides on how to troubleshoot a computer, so I thought I’d put together my own version of a simple list I generally follow when trying to identify a problem. Obviously this is a very general simplified version, and once with enough experience troubleshooting something you start to develop an instinct about where to zoom in and narrow the search process.
You don’t necessarily need to follow the order or the whole guide, usually you’ll get hints that will lead to the solution along the way.
Before Anything, CREATE A BACKUP FIRST! (if possible)…
Try avoid doing something you cannot undo…
Take Notes (connections, settings, passwords), Pictures, Snapshots…Consider all Data Essential…
Especially if you’re unfamiliar with the information you’re handling…
If you ever have to decide only between saving Data or Hardware:
Hardware shouldn’t stand a chance!!!
I’ve seen too many techs delete or loose critical data on their way to fixing the problem.That would be like a Doctor not knowing whether to kill the Cancer or the patient…
Begin:
Check Power: (in all of it’s variants)
(is the thing plugged in?, battery voltage, etc.)
Reboot…Check Connections:
(Cables plugged in properly?, all the way in?, Cards seated properly?, corroded connectors?)- Test Hardware:
3.1. Unplug non-essential cards and peripherals.
(You might want to take some notes and/or pictures if the connections are complex)
3.2. Test RAM (memtest)
3.3. check hard drive (surface scan)
Last chance to GRAB A BACKUP!
Or you can also clone the data onto another drive and work on a copy of the original.
(Beyond this point, there be dragons!)
Once the hardware checks out… - Check Software:
4.1. Start in safe-mode,
4.2. Virus check,
4.3. Updates,
4.4. Check Logs.
All of that being said, there is no substitute for experience.