Computer Hardware, Architecture & Support Fundamentals
Most IT beginners can name parts — CPU, RAM, hard drive — but very few understand how they work together. That gap? It's what separates a good technician from a great one.
Computer Hardware, Architecture & IT Support Fundamentals
Foundation of Computer Systems for IT Support Professionals
Table of Contents
- General Introduction
- Concept Breakdown
- IT Support Perspective
- Learning Questions
- Practical Activities
1. General Introduction
What Is a Computer?
A computer is an electronic machine that processes data according to a set of instructions (a program). It accepts input, processes that input, stores information, and produces output. Computers range from the smartphone in your pocket to the servers powering the internet — but they all share the same fundamental principles.
At the most basic level, every computer does four things:
| Function | Description | Example |
|---|---|---|
| Input | Accepts data from the outside world | Typing on a keyboard |
| Processing | Performs operations on that data | CPU calculating a sum |
| Storage | Saves data temporarily or permanently | RAM holding open files; HDD saving documents |
| Output | Delivers results to the user or another system | Monitor displaying a webpage |
What Is Computer Hardware?
Computer hardware refers to all the physical, tangible components of a computer system — the parts you can touch, see, and replace. Hardware is the body of the computer.
Examples include:
- The CPU (the chip that does the thinking)
- RAM modules (temporary memory)
- Hard drives or SSDs (permanent storage)
- The motherboard (the main circuit board connecting everything)
- Input/output devices such as keyboards, mice, monitors, and USB drives
Hardware by itself does nothing — it needs software (instructions) to function. The relationship between hardware and software is symbiotic: software tells hardware what to do, and hardware makes it physically happen.
What Is Computer Architecture?
Computer architecture is the design of a computer system — the blueprint that defines how the hardware components are organized, how they communicate, and what capabilities the system offers.
Think of it like the architectural plan of a building. The architect decides:
- How many rooms (components) are there?
- How big are they? What are they for?
- How do people (data) move between them?
In computing, architecture decisions include:
- How many bits the CPU processes at once (32-bit vs. 64-bit)
- How the CPU communicates with memory
- The instruction set the CPU understands (x86, ARM, etc.)
- How input/output devices connect to the system
Architecture defines what the system can do.
What Is Computer Organization?
Computer organization is closely related to architecture but focuses on how the hardware actually implements the architectural design — the practical, physical reality of the system.
If architecture is the blueprint, organization is the construction.
Organization covers:
- How data flows through buses (electrical pathways)
- The actual speed and timing of memory operations
- How control signals are sent between components
- The physical layout of circuits on a motherboard
💡 Key distinction: Architecture asks "What should this system be able to do?" — Organization asks "How is it physically built to do it?"
Why Does This Matter for IT Support?
As an IT Support professional — whether you work at a Help Desk, as a System Administrator, or as a Field Technician — you are the first line of defense when hardware fails or systems underperform.
You will regularly encounter situations like:
- A user's computer running unusually slowly → Could be a RAM, CPU, or storage issue
- A machine failing to boot → Could be a failing hard drive, corrupted OS, or bad RAM
- A peripheral device not recognized → Could be a driver issue or failed I/O port
- Overheating and unexpected shutdowns → Could be a CPU cooling or airflow problem
Without a foundational understanding of what hardware does and how it interacts, diagnosing these problems becomes guesswork. With it, you follow a logical, systematic process — and you fix things faster and more reliably.
2. Concept Breakdown
2.1 Computer Hardware Overview
Computer hardware can be divided into several categories based on function:
Core Internal Components
| Component | Role |
|---|---|
| CPU (Central Processing Unit) | The "brain" — executes instructions and processes data |
| RAM (Random Access Memory) | Short-term, fast memory the CPU uses while programs are running |
| Motherboard | The main circuit board that connects and allows communication between all components |
| Storage (HDD/SSD) | Long-term memory that stores files, the operating system, and applications |
| Power Supply Unit (PSU) | Converts wall power (AC) into usable power (DC) for internal components |
| GPU (Graphics Processing Unit) | Handles rendering of visuals; can be integrated in the CPU or a separate card |
| Cooling System | Fans and heat sinks that prevent components from overheating |
External / Peripheral Components
| Category | Examples |
|---|---|
| Input devices | Keyboard, mouse, microphone, scanner, webcam |
| Output devices | Monitor, printer, speakers |
| Storage devices | USB flash drives, external hard drives, optical drives |
| Network devices | Network Interface Card (NIC), Wi-Fi adapter |
The Motherboard — The Hub of Everything
The motherboard deserves special attention because everything connects to it. Key features include:
- CPU socket — where the processor physically sits
- RAM slots (DIMM slots) — where memory modules are inserted
- PCIe slots — expansion slots for graphics cards, network cards, etc.
- SATA/NVMe connectors — connect storage drives
- USB, audio, and network ports — connect peripheral devices
- BIOS/UEFI chip — firmware that initializes hardware during startup
2.2 Computer Architecture vs Organization
This distinction often confuses beginners, but it's important — especially for understanding IT documentation and specifications.
Computer Architecture
Architecture is concerned with the logical design and the programmer's view of the system. It answers questions like:
- What instructions can this CPU execute? (Instruction Set Architecture — ISA)
- How large is a memory address? (32-bit or 64-bit)
- How does the CPU communicate with RAM?
- How many cores does the processor have?
The x86-64 architecture (used in most Windows/Linux PCs) and ARM architecture (used in most smartphones and Apple's M-series chips) are examples of architectural families.
Computer Organization
Organization is concerned with the physical implementation — how the architecture is realized in silicon and circuits. It answers questions like:
- How fast does data travel between the CPU and RAM? (Bus speed / clock frequency)
- How many pipeline stages does the CPU have?
- What is the physical cache hierarchy?
- How are control signals timed?
Practical Analogy
Think of a restaurant. Architecture = the menu and the dining concept (what the restaurant offers, how it's organized for customers). Organization = the kitchen layout, the actual cooking equipment, and the workflow the chefs follow. Customers interact with the architecture. The kitchen staff operates within the organization.
IT Support Relevance
When you read a computer's specification sheet:
- "64-bit Intel Core i7, 3.4GHz" → Architecture details
- "DDR5 RAM, 4800MHz, dual-channel" → Organization details
Both matter when diagnosing compatibility issues (e.g., installing the wrong type of RAM).
2.3 The CPU and the Execution Cycle
The Central Processing Unit (CPU) is the most critical component in a computer. It is responsible for executing every instruction — from loading a webpage to running complex software.
CPU Internal Components (High Level)
| Component | Function |
|---|---|
| ALU (Arithmetic Logic Unit) | Performs mathematical calculations and logical comparisons |
| Control Unit (CU) | Directs operations — tells the CPU what to do and in what order |
| Registers | Tiny, extremely fast storage cells inside the CPU for immediate use |
| Cache (L1, L2, L3) | Fast memory built into or very close to the CPU to reduce delays |
| Clock | Generates regular pulses that synchronize all CPU operations (measured in GHz) |
The Fetch-Decode-Execute Cycle
Every single instruction a computer runs — from clicking a button to rendering a video — passes through the CPU execution cycle. This cycle repeats billions of times per second.
- Fetch — The Control Unit retrieves the next instruction from RAM (at the address pointed to by the Program Counter register).
- Decode — The instruction is translated from binary code into a signal the CPU understands.
- Execute — The ALU or another CPU component performs the operation (add, compare, move data, etc.).
- Store (Write Back) — The result is saved to a register or back to memory.
Clock Speed and Cores
- Clock speed (GHz) measures how many cycles per second the CPU can perform. A 3.0 GHz CPU completes 3 billion cycles per second.
- Cores are independent execution units within a single CPU chip. A quad-core CPU can execute 4 instruction streams simultaneously.
- Threads (with Hyper-Threading/SMT technology) allow a single core to manage 2 instruction streams at once.
💡 IT Support Note: A high CPU usage (e.g., consistently at 95–100%) often indicates a runaway process, insufficient cores for the workload, or malware — all diagnosable through Task Manager (Windows) or
top/htop(Linux).
2.4 Memory Systems
Memory in computing follows a hierarchy — the faster the memory, the more expensive and physically limited it is.
RAM (Random Access Memory)
RAM is the working memory of the computer — the space where the OS, active applications, and data in use are held while the computer is running.
Key characteristics:
- Volatile — all contents are lost when power is removed
- Speed — much faster than storage (SSDs or HDDs)
- Capacity — typically 8GB–64GB in consumer systems
- Type — modern systems use DDR4 or DDR5 RAM
🛠️ IT Support Scenario: A computer runs well with few applications open, but slows to a crawl when more are opened. This is a classic sign of RAM saturation — the system starts using the much-slower hard drive as virtual memory (paging/swapping).
Cache Memory
Cache is ultra-fast memory built directly into the CPU (or very close to it). It stores recently used or frequently needed data so the CPU doesn't have to wait for RAM.
- L1 cache — Smallest (~64KB), fastest, one per core
- L2 cache — Medium (~256KB–1MB), slightly slower, one per core
- L3 cache — Larger (~4MB–32MB), shared among all cores, slowest of the three
Storage — HDD vs SSD
| Feature | HDD (Hard Disk Drive) | SSD (Solid State Drive) |
|---|---|---|
| Technology | Spinning magnetic platters | Flash memory chips |
| Speed | ~100–150 MB/s (sequential) | ~500 MB/s – 7,000 MB/s |
| Durability | Vulnerable to physical shock | No moving parts — more durable |
| Cost | Cheaper per GB | More expensive per GB |
| Use case | High-capacity bulk storage | OS drive, performance-critical storage |
Virtual Memory
When RAM is full, the operating system uses a portion of the storage drive as virtual memory (called a pagefile in Windows or swap in Linux). This is significantly slower than real RAM and causes the system to slow down noticeably.
2.5 Input/Output Systems
Input/Output (I/O) systems manage how the computer communicates with the outside world — with users, peripherals, and other systems.
I/O Devices
- Input devices send data to the computer: keyboards, mice, scanners, microphones, cameras
- Output devices receive data from the computer: monitors, printers, speakers
- Bidirectional devices both send and receive: network cards, USB drives, touchscreens
How I/O Works — The Role of Buses and Controllers
Every peripheral device communicates with the CPU through a chain involving:
- Device (e.g., USB keyboard)
- Controller (hardware chip that manages device communication)
- Bus (electrical pathway: USB bus, PCIe bus, SATA bus)
- CPU / Memory (processes the incoming data)
Common Interfaces and Buses
| Interface | Common Uses | Notes |
|---|---|---|
| USB (2.0 / 3.x) | Keyboards, mice, flash drives, webcams | Universal; very common |
| PCIe | GPUs, NVMe SSDs, network cards | High-speed expansion slot |
| SATA | HDDs, SSDs, optical drives | Storage interface |
| HDMI / DisplayPort | Monitors, projectors | Video output |
| Ethernet (RJ-45) | Wired network connections | Via NIC |
| Bluetooth / Wi-Fi | Wireless peripherals, networking | Wireless I/O |
Device Drivers
A device driver is a piece of software that allows the operating system to communicate with a hardware device. Without the correct driver, hardware either doesn't work or works incorrectly.
🛠️ IT Support Scenario: A user plugs in a new printer and it isn't recognized. You check Device Manager and see a yellow exclamation mark — a missing or corrupted driver. Installing the correct manufacturer driver resolves the issue.
Interrupts
When a device needs the CPU's attention, it sends an interrupt request (IRQ) — a signal that tells the CPU to pause its current task and handle the device's request. This is how hardware events (keypresses, mouse movements, network packets) are handled efficiently.
2.6 System Interaction — How Everything Works Together
Now that we've covered each component individually, let's see how they interact as a unified system — using a familiar scenario: opening a web browser.
Step-by-Step: What Happens When You Open a Browser
User double-clicks browser icon
│
▼
[1] INPUT: Mouse sends click signal via USB → USB controller → CPU receives interrupt
│
▼
[2] CPU: Fetches and decodes the "open application" instruction from OS
│
▼
[3] STORAGE: OS reads browser program files from SSD/HDD
│
▼
[4] RAM: Browser program code is loaded into RAM for fast CPU access
│
▼
[5] CPU: Executes browser code, processes rendering instructions
│
▼
[6] GPU: Renders the visual interface (windows, text, images)
│
▼
[7] OUTPUT: GPU sends rendered frames to the monitor via HDMI/DisplayPort
│
▼
[8] NETWORK: Browser sends HTTP request via NIC → Internet → Receives web data
│
▼
[9] ALL SYSTEMS: Continue working in a coordinated loop as you browse
This entire process — from double-click to a fully rendered webpage — takes fractions of a second, but involves every major hardware subsystem working in coordination.
The Role of the Operating System
The Operating System (OS) is the critical software layer that manages all hardware resources:
- Allocates RAM to running programs
- Schedules CPU time across multiple processes
- Manages I/O device communication
- Handles file storage and retrieval
- Provides a user interface
Common examples: Windows 11, macOS, Ubuntu Linux
💡 Without an OS, hardware has no coordination — it would be like having all the instruments of an orchestra but no conductor.
3. IT Support Perspective
This section connects each hardware concept to the real challenges IT Support professionals face daily.
3.1 CPU — Troubleshooting and Diagnostics
Common CPU-related IT issues:
| Symptom | Possible Cause | Diagnostic Approach |
|---|---|---|
| System very slow | High CPU usage, insufficient cores | Check Task Manager / top for CPU % per process |
| System overheating & shutting down | Thermal paste dried out, cooling fan failure | Check CPU temperatures (HWMonitor, CoreTemp) |
| Computer won't boot, no POST | CPU improperly seated, dead CPU | Check CPU socket, listen for POST beep codes |
| Sudden crashes / BSODs | CPU instability, overclocking issues | Review Event Viewer logs; check for overclocking settings in BIOS |
Practical note: In Help Desk work, CPU issues are often caused by software (a rogue process consuming 100% CPU) rather than hardware failure itself. Always check software first.
3.2 RAM — Performance and Failure Diagnostics
Common RAM-related IT issues:
| Symptom | Possible Cause | Diagnostic Approach |
|---|---|---|
| Constant slowness, heavy disk activity | Insufficient RAM (paging) | Check RAM usage in Task Manager; check pagefile activity |
| Random BSODs (Blue Screen of Death) | Faulty RAM module | Run Windows Memory Diagnostic or MemTest86 |
| System won't POST / continuous beeps | RAM not seated correctly | Reseat RAM modules; test one stick at a time |
| "Your computer is low on memory" warnings | Too many programs open / RAM leak | Close applications; check for memory leaks in dev tools |
Practical note: RAM is one of the easiest and cheapest upgrades to recommend to users with slow computers. Upgrading from 4GB to 16GB can dramatically improve everyday performance.
3.3 Storage — Performance, Failure, and Data Loss
Common storage-related IT issues:
| Symptom | Possible Cause | Diagnostic Approach |
|---|---|---|
| Very slow file access, long boot times | Failing HDD, heavily fragmented disk | Run CHKDSK (Windows), check S.M.A.R.T. data (CrystalDiskInfo) |
| Files disappearing or corrupt | HDD failing, filesystem errors | Backup immediately; run filesystem check |
| System won't boot — "No bootable device" | Boot drive not detected, corrupted MBR/GPT | Check BIOS boot order; run bootrec /fixmbr in recovery |
| Clicking sounds from the computer | Mechanical HDD head failure | Critical: backup immediately — drive is failing |
Practical note: A clicking HDD is a hardware emergency. Data recovery becomes exponentially harder (and more expensive) with each passing minute the drive continues to be used.
3.4 Motherboard — The Hardest Diagnosis
Motherboard failures are among the most difficult to diagnose because the board connects everything — a failed motherboard can mimic the symptoms of almost any other component failure.
Common indicators of motherboard failure:
- System won't POST at all, no beep codes
- USB ports, audio ports, or LAN suddenly stop working
- System powers on for 1–2 seconds then shuts off
- Visible damage: burnt capacitors, burn marks, swollen capacitors
Diagnostic approach:
- Test with known-working RAM and CPU
- Clear CMOS (reset BIOS settings)
- Inspect visually for physical damage
- If all components test individually but system still fails → suspect motherboard
3.5 I/O Devices — Common Help Desk Tickets
I/O problems are among the most common Help Desk tickets. Most are solved quickly with the right methodology.
Common I/O issues and solutions:
| Issue | First Steps | If That Fails |
|---|---|---|
| USB device not recognized | Try different USB port; try device on different PC | Check Device Manager; update/reinstall drivers |
| Monitor has no signal | Check cable connections (HDMI/DP); try different cable | Test with different monitor; check GPU seating |
| Keyboard/mouse not working | Try different USB port; try wireless receiver reset | Test on another PC; suspect hardware failure |
| Printer not printing | Check connection; restart print spooler service | Reinstall driver; check IP address (network printers) |
| No audio | Check volume; check audio output device setting | Update audio driver; check physical headphone jack |
3.6 System-Level Thinking in IT Support
One of the most important skills in IT Support is thinking at the system level — understanding that a symptom rarely has only one possible cause.
Example: A computer that randomly freezes and reboots could be caused by:
- CPU overheating (thermal issue)
- Faulty RAM (memory error)
- Failing PSU (power delivery issue)
- Corrupted OS files (software issue)
- Malware (security issue)
A skilled IT Support professional rules out causes systematically:
- Check the simplest/cheapest causes first (settings, software, drivers)
- Use diagnostic tools before replacing hardware
- Change one variable at a time
- Document findings as you go
This is called the CompTIA troubleshooting methodology and it applies directly to everything covered in this module.
4. Learning Questions
The following questions are designed to test your understanding progressively — from basic recall to applied thinking.
Foundational (Basic Recall)
-
Define computer hardware in your own words. Give three examples of internal hardware components and two examples of external (peripheral) hardware.
-
What are the four fundamental functions every computer performs? Provide a real-life example of each.
-
What does CPU stand for, and what is its primary role in a computer system?
-
Explain the difference between RAM and storage (HDD/SSD). Why does a computer need both?
-
What is a motherboard, and why is it considered the central component of a computer system?
Conceptual Understanding
-
In your own words, explain the difference between computer architecture and computer organization. Use the restaurant analogy (or one of your own) to illustrate the distinction.
-
Describe the Fetch-Decode-Execute cycle. What happens at each stage? Why does this cycle matter for understanding CPU performance?
-
Explain the memory hierarchy. Why is there a need for multiple levels of memory (registers, cache, RAM, storage) rather than just one type?
-
What is virtual memory, and when does a computer system use it? What effect does virtual memory usage have on performance?
-
What is a device driver, and what role does it play in allowing hardware to function correctly?
Applied / IT Support Thinking
-
A user reports that their computer is very slow when multiple applications are open, but runs fine with only one or two. Which hardware component is most likely the bottleneck? What would you check first?
-
A technician hears a repetitive clicking sound from a computer's case. What component is most likely responsible, and what is the correct immediate course of action?
-
A computer powers on (fans spin, LEDs light up) but the monitor shows no image and no operating system loads. List at least three possible causes and explain how you would begin diagnosing this.
-
Explain the relationship between clock speed and number of cores in a CPU. Is a higher GHz always better? Give an example of a scenario where more cores matters more than higher clock speed.
-
A user plugs in a USB device and nothing happens — the device is not recognized. Walk through a systematic troubleshooting process (at least 4 steps) you would follow to diagnose this issue.
5. Practical Activities
These activities simulate real IT Support scenarios. For each one, read the scenario carefully, think through your diagnosis, and write out your reasoning step by step. Suggested solution approaches are provided — but try to work through your own thinking before reading them.
Activity 1: The Mysteriously Slow Computer 🐌
Scenario: A user calls the Help Desk complaining that their computer has been "really slow" for the past week. It takes several minutes to boot up, applications take a long time to open, and the hard drive activity light is constantly blinking. They have not installed any new software recently.
Your Task:
- What components or issues could be causing this?
- What diagnostic tools would you use?
- What is your step-by-step troubleshooting approach?
Suggested Approach (read after your own attempt):
Consider: RAM saturation, storage failure (check S.M.A.R.T.), malware, too many startup programs. Use Task Manager (CPU/RAM/Disk tabs), CrystalDiskInfo for drive health, and Windows Defender for a malware scan. Constant disk activity combined with slowness strongly suggests either a failing HDD or RAM overflow triggering paging.
Activity 2: The Computer That Won't Boot 💀
Scenario: You receive a ticket: "My computer won't turn on." When you arrive, you observe that the computer does power on (fans spin, power LED is lit), but there is no display on the monitor, no operating system loads, and you hear three short beeps from the case speaker.
Your Task:
- What does the beep pattern tell you?
- What components should you investigate first?
- Describe your diagnostic steps.
Suggested Approach:
Beep codes vary by BIOS manufacturer — three short beeps often indicate a RAM error in common BIOS versions (AMI, Phoenix). Start by reseating RAM modules (power off, remove, reinsert firmly). Test one stick at a time if multiple sticks are installed. Also verify the monitor cable and try a different monitor to rule out display issues.
Activity 3: RAM or Storage? 🤔
Scenario: Two different users on the same Help Desk queue both report "slow computers."
- User A: "It's slow all the time, even right after startup, before I open anything."
- User B: "It's fine when I first start it, but gets slower and slower as I open more programs."
Your Task:
- Based on their descriptions, which type of issue is each user likely experiencing?
- Which component would you investigate first for each user?
- What diagnostics would you run?
Suggested Approach:
User A is slow from the start — before RAM saturation can occur. This points to a storage issue (slow/failing HDD, corrupted OS), or possibly malware loading at startup. User B is fine initially but degrades — this is a classic RAM saturation pattern. Check Task Manager (Disk tab) for User A; check Task Manager (Memory tab) for User B.
Activity 4: The USB Device That Disappeared 🔌
Scenario: A user's USB mouse suddenly stopped working mid-session. They haven't changed anything. The mouse's LED doesn't light up when connected. They've tried restarting the computer — still nothing.
Your Task:
- List all possible causes (hardware and software).
- Design a step-by-step troubleshooting workflow.
- At what point would you conclude it's a hardware failure?
Suggested Approach:
Step 1: Try the mouse in a different USB port. Step 2: Try the mouse on a completely different computer. Step 3: Try a different known-working mouse in the original port. Step 4: Check Device Manager for errors on the USB controller. Step 5: Check for Windows updates or driver updates. If the mouse works on another PC but no mouse works on the original port → suspect USB controller/motherboard issue. If the mouse works on no PC → suspect dead mouse.
Activity 5: Overheating and Mystery Shutdowns 🔥
Scenario: A user reports that their desktop computer randomly shuts off without warning, usually after about 30–45 minutes of use. After it shuts off, it won't turn back on for several minutes. There are no error messages — the computer just goes black and powers off.
Your Task:
- What is the most likely cause of this behavior?
- What hardware components could be responsible?
- How would you investigate and resolve it?
Suggested Approach:
The pattern (works for a while, shuts off, won't restart immediately, then works again after cooling) is a textbook thermal shutdown — a safety feature CPUs and motherboards use to prevent permanent damage. Investigate: 1) Use HWMonitor to check CPU/GPU temperatures. 2) Open the case and inspect fans — are they spinning? Are they clogged with dust? 3) Check that the CPU cooler is properly seated and that thermal paste hasn't dried out. 4) Consider the PSU — intermittent PSU failures can also cause sudden shutoffs (PSU testers are cheap and useful).
Activity 6: The Boot Order Problem 📀
Scenario: A technician reinstalled Windows on a user's desktop. After the installation appears to complete successfully, the computer reboots — but instead of loading Windows, it goes back to the Windows installation screen and starts the setup process from scratch, as if the installation never happened.
Your Task:
- What is causing this behavior?
- Where (in what tool/interface) would you fix this?
- What exactly would you change?
Suggested Approach:
This is a classic boot order issue in the BIOS/UEFI. The installer USB/DVD is still first in the boot order, so the computer boots from it instead of the newly installed Windows drive. Fix: Enter BIOS/UEFI setup (usually by pressing F2, F10, F12, or DEL during startup), navigate to Boot settings, and move the internal SSD/HDD to the top of the boot priority list. Alternatively, remove the USB/DVD before rebooting. Save and exit BIOS.
Activity 7: The Performance Upgrade Decision 📊
Scenario: A small business owner asks for your advice. They have a 5-year-old desktop PC used for office work (email, spreadsheets, web browsing, video calls). The machine has a decent CPU (Intel Core i5, 6th gen), but only 4GB of RAM and an old spinning HDD. The owner has a budget of approximately $100–150 USD. What upgrade(s) would you recommend and why?
Your Task:
- Analyze the likely performance bottlenecks given the hardware profile.
- Recommend specific upgrades within the budget.
- Justify your recommendation using what you've learned in this module.
Suggested Approach:
The CPU is adequate for the workload. The biggest bottlenecks are almost certainly: 1) 4GB RAM — insufficient for modern multitasking (Windows 10/11 + browser + video call easily consumes 4–6GB). 2) HDD — dramatically slower than an SSD for OS boot and application loading. Recommended upgrades: 8–16GB DDR4 RAM (
$25–40) + a 240–500GB SSD ($40–60). These two upgrades together typically cost under $100 and will make a 5-year-old machine feel dramatically faster — often more impactful than buying a new PC.
📎 Module Summary
| Concept | Key Takeaway |
|---|---|
| Computer Hardware | Physical components: CPU, RAM, storage, motherboard, I/O devices |
| Computer Architecture | The design and logical organization of a computing system |
| Computer Organization | The physical implementation of architectural design |
| CPU | Executes instructions via the Fetch-Decode-Execute cycle |
| Memory Hierarchy | Registers → Cache → RAM → Storage (fast & small → slow & large) |
| I/O Systems | Devices, controllers, buses, and drivers enable external communication |
| System Interaction | All components work in coordination, managed by the OS |
| IT Support Link | Every hardware concept maps directly to real-world troubleshooting scenarios |