Software Troubleshooting practice questions

Run the Windows Memory Diagnostic tool to test the system RAM.

Why it fails: Memory diagnostic tools test system RAM, but the crash began after installing a new graphics card and the stop code points to a driver IRQL issue. While faulty RAM can cause BSODs, the timing strongly suggests a graphics-related cause. Testing RAM is a reasonable later step but not the immediate next action.

Disable the graphics card in Device Manager and use the integrated GPU.

Why it fails: Disabling the new graphics card would bypass the problem but defeats the purpose of the upgrade. It is a workaround, not a resolution. The technician should first attempt to make the new hardware work properly, such as by updating firmware, before resorting to disabling the device.

Roll back the graphics driver to a previous version.

Why it fails: Rolling back the driver is a logical step if the new driver caused the issue, but the technician already installed the latest driver from the manufacturer. Rolling back would revert to an older driver that may still be incompatible with the new hardware, and it does not address potential hardware incompatibilities or other driver conflicts.

Reimage the computer immediately without attempting removal.

Why it fails: Reimaging is a valid last resort when an infection cannot be cleaned or when policy requires it, but it is not the first safe remediation step for a browser redirect. It destroys user data and applications, so technicians should first attempt containment and offline cleaning before resorting to a full reimage.

Run a full antivirus scan from within the infected operating system.

Why it fails: Running a scan from the infected OS is risky because sophisticated malware can hide from or disable the installed antivirus. While it may work for simple infections, it is not the safest approach. A bootable rescue environment or offline scan is preferred to ensure the malware cannot interfere with detection and removal.

Disable System Restore to prevent the malware from returning.

Why it fails: Disabling System Restore removes restore points that could be valuable for recovery if remediation fails. Malware can hide in restore points, but deleting them all is not a required containment step and eliminates a safety net. The better practice is to clean the system and then create a new known-good restore point.

Use the Windows Activation Troubleshooter to resolve the issue.

Why it fails: The Activation Troubleshooter is designed for common activation problems, but it may not resolve issues caused by a significant system date discrepancy. After correcting the date, the activation state may still be invalid, and the troubleshooter might not reset it. The slmgr /rearm command is more direct in this scenario.

Run the command sfc /scannow to repair system files.

Why it fails: System File Checker repairs corrupted Windows system files, but the activation problem is not due to file corruption. The incorrect date likely caused the activation to expire or become invalid. sfc /scannow does not reset activation timers or license status, so it would not resolve the issue.

Reinstall Windows using the original installation media.

Why it fails: Reinstalling Windows is a drastic step that would erase programs and data. The activation issue is likely due to the incorrect system date corrupting the activation state. Reinstallation is unnecessary and does not guarantee activation if the underlying cause, such as a hardware change or invalid key, is not addressed.

Perform a clean boot using msconfig and disable all non-Microsoft services.

Why it fails: A clean boot is useful for isolating the cause of a startup problem, but here the cause is already known from Task Manager's startup impact rating. Disabling all non-Microsoft services is overly broad and may disable other needed services, making it a less precise first action than addressing the identified startup item.

Use msconfig to set the computer to Safe Boot with minimal services.

Why it fails: Safe Boot is a diagnostic mode that loads a minimal set of drivers and services. Leaving the system in Safe Boot would prevent normal operation and does not resolve the slow startup caused by a specific application. It is not an appropriate first step when the offending startup item is already identified.

Run the System File Checker (sfc /scannow) to repair corrupted system files.

Why it fails: System File Checker repairs protected Windows system files, but the issue began after installing a third-party backup utility and Task Manager identifies it as high startup impact. Running SFC is unlikely to change the startup behavior of that application and would not address the specific performance bottleneck observed.

Update the graphics card driver to the latest version.

Why it fails: Graphics driver issues typically cause different stop codes, such as VIDEO_TDR_FAILURE or similar. CRITICAL_PROCESS_DIED usually points to a critical system process, not necessarily graphics. Updating the GPU driver is unlikely to resolve this specific stop code and may introduce new issues if the driver is incompatible.

Replace the hard drive with a new solid-state drive (SSD).

Why it fails: While a failing drive can cause blue screens, there is no evidence of drive failure in this scenario. Replacing the drive is premature and would require reinstalling the OS and applications. Other diagnostics, such as checking drive health with SMART data, should be performed before considering hardware replacement.

Perform a clean installation of Windows 11.

Why it fails: A clean install is a drastic measure that erases all data and applications. It should be a last resort after simpler troubleshooting steps have failed. Because the cause is unknown, reinstalling Windows may not even resolve the issue if it is hardware-related, and it would unnecessarily inconvenience the user.

Run System File Checker (SFC) with the /scannow parameter.

Why it fails: SFC scans and repairs protected Windows system files, but the crash began immediately after installing third-party cleanup software. The corrupt or incompatible component is almost certainly that utility's driver or service, not a native Windows file, so SFC would likely find nothing to repair and would not remove the offending third-party software.

Perform a System Restore to a point before the utility was installed.

Why it fails: System Restore can roll back system changes, but it also reverts unrelated updates and settings and may not be enabled. Since the suspect application is known and can be cleanly uninstalled, using System Restore first is unnecessarily disruptive and risks removing other legitimate changes made after the restore point.

Run the Windows Memory Diagnostic tool to test for faulty RAM.

Why it fails: Memory faults can cause blue screens, but the crash is tightly correlated with installing a specific utility and disappears in Safe Mode. That pattern points to software, not hardware. Memory diagnostics would take time and likely return clean results, delaying removal of the actual cause.

Delete the user's profile folder from C:\Users and have the user log in again.

Why it fails: Deleting the profile folder removes the user's data, including documents, desktop files, and application settings. This would resolve the logon issue but cause data loss, which is not acceptable when the goal is to preserve data. A less destructive approach should be used first.

Recreate the user's account and copy the contents of the old profile folder to the new one.

Why it fails: Recreating the account and copying data can work, but it is more time-consuming and may not preserve all settings and permissions. The registry edit is a quicker, less invasive solution that directly targets the cause. Copying files can also lead to permission issues if not done correctly.

Run the System File Checker (SFC) utility to repair corrupted system files.

Why it fails: While SFC can repair system files, it does not address user profile corruption. The error is specific to the user's profile and its registry entries. SFC might be part of a broader troubleshooting process, but it is not the direct fix for a corrupted profile that prevents logon.

chkdsk /r

Why it fails: chkdsk /r locates bad sectors and recovers readable information, which helps with file system corruption. However, it does not rebuild the Boot Configuration Data store, so it will not fix an OS-not-found error caused by a damaged BCD. It may be useful after other repairs but is not the correct command here.

diskpart /clean

Why it fails: diskpart with the clean parameter wipes partition information from the selected disk. Running it would destroy the existing partitions and data, turning a boot configuration problem into total data loss. It is never an appropriate repair step when the drive is healthy and detected but merely fails to boot.

bootrec /fixmbr

Why it fails: bootrec /fixmbr writes a new master boot record compatible with the current partition table. On a UEFI system using GPT, the MBR is not the active boot mechanism, and this command does not rebuild the Boot Configuration Data store, so it would not resolve an error about the operating system not being found.

The device needs a factory reset to clear cache.

Why it fails: A factory reset might remove malware, but it is not the most likely cause; it is a potential solution. The question asks for the cause, not the fix. Clearing cache does not remove malware. The symptoms strongly point to malware, not just cache buildup.

The device's storage is nearly full.

Why it fails: While low storage can slow down a device, it does not cause pop-up ads. The presence of ads indicates a software issue, likely malware. Storage fullness would not explain the ads, so it is not the most likely cause.

The battery is failing and needs replacement.

Why it fails: A failing battery can cause quick drain, but it would not cause pop-up ads or general slowness. The ads are a clear sign of malicious software. Battery replacement would not address the adware or performance issues.

Use Disk Cleanup to remove temporary files.

Why it fails: Disk Cleanup frees space by removing temporary and unnecessary files. It can improve performance if the drive is nearly full, but it does not diagnose a failing hard drive. The symptoms described—constant activity and freezes—are more indicative of hardware degradation than low disk space.

Run the Windows Memory Diagnostic tool.

Why it fails: Windows Memory Diagnostic tests RAM, not the hard drive. While faulty RAM can cause freezes, the constant hard drive activity and the technician's suspicion of a failing HDD point to storage. Testing memory does not confirm or rule out disk problems and is not the appropriate diagnostic here.

Defragment the hard drive using the built-in Windows tool.

Why it fails: Defragmentation reorganizes files to improve access times on a healthy HDD, but it does not diagnose a failing drive. In fact, heavy defragmentation on a drive with bad sectors can stress it further and accelerate failure. It is not a diagnostic step for suspected hardware failure.

The paging file is disabled, forcing excessive disk access.

Why it fails: A disabled paging file can cause memory pressure and more disk activity, but it would not typically produce constant 100% active time with near-zero throughput on an SSD. The symptom points to storage subsystem latency, not memory management, and the paging file setting is not the most likely cause here.

The SSD is failing and should be replaced immediately.

Why it fails: An SSD can fail, but sudden 100% disk usage with low throughput on a healthy, updated system more often indicates a driver or service issue. Replacing the drive before checking SMART data and the storage driver is premature and expensive, and it may not resolve the symptom if the root cause is software.

Windows Search indexing is still building its initial index.

Why it fails: Initial indexing does cause heavy disk activity, but it normally completes within hours and would show measurable throughput. On an already-running system that is fully updated, persistent 100% active time with very low throughput is not consistent with indexing and instead suggests a driver or controller problem.

The System Configuration utility (msconfig) to set a selective startup.

Why it fails: Msconfig is an older tool and is less commonly used now; Task Manager provides similar startup management. Using msconfig to disable services can cause instability if not done carefully. Task Manager is the modern, safer first choice for managing startup impact.

The Event Viewer to look for errors during startup.

Why it fails: Event Viewer can reveal errors, but it is not the first step for general slowness. It is more useful when there are specific failures. Checking startup programs is faster and more likely to yield immediate improvement without deep analysis.

The Disk Management console to check for disk errors.

Why it fails: Disk Management is for managing partitions, not for checking disk health. Disk errors would typically cause crashes or file corruption, not just slow startup. Tools like chkdsk are better for disk errors, but startup programs are a more common cause of slowness.

Update the Android operating system to the latest version.

Why it fails: Updating the OS can fix bugs and improve performance, but the issue began after installing apps from a third-party store, suggesting an app-related cause. An OS update may not address a specific app's excessive battery drain and could introduce new variables. It is not the immediate first step.

Uninstall all apps installed from the third-party store.

Why it fails: Uninstalling all recently installed apps may resolve the issue, but it is a broad action that removes potentially useful apps. It does not confirm which app caused the problem. Checking battery usage first is more precise and preserves user data and functionality.

Perform a factory reset of the device.

Why it fails: A factory reset erases all user data and settings, which is a drastic step that should be reserved for when other troubleshooting fails. It does not identify the specific cause and may be unnecessary if the issue is due to a single misbehaving app. It is not the first action to take.

Enable System Restore and create a restore point.

Why it fails: Creating a restore point after infection is not helpful because the restore point would include the malware. System Restore is useful for reverting to a pre-infection state, but only if a clean restore point exists. Enabling it now does not remediate the current infection.

Reimage the computer immediately without attempting removal.

Why it fails: Reimaging is a drastic step that should be considered only if removal efforts fail or if the infection is severe. It erases all data and requires reinstalling applications. Attempting removal first is less disruptive and often sufficient. Reimaging without trying other methods is premature.

Educate the user on safe browsing habits.

Why it fails: User education is important for prevention but does not remediate an existing infection. It should be done after the malware is removed. The immediate next steps should focus on eliminating the malware, not on training, which can be addressed later.

The DNS server is returning incorrect results.

Why it fails: DNS problems cause name resolution failures or redirection to malicious sites, but they do not add toolbars or change homepage settings persistently. The visible browser modifications indicate software installed on the system, not a network resolution issue. Checking DNS would not remove the unwanted toolbars.

The user's roaming profile is corrupt.

Why it fails: A corrupt roaming profile would affect many settings across applications, not just browser homepage and toolbars. It also typically causes logon errors or missing desktop items. The symptom is specific to browser configuration, which points to unwanted software rather than profile corruption.

The browser needs to be updated to the latest version.

Why it fails: An outdated browser may have security vulnerabilities, but it does not spontaneously change the homepage or install toolbars on its own. The observed changes are the result of unwanted software already present. Updating the browser alone would not remove the PUP or restore the original settings.