Skip to content
Tutorials Center
My learning

Topics

Lesson 41 of 55 ยท Security and Care

Troubleshooting, Performance and Upgrades

Learn a systematic way to diagnose computer problems, read Task Manager or Activity Monitor, find the bottleneck, decide on RAM or SSD upgrades and trace boot failures.

"My computer is slow" and "it won't start" are among the most common sentences in computing, and the usual response, trying random things and hoping, wastes time and sometimes makes the problem worse. Skilled technicians do something different. They observe, form a guess, test one change at a time, and use the machine's own measurements to find out what is actually limiting it.

This lesson gives you a method for diagnosing problems, shows how to read the system monitor that every operating system includes, explains bottleneck thinking (the slowest part decides the speed), helps you decide when more RAM or an SSD is worth buying, and walks through the boot process to localize start-up failures. It combines ideas from Memory: RAM, Cache and the Memory Hierarchy, Storage: HDD, SSD and Beyond, The CPU and Processes, Threads and Scheduling.

A systematic method

  1. Describe the problem precisely. "Slow" is vague. "The browser takes 30 seconds to open, but a text editor opens instantly" already tells you a lot.
  2. Find out what changed. New software, an update, a new device, a full disk? Most problems follow a change.
  3. Reproduce it. Can you make it happen again? Does it happen for everything or one program, for everyone or one user, on Wi-Fi and on a cable?
  4. Check the simple and cheap things first. Is it plugged in? Is the disk full? Is the internet service itself down? Have you restarted?
  5. Measure. Open the system monitor and look before guessing.
  6. Change one thing at a time, and check whether it helped. If you change five things, you will not know which one fixed it, or which broke something new.
  7. Undo what did not help, and write down what you tried, especially when you ask someone else for help.
  8. Keep your data safe first. Before risky steps such as reinstalling, make sure the files are backed up (see Backups and Data Recovery).
flowchart LR
  A["Describe<br/>the symptom"] --> B["Guess a cause"]
  B --> C["Test with ONE change"]
  C --> D{"Fixed?"}
  D -->|"yes"| E["Note the cause<br/>and the fix"]
  D -->|"no"| F["Undo it, learn from<br/>the result"]
  F --> B

Troubleshooting is a loop of guess, test, and learn, with one change per round.

A restart really is a good first step, and not superstition: it clears memory that programs forgot to release, stops runaway processes, and finishes pending updates. But a problem that comes back after every restart needs a diagnosis.

Reading the system monitor

Windows has Task Manager (press Ctrl+Shift+Esc), macOS has Activity Monitor, and Linux has tools such as top, htop or a graphical System Monitor. They all show the same four resources and a list of processes:

  • CPU: how busy the processor is, as a percentage of its total capacity. A high number for a long time means something is computing hard. Also look at per-core graphs: if one core is at 100% and the others are idle, the busy program uses only one thread.
  • Memory: how much RAM is in use and how much is free or cached. High use is not automatically bad: operating systems use spare RAM as a cache on purpose. The warning signs are very high use together with heavy swapping (or "page file" activity) and sluggishness; see Memory Management.
  • Disk: the percentage of time the drive is busy, plus reads and writes per second. A hard disk stuck near 100% makes everything wait.
  • Network: current send and receive speed.

Also useful: temperature and clock speed (a hot chip lowers its own speed, called thermal throttling), and the startup list, programs that launch with the computer and silently use memory and CPU.

To find the culprit, sort the process list by the column that is high (CPU, memory or disk) and see which program is at the top. If it is something you recognize and are using, that is the load. If it is unfamiliar, search for its exact name before ending it; ending a system process can close the session. If it is a program you do not need, close it, disable it at startup, or uninstall it.

Common patterns

Symptom Likely cause First thing to try
Everything slow after hours of use, memory use grows A leaking application Restart that application
Disk at 100%, machine freezes, old hard disk Swapping, antivirus scan, or slow HDD Free RAM, wait for scan, consider an SSD
One program slow, fan loud, CPU 100% Busy loop or heavy task Check what the program is doing; update it
Slow after waking from sleep, one website slow Network or the site Test another site and another device
Slow and hot, fan always loud Dust or blocked vents, thermal throttling Clean vents, improve airflow
Slow and unfamiliar processes Malware or unwanted software Scan; see Malware, Phishing and Safe Habits

Bottleneck thinking

A computer is a chain of parts that hand work to each other: the disk feeds RAM, RAM feeds the CPU, the CPU produces results. At any moment, one part is usually the slowest, and that part decides the pace of the whole task: the bottleneck. Speeding up any other part changes almost nothing. Buying a faster CPU for a machine that is waiting on a slow hard disk is like putting a bigger engine in a car with a blocked fuel line.

So the question is always: which resource is saturated while the others sit idle? The stand-in below applies simple rules to snapshots of a system monitor. It is intentionally basic. A real diagnosis considers history over time, but the reasoning is the same.

JS A bottleneck finder

Press Run (or Ctrl + Enter) to see the console output here.

No output.

In the first case the disk is saturated because the system is swapping, so the real root cause is memory. Fixing memory first (closing tabs, adding RAM) would usually also calm the disk. Bottlenecks can be chains of cause and effect, so read all the signals together.

Upgrades: what is worth it

Upgrades only help when they target the bottleneck. Rough guidance for typical home and office use:

  • Replace a hard disk with an SSD. For an older computer that boots in minutes and opens programs slowly, this is usually the biggest improvement per dollar. Start-up and program loading drop from minutes to seconds because an SSD answers random requests tens to hundreds of times faster.
  • Add RAM when you are actually swapping. If Task Manager shows memory near the limit with heavy disk activity during normal use, more RAM helps a lot. If memory use is moderate, more RAM does nothing. As a rough guide, 8 GB handles light use today, 16 GB is comfortable for everyday multitasking and light creative work, and 32 GB or more serves heavy editing, virtual machines and large datasets. Check whether your device even allows RAM upgrades: many thin laptops have it soldered to the board.
  • Upgrade the CPU or whole computer when the CPU is saturated across all cores during your normal tasks, or the machine no longer gets security updates. Often the CPU cannot be swapped on laptops, so this means a new machine.
  • Add or upgrade the GPU for games, 3D and some AI and video work; it does little for office tasks.
  • Improve the network (a better router position, a cable instead of Wi-Fi, a faster plan) when only online tasks are slow.
  • Free up disk space. Drives that are nearly full get slower and leave no room for swap or updates; clear what you do not need.

Before spending money, ask: will this change the resource that is saturated? If you cannot answer, measure first.

When the computer will not start

Starting a computer is a relay race, covered in What an Operating System Does. Each stage hands over to the next, so where it stops tells you where to look. The stand-in lists the stages and names the usual suspects after the last stage that worked.

JS Where did the boot stop?

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Practical steps that follow from the stages:

  • No signs of life: check the outlet, the power cable and any switch; try a different cable; for a laptop, try the charger alone to rule out a dead battery.
  • Lights and fans but no picture: try another cable or monitor; reseat the memory modules; unplug extra devices.
  • "No bootable device" or similar message: unplug USB drives, check the boot order in the firmware settings, and listen for a failing drive. This may mean the drive has died, so back up what you can.
  • Boot loops or crashes while loading the operating system: try safe mode (a minimal start-up with basic drivers), undo the last update or driver, or use the recovery tools offered on screen. A reinstall is the last resort, after the data is safe.
  • Blue screen or a kernel panic: note the stop code or message; it points to a driver, memory or disk fault. Repeated random crashes often indicate failing RAM or overheating.

Know when to stop

Some problems are not worth fixing yourself: a swollen battery (stop using the device), liquid damage, a drive making clicking sounds with important data on it, or any repair that voids a warranty you want to keep. Stop, make the device safe, and consult a professional.

What is real here and what is a stand-in? The troubleshooting method, the four resources in the monitor, thermal throttling, boot stages and upgrade advice are real. The diagnosis rules above use made-up numbers and thresholds for teaching. A real tool looks at trends over time, and experienced people also read logs and error codes, which this lesson does not cover.

Check your understanding

Quick check ยท 5 questions

of 5 answered You scored / 5 ยท perfect!

  1. 1. Why should you change only one thing at a time when troubleshooting?

    With several simultaneous changes you cannot tell which one mattered, and you may introduce new problems.
  2. 2. In Task Manager one CPU core is at 100% while seven others are idle. What does this suggest?

    A single-threaded task can use only one core. A faster core would help, additional cores would not.
  3. 3. A very old computer with a hard disk takes minutes to start and its disk activity sits near 100%. Which upgrade will most likely help most?

    The disk is the bottleneck. An SSD answers random requests far faster, which transforms boot and program loading times.
  4. 4. Memory use shows 85% but the machine is fast and the disk is quiet. What is the right conclusion?

    High memory use alone is not a fault. It matters when the system begins swapping and responsiveness drops.
  5. 5. The screen shows a manufacturer logo but then reports that no bootable device was found. Which stage worked and which failed?

    The firmware ran (the logo appeared) but found nothing to start from, so check the boot order, cables and the drive.

Summary

  • Troubleshoot methodically: describe the symptom, find what changed, reproduce, check simple causes, measure, change one thing at a time, and keep notes.
  • Task Manager or Activity Monitor shows CPU, memory, disk and network; sort by the busy column to find the responsible process.
  • The bottleneck is the saturated resource that limits everything else; upgrades help only if they target it, and a cause can be hiding behind its effects (swapping shows up as busy disk).
  • An SSD is the best upgrade for a slow hard-disk machine; more RAM helps only when the system actually swaps.
  • A boot failure points to a stage: power, firmware self-test, boot device, operating system, login. Safe mode and recovery tools come before reinstalling, and data comes first.
  • Know when to stop and ask a professional.

Next, put what you know into daily practice: Files, Folders and Staying Organized.