Case Studies: The Slow Laptop and the Intermittent Wi-Fi
Where you are: Module 14 — Case Studies and Final Assessment · Lesson 14.2 · Based on Chapter 14 (Case Studies 2 and 3) of Dr. Tahseen Al Doori's Troubleshooting Essentials.
What you'll be able to do
- Trace Case Studies 2 and 3 through the seven steps and state the evidence that confirmed each cause.
- Explain how resource monitoring exposed the slow laptop's real cause.
- Explain how an occurrence log exposed the pattern behind an intermittent fault, and why the 5 GHz band helped.
- Evaluate the decisions in both cases and suggest a further preventive measure.
Watch: Case Studies: The Slow Laptop and the Intermittent Wi-Fi
The video takes two very different faults. In the first, a laptop's Task Manager tells the story. In the second, a fault that disappears whenever someone looks for it is caught by writing down every occurrence. As you watch, think about:
- Which of the three theories in Case 2 did the evidence actually point to, and was it on the list?
- What would the occurrence log have looked like if the access point itself were faulty?
- In Case 3, how many changes were made at once, and does that matter?
Case Study 2: the slow laptop
| Step | What happened (book, Case Study 2) |
|---|---|
| 1 Identify | A manager's laptop has become very slow over two weeks, especially at startup. No new hardware was added. |
| 2 Theory | Low storage, startup programs or malware. |
| 3 Test | Storage is 97% full; Task Manager shows disk use at 100%. A cloud-sync tool is downloading a large shared folder. |
| 4–5 Plan and implement | The sync tool is configured to keep files online only, freeing 80 GB. |
| 6 Verify | Startup time falls from four minutes to forty seconds; the manager confirms normal speed. |
| 7 Document and prevent | Online-only sync is added to the standard laptop configuration. |
The reasoning
Identify. "Over two weeks" says the problem grew gradually rather than appearing suddenly. "No new hardware" removes one category from the start, and "especially at startup" hints at something that launches or reads heavily when the laptop starts.
Theory. The three theories come straight from the book's checklist for slow systems in Chapter 8 and from the fifth quick-win check in Chapter 5 (updates, storage and resources). Starting with low storage follows the principle start simple.
Test. Two observations confirm the cause. Storage at 97% is far beyond the Chapter 8 guideline of keeping at least 10–15% of the drive free, and a full disk causes crashes, failed saves and slowness. Task Manager, the Chapter 7 monitoring tool, shows the disk working at 100% and names the process responsible: a cloud-sync tool downloading a large shared folder. This is the lesson the book draws in its chapter summary: resource monitoring revealed the real cause. Notice that the sync tool was not on the theory list by name. That is normal. Theories point you to the right place to look; the tools then show you what is actually there.
Plan and implement. Keeping files online only is a single, reversible change that addresses both observations at once: it frees 80 GB and stops the heavy download.
Verify. The verification is measured: four minutes to forty seconds. Measurements turn "it feels faster" into evidence, and the manager's confirmation closes the loop with the user.
Document and prevent. Adding online-only sync to the standard laptop configuration is a Chapter 12 preventive measure (standard configurations prevent faults caused by inconsistent settings). It protects every laptop, not just this one.
Evaluating Case 2
| Decision | Assessment |
|---|---|
| Began with the cheapest theory, low storage | Sound: start simple |
| Used Task Manager rather than guessing | Strong: evidence, not assumption |
| Made one change and measured the result | Strong: one variable, and a clear before-and-after |
| Fixed the standard configuration | Strong: prevents recurrence on other laptops |
Our commentary: before switching to online-only, a careful technician confirms the files really are stored in the cloud, so that freeing local space cannot lose anything (principle 6, protect what matters). And the case answers review question 3 only partly: online-only sync is one preventive measure, but others are possible, for example monitoring and alerts for low disk space (Chapter 12), so the next laptop is caught at 85% rather than 97%.
Case Study 3: the intermittent Wi-Fi drop
| Step | What happened (book, Case Study 3) |
|---|---|
| 1 Identify | A meeting room's Wi-Fi drops several times a day, usually around midday. Other rooms are unaffected. |
| 2 Theory | Interference, overloaded access point or a faulty access point. |
| 3 Test | An occurrence log shows that drops coincide with lunchtime use of a microwave in the adjoining kitchen, which operates in the 2.4 GHz band. |
| 4–5 Plan and implement | The access point is configured to prefer the 5 GHz band and is moved away from the kitchen wall. |
| 6 Verify | No drops are recorded over the following two weeks. |
| 7 Document | The cause and the change are recorded in the network documentation. |
An access point is the device that provides the Wi-Fi signal in an area. Wi-Fi uses radio frequency bands; the two named in this case are 2.4 GHz and 5 GHz.
The reasoning
Identify. Two facts frame the problem. Several times a day, usually around midday is a time pattern. Other rooms are unaffected is a comparison that confines the fault to this room's area, which is the comparison technique from Chapter 6 applied to scope.
Theory. All three theories are plausible from Chapter 9, whose physical-layer checks include interference from microwaves, thick walls and neighbouring networks. The question is how to tell them apart, because intermittent faults disappear when examined.
Test. Chapter 4's method for intermittent problems is to keep a log of every occurrence with the date, time, activity and conditions, until a pattern appears. Think about what each theory predicts (our reasoning):
| Theory | Pattern you would expect in the log |
|---|---|
| Faulty access point | Drops at random times, whatever is happening |
| Overloaded access point | Drops when the room is full, for example during large meetings |
| Interference | Drops whenever the interfering source is active |
The log matched the third pattern: drops coincided with lunchtime use of the microwave in the kitchen next door. The book notes that the microwave operates in the 2.4 GHz band, the same band the Wi-Fi was using.
Plan and implement. Two changes, both aimed at the confirmed cause: prefer the 5 GHz band, which the microwave does not occupy, and move the access point away from the kitchen wall.
Verify. For an intermittent fault, one good test proves nothing: the fault may simply not have happened yet. Two weeks without a drop, covering many lunchtimes, is meaningful evidence.
Document. The cause and the change go into the network documentation, so the next person to move the access point knows why it is where it is.
Evaluating Case 3
The occurrence log is the hero of this case, and it answers review question 2: the isolation came from comparison (this room against unaffected rooms) combined with an occurrence log that tied the drops to a specific source.
Our commentary on what you might do differently: the team made two changes at once, which Chapter 2 warns against, because if the problem disappears you cannot tell which change fixed it. Here it is a defensible trade-off: both changes target the same confirmed cause, and the goal is a reliable room rather than an experiment. The cost is lost knowledge: nobody knows whether the 5 GHz setting alone would have been enough. A team that wanted to learn more could have changed the band first, logged for a week, then moved the access point.
Different faults, same method. A tool (Task Manager) revealed what was happening now; a log revealed what happened over time. In both cases the evidence, not a hunch, chose the fix.
Try it
Do this on your own device or a training device; it changes nothing.
- Open Task Manager (Ctrl+Shift+Esc on Windows), Activity Monitor (macOS) or
top(Linux). Record your free storage, and which process uses the most CPU, memory and disk. - Start a simple occurrence log for any small intermittent annoyance you experience (a Bluetooth headset that disconnects, a slow website). For five days record date, time, activity and conditions for each occurrence.
- At the end, write one sentence describing any pattern, or state that you need more data.
Completion criteria: a resource snapshot with three named processes; at least five days of log entries with all four fields; a pattern statement that is supported by the entries.
Knowledge check
In Case Study 2, which evidence revealed the real cause of the slowness?
In Case Study 3, what exposed the pattern behind the intermittent Wi-Fi drops?
Why was preferring the 5 GHz band an appropriate change?
Why did the team wait two weeks before treating Case 3 as fixed?
Answers explained
- d — Measured storage and Task Manager named the cause; age and malware were not the findings, and the user's description pointed to the symptom, not the cause.
- a — The book's summary credits the occurrence log; a cable tester is for wired links, replacing hardware is not a test of a theory, and a single afternoon test would miss a lunchtime fault.
- b — The case ties the fault to the microwave's 2.4 GHz band; the other statements are not claims made in the case.
- c — Two weeks covered many lunchtimes; there was no new access point, and nothing says the microwave stopped being used.
Key takeaways
- Case 2: resource monitoring (Task Manager) found a cloud-sync tool filling a 97% full disk; one reversible change freed 80 GB and cut startup from four minutes to forty seconds.
- Case 3: comparison with other rooms plus an occurrence log linked midday drops to a 2.4 GHz microwave; preferring 5 GHz and moving the access point stopped the drops.
- Measure the verification, and for intermittent faults verify over time.
- Prevention belongs in the standard configuration and the network documentation, so the fix outlives the ticket.
Sources
- Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), Chapter 14 Case Studies 2–3 and review questions 2–3, §2.2, §4.4, §5.5, §6.3, §7.1, §8.3, §9.2, §12.4
