A Slow Laptop: Memory, a Full SSD, or Something Else
A paralegal at a 60-person law firm reports that her three-year-old laptop 'takes forever' and that Outlook and Teams freeze when she switches between them. The ticket has been open twice and both times closed with 'no fault found.' The machine has 8 GB RAM, a 256 GB SATA SSD that is 92% full, and a five-year-old i5. During a 10-minute observation with her normal workload open - Outlook, Teams, four browser tabs, and a PDF viewer - Task Manager shows CPU averaging 12%, memory at 88% steady with spikes to 97%, and disk at 100% with queue lengths of 3–6. Boot time to a usable desktop is about 45 seconds. Startup impact lists 14 entries. The user has asked for a new laptop; her manager has asked IT to 'just reimage it' because that fixed a similar complaint last quarter. The firm replaces laptops on a four-year cycle, and hers is due in eight months.
1. Interpret the counters. What do they support, what do they rule out, and what would you measure before proposing a fix?
Read the worked answer
The counters are unusually clear, so start with what they eliminate.
Ruled out (mostly): CPU at 12% argues against a runaway process, a crypto-miner, or malware-driven load. The 45-second boot is unremarkable for a five-year-old i5 with 14 startup entries, so boot is not the primary complaint.
Supported: memory at 88% steady, hitting 97%, with disk at 100% and a queue of 3–6, is the classic paging signature - the machine is not out of CPU, it is out of RAM, so the OS is swapping to a disk. That explains why switching between Outlook and Teams (both large working sets) triggers freezes rather than general slowness.
Before fixing, measure three things: (1) Is it a SATA SSD or a spinning disk? The ticket never confirmed it - a 92%-full SSD writes slowly due to limited free blocks and reduced over-provisioning, but a failing or nearly full HDD is far worse. Check SMART and the model string. (2) Confirm the page file is doing the work - Resource Monitor's 'hard faults/sec' is the direct evidence. (3) Determine whether 8 GB is genuinely the ceiling for her workload: check the committed bytes figure, not just the percentage.
Do not reimage yet. A reimage erases the evidence and will not add RAM.
2. Rank the remediation options by cost, disruption, and likelihood of resolving the complaint. Justify your chosen order.
Read the worked answer
1. Free the disk (near zero cost, minimal disruption). Get the SSD to at least 20–25% free - move local Downloads and old matter files to the file server, clear Outlook OST bloat, remove unused apps. A near-full SSD throttles writes and can leave no room for the page file to grow. This is an hour of technician time and may be enough on its own.
2. Trim startup and background load (free). 14 startup entries on 8 GB is a meaningful slice of a scarce resource. Disable non-essential entries and re-measure - this is reversible and testable.
3. Add RAM to 16 GB (roughly $40–80, one short downtime). If measurement confirms memory pressure is the cause of the freezes, this is the highest-value fix and extends the machine past its replacement date. It addresses the actual complaint, not a symptom.
4. Reimage (hours of user downtime). Justified only if you find profile corruption or a persistent malware finding. It fixes nothing that is full, and the user loses a day of billable work.
5. Replace the laptop (deferred). It is eight months from the cycle anyway. Spending the replacement at month 40 to solve a RAM problem wastes a machine that has life left.
The order follows one rule: cheapest reversible action that addresses the measured cause first, and confirm with the user's own workload after each step.