CompTIA A+ Exam  >  CompTIA A+ Notes  >   Core 2  >  Software Troubleshooting

Software Troubleshooting

Overview

Software troubleshooting focuses on identifying and resolving operating system errors, application failures, performance issues, and user environment problems in Windows, macOS, and Linux. This chapter covers systematic diagnostic approaches, common software symptoms, and corrective actions tested heavily on the CompTIA A+ Core 2 exam. Mastering these troubleshooting methodologies is critical for help desk scenarios and performance-based questions.

Core Concepts

Common Windows OS Symptoms and Solutions

Blue Screen of Death (BSOD) indicates a critical system error that forces Windows to stop. The system displays a blue screen with a stop code that identifies the specific fault. Modern Windows versions show QR codes and friendly messages, but the underlying cause is typically driver conflicts, hardware failures, or corrupted system files.

  • Check stop code (e.g., IRQL_NOT_LESS_OR_EQUAL, PAGE_FAULT_IN_NONPAGED_AREA)
  • Boot into Safe Mode to isolate third-party driver issues
  • Run sfc /scannow to repair system files
  • Use chkdsk /f /r to check disk integrity
  • Update or roll back recently changed drivers
  • Check Event Viewer for detailed error logs

Slow profile load occurs when user profiles take excessive time to load at login. Corrupted user profiles, oversized registry hives, or network delays accessing roaming profiles cause this symptom.

  • Create new user profile and migrate data
  • Delete temporary profile copies in C:\Users
  • Check network connectivity for domain/roaming profiles
  • Clear temporary files using Disk Cleanup
  • Disable unnecessary startup programs via Task Manager > Startup tab

Application crashes manifest as programs closing unexpectedly, freezing, or displaying error messages. Compatibility issues, missing dependencies, corrupted application files, or insufficient resources trigger crashes.

  • Check Event Viewer > Application logs for error details
  • Run application in compatibility mode (right-click > Properties > Compatibility)
  • Reinstall or repair the application
  • Update to latest application patches
  • Verify .NET Framework, Visual C++ redistributables are installed
  • Increase virtual memory if system resources are low

Boot failures prevent Windows from starting normally. Symptoms include black screens, spinning circles that never complete, or error messages like "Operating System Not Found" or "Boot Device Not Found."

  • Access Advanced Boot Options (F8 or Shift+F8 during boot)
  • Use bootrec /fixmbr to repair Master Boot Record
  • Use bootrec /fixboot to write new boot sector
  • Use bootrec /rebuildbcd to rebuild Boot Configuration Data
  • Run Startup Repair from Windows Recovery Environment
  • Verify boot order in BIOS/UEFI settings

Missing DLL files appear as error messages when launching applications, stating that a specific .dll file cannot be found. Incomplete installations, corrupted updates, or malware removal cause missing dependencies.

  • Reinstall the affected application completely
  • Run sfc /scannow to restore system DLLs
  • Install missing Visual C++ redistributables from Microsoft
  • Register DLLs manually using regsvr32 filename.dll
  • Avoid downloading individual DLLs from untrusted websites

Application and Service Management

Services are background processes that run without user interaction. Critical Windows functions depend on services running properly. Access via services.msc or Task Manager > Services tab.

  • Startup types: Automatic, Automatic (Delayed Start), Manual, Disabled
  • Dependencies tab shows which services require others to function
  • Recovery tab configures automatic restart actions on failure
  • Log on tab determines which account runs the service
  • Stop/Start/Restart services to resolve application issues
  • Check service status when troubleshooting network, printing, or security problems

Task Manager provides real-time system monitoring and process control. Access via Ctrl+Shift+Esc or right-click taskbar.

  • Processes tab shows CPU, memory, disk, and network usage per application
  • Performance tab displays overall resource utilization graphs
  • Startup tab manages which programs launch at login
  • Details tab shows individual process executable names and PIDs
  • End Task terminates unresponsive applications
  • Resource Monitor (accessible from Performance tab) provides deeper analysis

Event Viewer logs system events, errors, and warnings. Access via eventvwr.msc or Computer Management.

  • Application logs record software-related events
  • System logs record OS and driver events
  • Security logs track authentication and access events
  • Event IDs identify specific error types (e.g., Event ID 41 = unexpected shutdown)
  • Filter logs by Event Level (Critical, Error, Warning, Information)
  • Export logs for documentation or escalation

Performance Optimization

Disk usage at 100% causes extreme slowness even when CPU usage is low. Windows Update, search indexing, antivirus scans, or failing drives trigger constant disk activity.

  • Check Task Manager > Performance > Disk to identify processes
  • Disable Windows Search service temporarily
  • Run chkdsk /f /r to detect disk errors
  • Disable Superfetch/SysMain service
  • Update disk controller drivers
  • Consider upgrading to SSD if using mechanical drive

High CPU usage from a single process indicates runaway applications or malware. Normal idle CPU should be below 10%.

  • Identify process in Task Manager > Processes tab
  • Research unfamiliar process names online before terminating
  • Check for malware using Windows Defender or third-party scanner
  • Update applications showing high CPU usage
  • Uninstall problematic applications
  • Check for Windows Update processes (TiWorker.exe, MoUSoCoreWorker.exe)

Excessive memory usage leads to sluggish performance and increased paging. Memory leaks in applications cause gradual consumption until system becomes unresponsive.

  • Sort Task Manager processes by memory column
  • Restart applications with memory leaks
  • Increase physical RAM if consistently at 80%+ usage
  • Adjust virtual memory (pagefile) settings manually if needed
  • Close unnecessary browser tabs and background applications

Windows Update Issues

Windows Update failures prevent security patches and feature updates from installing. Error codes, insufficient disk space, or corrupted update components cause update problems.

  • Run Windows Update Troubleshooter from Settings > Update & Security
  • Delete contents of C:\Windows\SoftwareDistribution\Download
  • Restart Windows Update service (wuauserv)
  • Run DISM /Online /Cleanup-Image /RestoreHealth to repair system image
  • Run sfc /scannow after DISM completes
  • Free up disk space (updates require minimum 8-16 GB free)
  • Check Windows Update error codes for specific solutions

Browser and Application Issues

Browser redirection occurs when visiting legitimate sites automatically redirects to unwanted pages. Browser hijackers, malicious extensions, or modified DNS settings cause redirects.

  • Remove suspicious browser extensions
  • Reset browser settings to defaults
  • Check DNS settings (should be automatic or trusted DNS like 8.8.8.8)
  • Scan for malware using Windows Defender Offline
  • Clear browser cache, cookies, and history
  • Check hosts file (C:\Windows\System32\drivers\etc\hosts) for unauthorized entries

Certificate warnings display when browsers cannot verify a website's security certificate. Expired certificates, incorrect system date/time, or man-in-the-middle attacks trigger warnings.

  • Verify system date and time are correct
  • Clear browser SSL state and cached certificates
  • Update browser to latest version
  • Check if corporate proxy or firewall is intercepting HTTPS
  • Verify certificate chain in browser (click padlock icon)
  • Do not bypass legitimate certificate errors on financial or sensitive sites

macOS and Linux Software Issues

macOS spinning wheel (beach ball) indicates an application is not responding. Insufficient resources, corrupted preferences, or application bugs cause this symptom.

  • Force quit application (Command+Option+Esc)
  • Check Activity Monitor for high CPU/memory processes
  • Delete application preference files from ~/Library/Preferences
  • Boot into Safe Mode (hold Shift during startup)
  • Repair disk permissions using Disk Utility
  • Reset NVRAM/PRAM (Command+Option+P+R at startup)

Linux package management errors occur when installing or updating software through package managers. Dependency conflicts, locked databases, or corrupted repositories cause errors.

  • Run sudo apt update (Debian/Ubuntu) to refresh repository lists
  • Run sudo apt --fix-broken install to resolve dependencies
  • Run sudo yum update (Red Hat/CentOS) or sudo dnf update (Fedora)
  • Clear package manager cache
  • Check /var/lib/dpkg/lock or /var/lib/rpm for lock files
  • Verify repository URLs in /etc/apt/sources.list or /etc/yum.repos.d/

Troubleshooting

1. Symptom: User reports computer becomes extremely slow after about 30 minutes of use, with Task Manager showing memory usage at 99% and one application consuming 8 GB of RAM that grows continuously.

Likely Cause: Memory leak in the application causing it to allocate RAM without releasing it properly.

Fix: Restart the affected application immediately to free memory, check for application updates or patches that address the memory leak, and if no fix exists, schedule regular application restarts or consider alternative software. Monitor memory usage in Task Manager after restarting to confirm the leak pattern.

2. Symptom: Windows 10 PC displays "Operating System Not Found" error on startup, though the system worked fine yesterday and no hardware changes were made.

Likely Cause: Corrupted Boot Configuration Data (BCD) or damaged Master Boot Record (MBR) preventing the system from locating the Windows installation.

Fix: Boot from Windows installation media, select Repair Your Computer > Troubleshoot > Command Prompt, then execute bootrec /fixmbr, followed by bootrec /fixboot, and finally bootrec /rebuildbcd. Restart the computer and verify boot order in BIOS if issue persists.

3. Symptom: Employee cannot access any websites, receiving "This site can't be reached" errors in all browsers, but can ping 8.8.8.8 successfully and other networked applications work normally.

Likely Cause: DNS resolution failure preventing domain names from translating to IP addresses, while direct IP connectivity remains functional.

Fix: Open Network Adapter properties, select Internet Protocol Version 4 (TCP/IPv4), and manually configure DNS servers to 8.8.8.8 (primary) and 8.8.4.4 (secondary), then run ipconfig /flushdns to clear DNS cache. Test website access and verify DNS settings persist after reboot.

Step-by-Step Procedures

Task: Performing System File Check and DISM Repair on Windows

  1. Right-click Start menu and select Command Prompt (Admin) or Windows PowerShell (Admin)
  2. Type sfc /scannow and press Enter to scan and repair corrupted system files
  3. Wait for scan to complete (typically 15-30 minutes); do not interrupt the process
  4. If SFC reports it found corrupted files but could not repair them, proceed to DISM
  5. Type DISM /Online /Cleanup-Image /CheckHealth to verify image corruption exists
  6. Type DISM /Online /Cleanup-Image /RestoreHealth and press Enter to download and replace corrupted files from Windows Update
  7. Wait for DISM to complete (may take 20-40 minutes depending on corruption extent)
  8. Run sfc /scannow again after DISM completes to repair files using the restored image
  9. Restart the computer and test whether the original issue is resolved
  10. Check Event Viewer > Windows Logs > System for details if issues persist

Practice Questions

Q1: A user reports their Windows 10 computer displays a blue screen with the stop code DRIVER_IRQL_NOT_LESS_OR_EQUAL during startup. What is the BEST first troubleshooting step?
(a) Reinstall Windows immediately
(b) Boot into Safe Mode and uninstall recently updated drivers
(c) Run chkdsk /f from Command Prompt
(d) Replace the motherboard

Ans: (b)
BSOD stop codes referencing "DRIVER" indicate driver issues, and Safe Mode allows Windows to load without third-party drivers, enabling you to roll back or uninstall the problematic driver causing the crash.

Q2: An employee's computer takes 10 minutes to load their desktop after entering their password. Which TWO actions are most likely to resolve this slow profile load issue?
(a) Disable unnecessary startup programs in Task Manager
(b) Increase monitor resolution
(c) Create a new user profile and migrate data
(d) Install additional RAM
(e) Upgrade the power supply

Ans: (a) and (c)
Excessive startup programs delay desktop readiness, and corrupted user profiles commonly cause prolonged login times; creating a fresh profile eliminates profile corruption while disabling startup programs reduces load time.

Q3: A technician needs to repair corrupted Windows system files that SFC could not fix. What is the correct command sequence?
(a) sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow
(b) DISM /Online /Cleanup-Image /RestoreHealth only
(c) chkdsk /f /r, then sfc /scannow
(d) bootrec /rebuildbcd, then DISM /Online /Cleanup-Image /RestoreHealth

Ans: (a)
SFC runs first to attempt basic repairs, DISM restores the component store from Windows Update when SFC fails, and running SFC again after DISM allows it to repair files using the now-restored system image.

Q4: Performance-based task - You are troubleshooting a computer that displays "Operating System Not Found" on boot. You have booted to Windows installation media and opened Command Prompt. List the exact commands in the correct order to repair the boot configuration.

Ans:
1. bootrec /fixmbr
2. bootrec /fixboot
3. bootrec /rebuildbcd
4. exit (to close Command Prompt)
5. Restart computer
This sequence repairs the Master Boot Record, writes a new boot sector, rebuilds the Boot Configuration Data store, and then tests the repair by restarting.

Q5: A help desk receives multiple calls about browsers redirecting legitimate websites to advertising pages. After removing malicious browser extensions, what should the technician check NEXT?
(a) Monitor refresh rate
(b) DNS settings and hosts file entries
(c) Windows activation status
(d) Installed fonts

Ans: (b)
Browser hijackers frequently modify DNS settings to rogue servers or add entries to the hosts file that redirect specific domains, so verifying these settings is the logical next step after removing malicious extensions.

Q6: A macOS user reports applications frequently freeze with the spinning beach ball appearing. The user states this started after upgrading to a new macOS version. What is the BEST troubleshooting approach?
(a) Replace the hard drive
(b) Boot into Safe Mode and delete application preference files from ~/Library/Preferences
(c) Downgrade to the previous macOS version immediately
(d) Reinstall the applications without removing preferences

Ans: (b)
Safe Mode loads only essential system components and can reveal whether third-party software causes the freezing, while corrupted preference files from the OS upgrade commonly cause application hangs and should be deleted to force applications to create fresh configurations.

Q7: Which of the following represents best practice when a critical Windows service fails to start?
(a) Disable the service permanently to prevent future errors
(b) Check Event Viewer for specific error details, verify service dependencies are running, and attempt to restart the service
(c) Immediately reinstall Windows
(d) Change the service to run under a different user account without investigating

Ans: (b)
Methodical troubleshooting starts with gathering information from Event Viewer to understand why the service failed, checking dependencies ensures required services are running, and attempting restart may resolve temporary issues without escalating unnecessarily.

Quick Review

  • sfc /scannow scans and repairs corrupted Windows system files; run before DISM when troubleshooting system stability
  • DISM /Online /Cleanup-Image /RestoreHealth repairs the Windows component store when SFC cannot fix corruption
  • bootrec /fixmbr, bootrec /fixboot, bootrec /rebuildbcd sequence repairs boot configuration when "Operating System Not Found" appears
  • Event Viewer logs are categorized as Application (software events), System (OS/driver events), and Security (authentication/access events)
  • Blue Screen stop codes starting with "DRIVER" indicate driver conflicts requiring Safe Mode boot and driver rollback
  • Slow profile loads are resolved by disabling startup programs (Task Manager > Startup) or creating new user profiles
  • Browser redirects require removal of malicious extensions, checking DNS settings, and examining the hosts file (C:\Windows\System32\drivers\etc\hosts)
  • Services.msc manages Windows background services; check Dependencies tab when troubleshooting service startup failures
  • Disk usage at 100% commonly results from Windows Search, Superfetch/SysMain, or Windows Update processes
  • macOS spinning beach ball is resolved by force quit (Command+Option+Esc), Safe Mode boot, or deleting preference files from ~/Library/Preferences
The document Software Troubleshooting is a part of the CompTIA A+ Course CompTIA A+ Core 2.
All you need of CompTIA A+ at this link: CompTIA A+

Top Courses for CompTIA A+

Related Searches
Previous Year Questions with Solutions, Viva Questions, mock tests for examination, Software Troubleshooting, Free, study material, pdf , Extra Questions, practice quizzes, Summary, Objective type Questions, shortcuts and tricks, Important questions, past year papers, ppt, Semester Notes, Exam, video lectures, Software Troubleshooting, Software Troubleshooting, MCQs, Sample Paper;