Causes of common problems - Learn Tech From Zero

4.4 Given a scenario, troubleshoot common OS and software problems.

What it is: Drivers are software that allow the operating system to communicate with hardware (like network cards, storage drives, or printers). Modules are software components that add functionality to the OS.
Problem: If a driver is made for a different OS version or hardware, the OS might crash, freeze, or fail to detect the device.
Example: Installing a network card driver designed for Windows Server 2016 on Windows Server 2019 may prevent the server from connecting to the network.

Exam tip: Always check OS version and hardware compatibility before installing drivers.

What it is: Patches are updates released by software vendors to fix bugs or security issues.
Problem: If a patch is installed incorrectly, it can make the system unstable or break applications.
Example: Applying a patch for a database server without following the vendor instructions may stop the database service from starting.

What it is: Some drivers or applications are poorly written or not tested thoroughly.
Problem: They can cause system crashes, memory errors, or unexpected reboots.
Example: A beta version of a printer driver could cause the print spooler service to crash repeatedly.

What it is: In enterprise networks, servers often join a domain for centralized management and security.
Problem: If a server isn’t joined, users may not authenticate, and policies may not apply correctly.
Example: A file server not joined to the domain might reject login requests from domain users.

What it is: Clock skew occurs when the server’s system time is significantly different from other servers or network devices.
Problem: Time-sensitive services (like authentication, logging, or scheduled tasks) may fail.
Example: Active Directory authentication fails if the server’s time is off by more than 5 minutes from the domain controller.

What it is: Memory leaks happen when software consumes RAM but doesn’t release it after use.
Problem: Over time, this reduces available memory, slowing down the server or causing crashes.
Example: A monitoring application slowly consumes memory over days, eventually making the server unresponsive.

What it is: This occurs when a program writes more data into memory than it should.
Problem: Can cause application crashes or allow attackers to execute malicious code.
Example: A poorly coded web service crashes when it receives more data than expected from a client.

This is a broad category where software or dependencies don’t work well together. It includes:

Using old or unpatched libraries or software modules can introduce vulnerabilities or instability.
Example: An outdated encryption library in a server application could prevent secure connections.

Mismatched software versions may not work together.
Example: Running a backup tool version 2.1 with a database version 3.0 that requires 2.5.

Problem: Updates may fail to install due to connectivity issues, missing prerequisites, or conflicts.
Result: Security vulnerabilities remain, or software may continue to malfunction.
Example: A failed Windows Server update leaves critical services unable to start.

Problem: Missing updates can leave software with bugs or vulnerabilities that affect stability.
Example: Not installing database server security patches could lead to failed connections or data corruption.

What it is: Some software needs other components to run (like libraries, frameworks, or services).
Problem: If these dependencies are missing, the application may not start.
Example: A web application fails because the required version of .NET Framework is not installed.

Problem: Sometimes an update for one system component can break other components that rely on it.
Example: Updating the OS network stack may cause older monitoring tools to stop working.

What it is: Applications need correct permissions to access files, network resources, or system settings.
Problem: Wrong permissions can cause errors or crashes.
Example: A backup application cannot write to a network share because it lacks write permissions.

CPU Affinity: Determines which CPU cores a process can use.
CPU Priority: Determines how much CPU time a process receives.
Problem: Setting these incorrectly can starve critical processes or overload others.
Example: Assigning all cores to a non-critical process may slow down the main database server.

Always check software and driver compatibility before installation.
Apply patches and updates carefully, ensuring prerequisites are met.
Monitor memory and CPU usage to detect leaks or improper affinity.
Verify server domain membership and system time synchronization.
Ensure all dependencies are present, and permissions are correctly configured.
Understand that updates can sometimes break dependent software.