NewAI Content Creation is now live in Early Access
Turning Point Training Instituteby Training Center
Skip to content
0%
Module 8 — Computer and Hardware TroubleshootingLesson 4 of 4
5 min readBeginner

Where you are: Module 8 — Computer and Hardware Troubleshooting · Checkpoint and Lab · Based on Chapter 8 of Dr. Tahseen Al Doori's Troubleshooting Essentials.

Recap

First decide whether a computer has no power (nothing happens) or no boot (it powers on but does not start). No power: trace the supply chain from socket to device, removing accessories; for desktops, test the power supply with a tester or known-good unit, never by opening it. No boot: read the display, beep and light codes and messages, and link them to what changed. Slow or freezing: restart, check storage (keep 10–15% free), monitor processes, trim startup items, update and scan, check heat, consider the drive. Overheating: loud fans, a hot case and shutdowns under load; clean vents and keep airflow clear. Failing storage: back up first, troubleshoot second. Failing memory: test with Windows Memory Diagnostic or MemTest86 and isolate one module at a time. Before opening any computer: shut down, unplug, remove the battery, discharge, wear an anti-static strap and respect the warranty.

Checkpoint quiz

A laptop shows no lights and no fan activity even on its charger. After checking the socket and charger, what does the book suggest next?

A desktop starts, shows the manufacturer's logo, then displays 'No boot device found'. What should you investigate?

A computer shuts down every afternoon during video calls, and its fans are always loud. Which category of fault is the strongest theory?

A user's drive is grinding and one folder has become unreadable. The user has no backup. What is the correct order of actions?

Random crashes and blue screens continue on a desktop with two memory modules, and Windows Memory Diagnostic reports errors. After following the safety routine, what is the next isolation step?

Lab: Read the symptoms

This module has no lab in the book, so this is a simulated diagnosis lab built from the book's procedures. It needs no tools and no opened equipment.

Goal: diagnose six fictional hardware cases using only the symptoms, choosing the correct procedure, the first safe action and the point at which to stop or escalate.

Safe setup: pen and paper or a document, Chapter 8 of the course notes, and the problem log template (Appendix B of the book). Do not open, repair or run diagnostics on any real device for this lab.

Cases (all fictional):

  1. A desktop is completely dead after an office move. The monitor on the same power strip works.
  2. A laptop powers on with its keyboard backlight lit, but the screen stays black.
  3. A PC restarts in a loop after an overnight update.
  4. A laptop used on a sofa switches off during video exports; it runs normally for email.
  5. A desktop hard disk clicks, and the owner's accounting file is corrupt. The last backup is three months old.
  6. A desktop crashes at random with a MEMORY_MANAGEMENT stop code; it has four memory modules.

Steps:

  1. For each case, classify the fault: no power, no boot, slow/freezing, overheating, failing storage or failing memory.
  2. Write a one-sentence problem statement using the template from Module 4.
  3. List the book's procedure steps that apply, in order.
  4. Name the first safe action and the evidence it would produce.
  5. Mark any safety rule that applies (unplug, anti-static, warranty, never open the power supply, back up first).
  6. State the point at which you would stop and escalate, and why.

What to record: a completed problem log entry for each case, covering classification, problem statement, procedure, first action, safety rule and escalation point.

Completion criteria:

  • All six cases classified correctly.
  • Case 5 starts with a backup and contains no repair before it.
  • Case 6 uses a memory test and one-module-at-a-time isolation, with the safety routine before the case is opened.
  • At least two cases name a qualified technician, the manufacturer or escalation as the right next step.

Answers explained — 1: the book's no-power steps continue with removing accessories and discharging a laptop; reinstalling, opening the case or changing the boot order do not apply when there is no power. 2: the book links this message to storage detection and boot order, so firmware settings and the drive connection come first; power, DNS and the monitor cable are ruled out by the logo appearing. 3: shutdowns under load with constantly loud fans are the book's overheating symptoms. 4: with suspected storage failure the book's rule is back up first; chkdsk /f, defragmenting and repeated restarts make a failing drive work harder. 5: testing one module at a time is remove-and-restore for memory; the power supply and startup programs do not isolate a faulty module.

Sources

  • Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), Chapter 8 (§8.1–8.6, Safety First box), §4.6 (problem statement template), §13.1 and Appendix B