Os Troubleshooting

19 min read3,659 words

OS Troubleshooting

OS troubleshooting is the systematic process of identifying, diagnosing, and fixing problems related to an operating system, hardware, drivers, applications, filesystems, networking, booting, and system performance.

Exam definition

Operating system troubleshooting is the systematic process of identifying the cause of an OS-related problem and applying appropriate corrective actions to restore normal system operation.

1. Why OS Troubleshooting Is Needed

An operating system can have problems such as:

  • System not booting
  • Blue screen / system crash
  • Black screen
  • System freezing
  • Slow performance
  • Application not starting
  • High CPU usage
  • High RAM usage
  • Disk full
  • Network not working
  • Driver problems
  • Permission errors
  • Filesystem corruption
  • Update failures
  • Malware/security problems
  • Missing system files

2. Basic Troubleshooting Process

A good troubleshooting process follows a systematic approach:

Problem ↓ Identify symptoms ↓ Collect information ↓ Form a hypothesis ↓ Test the hypothesis ↓ Apply solution ↓ Verify ↓ Document

Memory trick

Identify → Analyze → Test → Fix → Verify

3. Step 1 — Identify the Problem

First determine exactly what is wrong.

For example:

"My computer is slow."

This is too general.

Investigate:

Is CPU usage high? Is RAM full? Is disk usage high? Is network slow? Is one application causing the problem? Did the problem start after an update?

The goal is to convert a vague complaint into a measurable symptom.

4. Step 2 — Collect Information

Ask:

  • When did the problem start?
  • What changed recently?
  • Did you install software?
  • Did you update the OS?
  • Did you install a driver?
  • Did hardware change?
  • Does the problem happen every time?
  • Is it affecting one user or everyone?
  • What error message appears?

For example:

Yesterday → system worked normally Today → Wi-Fi stopped working Recent change → network driver update

This gives you a useful starting hypothesis.

5. Step 3 — Check the Simplest Things First

Before doing complicated troubleshooting, check basic things.

For example, if the network doesn't work:

Wi-Fi enabled? ↓ Connected to correct network? ↓ IP address obtained? ↓ Gateway reachable? ↓ DNS working? ↓ Internet working?

Don't immediately reinstall the operating system.

6. Troubleshooting by Layers

A useful approach is to troubleshoot from lower-level components upward.

Hardware ↓ Firmware ↓ Boot ↓ Kernel ↓ Drivers ↓ Services ↓ Network ↓ Applications ↓ User configuration

Example:

Application cannot connect to Internet ↓ Is application running? ↓ Is OS network interface working? ↓ Does system have an IP? ↓ Does gateway respond? ↓ Does DNS resolve? ↓ Does Internet respond?

7. Common OS Troubleshooting Categories

CategoryExample
BootOS doesn't start
CPU100% CPU
MemoryRAM exhausted
StorageDisk full
FilesystemCorruption
DriversDevice not working
NetworkNo Internet
ProcessApplication frozen
ServicesService failed
PermissionsAccess denied
UpdatesUpdate fails
SecurityMalware/suspicious activity
PerformanceSystem very slow

8. Boot Problems

A common serious OS problem is:

The computer does not boot.

Basic boot chain:

Power ↓ BIOS/UEFI ↓ Boot Device ↓ Bootloader ↓ Kernel ↓ System Initialization ↓ Services ↓ Login

The troubleshooting strategy is to determine where the chain stops.

9. No Power vs No Boot

These are different problems.

No power

Power button ↓ Nothing happens

Check:

  • power cable
  • adapter
  • battery
  • power supply
  • motherboard indicators

No boot

The computer powers on but doesn't load the OS.

Power ON ↓ BIOS/UEFI ↓ Error / boot failure

Possible causes:

  • incorrect boot device
  • damaged bootloader
  • disk failure
  • corrupted filesystem
  • OS corruption

10. Bootloader Problem

Suppose:

Power ↓ UEFI ↓ Bootloader ❌

The OS kernel may never be loaded.

Linux systems commonly use bootloaders such as GRUB.

Windows uses Windows Boot Manager.

Possible troubleshooting tools depend on the platform and boot mode.

11. Safe Mode

Safe Mode starts Windows with a minimal set of drivers and services.

It can help determine whether:

  • third-party drivers
  • startup programs
  • recently installed software

are causing problems.

Conceptually:

Normal Boot ↓ Many drivers + services + startup programs Safe Mode ↓ Minimal drivers + essential services

Linux has different recovery/minimal-boot mechanisms rather than a single identical "Safe Mode."

12. Linux Recovery Mode

Linux distributions may provide recovery options through the bootloader or rescue environments.

Possible tasks include:

  • filesystem checks
  • package repair
  • bootloader repair
  • resetting configuration
  • accessing a root shell

The exact procedure differs by distribution.

13. Windows Recovery Environment

Windows provides Windows Recovery Environment (WinRE).

It can provide tools such as:

  • Startup Repair
  • System Restore
  • Command Prompt
  • Uninstall Updates
  • Reset/recovery options

Useful when normal Windows startup fails.

14. High CPU Usage

Suppose the computer becomes slow.

Check CPU usage.

Linux

top

or:

htop

Windows

Task Manager

or PowerShell:

Get-Process

macOS

Activity Monitor

or:

top

15. Finding the CPU-Hungry Process

Conceptually:

CPU = 100% ↓ Which process? ↓ Process A → 2% Process B → 95% ← Problem candidate Process C → 3%

Possible causes:

  • infinite loop
  • heavy computation
  • runaway application
  • background update
  • malware
  • driver problem

Don't automatically kill a process before understanding what it is, especially system processes.

16. High Memory Usage

If RAM is almost completely consumed:

RAM ████████████████████ 98%

Possible causes:

  • too many applications
  • memory leak
  • browser tabs
  • virtual machines
  • containers
  • large datasets
  • background services

Check memory usage.

Linux

free -h

and:

top

Windows

Task Manager → Performance → Memory

PowerShell:

Get-Process

macOS

Activity Monitor → Memory

17. Memory Leak

A memory leak occurs when a program continues consuming memory without properly releasing memory it no longer needs.

Example:

Time ↓ 10 min → 200 MB 20 min → 500 MB 30 min → 1 GB 40 min → 2 GB

Eventually:

RAM exhausted ↓ Swapping/paging ↓ System becomes slow

18. Disk Full

Check available disk space.

Linux

df -h

To find large directories:

du -sh *

Windows

Get-Volume

or:

dir

Graphical:

Settings → System → Storage

macOS

df -h

19. Disk Full Troubleshooting

Find:

Large files Large logs Caches Downloads Old backups Unused applications Container images VM disks

For example, Docker can consume significant storage through:

  • images
  • stopped containers
  • volumes
  • build cache

So container storage should be checked separately when relevant.

20. Disk Health

A disk can be:

Full

without being physically damaged.

These are different problems:

Disk capacity problem

Disk → 99% full

Disk health problem

SSD/HDD → hardware errors

Check appropriate health tools such as SMART information where supported.

21. Filesystem Problems

Filesystem corruption can cause:

  • files not opening
  • boot failure
  • read/write errors
  • unexpected crashes
  • missing directories

General process:

Detect filesystem problem ↓ Back up important data ↓ Unmount if required ↓ Run filesystem check ↓ Repair ↓ Verify

Linux example

Filesystem tools depend on filesystem type. A common example is:

fsck

Important: filesystem repair should be performed carefully and normally on an appropriate unmounted filesystem or from a recovery environment.

22. Windows Filesystem Troubleshooting

Windows provides:

chkdsk

For example:

chkdsk C:

Repair operations may require elevated privileges and, for the system volume, may be scheduled for the next reboot.

23. Windows System File Problems

Windows has tools for repairing system components.

System File Checker

sfc /scannow

It checks protected system files.

DISM

DISM /Online /Cleanup-Image /RestoreHealth

DISM can repair the Windows component store used by system-file repair.

Typical sequence when appropriate:

DISM ↓ SFC ↓ Reboot ↓ Verify

24. Linux Package Problems

On Debian-based distributions such as Ubuntu/Kali, package issues can sometimes be investigated with:

sudo apt update

and package repair mechanisms such as:

sudo apt --fix-broken install

Then verify the application/package.

Do not blindly remove packages when troubleshooting dependency problems.

25. Driver Problems

A driver allows the OS to communicate with hardware.

OS ↓ Driver ↓ Hardware

If the driver fails:

OS ↓ Driver ❌ ↓ Hardware

Possible symptoms:

  • Wi-Fi doesn't work
  • sound doesn't work
  • display problems
  • USB device not detected
  • printer doesn't work

26. Windows Driver Troubleshooting

Open:

Device Manager

You can inspect devices and driver status.

Command:

devmgmt.msc

PowerShell can also help inspect devices depending on what you need to diagnose.

27. Linux Device Troubleshooting

Useful commands:

lsusb

USB devices.

lspci

PCI devices.

lspci -k

Shows associated kernel drivers/modules where available.

dmesg

Shows kernel messages.

For systemd systems:

journalctl

can provide detailed logs.

28. Network Troubleshooting

Network troubleshooting should be systematic.

Use:

Physical/Wi-Fi ↓ Interface ↓ IP address ↓ Default gateway ↓ DNS ↓ Internet/service

29. Step 1 — Check Network Interface

Linux

ip addr

Windows

ipconfig

macOS

ifconfig

Check whether the interface is:

UP

and has an appropriate IP address.

30. Step 2 — Check Gateway

Find your default gateway.

Linux

ip route

Windows

ipconfig

Then test the gateway:

ping <gateway-ip>

If the gateway cannot be reached, investigate the local network before blaming DNS or the Internet.

31. Step 3 — Test Internet Without DNS

Try a known IP address when appropriate.

Conceptually:

Can reach IP? ↓ YES ↓ Maybe DNS problem

If IP connectivity works but domain names don't resolve, investigate DNS.

32. Step 4 — Test DNS

Linux:

dig example.com

or:

nslookup example.com

Windows:

nslookup example.com

If:

ping IP → works DNS lookup → fails

the problem may be DNS-related.

33. Step 5 — Test Application Connectivity

For HTTP/HTTPS:

curl -I https://example.com

This helps distinguish:

Network works ↓ DNS works ↓ HTTP service problem

34. Network Troubleshooting Flow

No Internet ↓ Interface enabled? ↓ Has IP address? ↓ Gateway reachable? ↓ DNS works? ↓ Internet IP reachable? ↓ Application/service reachable?

This is much better than immediately changing random network settings.

35. Application Not Starting

Suppose:

Application ↓ Doesn't start

Check:

  1. Is the application installed?
  2. Is the executable available?
  3. Are dependencies installed?
  4. Are permissions correct?
  5. Is another process already using required resources/ports?
  6. What does the application log say?
  7. Did an update change its configuration?

36. Application Crashes

Possible causes:

  • bugs
  • missing libraries
  • corrupted configuration
  • incompatible version
  • insufficient memory
  • permission problems
  • damaged files
  • driver problems

First check:

Error message ↓ Logs ↓ Recent changes ↓ Dependencies

37. Port Conflict

A common development problem:

Application wants port 3000 ↓ Port already in use ↓ Application fails

Linux/macOS

lsof -i :3000

or:

ss -ltnp

Windows

netstat -ano | findstr :3000

Then identify the process.

38. Service Troubleshooting

Modern Linux systems often use systemd.

Check service status:

systemctl status nginx

Restart if appropriate:

sudo systemctl restart nginx

View logs:

journalctl -u nginx

Windows:

Get-Service

or:

sc query

39. macOS Service/Process Troubleshooting

macOS uses launchd for system and user services.

Useful tools include:

launchctl

For general processes:

ps

and:

top

Logs can also be inspected through the macOS logging system.

40. System Logs

Logs are one of the most important troubleshooting sources.

They tell you:

What happened? When? Which component? What error?

Linux

journalctl

Also commonly:

/var/log/

depending on the distribution/service.

Windows

Event Viewer

or:

Get-WinEvent

macOS

The Console application and:

log

can be used for system logging.

41. Process Frozen

If an application stops responding:

Application ↓ Not responding

First determine whether it is actually frozen or simply busy.

Check:

  • CPU
  • memory
  • disk I/O
  • network
  • application logs

Then terminate it if necessary.

Linux

kill PID

If a process refuses to terminate and you understand the consequences:

kill -9 PID

SIGKILL should be a last resort because the process cannot clean up normally.

42. Windows Process Management

List processes:

tasklist

Terminate:

taskkill /PID 1234

Force termination:

taskkill /PID 1234 /F

Use force carefully because unsaved data can be lost.

43. Permissions Problems

Typical error:

Permission denied

Check:

Who owns the file? What permissions exist? What user is running the application? What groups does the user belong to?

Linux

ls -l file.txt

Example:

-rw-r--r--

Ownership:

ls -l

Change permissions:

chmod

Change ownership:

chown

44. Windows Permissions

Useful commands/tools:

icacls

and:

Properties → Security

PowerShell:

Get-Acl

Permissions are based on Windows security descriptors and ACLs.

45. System Update Problems

An OS update can fail because of:

  • insufficient storage
  • broken package dependencies
  • interrupted update
  • incompatible driver
  • corrupted update files
  • network problems

Basic approach:

Check error ↓ Check storage ↓ Check network ↓ Check update logs ↓ Repair package/system components ↓ Retry

Avoid interrupting critical OS updates unless necessary.

46. Performance Troubleshooting

If the entire system is slow:

Check CPU ↓ Check RAM ↓ Check Disk ↓ Check Network ↓ Check Processes ↓ Check Startup Services ↓ Check Temperature/Hardware

Linux

top free -h df -h

Windows

Task Manager

macOS

Activity Monitor

47. CPU vs RAM vs Disk Bottleneck

CPU bottleneck

CPU → 100% RAM → normal Disk → normal

Likely CPU-intensive process.

RAM bottleneck

RAM → nearly full Swap/pagefile → high activity

Possible memory pressure.

Disk bottleneck

Disk utilization → very high CPU → moderate

Possible heavy I/O or storage problem.

48. System Freeze

If the entire system freezes:

Possible causes:

  • driver failure
  • RAM problems
  • overheating
  • disk problems
  • kernel crash
  • hardware fault
  • runaway process
  • severe resource exhaustion

Troubleshooting:

Check logs after reboot ↓ Check temperatures ↓ Check RAM ↓ Check storage health ↓ Check drivers ↓ Check recent changes

49. Overheating

Symptoms:

  • fan running constantly
  • sudden shutdown
  • throttling
  • poor performance
  • system instability

Possible causes:

  • blocked ventilation
  • dust
  • failing fan
  • high CPU/GPU workload
  • poor thermal contact
  • high ambient temperature

The OS can monitor temperatures where hardware exposes appropriate sensors, but physical inspection may also be required.

50. Malware and Security Troubleshooting

If you suspect malware:

Disconnect/isolate if appropriate ↓ Preserve important evidence ↓ Check suspicious processes ↓ Check startup/persistence ↓ Run trusted security tools ↓ Patch system ↓ Change compromised credentials ↓ Restore/rebuild if necessary

Don't immediately delete suspicious files if you need forensic evidence.

For ordinary home troubleshooting, use trusted security software and keep the OS updated.

51. Backup Before Major Repair

Before destructive troubleshooting:

Important Data ↓ Backup ↓ Repair

Examples of risky actions include:

  • filesystem repair
  • partition changes
  • OS reset
  • disk formatting
  • bootloader changes
  • deleting system files

Always understand what an operation will change before executing it.

52. Troubleshooting Decision Tree

OS Problem │ ┌──────────┴──────────┐ ↓ ↓ Doesn't boot Boots normally │ │ Boot/Firmware What is wrong? Disk/OS files │ │ ┌──────┼───────┐ │ ↓ ↓ ↓ │ Slow Network App │ │ │ │ │ CPU IP Logs │ RAM DNS Process │ Disk Gateway Dependencies │ ↓ Recovery

53. Troubleshooting Tools by OS

TaskLinuxWindowsmacOS
Processesps, top, htopTask Manager, tasklistActivity Monitor, ps, top
Memoryfree, topTask ManagerActivity Monitor
Disk spacedf, duStorage, Get-Volumedf, Storage settings
Networkip, ping, ssipconfig, ping, netstatifconfig, ping, netstat
DNSdig, nslookupnslookupdig, nslookup
LogsjournalctlEvent Viewer, Get-WinEventConsole, log
Deviceslsusb, lspciDevice ManagerSystem Information
Filesystemfsckchkdskdiskutil tools
System filespackage toolsSFC, DISMOS recovery/update mechanisms
ServicessystemctlGet-Service, sclaunchctl

54. Troubleshooting Method: Divide and Conquer

Instead of testing everything simultaneously, divide the system into sections.

Example:

Internet not working ↓ Physical/Wi-Fi? ↓ Network interface? ↓ IP? ↓ Gateway? ↓ DNS? ↓ Application?

This quickly narrows down the faulty layer.

55. Change One Thing at a Time

Suppose an application isn't working.

Don't do:

Update OS Change DNS Reinstall application Change firewall Change permissions Restart services

all at once.

Instead:

Test 1 ↓ Result ↓ Test 2 ↓ Result ↓ Fix

Otherwise, you won't know which change actually solved the problem.

56. Reproduce the Problem

If possible, reproduce the problem consistently.

For example:

Start application ↓ Open file ↓ Click button ↓ Crash

If you can reproduce it, diagnosis becomes much easier.

57. Check Recent Changes

A powerful troubleshooting question is:

What changed before the problem started?

Possible changes:

New software New driver OS update Configuration change Hardware change Network change Permission change

If:

Everything worked ↓ Driver updated ↓ Wi-Fi stopped

the driver update becomes an important hypothesis.

58. Root Cause vs Symptom

Suppose:

System is slow

This is a symptom.

You discover:

RAM exhausted

This is closer to a cause.

You discover:

Application has a memory leak

This may be the root cause.

Memory leak ↓ RAM exhaustion ↓ Heavy swapping ↓ System slow

Good troubleshooting tries to find the underlying cause rather than just hiding the symptom.

59. Verify the Solution

After fixing something:

Apply fix ↓ Restart/reload if required ↓ Reproduce original problem ↓ Confirm it is solved

Don't assume:

"I changed something, therefore it's fixed."

60. Document the Solution

For professional troubleshooting, record:

Problem: Cause: Evidence: Solution: Commands/actions: Result:

Example:

Problem: Application could not start. Cause: Port 3000 was already occupied. Evidence: Process listening on port 3000. Solution: Stopped the conflicting process. Result: Application started successfully.

This makes future troubleshooting faster.

61. Golden Troubleshooting Rules

Remember these:

Rule 1

Understand the symptom before changing anything.

Rule 2

Start with simple checks.

Rule 3

Check logs and error messages.

Rule 4

Change one thing at a time.

Rule 5

Back up important data before risky operations.

Rule 6

Verify the fix.

Rule 7

Find the root cause, not only the symptom.

62. Complete OS Troubleshooting Flow

PROBLEM │ ↓ Identify Symptom │ ↓ Collect Information │ ↓ Check Recent Changes │ ↓ Check Simple Causes │ ↓ Check Logs / Errors │ ↓ Form Hypothesis │ ↓ Test It │ ┌──────┴──────┐ ↓ ↓ Correct Incorrect │ │ ↓ ↓ Fix New Hypothesis │ │ └──────┬──────┘ ↓ Verify ↓ Document

🧠 OS Troubleshooting — Exam Revision

Definition

OS troubleshooting is the systematic process of identifying, diagnosing, and resolving operating-system problems involving booting, processes, memory, storage, filesystems, drivers, networking, applications, and system services.

Main steps

Identify ↓ Collect information ↓ Analyze ↓ Hypothesis ↓ Test ↓ Fix ↓ Verify ↓ Document

Remember the major areas:

BOOT → CPU → RAM → DISK → DRIVER → NETWORK → PROCESS → SERVICE → APPLICATION → SECURITY

Important commands to remember

Linux

top free -h df -h du -sh * ip addr ip route ping ss dig journalctl systemctl dmesg lsblk

Windows

tasklist ipconfig ping nslookup netstat chkdsk sfc /scannow

macOS

top df -h ifconfig ping lsof diskutil log launchctl

🎯 Final OS Roadmap Complete

You have now covered the complete roadmap:

Introduction ↓ Types of OS ↓ OS Architecture ↓ System Calls ↓ Processes ↓ Threads ↓ Multithreading ↓ Process Communication ↓ Process Scheduling ↓ CPU Scheduling ↓ Deadlocks ↓ Deadlock Handling ↓ Memory Management ↓ Memory Allocation ↓ Paging ↓ Segmentation ↓ Virtual Memory ↓ File System ↓ File Management ↓ Directory Management ↓ File Allocation ↓ Disk Management ↓ Disk Scheduling ↓ Storage ↓ I/O Management ↓ Device Management ↓ Interrupts ↓ Linux ↓ Linux Commands ↓ Windows ↓ Windows Commands ↓ macOS ↓ macOS Commands ↓ Boot Process ↓ Virtualization ↓ Containers ↓ OS Troubleshooting

Keep learning. Keep building. Keep growing.

© 2026 Ugenz Academy