Lesson 17: Windows and Mobile OS Troubleshooting
CompTIA A+ Core 2 (220-1202) · Objectives 220-1202 3.1, 220-1202 3.2 · Download .docx
Objectives
- Troubleshoot common Windows OS problems: boot failures, BSODs, slow performance, services and updates.
- Troubleshoot mobile OS and application problems.
Key terms
- BSOD
- Blue Screen of Death; a Windows stop error screen shown when a critical fault, often a driver, memory, or hardware problem, forces the system to halt.
- Application fails to launch (mobile)
- Mobile symptom where an app will not open, often fixed by force-stopping it, clearing its cache, updating it, or reinstalling it.
- Degraded performance
- Symptom where a system runs noticeably slower than normal, often from low resources, too many startup apps, malware, or a failing drive.
- Random reboots (mobile)
- Mobile symptom where the device restarts unexpectedly, often from a failing battery, overheating, faulty apps, or OS bugs.
- No OS found
- Startup error meaning firmware cannot locate a bootable operating system, caused by wrong boot order, a damaged boot record, or a failed drive.
- Battery life issues
- Mobile symptom of fast battery drain, typically caused by bright screens, background apps, weak signal, aging batteries, or malware.
- Services not starting
- Symptom where a Windows service fails at boot, often due to a disabled dependency, wrong account credentials, or corrupted files.
- Screen does not autorotate
- Mobile symptom where the display stays in one orientation, usually because rotation lock is on or the app does not support rotation.
- Application crashing
- Symptom where a program closes unexpectedly or freezes, often from bugs, corrupted files, incompatibility, or insufficient memory.
- NFC
- Near-Field Communication; very short-range wireless technology, a few centimeters, used for contactless payments, digital keys, and quick device pairing.
- Low memory warning
- Windows alert that RAM and the paging file are nearly exhausted, usually fixed by closing apps, enlarging virtual memory, or adding RAM.
- OS fails to update (mobile)
- Mobile symptom where an update will not install, often from low storage, low battery, poor connectivity, or an unsupported device.
- Virtual memory
- Drive space Windows uses as an overflow for RAM, letting more programs run but much more slowly than real memory.
- USB controller resource warning
- Windows message that a USB controller has run out of bandwidth or endpoints because too many devices share it.
- System instability
- Symptom of random freezes, crashes, and errors, often caused by faulty drivers, overheating, failing RAM, or corrupted system files.
The concept
220-1202 3.1 — Troubleshoot common Windows OS problems: boot failures, BSODs, slow performance, services and updates. BSOD after driver update: A stop error that begins immediately after a driver update is almost always caused by that driver. Safe Mode loads only basic drivers (including a generic display driver), so Windows stays up long enough to use Device Manager's Roll Back Driver. Random stop errors after RAM: Stop errors that occur at random and show varying stop codes usually indicate a hardware fault, and faulty or mismatched RAM is the classic cause. Because the problem began right after the module was added, testing it with Windows Memory Diagnostic or simply removing it confirms the theory quickly. Degraded performance in Task Manager: The exhibit shows one process using about 97% of the CPU, which explains the slowdown. The technician should find out what owns the process (a legitimate updater stuck in a loop or something unwanted) before ending it or disabling it on the Startup apps tab, so the fix is correct and lasting. Startup apps slow login: Every enabled startup item launches at sign-in and competes for CPU, disk and memory, so a long list of high-impact items is a common cause of degraded performance. Disabling unneeded entries on the Startup apps tab removes the load without uninstalling anything. Boot stage identification: Windows Boot Manager is the boot loader; it reads the Boot Configuration Data (BCD) store to learn where Windows is installed. A missing or corrupt BCD means the firmware handed off successfully but the boot loader cannot continue. Rebuild BCD command: bootrec /rebuildbcd searches all disks for Windows installations and lets the technician add them to a new BCD store, which Windows Boot Manager reads at startup. Related bootrec switches are /fixmbr, /fixboot and /scanos; Startup Repair in Windows RE automates many of the same fixes.
220-1202 3.2 — Troubleshoot mobile OS and application problems. App fails to launch: When an OS update changes the platform, older app versions can crash at launch until the developer ships a compatible update. With a restart already tried, installing the waiting app update is the next targeted step; clearing cache or reinstalling would follow if it still fails. Force stop frozen app: Force stop terminates every process belonging to the app, including background services, so the next launch starts fresh. It is the standard first fix for an app that fails to close and affects nothing else on the device. App fails to update: App updates need free space to download the package and unpack it alongside the existing version. With almost no space left, the update fails until the user removes or offloads unused apps, old videos or downloads. App fails to install: Apps declare a minimum OS version, and the store hides or blocks installs on devices below it. Because an OS update is available, installing it should meet the app's requirement. Slow phone, full storage: Flash storage slows down when it is nearly full because the OS has little room for caches, temporary files and wear-leveling. With no sign of a rogue app, freeing space (removing unused apps, offloading photos and video) is the most likely fix for slow response. Clear cache vs storage: The cache holds temporary data the app can rebuild, and stale or corrupted cache files after an update often cause outdated content and broken features. Clearing the cache keeps account data and settings, so it comes before clearing storage or reinstalling.
Worked examples
Common mistakes
- Random stop errors after RAM: choosing “Roll back the most recent Windows quality update” is a common mistake. No update was installed in this window, so there is nothing to tie the stop errors to an update.
- Slow phone, full storage: choosing “Turn on the phone's battery saver mode” is a common mistake. Battery saver reduces performance to save power, so it would make the phone feel slower.
- Temporary profile rebuild: choosing “Add RAM so profiles load faster at sign-in” is a common mistake. The other users load quickly on the same hardware, so resources are not the problem.
- No OS found, drive missing: choosing “Secure Boot has been disabled in the firmware” is a common mistake. Disabling Secure Boot does not hide drives from the firmware's storage list.
- Battery drain from app: choosing “Reset the phone's network settings” is a common mistake. Network resets fix connectivity problems and do not change one app's battery use.
- App fails to launch: choosing “Turn on developer mode and enable USB debugging” is a common mistake. Developer options are for app testing and add security risk; they do not repair an incompatible app.
Self-check
Try each one before you look. A miss here costs nothing and tells you exactly what to reread.
Canvas is the official record. This companion enhances the PGCC curriculum; it does not replace it. Last name and class year only. Students with a 504 plan or IEP: your accommodations apply.