Courseiva

220-1101 Hardware and Network Troubleshooting Practice Question

A technician is troubleshooting a desktop computer that frequently experiences blue screen errors (BSODs) with various stop codes. The technician suspects a hardware issue. Which of the following should the technician perform to help identify the cause? (Choose two.)

⚠ Common exam trap

The trap here is choosing actions that are fixes rather than diagnostics, such as updating BIOS or replacing the PSU, instead of gathering evidence first.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Check the Event Viewer for critical system errors.

BSODs with varying stop codes often point to memory or driver issues. Running Windows Memory Diagnostic tests the RAM, a common culprit. Checking Event Viewer can reveal logged errors that correlate with the BSODs. Together, these steps help identify whether the issue is memory-related or caused by a specific driver or hardware component.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    Update the motherboard BIOS to the latest version.

    Why it's wrong here

    While a BIOS update can fix compatibility issues, it is not a diagnostic step. Updating BIOS is a potential fix, but it does not help identify the cause of the BSODs. It also carries risk, so it should be done after other diagnostics. The question asks for steps to help identify the cause, not resolve it.

  • ✗

    Run a hard drive diagnostic utility to check for bad sectors.

    Why it's wrong here

    While a failing hard drive can cause BSODs, the stop codes are varied, and the technician suspects a hardware issue broadly. Running a hard drive diagnostic is a good step, but it is not one of the two best general diagnostic steps for BSODs. Memory and event logs are more directly related to the varied stop codes.

  • ✓

    Check the Event Viewer for critical system errors.

    Why this is correct

    Event Viewer logs critical errors, including those related to hardware failures and bug checks. Reviewing the logs around the time of the BSODs can reveal patterns, such as a specific driver or hardware component failing. This helps narrow down the cause before replacing parts.

  • ✗

    Replace the power supply with a higher-wattage unit.

    Why it's wrong here

    Replacing the PSU is a hardware change, not a diagnostic step. It might solve the issue if the PSU is faulty, but it does not help identify whether the PSU is the cause. A multimeter or PSU tester would be more appropriate for diagnosis. This action is premature without evidence.

  • ✓

    Run the built-in Windows Memory Diagnostic tool.

    Why this is correct

    Faulty RAM is a common cause of BSODs with varying stop codes. Windows Memory Diagnostic tests the RAM for errors. If it reports problems, the technician can then test individual sticks to isolate the faulty module. This is a non-destructive test that can be run from the operating system or boot menu.

About these practice questions

One of 896 original 220-1101 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written and reviewed by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

Last reviewed September 2026 · checked against the official CompTIA exam blueprint

This 220-1101 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 220-1101 exam.