Hardware practice questions

The M.2 slot is keyed for B+M and the drive is keyed for M only.

Why it fails: Keying determines whether the drive physically fits and which interface lanes are available. However, an M.2 PCIe 4.0 x4 slot typically uses an M key, and an NVMe PCIe 3.0 x4 drive also uses an M key. If the drive physically inserted without force, keying is not the cause. The scenario states the drive was installed, implying it fit. Therefore, this is not the most likely reason for non-detection.

The M.2 slot is wired for SATA only and does not support PCIe NVMe drives.

Why it fails: The motherboard specification explicitly states the slot supports PCIe 4.0 x4 and SATA. Therefore, the slot does support NVMe PCIe drives. If the slot were SATA-only, an NVMe drive would indeed not be detected, but that contradicts the given specification. This option is plausible only if the specification were misread, but the scenario says the spec lists PCIe support. Thus, it is not the most likely cause.

The M.2 drive requires a separate power cable that was not connected.

Why it fails: M.2 drives are powered directly through the M.2 slot; they do not use separate power cables like 2.5-inch SATA SSDs. This is a fundamental design difference. If a technician expected a power cable, they might overlook the actual issue. Because M.2 drives draw power from the slot, a missing cable cannot be the cause of non-detection. This option is technically inaccurate for M.2 form factors.

Replace the M.2 SSD with a SATA SSD.

Why it fails: Replacing the drive is premature because the issue may be a configuration problem. The M.2 SSD is likely functional; the lack of detection could be due to BIOS settings or slot sharing. Swapping to a SATA SSD would require different cabling and might not solve the underlying issue if the M.2 slot is disabled. The technician should troubleshoot the current setup before replacing parts.

Update the motherboard BIOS to the latest version.

Why it fails: While a BIOS update can add support for newer drives, it is not the first step. If the motherboard is new and supports NVMe, the drive should be detected unless there is a configuration issue. Updating BIOS carries risk and should be done after simpler checks. The technician should first verify that the M.2 slot is enabled and not conflicting with other ports.

Check that the SSD is properly seated in the slot.

Why it fails: Proper seating is important, but if the drive is not seated, it usually wouldn't fit or would be loose. The technician likely already ensured it clicked into place. However, reseating is a valid step, but it is not the first check if the slot might be disabled. In many cases, the drive appears seated but is not detected due to BIOS settings. Therefore, checking BIOS is a more logical first step.

Add a dedicated graphics card.

Why it fails: A dedicated GPU can accelerate video rendering and improve gaming, but the scenario emphasizes overall performance for video editing and multitasking. While beneficial, it may not provide as immediate a boost as storage and memory if the system is currently bottlenecked by slow storage and insufficient RAM. Additionally, the question asks for the most significant improvement, and storage and RAM are more foundational for general responsiveness.

Replace the CPU with a higher-core-count model.

Why it fails: A CPU upgrade can improve video editing performance, but it often requires a compatible motherboard and may be costly. The current system likely has a capable CPU, and the bottlenecks are more likely storage and RAM. Without knowing the CPU model, it is less certain to provide the most significant improvement compared to storage and memory upgrades, which are universally beneficial.

Upgrade the power supply to 750W.

Why it fails: A higher-wattage power supply does not directly improve performance unless the current PSU is insufficient for added components. The scenario does not indicate power issues. Upgrading the PSU alone would not address storage or memory bottlenecks. It is only necessary if adding a power-hungry component like a high-end GPU, which is not one of the chosen upgrades.

The PSU's total wattage of 500W is too low for the system's components.

Why it fails: While 500W total may seem low, the critical factor is the 12V rail's amperage. The total wattage includes 3.3V and 5V rails, which are less relevant for high-power components. A 500W PSU could theoretically handle the load if the 12V rail had sufficient amperage. However, with only 30A on 12V, the rail is the bottleneck. Therefore, total wattage alone is not the primary issue; the rail distribution is.

The GPU requires a dedicated 12V rail that is not available on this PSU.

Why it fails: Modern PSUs often use a single 12V rail, which simplifies power distribution. A dedicated rail is not a requirement; a single rail with sufficient amperage can power multiple components. The problem here is the amperage capacity, not the lack of a dedicated rail. Claiming a dedicated rail is needed is a misconception. Thus, this is not the most likely cause.

The CPU and GPU are drawing power from the 5V rail instead of the 12V rail.

Why it fails: CPUs and GPUs primarily draw power from the 12V rail, not the 5V rail. The 5V rail typically powers drives, USB, and some motherboard components. If they were drawing from 5V, the system would likely not function at all due to insufficient power. This option is technically incorrect. Therefore, it cannot explain the shutdowns under load.

Replace the CMOS battery.

Why it fails: A dead CMOS battery typically causes the system to lose date/time settings or BIOS configuration, but it does not usually cause beep codes or a no-video condition. Replacing the battery is a valid maintenance step, but it is not the first action for a beep-code boot failure. The technician should address the likely RAM contact issue first.

Update the BIOS to the latest version.

Why it fails: Updating the BIOS is not appropriate when the system cannot boot or display video. BIOS updates require a stable boot environment and are risky if the system is unstable. The beep code indicates a hardware issue, not a firmware bug. Attempting a BIOS update could brick the motherboard if the process is interrupted.

Replace the power supply with a higher-wattage unit.

Why it fails: A higher-wattage power supply is unnecessary here because the system powers on, indicating the PSU is likely functioning. Beep codes specifically point to a hardware fault, often RAM, not insufficient power. Replacing the PSU would not address the beep pattern and wastes time and resources. The technician should first try simpler, targeted fixes.

The video cable is loose.

Why it fails: A loose video cable would typically cause flickering, color distortion, or no image at all, rather than uniform dimness. If the cable were loose, the external monitor would not be affected because it uses a separate connection. The symptom of a consistently dim internal display while external output is normal points away from a cable issue. Reseating the cable might help if there is intermittent contact, but it is not the most likely cause here.

The inverter has failed.

Why it fails: An inverter failure would cause the backlight to not turn on at all, resulting in a completely dark screen, not just dim. Inverters are found in older CCFL-backlit laptops, but many modern laptops use LED backlights that do not have an inverter. Since the external monitor works, the GPU is fine, but the dim internal display suggests a backlight issue that could be the inverter, but it's less likely if the screen is still visible. The symptom of dimness rather than total darkness points to a different cause.

The GPU is overheating.

Why it fails: GPU overheating would affect both internal and external displays, often causing artifacts, crashes, or shutdowns. Since the external monitor works perfectly, the GPU is not the problem. Overheating would also likely produce other symptoms like fan noise or performance throttling. The dim internal display isolated to the laptop panel suggests a display-specific component failure.

The CPU cooler is not compatible with the CPU socket.

Why it fails: If the cooler were incompatible, it likely wouldn't mount properly, and the system might not boot or would overheat immediately. The fact that it runs for a while before shutting down suggests the cooler is mounted but inefficient. Compatibility issues would typically be evident at installation. The symptoms point to degraded thermal interface material rather than an incompatible cooler.

The case fans are not providing enough airflow.

Why it fails: Inadequate case airflow can contribute to overheating, but the hot exhaust air suggests heat is being expelled, so airflow is present. If case fans were the sole issue, the CPU heatsink might still be cool. The critical thermal shutdown points to the CPU itself overheating, likely due to poor contact with the heatsink. While case airflow is important, it is not the most likely cause here.

The power supply is failing under load.

Why it fails: A failing power supply can cause random shutdowns, but it would not typically trigger a thermal shutdown event. The event log specifically indicates a thermal issue, and the hot exhaust confirms overheating. A PSU problem would more likely cause sudden power loss without thermal warnings. The technician should address the thermal issue first, as it is directly evidenced.