NewAI Content Creation is now live in Early Access
Turning Point Training Instituteby Training Center
Skip to content
0%
Module 7 — Essential Diagnostic ToolsLesson 1 of 5
Video lesson

Watching the System: Monitors and Event Logs

BeginnerVideo lesson
10 min readBeginner

Where you are: Module 7 — Essential Diagnostic Tools · Lesson 7.1 · Based on Chapter 7 (§7.1–7.2) of Dr. Tahseen Al Doori's Troubleshooting Essentials.

What you'll be able to do

  • Choose the right built-in monitoring tool for Windows, macOS or Linux.
  • Use a monitor to identify which process is using the processor (CPU), memory, disk or network.
  • Locate the event logs on each platform and match an entry to the time a fault occurred.
  • Recognise a Device Manager warning and explain what it tells you about a device or driver.

Watch: Watching the System

The video follows a fictional office laptop that keeps freezing. You will see how a monitoring tool shows what the computer is doing at the moment of the fault, and how the event log shows what went wrong and when. As you watch, keep these questions in mind:

  • Why does the author say that tools turn guesses into evidence?
  • Why is the time of an event log entry so important?
  • What does a monitor tell you that a log cannot, and the other way round?

Tools turn guesses into evidence

Chapter 7 opens with a simple idea: a diagnostic tool replaces a guess with something you can observe and record. In Step 2 of the seven-step methodology you list probable causes; in Step 3 you test them. Tools are how most of those tests are carried out. The tools in this lesson are already built into almost every computer, so nothing needs to be installed before you can use them.

There are two families of tool here:

  • Monitors show what the system is doing now: which programs are running and how much of each resource they use.
  • Logs show what the system recorded: errors, warnings and significant events, each with a time stamp.

System monitoring tools (§7.1)

ToolPlatformWhat it shows
Task Manager (Ctrl+Shift+Esc)WindowsRunning applications; CPU, memory, disk and network use; startup programs
Resource MonitorWindowsDetailed per-process use of CPU, memory, disk and network
Activity MonitormacOSProcesses; CPU, memory, energy, disk and network use
top / htopLinux, macOSA live list of processes and resource use in the terminal
Device ManagerWindowsHardware devices and driver status, with warning icons for faulty devices

Adapted from the book's Table 7.1.

A few terms first. A process is a program (or part of one) that is currently running. The CPU (central processing unit) carries out instructions; memory (RAM) holds the data that running programs are using; disk activity is reading and writing to storage. When any one of these is close to 100% for a long time, everything else on the computer has to wait, and the user experiences slowness or freezing.

How to use a monitor well:

  1. Open it while the problem is happening. A monitor shows the present moment. If the slowness has passed, so has the evidence.
  2. Sort by the resource in question. Click the CPU, Memory or Disk column heading so the heaviest process rises to the top.
  3. Watch for a while. A brief spike is normal; a process that stays at the top for minutes is a candidate cause.
  4. Compare with a baseline. Chapter 4 taught you to record what normal looks like. Knowing that this laptop normally idles at a few per cent CPU makes a reading of 95% meaningful.
  5. Record before you act. Note the process name and figures before you change anything. Ending a process you do not recognise can lose unsaved work or stop something important.

On Linux, top refreshes the list continuously in the terminal; press q to quit. htop is a friendlier variant with colour and scrolling; if it is not available on a system, top gives the same core information.

Device Manager is different from the others: it lists the hardware Windows knows about and whether a working driver (the software that lets the operating system control a device) is loaded. A device with a warning icon is reporting a problem. This links directly to the isolation techniques in Module 6: a warning that appeared after a driver update points to rollback.

Beyond the book (2026 note): Microsoft's current guidance for Windows 11 also opens Task Manager by right-clicking the Start button and choosing Task Manager; the Startup apps tab lists programs that start at sign-in and shows their startup impact, and the same list is available under Settings > Apps > Startup. In Device Manager, Microsoft advises looking for devices marked with an exclamation point (!), then trying a driver update, and disabling or uninstalling the device if that does not help. Sources: Configure Startup applications in Windows · Troubleshooting Windows unexpected restarts and stop code errors

Event logs (§7.2)

Operating systems keep a written record of errors, warnings and significant events. Each entry normally carries a time, a level (information, warning, error), a source (the component that wrote it), often an event ID or error code, and a short message.

  • Windows: Event Viewer groups entries under Windows Logs: Application (events from programs), System (events from Windows components and drivers) and Security (sign-in and audit events).
  • macOS: the Console app shows system log messages and reports.
  • Linux: logs are read with journalctl or found as files under /var/log.

The book's key technique is to look for errors logged at the same time as the fault. A log may contain thousands of harmless warnings; the entry that matters is the one whose time stamp lines up with the moment the user saw the problem. That entry usually names the failing component and gives a code you can research in vendor documentation, which is exactly the research Step 2 asks for.

text
Windows   Event Viewer > Windows Logs > System   (filter by Error, check the time)
macOS     Console app > Log messages             (search around the time of the fault)
Linux     journalctl                             (or read files in /var/log)

Beyond the book (2026 note): Microsoft Learn shows Event Viewer being opened by pressing Windows key + R, typing eventvwr.msc and selecting OK, then expanding Windows Logs and using Filter Current Log to narrow entries by source. On Linux systems that use systemd, journalctl -b shows messages from the current boot and -p err filters to the error priority and anything more severe; --since limits entries to a start time (for example journalctl -b -p err --since "09:00"). Sources: chkdsk (Viewing chkdsk logs), Microsoft Learn · journalctl(1), man7.org

Never clear a log while troubleshooting. It is evidence, and someone you escalate to may need it.

Worked example

(Fictional scenario.) A finance assistant reports that her laptop "freezes for about half a minute, several times a day". It is Windows 11 and nothing was installed recently.

  1. Identify. You ask her to note the time of each freeze. Over one morning she records 09:12, 10:47 and 11:30.
  2. Monitor. During the next freeze you open Task Manager. CPU is low, but Disk sits at 100% and no single program explains it.
  3. Log. In Event Viewer, under Windows Logs > System, you filter for warnings and errors. Entries from the disk component appear at 09:12, 10:47 and 11:30, exactly matching her notes.
  4. Theory. The storage device may be failing. This is now a theory backed by two independent pieces of evidence, not a guess.
  5. Next step. Because data could be at risk, the first action is a backup, not a repair. You will study why in Module 8.

Notice the pattern: the monitor narrowed the problem to disk; the log's time stamps tied that to a specific component.

Try it

Use your own computer: every action below only reads information and changes nothing.

  1. Open your platform's monitor (Task Manager, Activity Monitor or top). With only your usual programs open, record a baseline: CPU %, memory in use, and the three processes using the most memory.
  2. Open a large web page or video and record how the figures change. Close it and confirm they return to the baseline.
  3. Open your event log (Event Viewer, Console or journalctl). Find the most recent error. Record its time, source and any ID or code.
  4. Look up that source or code in the vendor's official documentation and write one sentence on what it means and whether it matters.

Completion criteria: a baseline table, a before/after comparison, and one log entry recorded with time, source, code and a one-sentence interpretation. Do not end processes, change drivers or clear logs.

Knowledge check

A user says their PC is slow right now. Which tool shows you which process is using the most CPU at this moment?

On Windows, which Event Viewer log would you check first for an error written by a hardware driver?

You find 40 warnings in a log. What is the most useful way to decide which entry matters?

Where would you look for system logs on a Linux computer?

Answers explained — 1: Task Manager shows live per-process resource use; Event Viewer shows recorded history, nslookup tests DNS and System Restore rolls back changes. 2: driver and Windows component events go to the System log; Application holds program events and Security holds sign-in and audit events. 3: the book's technique is to match the time of the entry to the time of the fault; wording and age are not evidence, and deleting a log destroys evidence. 4: Linux logs are read with journalctl or under /var/log; Device Manager is Windows, and Activity Monitor and Console are macOS.

Key takeaways

  • Tools turn guesses into evidence: use them to carry out the tests in Steps 2 and 3.
  • Monitors show what the system is doing now; open them while the fault is happening and compare with a baseline.
  • Logs show what went wrong; the entry that matters is the one logged at the same time as the fault.
  • Device Manager warnings point to a device or driver, often after a recent change.
  • Record before you act, and never clear a log you are investigating.

Sources