NewAI Content Creation is now live in Early Access
Turning Point Training Instituteby Training Center
Skip to content
0%
Module 7 — Essential Diagnostic ToolsLesson 5 of 5
13 min readBeginner

Where you are: Module 7 — Essential Diagnostic Tools · Midpoint Review of Modules 1–7 (Parts I and II) · Based on Chapters 1–7 of Dr. Tahseen Al Doori's Troubleshooting Essentials.

How to use this review

You have now completed the foundations (Part I) and the diagnostic techniques (Part II). Everything in Part III and Part IV builds on them. Use this review in three passes:

  1. Read the revision summary and tick off each point you could explain to someone else without notes.
  2. Answer the 15 questions without looking back. Most are scenarios: decide what you would actually do.
  3. Read the explanations for every question, including the ones you answered correctly, and revisit the module named for any you missed.

Allow about 45 minutes.

Revision summary

Module 1 — Introduction to Troubleshooting

  • Troubleshooting is the systematic process of identifying, diagnosing and resolving problems so that a system returns to normal operation. It is the investigation that answers what is actually wrong?
  • Repair corrects a fault that is already known. Maintenance is planned work that keeps a system healthy before it fails. Troubleshooting comes before repair.
  • Trial and error wastes time, can introduce new faults and leaves no record. A structured method brings four benefits: speed, safety, repeatability and knowledge.
  • Six problem categories: hardware, network, software, account and access, user and process, environmental. Recognising the category early suggests where to start.
  • Downtime costs individuals time and frustration, and costs organisations sales, staff time, deadlines, reputation and sometimes safety or regulatory standing.

Module 2 — The Troubleshooting Mindset

  • The seven principles: stay calm; be curious, not certain; start simple; change one thing at a time; observe before acting; protect what matters; write it down.
  • "What changed?" is the most powerful first question. When a user says nothing changed, ask specific questions: installed or updated, moved or cleaned, power off, someone else used it.
  • Common mistakes: jumping to a fix, ignoring error messages, changing many things at once, assuming "it can't be that", not asking what changed, working without notes.
  • Cognitive biases: confirmation bias (seeing only supporting evidence), anchoring (fixing on the first information, such as the user's own diagnosis), availability bias (assuming it is whatever caused the last similar problem), sunk-cost thinking (persisting with a failing approach because of the time already spent).

Module 3 — The Universal Seven-Step Methodology

IdentifyTheoryTestPlanImplementVerifyDocument
StepKey questionOutput
1 Identify the problemWhat exactly is wrong?A clear problem statement
2 Establish a theory of probable causeWhat could cause this?A ranked list of probable causes
3 Test the theory to determine the causeIs this theory correct?A confirmed or rejected cause
4 Establish a plan of actionHow will it be fixed safely?Steps, backup and rollback plan
5 Implement the solution or escalateWas the plan applied carefully?The change, or an escalation
6 Verify full system functionalityDoes everything work now?User confirmation; preventive measures
7 Document findings, actions and outcomesWhat was learned?A written record
  • Steps 2 and 3 loop until a cause is confirmed or the problem is escalated. No fix is applied before a cause is confirmed.
  • The method is complete only when the result is verified with the user and recorded.

Module 4 — Identifying and Defining the Problem

  • 5W1H: What (exactly happens, and what should happen), When (started; always or sometimes), Where (device, room, site, network, application), Who (one person, a team, everyone), Which (changes happened just before), How (is it triggered; can it be repeated).
  • Ask open questions first, then closed questions, avoid jargon, and ask the user to demonstrate the problem.
  • Evidence: exact error messages and codes, physical symptoms, logs and history, scope, recent changes.
  • Reproduce the fault to make testing fast. For intermittent faults, keep an occurrence log (date, time, activity, conditions) until a pattern appears.
  • A baseline records normal behaviour so that abnormal behaviour stands out.
  • Problem statement template (the book's wording): "Since [when], [who] cannot [what] on [where]. It happens [always / intermittently] when [how]. The most recent change was [which]. The error shown is “[exact message]”."

Module 5 — Quick-Win Checks

  • The five checks, in order: 1 Power · 2 Connections · 3 Restart · 4 Settings and input · 5 Updates, storage and resources.
  • Network power-cycle order: modem, wait 60 seconds, router, then the end device.
  • A wrong date and time breaks logins and secure websites.
  • A restart clears temporary memory, ends stuck processes, reloads drivers and configuration and re-establishes connections, but it treats the symptom. If a quick win has to be repeated, it is a workaround, not a fix.

Module 6 — Isolation Techniques

TechniqueUse it when
Half-splitA long chain of components or stages (each test removes half the possibilities; 8 components need at most 3 tests)
SubstitutionSpare known-good parts or a second device are available
ComparisonAn identical working system exists
RollbackThe problem began after a known change
Remove and restoreMany add-ons, applications or accessories are installed (the last item restored when the fault returns is the cause)
Bottom-upThere is no obvious starting point, or hardware or connectivity is suspected
Top-downOnly one application is affected
Follow the flowData or a signal passes through stages from source to destination

Module 7 — Essential Diagnostic Tools

  • Monitoring: Task Manager and Resource Monitor (Windows), Activity Monitor (macOS), top/htop (Linux, macOS), Device Manager (Windows drivers).
  • Logs: Event Viewer (Windows Logs: Application, System, Security), Console (macOS), journalctl or /var/log (Linux). Look for errors logged at the time of the fault.
  • Network commands: ipconfig /all, ip addr, ifconfig; ping; tracert/traceroute; nslookup; netstat -an; ipconfig /release, /renew, /flushdns. An address starting 169.254 means no response from a DHCP server.
  • Five-step connectivity sequence: ping 127.0.0.1 → ipconfig → ping the default gateway → ping 8.8.8.8 → ping a name. The first failure shows where the fault lies.
  • Recovery tools: automated troubleshooters, safe mode, System Restore and Time Machine, disk checkers, System File Checker.
  • Hardware tools and safety: multimeter, cable tester, power supply tester, loopback plug, anti-static strap, known-good spares. Disconnect power before opening equipment, and never open power supplies or monitors.

Midpoint questions

Last month a technician fixed a recurring printer error and wrote the cause and fix in the ticket. This month a colleague meets the same error and resolves it in five minutes by searching the tickets. Which benefit of a structured method does this show?

Since moving to the finance team on Monday, a member of staff gets Access denied when opening the finance shared folder. Their laptop, network and other folders work normally. Which problem category should guide where to start?

A user insists that nothing changed before their laptop stopped connecting to the office Wi-Fi. What is the best next step?

After three hours reinstalling a database client, a technician refuses to test the network theory a colleague suggests, saying too much time has gone into the reinstall to stop now. Which bias is this?

Before changing anything on a small office router, a technician photographs every settings page and exports the configuration to a USB drive. Which of the seven principles is being applied?

A technician has gathered the facts and written a clear problem statement. What should the output of the next step be?

An email fault has been fixed. The technician repeats the action that originally failed, checks that receiving and calendar sync still work, and asks the user to confirm that everything works for them. Which step of the method is this?

You are interviewing a user about a frozen screen. Which question should you ask first?

A lab computer has become slow. The technician compares its list of startup programs and software versions with the record kept for the standard lab image when it was installed, and finds two extra startup items. What has the technician used?

Every device in a home office has lost internet access. The technician decides to power-cycle the network equipment. Which order is correct?

A user's documents fail to save with a message that there is not enough space, and the computer has become sluggish. Which quick-win check is most directly aimed at this fault?

A laptop will not charge. The technician borrows a colleague's identical charger, which is known to work, and the laptop starts charging. Which isolation technique was used, and what does it show?

Only one application on a computer misbehaves; every other program, the network and the hardware work normally. Which approach is the most suitable starting point?

A Linux server crashed at 02:14. Where should you look first for errors logged at that time?

Users report that a cloud application is slow. Which command shows the path to the server and the hop where delays jump?

Answers explained

  1. a — The colleague benefited from a written record; the book calls this the knowledge benefit. Speed, safety and repeatability are real benefits but are not what made the second fix fast here. (Module 1)
  2. c — Access denied after a change of team, with everything else working, points to account and access (permissions or group membership). There is no sign of a hardware, network or environmental fault. (Module 1)
  3. b — General questions miss details; specific questions recover them. Replacing hardware or resetting the device jumps to a fix before the problem is understood, and pressuring the user does not produce better information. (Module 2)
  4. d — Continuing with a failing approach because of time already invested is sunk-cost thinking. Anchoring is fixing on the first information received; confirmation bias is ignoring evidence against a theory; availability bias is assuming the cause of the last similar problem. (Module 2)
  5. a — Recording original settings and keeping a backup before a change is "protect what matters". The other principles are valuable but do not describe saving the configuration. (Module 2)
  6. c — After Step 1 comes Step 2, whose output is a ranked list of probable causes. A confirmed cause is the output of Step 3, a backup and rollback plan belongs to Step 4, and escalation happens in Step 3 or Step 5 only when needed. (Module 3)
  7. b — Step 6 confirms that the original problem is resolved and nothing else is broken: repeat the failed action, check related functions and ask the user to confirm. Steps 3, 4 and 5 all come before there is a fix to verify. (Module 3)
  8. d — Open questions come first because they let the user describe events in their own words. The other options are closed questions, useful later to confirm specific details. (Module 4)
  9. a — A record of normal behaviour used for comparison is a baseline. Half-split divides a chain, rollback undoes a change and an occurrence log records repeated events. (Module 4)
  10. c — The book's order is modem, wait 60 seconds, router, then the end device, so each device starts once the device it depends on is ready. (Module 5)
  11. b — A full disk causes failed saves and slowness; Check 5 covers free storage, updates and exhausted resources. Power, connections and settings do not explain a lack of space. (Module 5)
  12. c — Swapping in a known-good part is substitution; because the problem disappeared, the removed charger is at fault. Comparison sets two systems side by side without swapping; rollback and remove-and-restore do not apply. (Module 6)
  13. a — The book recommends top-down when only one application misbehaves. Bottom-up suits hardware or connectivity faults, and the other options look far beyond where the evidence points. (Module 6)
  14. d — On Linux, logs are read with journalctl or found under /var/log. Event Viewer and Device Manager are Windows tools; Console is the macOS log viewer. (Module 7)
  15. b — tracert and traceroute show the path and the hop where replies stop or delays jump. nslookup tests name resolution, netstat -an shows connections and ports, and /flushdns clears the DNS cache. (Module 7)

Where to revise

If you missed questionRevisit
1, 2Module 1 — Introduction to Troubleshooting
3, 4, 5Module 2 — The Troubleshooting Mindset
6, 7Module 3 — The Universal Seven-Step Methodology
8, 9Module 4 — Identifying and Defining the Problem
10, 11Module 5 — Quick-Win Checks
12, 13Module 6 — Isolation Techniques
14, 15Module 7 — Essential Diagnostic Tools

Sources

  • Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), Chapters 1–7 (§1.1–1.4, §2.1–2.5, §3.1–3.8, §4.1–4.6, §5.1–5.6, §6.1–6.7, §7.1–7.5)