Boot problems turn simple support tickets into urgent incidents because users can't work until Windows starts. In real help desk work, you need a method you can repeat under pressure. CompTIA A+ Core 2 (220-1202), Domain 3.0 Software Troubleshooting, Objective 3.1 Given a scenario, troubleshoot common Windows OS issues (Boot issues). The exam expects you to read symptoms, choose safe checks, and use the right recovery tool without making damage worse.
This guide focuses on what to notice first, which low-risk actions fix many cases, and how Windows recovery tools fit into a clean troubleshooting flow.
Spot the boot stage that is failing before you change anything
The fastest troubleshooting starts with one decision: which boot stage is failing. Each stage points to a different set of causes. If you skip this step, you may waste time in the wrong place, or you may cause data loss by "fixing" what wasn't broken.
Think of the boot process like a relay race. Hardware hands off to firmware (BIOS/UEFI), firmware hands off to a boot loader, then Windows loads drivers and services. When the handoff fails, the symptoms change in predictable ways. Therefore, the user's exact words matter.
Start by asking for the earliest point of failure. Do they see the vendor logo, spinning dots, a sign-in screen, or nothing at all? Next, record the exact message and any stop code. A photo from the user often saves minutes of back-and-forth.
Also capture recent changes before you act. Updates, a new SSD, a docking station, a BIOS update, or a BitLocker recovery prompt can narrow the cause. In addition, note whether this system uses full-disk encryption, because some recovery steps will trigger key requests.
Here's a quick way to map ticket language to likely stages:
| What the user reports | Likely failing stage | What it usually points to |
|---|---|---|
| "No lights, no fan, nothing" | Power delivery | Adapter, battery, PSU, board power |
| "Fans spin then shuts off" | Early hardware checks | RAM seating, CPU thermal, short, board fault |
| "Logo appears, then it says no boot device" | Firmware to boot device | Boot order, missing drive, failed SSD, UEFI settings |
| "Spinning dots forever, then restarts" | Windows loader or early kernel | Bad update, driver, disk errors, BCD issues |
| "Blue screen with INACCESSIBLE_BOOT_DEVICE" | Storage path to system disk | Driver, SATA mode change, controller issue, corruption |
Treat error text like evidence at a scene. If you change settings first, you erase your best clues.
Once you can name the stage, you can choose checks that are safe and targeted. That keeps you from jumping straight to re-installation, which is rarely the best first move.
Power-on and POST problems (no display, beeps, or instant shutdown)
POST means Power-On Self-Test. In plain terms, it's the computer's first hardware check after you press the power button. If POST fails, Windows never gets a chance to load, so software tools won't help yet.
Common signs include a black screen with no logo, beep codes, diagnostic LEDs, or a system that powers on briefly and stops. Sometimes the fan spins for a second, then the device shuts down. On desktops, you may see case lights but no video output.
Start with checks that don't risk data:
- Confirm the power cable and outlet, then check the PSU switch (desktop).
- Verify the monitor input (HDMI vs DisplayPort) and test with a known-good cable.
- Remove new USB devices and external drives, because some firmware tries to boot from them.
- Reseat RAM, then try booting with one memory stick in the recommended slot.
- Reseat the GPU (if present), or switch to onboard video when available.
Clear CMOS can help when a bad firmware setting blocks POST. However, do it only if policy allows, and document the current settings first when possible. On managed systems, changing firmware settings can violate standards or break device encryption workflows.
Laptops add a few extra variables. A weak battery can cause brownouts during startup, while a bad AC adapter can look like a dead system. Docking stations also cause confusion because they add power and display paths. Therefore, test boot with the dock removed, using the original charger, and with only essential devices connected.
If you get consistent beep codes or hardware fault lights, follow the vendor guide for that model. At this stage, "try random software fixes" only adds delay.
Boot loader and Windows start failures (boot loops, blue screens, "no boot device")
If the system passes POST and shows a logo, the next failures tend to involve boot selection, boot files, or early Windows loading.