Courseiva
Software Troubleshooting →hardMultiple Choice

220-1102 Software Troubleshooting Practice Question

A technician upgraded a Windows 10 workstation from 8GB to 16GB of RAM by installing two new matching DIMMs. After the upgrade, the workstation crashes intermittently with a stop code 'MEMORY_MANAGEMENT' (0x0000001A). The technician has run Windows Memory Diagnostic, which passed without errors, and the BIOS correctly reports 16GB of RAM. All other drivers and the OS are up to date. Which of the following should the technician do NEXT?

⚠ Common exam trap

Candidates often assume a passed memory diagnostic means the RAM is fully functional, overlooking that firmware-level memory controller training can still cause intermittent crashes, making a BIOS update the logical next step rather than replacing hardware or adjusting OS settings.

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

✓

Update the system BIOS/UEFI firmware

The MEMORY_MANAGEMENT stop code (0x0000001A) after a RAM upgrade, despite the memory passing Windows Memory Diagnostic and being correctly detected in BIOS, often indicates a compatibility issue between the new memory modules and the motherboard's memory controller. Updating the BIOS/UEFI firmware is the correct next step because newer firmware versions frequently include updated memory reference code (MRC) and improved support for higher-capacity or newer DIMMs, resolving latent timing or voltage issues that the diagnostic tool does not test under real-world load.

Answer analysis

Option-by-option breakdown

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

  • ✗

    Increase the system page file size

    Why it's wrong here

    Increasing the system page file size is a common response to low-memory symptoms, but the MEMORY_MANAGEMENT bugcheck (0x1A) is not a virtual memory shortage indicator. This stop code typically fires when the memory manager detects corruption in physical memory structures—often due to faulty RAM, unstable memory timings, or a driver scribbling on invalid memory. Enlarging the page file would merely increase the amount of disk space used as overflow; it cannot address the underlying hardware or low-level memory integrity problem that triggers this bugcheck.

  • ✓

    Update the system BIOS/UEFI firmware

    Why this is correct

    After physically installing additional RAM, the motherboard's UEFI/BIOS firmware must correctly initialize and train the memory controller for the new DIMM configuration. If the BIOS is outdated, its memory reference code (MRC) may not recognize or properly configure the new modules, leading to memory instability and stop codes such as MEMORY_MANAGEMENT. Updating the firmware to a version that adds support for the new memory module (or improves memory compatibility/timing) is a logical, minimally invasive step before considering hardware replacement.

  • ✗

    Disable xHCI hand-off in the BIOS settings

    Why it's wrong here

    Disabling xHCI hand-off in BIOS settings governs whether the BIOS or the operating system takes ownership of the USB 3.0 (eXtensible Host Controller Interface) controller during boot. This setting has no relationship to RAM management, memory integrity, or the virtual memory subsystem. While adjusting xHCI hand-off might resolve some USB-related boot or device recognition issues, it will not address a MEMORY_MANAGEMENT bugcheck, which points to physical memory or memory manager corruption rather than USB controller handoff problems.

  • ✗

    Replace the motherboard with a newer model

    Why it's wrong here

    Replacing the motherboard is an aggressive and costly action that should only be considered after all less invasive troubleshooting has been exhausted. A MEMORY_MANAGEMENT stop code after a memory upgrade is more commonly attributed to incompatible or faulty RAM, incorrect slot population, or outdated BIOS memory training settings—all of which can be checked and corrected before swapping hardware. If the new memory is detected in UEFI/BIOS and the system posts, the motherboard itself is likely functional; a sudden motherboard failure would more often manifest as a no-POST condition, not a specific bugcheck code.

Visual reference

Client Recursive Resolver Root DNS (13 root servers) TLD DNS (.com, .org, …) Authoritative example.com query IP addr answer

Go deeper

Related to this question

About these practice questions

One of 925 original 220-1102 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 by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This 220-1102 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-1102 exam.