Objective 3.1: Given a scenario, troubleshoot common Windows OS issues

Cert: CompTIA A+ Core 2 (220-1202) V15 Domain: 3.0 Software Troubleshooting Weight: Part of the 23% Software Troubleshooting domain Depth: Given a scenario, troubleshoot. The candidate must diagnose and resolve common Windows OS issues by symptom shape.

What this objective tests

You should recognize each Windows OS symptom and apply the right diagnostic path: BSOD, performance, boot, shutdowns, services, app crashes, memory warnings, USB warnings, instability, no-OS-found, slow profiles, time drift.

Key facts

Blue Screen of Death (BSOD):

• Windows stop error caused by a kernel-level failure (driver, hardware, corrupted system file).
• Note the stop code (KMODE_EXCEPTION_NOT_HANDLED, IRQL_NOT_LESS_OR_EQUAL, PAGE_FAULT_IN_NONPAGED_AREA, etc.).
• First step: search the stop code. Most map to a specific cause (driver, RAM, disk, antivirus conflict).
• Recent change is often the culprit: new driver, new app, hardware swap. Roll back if recent.

Degraded performance:

• System feels slow. Open Task Manager / Resource Monitor.
• Top CPU consumer? Top memory? Top disk? Top network? Identify and address.
• Common causes: malware, runaway process, disk near full, RAM exhaustion, failing drive (high disk wait time), background updates.

Boot issues:

• Won't POST: hardware issue (not the OS layer).
• POST then no boot device: storage missing, boot order wrong, MBR/GPT corruption.
• Booting but Windows fails: corrupted system files, broken driver, recent update.
• Use Windows Recovery Environment (Shift + Restart, or boot from install media): Startup Repair, Command Prompt with sfc/DISM/bootrec.

Frequent shutdowns:

• Could be thermal (CPU/GPU overheating), power (failing PSU, battery), driver, BSOD that auto-restarts.
• Check Event Viewer System log for Kernel-Power 41 events (unexpected shutdown signature, covered in Core 1 obj 5.2).
• Inspect temperatures (HWInfo, vendor utility). Inspect Event Viewer for hardware errors.

Services not starting:

• A Windows service fails to start at boot. Check Event Viewer for the service's error.
• Common causes: missing dependency, corrupted service binary, permissions issue on service account.
• Verify in services.msc: Startup Type, Log On As, Dependencies.

Applications crashing:

• Single app crashing repeatedly: app-specific issue. Reinstall, update, clear app cache.
• Multiple apps crashing: OS-level issue. Run sfc /scannow, check for failing hardware, scan for malware.
• Check Event Viewer Application log for Faulting Module Name.

Low memory warnings:

• Windows pop-up: "Your computer is low on memory." Apps may close.
• Real cause: physical RAM exhausted, page file undersized or on a slow drive, memory leak in a specific app.
• Identify the top memory consumer in Task Manager. Add RAM if workload requires.

USB controller resource warnings:

• "USB device descriptor request failed" or "Not enough USB controller resources."
• Common when many USB devices share one controller. Move some devices to a powered USB hub, or to a different USB port (different controller).

System instability:

• Generic "things break randomly" symptom. Run Reliability Monitor (perfmon /rel) for a timeline.
• Check for failing hardware (RAM with MemTest86, drive with SMART), recent driver updates, malware.

No OS found:

• BIOS/UEFI POSTs but the boot loader can't find Windows.
• Boot order wrong, drive disconnected, MBR/GPT corrupted, boot files damaged.
• Fix: verify boot order, run bootrec /fixmbr /fixboot /rebuildbcd from Recovery Environment.

Slow profile load:

• Sign-in takes minutes after entering credentials.
• Causes: roaming profile (slow network), Group Policy processing delays, large profile size (e.g., huge Desktop or Documents folders), profile corruption.
• Check Event Viewer User Profile Service log. Consider folder redirection to move user data off the profile.

Time drift:

• System clock not staying synchronized.
• Causes: dead CMOS battery, NTP not configured, network issues reaching NTP server, virtualization clock drift (VM time problems).
• Verify NTP source: w32tm /query /source and w32tm /query /status.
• Critical for Kerberos auth: clock skew > 5 minutes breaks domain logon.

Common gotchas

• Auto-restart on BSOD hides the stop code. Disable auto-restart (System Properties > Advanced > Startup and Recovery) so the BSOD stays on screen.
• "Low memory" only addressed with more RAM. Sometimes a memory-leaking app is the real fix. Identify the consumer first.
• No OS found and the fix is "reinstall Windows." Often a boot configuration issue (bootrec /rebuildbcd) recoverable without reinstall.
• Time drift on a VM blamed on Windows. Underlying hypervisor often the source. Configure host time-sync.
• Slow profile = "user's account is broken." Often huge OneDrive sync target on the desktop. Check profile size.

Real-world context

Diagnostic toolkit for Windows OS issues:

• Event Viewer (eventvwr.msc): Always first stop for OS-level issues.
• Reliability Monitor (perfmon /rel): Timeline of system failures and changes.
• Task Manager / Resource Monitor: Performance investigation.
• sfc /scannow: System file integrity check.
• DISM /Online /Cleanup-Image /RestoreHealth: Repair the component store before sfc.
• chkdsk /f: Filesystem integrity check (covered in Core 1).
• Recovery Environment (Shift+Restart > Troubleshoot > Advanced): Startup Repair, Command Prompt, System Restore, Reset.
• Safe Mode: Boot with minimal drivers/services. Isolates third-party from OS.
• Memory diagnostic (mdsched.exe): RAM check at boot.

Sources

• [CompTIA A+ 220-1202 Exam Objectives Version 4.0, Section 3.1](../../../../../../30-RevyTechJourney/CompTIA%20A%2B%20220-1202%20Exam%20Objectives%20%284.0%29.pdf)
• [Microsoft Learn: Troubleshoot stop errors (BSOD)](https://learn.microsoft.com/en-us/troubleshoot/windows-client/performance/stop-error-or-blue-screen-error-troubleshooting)
• [Microsoft Learn: Windows Recovery Environment](https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-recovery-environment--windows-re--technical-reference)
• [Microsoft Learn: System File Checker](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/sfc)