NewAI Content Creation is now live in Early Access
Turning Point Training Instituteby Training Center
Skip to content
0%
Module 11 — Printers, Mobile Devices and PeripheralsLesson 4 of 4
5 min readBeginner

Where you are: Module 11 — Printers, Mobile Devices and Peripherals · Checkpoint · Based on Chapter 11 of Dr. Tahseen Al Doori's Troubleshooting Essentials.

Recap

Module 11 applied the method to the devices people use every day. Printers have seven checks, and a test page printed from the printer itself splits the printer from the computer and network. Phones and tablets follow six steps from a restart to a factory reset, which comes last and only after a verified backup. Keyboards and mice are checked for cables, batteries, pairing and layout; displays for input source, cables, display mode (Windows+P) and settings; audio for mute at three levels, device selection and permissions. One idea runs through all of it: separate the device from the computer. The half that fails holds the fault.

Knowledge check

A printer produces streaky, faded pages. Which cause does the book link to this symptom?

A tablet's Wi-Fi, mobile data and Bluetooth all keep failing. A restart, the storage, battery and update checks, and an airplane-mode toggle have not helped. What is the next step in the book's sequence?

A laptop shows its desktop normally, and the projector is on and set to the correct input, but the projector shows nothing. Which check is next in the book's list after the cable and adapter?

A user hears nothing from a video in one browser tab, although system sounds play. Which book check is most relevant?

A wireless mouse works perfectly on a colleague's computer but not on yours, even with fresh batteries. According to the chapter's key idea, where does the fault lie?

Answers explained

  1. B. The book links streaks or faded print to low toner or ink, or a dirty print head or drum. Garbled output points to the driver, and stuck jobs or a wrong default printer stop printing altogether rather than spoil it.
  2. A. Step 5 resets network settings when Wi-Fi, mobile data or Bluetooth fail. A factory reset is step 6 and needs a backup first; nothing points to the battery or to every app.
  3. C. After power, input source and cable, the book's next display check is the display mode (Windows+P). Lamps, reinstallation and factory resets are drastic and not in the list.
  4. D. Audio can be muted at the device, application and operating-system levels; system sounds working points to the application level. The other checks belong to other devices.
  5. A. The mouse works on another computer, so the mouse and batteries are fine; the failing half is your computer's side. Nothing suggests an intermittent fault.

Lab: Split Device from Computer

Goal: practise the chapter's key idea by isolating a peripheral fault with known-good substitutes and recording each test.

Safe setup: work in pairs on a lab or training computer with removable peripherals (a USB keyboard or mouse, a headset or speakers, and if available a monitor or projector). Your partner introduces one harmless, reversible fault while you look away. Suitable faults: unplug the headset at the computer end, select a different playback device, mute one level of audio, switch the monitor to the wrong input, change the keyboard layout setting, or remove the battery from a wireless mouse. Do not open any device, change drivers or use a computer you rely on for your own work. If no lab equipment is available, run the lab as a paper simulation: your partner writes the fault on a card and answers each test you describe.

Steps:

  1. Write a one-sentence problem statement for what you observe (Chapter 4 template).
  2. Do the quick wins first: power, connections and settings for the affected device (Chapter 5).
  3. Test the device on its own or elsewhere: the headset on a phone, the mouse on another computer, the monitor with another source.
  4. Test the computer with a known-good device: another headset, mouse or display.
  5. Decide which half holds the fault and state your theory.
  6. Make one change to fix it, then verify that the original task works and that nothing else changed.
  7. Swap roles and repeat with a different fault.

What to record: for each test, what you did, the result and what it ruled out; the half that failed; the cause; the single change you made; and how you verified it. Use the problem log fields from the course toolkit.

Completion criteria: two faults diagnosed (one in each role), each with a problem statement, at least one device-side test and one computer-side test, a correctly identified cause, one change and a verification. Every setting is returned to normal at the end.

Sources

  • Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), Chapter 11 (§11.1–11.5, Key Takeaway, Review Questions); §4.6; Chapter 5; §6.2; Appendix B