Chapter 4: System Configuration & Hardware Troubleshooting
BIOS/UEFI Setup, Power Issues, and System Diagnostics
Video Content Prompts
- Demonstrate BIOS/UEFI setup and configuration options
- Show boot device priority and boot troubleshooting
- Explain power supply testing and power issue diagnosis
- Cover POST errors, beep codes, and hardware diagnostics
- Troubleshoot display issues, overheating, and system performance
4.1 BIOS and UEFI
4.1.1 BIOS and UEFI
Firmware is special program code stored in flash memory, closely tied to the basic functions of specific hardware. Computer firmware helps initialize components on the motherboard so they can load the main operating system.
For many years, computers used basic input/output system (BIOS) firmware. Most motherboards now use unified extensible firmware interface (UEFI) instead. UEFI supports 64-bit CPU operation, has a graphical user interface (GUI) with mouse support, offers networking at boot, and provides better boot security. A computer with UEFI can also boot in legacy BIOS mode.
You can configure system settings through the firmware setup program, accessed by pressing a key during the boot process, usually when the computer vendor's logo appears. Common keys include Esc, Del, F1, F2, F10, or F12.
In a legacy BIOS setup program, you navigate using the keyboard arrow keys. Pressing Esc generally returns to the previous screen. When closing setup, you can choose to exit and discard changes or exit and save changes. UEFI setup programs use a graphical interface and have mouse support, though some advanced menus may still require keyboard navigation.
4.1.2 Boot and Device Options
One key system setup parameter is the boot option sequence or boot device priority, which determines the order in which the system firmware searches devices for a boot manager.
Typical choices include:
- Fixed disk (Hard Disk Drive or Solid State Drive): For drives connected via SATA, it's recommended to connect the boot disk to the lowest-numbered port. In modern systems, SSDs using NVMe via the M.2 or PCIe interface are often used as boot drives, offering faster speeds than SATA SSDs.
- Optical drive (CD/DVD/Blu-ray): If performing a repair or installation from optical media, you may need to set the optical drive as the highest priority.
- Universal Serial Bus: Most modern systems can boot from a USB drive formatted as a boot device. USB booting is commonly used for operating system installations and recovery utilities.
- Network/PXE (Preboot Execution Environment): Boots via the network adapter by retrieving boot instructions from a configured server.
4.1.3 USB Permissions
System firmware allows you to enable or disable controllers and adapters, including USB ports. Since USB connections can pose security risks, the firmware setup program may let you control USB permission by enabling or disabling individual or all USB ports.
4.1.4 Fan Considerations
Proper maintenance and configuration of cooling fans are crucial for optimal system performance and longevity. Regularly clean fans to prevent dust accumulation, which can obstruct airflow and lead to overheating, potentially damaging components.
Most cooling fans can be controlled through system settings, typically found under menus like Cooling, Power, or Advanced. Options usually include:
- Balanced: A standard setting for general use
- Cool: Runs fans at higher speeds for maximum cooling
- Quiet: Reduces fan speed, allowing for higher temperatures
- Fanless: Disables fans, relying on passive cooling
- Custom: Allows for personalized fan speed settings
Temperature Monitoring
There are two ways to monitor a computer's temperature:
- Manual Monitoring: Restart your computer and enter the BIOS/UEFI settings during boot to view real-time readings, including CPU temperature.
- Third-Party Applications: These applications monitor computer temperatures through sensors that collect data and trigger alerts when temperatures exceed safe limits.
4.1.5 Boot Passwords and Secure Boot
A boot password requires user authentication before the operating system loads. Different systems support various authentication methods, with typically two main passwords available:
- Supervisor/Administrator/Setup/BIOS Password: Restricts access to the system's BIOS/UEFI setup program
- User/System Password: Locks the entire system until authentication is provided
Secure boot is a UEFI feature that protects against malware by ensuring only trusted, digitally signed bootloaders are used. The system firmware checks the operating system's bootloader against pre-loaded cryptographic keys to verify its integrity.
4.1.7 Trusted Platform Modules
Encryption protects secure data by scrambling it in such a way that it can only be decrypted using the correct decryption key. UEFI-based systems provide secure storage for these keys, often using hardware-based solutions like the Trusted Platform Module (TPM).
A trusted platform module (TPM) is hardware that securely stores digital certificates, cryptographic keys, and hashed passwords. Each TPM chip has a unique, unchangeable endorsement key, establishing a root of trust. During boot, the TPM compares hashes of key system data to ensure they haven't been tampered with.
The TPM provides superior security by storing cryptographic keys in tamper-resistant hardware, isolating them from the OS and applications. The TPM's secure storage area can be used by disk encryption programs like Windows BitLocker to store their keys.
Hardware Security Module
A removable USB thumb drive can be used to store cryptographic keys. This is useful if the computer does not support TPM, as a recovery mechanism if the TPM is damaged, or if a disk needs to be moved to another computer. A secure USB key used to store cryptographic material is referred to as a hardware security module (HSM).
4.2 Power and Disk Issues
4.2.1 Troubleshoot Power Issues
Computer components need a constant, stable supply of power to run. If the computer won't start, it is likely due to a power problem. When a computer is switched on, the power supply unit (PSU) converts AC input voltage to DC voltage, which powers the motherboard components and peripheral devices.
To diagnose no power symptoms, check if the LEDs on the front panel are lit and if you can hear the fans. To isolate the cause of no power, try the following tests:
- Check other equipment: Ensure other devices in the area are working to rule out a power circuit fault
- Test the wall socket: Plug a known-good device into the wall socket
- Verify PSU connections: Ensure the PSU is properly connected and all switches are "on"
- Try another power cable: Check the plug's wiring and fuse with a multimeter
- Disconnect extra devices: Remove devices like plug-in graphics cards
- Test the PSU: Use a multimeter or power supply tester to check the PSU
4.2.2 Troubleshoot POST Issues
Once the CPU has been given the power good signal, the system firmware performs a power-on self-test (POST). The POST is a diagnostic program that checks the hardware components required to boot the computer.
If power is present but the computer does not start, try the following:
- Ask what has changed—system firmware updates may have failed
- Use the reset procedure
- Check cabling and connections—ensure all cables and adapter cards are correctly seated
- Check for faulty interfaces and devices—remove devices one at a time
- Check the PSU—there may be a fault preventing the power good signal
- Check for a faulty CPU or system firmware
Common POST Beep Codes
| Code | Meaning |
|---|---|
| 1 short beep | Normal POST - system is OK |
| 2 short beeps | POST error - error code shown on screen |
| No beep | Power supply, motherboard, or speaker problem |
| Continuous beep | System memory modules or memory controller problem |
| Repeating short beeps | Power supply fault or motherboard problem |
| 1 long, 1 short beep | Motherboard problem |
| 1 long, 2-3 short beeps | Video adapter error |
| 3 long beeps | Keyboard issue |
4.2.3 Troubleshoot Boot Issues
After completing the POST, the system searches for boot devices in the order specified in the boot sequence. If no bootable device is found, an error message is displayed.
If a fixed disk is not detected:
- Power Check: Ensure the drive is powered and look for activity LEDs
- Data Connections: Inspect data cables for damage and proper connection
- UEFI/BIOS Settings: Confirm the drive is enabled and settings are correct
- M.2/NVMe Drives: Ensure they are properly seated and detected
4.2.4 Troubleshoot Boot Sector Issues
If power and cabling issues are ruled out, suspect a problem with the device's boot sector and files. Corruption can occur due to disk faults, power failures, incorrect installation of multiple operating systems, or malware.
Boot Information Formatting: MBR and GPT
- Master Boot Record (MBR): Located in the first sector of the partitioned disk, holds partition information and boot code
- GUID Partition Table (GPT): Provides more robust and flexible partitioning compared to MBR
Damage to MBR or GPT can cause boot errors like "Boot device not found," "OS not found," or "Invalid drive specification."
Troubleshooting steps include:
- Check display connections
- Inspect boot errors
- Use antivirus boot disk if malware is suspected
- Utilize OS setup disk repair options
4.2.5 Troubleshoot OS Errors and Crash Screens
Common symptoms of errors after the boot device is found are usually due to software or device driver issues rather than hardware problems.
One of the most common symptoms in Windows is the Blue Screen of Death (BSOD). This crash screen indicates issues such as:
- System memory faults
- Hardware device or driver problems
- OS file corruption
- Overheating or power supply issues
To troubleshoot a BSOD:
- Use a camera to scan the QR code displayed on the screen
- Check the System log for "BugCheck" events
- Use the first hex value to search for more information online
4.2.6 Troubleshoot Drive Availability
Hard disk drives (HDDs) are more prone to mechanical failure, while solid-state drives (SSDs) are generally more reliable but have limited lifespan due to memory cell wear.
Common drive failure symptoms include:
- Unusual noise (HDD): Loud grinding, clicking, or scraping sounds indicate mechanical failure
- No LED status/activity: May indicate power or system issues
- Constant LED activity (Disk Thrashing): Could indicate insufficient RAM or faulty processes
- Bootable device not found: May point to file corruption or faulty drive
- Missing drives in OS: Check if drive has been initialized, partitioned, and formatted
- Read/Write failure: Signs of bad sectors on HDDs or bad blocks on SSDs
- Audible alarms: Enterprise-level drives may have alarms for drive failure
- Blue screen of death: Severe drive issues can cause system crashes
4.2.7 Troubleshoot Drive Reliability and Performance
Most fixed disks have a self-diagnostic program called Self-Monitoring Analysis and Reporting Technology (S.M.A.R.T.). S.M.A.R.T can alert the operating system if a failure is detected.
If you suspect a drive is failing or experience performance issues, run advanced diagnostic tests. Most disk vendors provide utilities for testing drives, and you can also use Windows utilities to query SMART and run manual tests.
Performance issues may be due to:
- Application load and general system resource issues
- File fragmentation (on HDDs)
- Limited remaining capacity
- Failing sectors (HDDs) or blocks (SSDs)
4.2.8 Troubleshoot RAID Failure
Redundant Array of Independent Disks (RAID) is configured to protect data against the failure of a single disk. There are two main scenarios for RAID failure:
- Device Failure: If one device fails, the volume will be "degraded" but data remains accessible
- Array Failure: Most desktop RAID solutions can tolerate only one disk loss
Troubleshooting steps:
- Unavailable Volume: Either more disks have failed than the array can tolerate, or the controller has failed
- Controller Failure: Data should be recoverable, though there may be file corruption
- Boot Process Issues: Use the RAID configuration utility to verify status
4.3 System and Display Issues
4.3.1 Troubleshoot Component Issues
Symptoms like system lockups, random shutdowns, continuous rebooting, OS blue screen/kernel panic errors, and application crashes can be challenging to diagnose. These issues are often caused by software problems, disk/file corruption, or malware.
Diagnostic steps:
- Eliminate Software Issues: Ensure software, disk/file corruption, and malware are not the causes
- Identify Patterns: Determine if the problem follows a pattern (e.g., thermal issues after running for a while)
- Check Power Supply: Verify stable voltages to the system
- Suspect Hardware: Consider problems with memory, CPU, or motherboard
- Observe Physical Symptoms: Look for physical symptoms to identify issues
4.3.2 Overheating
Excessive heat can easily damage sensitive computer circuitry. If a system feels hot to the touch, check for overheating issues. Unusual odors, such as burning smells or smoke, usually indicate overheating.
Techniques for diagnosing and correcting overheating:
- Temperature Sensors: Use internal temperature sensors accessible via driver or management software
- CPU Fan: Ensure the CPU fan is working properly and adequately sized
- Heat Sink: Verify proper fitting and clean/replace thermal paste if necessary
- Blanking Plates: Use plates to cover holes and maintain proper airflow
- Environment: Ensure the room is not unusually warm or dusty
4.3.3 Physical Damage
Physical damage typically affects peripherals, ports, and cables. Damage to other components is more likely if the unit has been in transit.
Motherboard issues to be aware of:
- Electrostatic Discharge (ESD), Electrical Spikes, or Overheating: Can damage soldered chips and components
- Careless Insertion: Can damage pins on integrated connectors
- Dirt and Chip Creep: Can cause adapter cards to work loose over time
Visible signs of damage include:
- Liquid Spills: Look for signs of liquid damage or dust clogging
- Scorch Marks and Capacitor Swelling: Blown components may leave scorch marks; swollen capacitors indicate damage
4.3.4 Troubleshoot Performance Issues
Performance issues are challenging to diagnose due to their varied causes. Use a structured approach:
- Check for overheating: High temperatures can cause throttling
- Check for misconfigurations: Verify compatibility of new components
- Verify the problem: Use diagnostic tests to compare performance against baselines
- Rule out software/configuration/networking issues: Users might describe performance as sluggish due to configuration problems
4.3.5 Troubleshoot Inaccurate System Date/Time
Accurate timekeeping is crucial for computers. The real-time clock (RTC) tracks date and time, powered by a coin-cell lithium battery (usually CR2032) when the computer is off.
If the time in system setup is incorrect, it may signal a failing RTC battery, which should be replaced with the same type. This battery is often called the "CMOS battery" because older systems stored settings in CMOS RAM.
4.3.6 Troubleshoot Missing Video Issues
If no image is displayed on the monitor or projector, first ensure the display device is plugged in and turned on. Verify the monitor is not in standby mode.
Physical Cabling Issues:
- Check cable and connectors between video card and monitor
- Ensure cables are securely connected and not damaged
- Verify cable specification matches application requirements
- Check cable and port compatibility with newer technologies
Burnt-Out-Bulb Issues:
Video projectors use high-intensity bulbs that have limited lifespan. Signs of failing bulb include dimming images and bulb health warnings. A completely failed bulb may produce a popping sound and show scorch marks.
Intermittent Projector Shutdown:
Typically caused by overheating. Ensure fans work properly, ventilation is clear, vents aren't blocked, and ambient temperature is within operating range.
4.3.7 Troubleshoot Video Quality Issues
Video quality issues can result from problems with the display or input source. Common issues include:
- Dim image: Check OSD to adjust brightness/contrast; power-saving modes may reduce brightness
- Fuzzy image: Often due to resolution mismatch between output and display's native resolution
- Flashing screen: Check video cable connections; may indicate failing backlight components
- Dead pixels: Stuck (bright) or dead (black) pixels in flat-panel displays
- Display burn-in: Static images displayed too long leave ghost images
- Incorrect color display: May require color calibration for accurate reproduction
- Audio issues: HDMI and DisplayPort transmit audio; DVI and VGA do not
- Sizing issues: Screen appears stretched, compressed, or has black bars
- Distorted image: Wavy or geometric warping, like pincushion effects