Hardware and Software Maintenance

# Hardware and Software Maintenance ## Objectifs et prérequis This chapter aims to equip Lower Sixth ICT students with the knowledge and practical skills to identify, diagnose, and correct common hardware and software faults in computer systems. Students will learn systematic troubleshooting methodologies, understand the causes and consequences of system failures, and apply corrective actions using appropriate tools and procedures. Emphasis is placed on real-world contexts relevant to Cameroon and sub-Saharan Africa, including environmental challenges, resource constraints, and common technology deployments in schools, small businesses, and government offices. Prerequisites: Students must have completed foundational ICT topics including computer system components (CPU, memory, storage, I/O devices), operating systems (Windows, Linux basics), basic networking concepts, and familiarity with common application software. Proficiency in using diagnostic tools (e.g., Device Manager, Task Manager, Command Prompt) and basic safety procedures (anti-static handling, power safety) is assumed. --- ## I. Hardware Faults Identification and Correction ### Context Hardware faults refer to physical malfunctions or failures in computer components that disrupt system operation. In Cameroonian and African contexts, hardware faults are frequently exacerbated by environmental factors such as dust, high humidity, unstable power supply (frequent outages and voltage spikes), and limited access to quality spare parts or technical support. Schools and small enterprises often rely on older or donated equipment, increasing susceptibility to wear and tear. Understanding hardware faults enables timely intervention, reduces downtime, and extends equipment lifespan—critical in resource-constrained settings. ### Definitions > A hardware fault is any physical defect or failure in a computer component that prevents the system from functioning correctly or at all. > POST (Power-On Self-Test) is a diagnostic sequence run by the BIOS/UEFI firmware immediately after power-on to verify essential hardware components (CPU, RAM, keyboard, etc.) are operational. > Beep codes are sequences of audible tones emitted by the motherboard speaker during POST to indicate specific hardware errors when video output is unavailable. ### Causes and Consequences Common causes of hardware faults include: - **Physical damage**: Dropping, liquid spills, or improper handling (common in mobile labs or shared school computers). - **Environmental factors**: Dust accumulation clogging fans and heat sinks (worsened in dry, sandy regions like the Far North); humidity causing corrosion on contacts (prevalent in coastal and southern zones). - **Power issues**: Voltage surges from unstable grid supply or lightning strikes damaging PSUs, motherboards, or peripherals (frequent during rainy season). - **Component degradation**: Electrolytic capacitor aging on motherboards or PSUs; hard drive mechanical wear; RAM module oxidation. - **Incorrect installation**: Misaligned RAM, loose cables, or improper CPU seating during upgrades or repairs. Consequences range from minor (slow performance, intermittent errors) to severe (system failure to boot, data loss, permanent hardware damage). In educational settings, hardware faults disrupt teaching schedules; in healthcare or administrative systems, they can compromise service delivery. ### Examples Concrets (Camerounais/Africains) - A secondary school in Yaoundé experiences frequent boot failures during harmattan season due to dust-clogged CPU fans causing overheating and thermal shutdown. - A small business in Douala loses data after a power surge destroys the PSU and motherboard during a thunderstorm; no surge protector was in use. - In a rural health center in the East Region, a donated computer fails to recognize USB drives due to corroded front-panel ports from high humidity. - A university lab in Buea encounters random system crashes traced to faulty RAM modules, identified via beep codes (one long, two short) indicating memory failure during POST. ### Vocabulary à Retenir - POST (Power-On Self-Test) - Beep codes - PSU (Power Supply Unit) - Thermal throttling - Corrosion - Surge protector - UPS (Uninterruptible Power Supply) - BIOS/UEFI - CMOS battery - Loopback plug ### Exemple de Sujet Type Examen avec Plan **Sujet**: A computer lab in a Bamenda secondary school reports that several desktop computers fail to boot after the rainy season. Upon inspection, technicians observe that the systems power on (fans spin) but display no video output and emit a repeating pattern of one long beep followed by two short beeps. Explain the likely hardware fault, identify the component involved, describe the diagnostic process used, and recommend two corrective actions suitable for the local context. **Plan attendu**: 1. **Identification of fault**: The beep code (1 long, 2 short) indicates a video/graphics card failure (common AMI BIOS beep code). 2. **Component involved**: Graphics card (either integrated or discrete GPU) or its connection to the motherboard/monitor. 3. **Diagnostic process**: - Listen to beep codes during POST. - Refer to motherboard manual or BIOS beep code chart. - Test with known-good graphics card or monitor. - Check video cable and monitor functionality. - Reseat graphics card (if discrete) or reset CMOS. 4. **Corrective actions**: - Clean and reseat the graphics card or RAM (if integrated graphics suspected). - Replace CMOS battery to reset BIOS settings (common failure after prolonged power loss). - If discrete GPU, test with another card or use integrated graphics; replace faulty card if available. - Install surge protector and consider UPS for future protection against power instability. --- ## II. Software Faults Identification and Correction ### Context Software faults encompass errors, bugs, or misconfigurations in operating systems, applications, or firmware that lead to abnormal system behavior, crashes, or security vulnerabilities. In Cameroonian and African ICT environments, software faults are often compounded by software piracy (leading to lack of updates/patches), use of outdated or unsupported operating systems (e.g., Windows XP in some schools), limited internet bandwidth hindering updates, and low digital literacy among users. Malware infections are particularly prevalent due to shared USB drives, pirated software, and inadequate antivirus coverage. Effective software fault management ensures system stability, security, and usability—vital for educational continuity and administrative efficiency. ### Definitions > A software fault is an error, flaw, or failure in a software program that causes it to produce incorrect or unexpected results, or to behave in unintended ways. > Safe Mode is a diagnostic startup mode in Windows that loads only essential drivers and services, used to troubleshoot software-related issues preventing normal boot. > System Restore is a Windows feature that reverts system files and settings to a previous restore point, undoing recent software changes without affecting personal files. ### Causes and Consequences Common causes of software faults include: - **Software bugs**: Coding errors in applications or OS updates (e.g., a patch causing driver conflicts). - **Malware infection**: Viruses, ransomware, or spyware introduced via email attachments, malicious websites, or infected USB drives (widespread in shared computing environments). - **Corrupted system files**: Due to improper shutdowns, disk errors, or failed updates. - **Driver incompatibility**: Outdated, incorrect, or conflicting device drivers (especially after hardware changes). - **Registry errors**: Invalid entries in the Windows Registry from incomplete uninstalls or malware. - **Resource exhaustion**: Memory leaks or excessive CPU usage from poorly optimized applications. - **Misconfiguration**: Incorrect network settings, user permissions, or service configurations. Consequences range from application crashes and slow performance to complete system unusability, data loss, or security breaches. In schools, software faults can render computer labs unusable for weeks; in government offices, they may disrupt payroll or record-keeping systems. Malware can lead to data theft or financial loss, particularly damaging for small enterprises. ### Examples Concrets (Camerounais/Africains) - A teacher in Garoua attempts to print a lesson plan but the printer spooler service keeps crashing; investigation reveals a corrupted printer driver from a recent Windows update. - A cybercafé in Bafoussam suffers a ransomware attack after a user opens an email attachment labeled “Invoice.pdf.exe”; files are encrypted, demanding payment in cryptocurrency—no recent backups exist. - In a Yaoundé administrative office, multiple computers experience frequent blue screens (BSOD) traced to a conflicting third-party antivirus software incompatible with the latest Windows update. - A student in Kumbi uses a pirated version of Windows 7 that fails to activate and receives no security updates, leading to a botnet infection used for DDoS attacks. - A primary school in Maroua reports computers slowing down over time; diagnosis shows excessive startup programs and temporary file accumulation due to lack of regular maintenance. ### Vocabulary à Retenir - Safe Mode - System Restore - BSOD (Blue Screen of Death) - Driver - Malware - Antivirus - Patch - Startup Programs - Disk Cleanup - Event Viewer - SFC (System File Checker) - DISM (Deployment Image Servicing and Management) ### Exemple de Sujet Type Examen avec Plan **Sujet**: A computer in a Ngaoundéré university department fails to start normally, freezing at the Windows logo. After three attempts, it automatically boots into Safe Mode. The user reports that the issue began after installing a new graphics design software. Explain the likely software fault, describe the steps to diagnose it using Safe Mode and system tools, and outline a corrective procedure that preserves user data. **Plan attendu**: 1. **Identification of fault**: The ability to boot into Safe Mode but not normal mode suggests a software conflict—likely a faulty or incompatible driver or service introduced by the new software. 2. **Diagnostic process**: - Boot into Safe Mode. - Use **Event Viewer** (Windows Logs > System) to check for critical errors around boot time. - Use **msconfig** or **Task Manager > Startup** to disable non-essential startup items and services. - Use **Device Manager** to check for warning signs (yellow exclamation) on display adapters. - Temporarily disable recently installed software or roll back its driver. - Run **sfc /scannow** in Command Prompt (admin) to check for corrupted system files. - Run **DISM /Online /Cleanup-Image /RestoreHealth** if SFC fails. 3. **Corrective actions**: - Uninstall the recently installed graphics software via Control Panel. - Roll back the graphics driver to the previous version (Device Manager > Display Adapter > Properties > Driver > Roll Back Driver). - If unresolved, use **System Restore** to revert to a point before the software installation. - After fix, restart normally and monitor for recurrence. - Advise user to create a restore point before installing new software and to use only licensed, compatible applications. --- ## Synthèse du chapitre - Hardware faults stem from physical damage, environmental stressors (dust, humidity, power instability), and component wear; identified via POST, beep codes, diagnostic tools, and physical inspection. - Software faults arise from bugs, malware, corrupted files, driver conflicts, and misconfigurations; diagnosed using Safe Mode, Event Viewer, System Restore, SFC, and DISM. - Effective troubleshooting follows a structured approach: observe symptoms, gather information, hypothesize causes, test solutions, and verify resolution. - Prevention is critical: use surge protectors/UPS, maintain clean environments, perform regular software updates, back up data, and avoid pirated software. - In Cameroonian and African contexts, solutions must prioritize affordability, accessibility, and sustainability—leveraging community knowledge, open-source tools, and low-cost interventions. - Both hardware and software maintenance require documentation, user training, and adherence to safety procedures to ensure long-term system reliability. --- ## Glossaire - **POST (Power-On Self-Test)**: Firmware diagnostic routine executed at startup to verify core hardware functionality. - **Beep codes**: Audio signals from the motherboard indicating specific hardware errors during POST when video is unavailable. - **PSU (Power Supply Unit)**: Component converting AC mains power to DC voltages for internal computer parts; vulnerable to surges and aging. - **Thermal throttling**: Automatic reduction of CPU/GPU speed to prevent overheating due to inadequate cooling. - **Corrosion**: Degradation of metal contacts caused by moisture and pollutants, common in humid climates. - **Surge protector**: Device that diverts excess voltage to protect equipment from power spikes. - **UPS (Uninterruptible Power Supply)**: Battery-backed power supply providing temporary power during outages and surge protection. - **BIOS/UEFI**: Firmware initializing hardware during boot and providing runtime services for the operating system. - **CMOS battery**: Small