CompTIA A+ Core 1 Domain 5: Hardware and Network Troubleshooting

After identifying the problem, the methodology's second step is forming a probable-cause theory before testing it, since the root cause is acknowledged as not yet confirmed.

• ADocumentation is genuinely the final step of the methodology, so recording outcomes now skips the four diagnostic and remediation stages that must precede any record-keeping.
• CPlanning a fix is the fourth step and presumes a confirmed cause; jumping here risks implementing changes against an unverified and possibly wrong theory.
• DImplementing or escalating is the fifth step; acting before theorizing and testing means changing configurations without evidence, which can introduce new faults and waste time.

Dell's two-amber, three-white pattern reports that no memory/RAM was detected, so reseating or swapping the DIMMs directly targets the component the POST diagnostic identified.

• BA BIOS/ROM failure is a different Dell two-and-two code, so replacing the board chases a fault the reported memory pattern did not actually indicate here.
• CCPU failure is signaled by a separate two-amber, one-white pattern, so reseating the processor addresses a component the reported memory code does not implicate at all.
• DAlthough the blank screen tempts a video-card swap, the LED memory code explains the no display because POST halts before initializing video when RAM is absent.

Microsoft reports roughly 70-75 percent of stop errors come from third-party drivers, and the crash followed a driver install that names a module, so reverting it is the prime move.

• AMicrosoft attributes only about 10 percent of stop errors to hardware, so assuming failed RAM ignores that a named .sys module points squarely at driver code.
• BA full reinstall is drastic and premature; Microsoft says only about 5 percent of crashes stem from operating system code, and a driver rollback is far less disruptive.
• CDisk checks address file-system errors, but the crash began right after a driver install and names a module, making storage corruption an unlikely first suspect.

Intel processors throttle and then automatically shut down at the Tjunction max threshold, so clearing the vents restores airflow and keeps the chip below that protective limit.

• AA weak adapter would cause charging or under-load brownouts regardless of temperature, but it does not explain shutdowns triggered specifically by sustained heavy thermal load.
• BBad memory typically yields crashes or stop errors at random times, not clean power-offs that correlate tightly with heat-generating workloads and blocked airflow.
• DA worn battery shortens runtime on DC power but does not cause shutdowns that begin only under heavy GPU or CPU load while the ventilation is obstructed.

Dell and HP both direct users to discontinue use, remove AC power, and have the swollen pack replaced through authorized service rather than improvised handling.

• BApplying pressure to or flattening a swollen pouch cell is explicitly prohibited by vendors because it can rupture the cell, so this action is both dangerous and wrong.
• CKeeping the swollen pack on the charger maintains charge and heat on a failing cell, which is the opposite of the guidance to disconnect AC and let it discharge.
• DDeliberately penetrating the cell is among the most hazardous actions possible and is specifically forbidden, as it can cause fire, venting, or chemical exposure.

Seagate and HP both state a SMART error predicts imminent failure even while the disk appears healthy, so backing up first and then replacing the drive protects the data.

• ASMART warnings are near-term failure predictions that often appear while the drive still passes basic use, so dismissing it risks abrupt and total loss of the data.
• BDefragmenting reorganizes files but cannot reverse the mechanical or wear-related degradation that a SMART threshold breach reports, so it will not truly resolve the warning.
• CClearing or disabling SMART in firmware only hides the alert without addressing the failing hardware, leaving the at-risk data exactly as exposed as it was before.

A 3F0 boot-device-not-found error appears after POST when firmware cannot locate a bootable drive, so confirming detection and boot order targets the real fault.

• AA RAM fault would stop the machine during POST before any boot-device message, but here POST completed and the logo appeared, which effectively rules memory out.
• CA power problem would prevent POST or cause shutdowns, not produce a specific firmware message that the system displayed only after successfully passing POST.
• DThe logo and the error message render fine, proving video works; a 3F0 error concerns storage and boot configuration, not the display driver in any way.

Per RFC 3927 and Microsoft, a host uses a 169.254.0.0/16 link-local address only when DHCP is unavailable, which points directly to a DHCP reachability problem.

• AA conflict produces a warning and a normal-range address, not a 169.254 self-assigned address, which instead signals the client never received any lease at all.
• BA DNS failure still leaves a valid routable IP obtained from DHCP, whereas a 169.254 address shows the client never obtained an address, a problem a layer below DNS.
• DA bad gateway only breaks off-subnet routing while the local IP stays valid, but a 169.254 address means no DHCP lease was obtained in the first place at all.

RFC 3927 and Microsoft state link-local packets stay on the local link and are never forwarded, so local pings succeed while any routed traffic necessarily fails.

• BFaulty cabling would break the local pings too, but those succeed reliably, so the loss of reach is about address scope rather than a physical media failure.
• CA dead switch would stop the two PCs from pinging each other, yet that local communication works fine, which disproves a total switch failure as the cause.
• DAlthough plausible-sounding, both hosts hold non-routable APIPA addresses, so traffic cannot leave the segment regardless of any firewall policy that is in place.

Windows raises this conflict when two interfaces claim the same address, so giving one host a distinct static IP or a DHCP lease removes the duplication and restores connectivity.

• AThe operating system explicitly reported an address conflict, a logical addressing problem, so swapping cables ignores the stated cause and cannot stop two hosts sharing one IP.
• BDNS maps names to addresses and is unrelated to two devices claiming the same IP, so clearing the resolver cache cannot remove a duplicate-address conflict on the link.
• CA firewall governs allowed traffic, not address assignment, so turning it off does nothing about the two interfaces both defending the identical IP that triggered the conflict.

Cisco documents that forcing full duplex on one side while the peer auto-negotiates makes the peer default to half-duplex, producing late collisions and very slow throughput.

• AHardware corruption is possible, but it is far less likely than the classic late-collision signature produced when one side is forced and the other side auto-negotiates.
• CAn over-length run usually prevents the link from coming up or drops it entirely, rather than yielding a stable up port with the specific late-collision pattern seen here.
• DDHCP only assigns addresses and has no role in link-layer speed or duplex, so a depleted scope would block addressing rather than generate physical collision counters.

Only one host lost its link light while peers on the same switch keep working, which isolates the fault to that station's cable or switch port at the physical layer.

• AA DHCP problem yields an APIPA address with an active link light, but here there is no link at all, indicating a physical-layer fault that sits below addressing.
• BGateway issues affect off-subnet routing while the link stays up, but a dark link light shows the connection never came up, so routing is not the first suspect here.
• DA failed switch would knock every connected device offline, but the other devices work fine, so a whole-switch failure cannot explain a single host's dark port.

A single normal POST beep suggests the system passed self-test, so a blank screen points to the display path: input selection, the cabling, or a loose graphics card.

• BA board failure typically halts POST with error codes or no beep, but a normal POST beep indicates core components initialized, which makes a board swap premature here.
• CNothing reaches the screen at all, not even firmware output, so this is a pre-OS video issue, and reinstalling Windows cannot fix a display that never even shows POST.
• DAbsent or failed RAM normally produces a distinct memory beep code and no normal POST tone, so the single healthy beep argues strongly against a memory fault here.

Total absence of lights, fans, and beeps indicates the system is not powering on, so confirming the power source and draining residual power must come before any POST analysis.

• ABeep codes only occur once a system has power and begins POST, but with no lights, fans, or sounds at all, the machine never reached the self-test stage to begin with.
• CReseating RAM addresses POST-level video faults, but a machine with no power, fans, or LEDs has not begun POST, so memory is not the first thing to check here.
• DAn OS load failure presupposes the system powered on and passed POST, but with no signs of life at all, storage is far downstream of the actual no-power symptom.

Fans spinning with no display and no beep is a classic no-POST symptom; unseated RAM or a loose video connection commonly halts POST, so reseating them is the logical first hardware check.

• AThe black screen never reaches the operating system, so reinstalling Windows cannot help; spinning fans with no POST indicate a hardware fault rather than corrupt boot files.
• CFans receiving power only proves the supply delivers some rails; a PSU can still be faulty, but swapping it first ignores the far more common unseated-RAM cause and wastes a costly part.
• DThe monitor and cable already tested good on another computer, so replacing them repeats a completed step and overlooks the internal no-POST cause such as memory or the graphics card.

Grinding and persistent clicking indicate imminent mechanical failure of a hard disk, so the priority is preserving data with an immediate backup before the drive dies and the data becomes unrecoverable.

• ADefragmentation issues heavy read/write commands that accelerate wear on a mechanically failing drive; the clicking and grinding signal head or platter damage, so defragmenting risks triggering total failure.
• BFirmware or driver updates address logical issues, not the mechanical head-crash and platter damage that grinding indicates; continued use lets the heads inflict further physical damage on the platters.
• DRepeated surface scans keep the damaged heads sweeping the platters under load, which worsens physical damage; scanning cannot repair mechanical wear and only delays the necessary backup and replacement.

Random dimming near light sources suggests the ambient light sensor, while flicker often stems from the display driver; disabling adaptive brightness and watching Task Manager separates a software cause from a hardware fault.

• AAuto-dimming near a window points to an ambient light sensor adjusting brightness, not a dying backlight; replacing the panel is costly and likely unnecessary before ruling out the software-driven brightness feature.
• BCable and inverter swaps target hardware faults, yet flicker that tracks driver state or an adaptive-brightness setting is usually software; replacing parts first skips the free software checks that often resolve flicker.
• CResolution governs image sharpness and scaling, not brightness regulation or driver-induced flicker, so lowering it cannot stop ambient-sensor dimming and only degrades the usable desktop without isolating the cause.

Ghost touches and a jumpy pointer are most often caused by an outdated or corrupt touchpad driver or overly high sensitivity, so updating or reinstalling the driver and lowering sensitivity is the logical first fix.

• BSwapping the palm-rest touchpad assembly is an expensive hardware step that should follow, not precede, the far more common software causes such as driver corruption or a too-sensitive touchpad configuration.
• CDisabling the keyboard removes a primary input device and does not address the touchpad registering phantom input; the erratic pointer originates from the touchpad or its driver, not from the keys.
• DA factory reset is a drastic, data-destroying action for an issue usually solved by a driver update or sensitivity change; reimaging wastes hours and may simply reinstall the same problematic driver.

Dust building up on vents and fans restricts airflow, so the processor overheats under load and the system shuts down or restarts to protect itself; cleaning the vents and fans restores cooling.

• AA bad update typically causes boot loops or blue screens at consistent points, not load-dependent thermal shutdowns; louder fans and heat-correlated power-offs point to cooling, not to a software regression.
• CA dead CMOS battery causes clock resets and BIOS-setting loss, not heat-triggered shutdowns under load; replacing it ignores the louder fans and the temperature-dependent pattern of the failures.
• DLow memory causes slowness or application crashes, not protective full-system power-offs that worsen with heat and louder fans; adding RAM does nothing about the thermal cause of the shutdowns.

Widely varying inter-arrival times are jitter, the variation in the delay of received packets, which disrupts the steady stream real-time audio needs and produces the choppy, robotic voice the users describe.

• AFull-speed downloads show bandwidth is adequate, so saturation is unlikely; throughput-oriented transfers tolerate delay variation that nonetheless cripples real-time voice, making a bandwidth upgrade an expensive misdiagnosis here.
• BDNS failures stop calls from connecting or registering at all; they do not produce choppy, robotic audio on calls that are already established and carrying voice, so name resolution is not the fault.
• DA duplex mismatch produces CRC errors, late collisions, and slow throughput across all traffic, yet downloads here run at full speed, so the symptom pattern does not fit a half/full-duplex negotiation fault.

A degraded RAID 5 still functions but has lost fault tolerance; replacing the failed physical disk lets the controller rebuild parity onto the new drive and restores redundancy without data loss.

• ARecreating the virtual disk reinitializes the member drives and destroys the existing data; a degraded RAID 5 is still readable, so the correct path is to rebuild onto a replacement, never to recreate.
• BDegraded means the array has lost its redundancy and is running on the surviving disks; a second disk failure would now cause total data loss, so leaving it unaddressed is risky, not safe.
• CInitializing or clearing member disks erases their RAID metadata and data; the array only needs the failed member replaced so parity can rebuild, making a full initialization a data-destroying overreaction.

When internal heat cannot be removed, the CPU reduces its clock speed to protect itself, so a hot chassis and a constantly running fan with moderate load point to thermal throttling that cleaning the cooling system relieves.

• BFragmentation marginally affects mechanical-drive seek times, not CPU clock speed, and produces no heat; a hot chassis with a constantly running fan points to a thermal cause that defragmenting cannot address.
• CAn outdated display driver may cause graphics glitches or video stutter, but it does not make the chassis hot or force the fan to run constantly; the heat signature instead indicates a cooling problem.
• DA nearly full disk can cause paging slowdowns, yet it does not generate the excess heat or constant fan activity described; the thermal symptoms indicate throttling rather than a storage-capacity bottleneck.

Vendor docs identify a depleted toner cartridge as the primary cause of uniform light/faded laser output, resolved by installing a new cartridge.

• BA failing fuser produces smeared or easily rubbed-off toner and repeating offset marks, not uniform whole-page fading that tracks a low-toner warning.
• CDrum or imaging-unit contamination produces localized vertical streaks or repeating spots, so a cleaning cycle does not fix gradual whole-page fading driven by toner depletion.
• DEconoMode deliberately reduces toner usage and makes the whole page lighter, so enabling it worsens the fading rather than resolving the underlying low-toner condition.

Vendor procedures attribute white vertical lines to a dirty corona wire or contaminated/clouded drum; cleaning the wire and inspecting the drum is the recommended first action.

• AReplacing toner is premature because a clean cartridge with a full supply still streaks when the corona wire or drum surface is contaminated; cleaning is the cheaper first step.
• BFuser faults create smeared, repeating, or poorly bonded toner rather than a single crisp white vertical line caused by uneven drum charging from a dirty corona wire.
• DA persistent physical line on every page points to an imaging-path hardware contamination, not a formatter or firmware fault, so board replacement is an expensive misdiagnosis.

Toner that smears when rubbed plus a repeating offset/ghost image are classic signs of a worn or contaminated fuser not melting toner onto the page.

• ALow toner causes light or faded output, not a repeating shadow image plus toner that rubs off, which indicates the page never reached proper fusing temperature.
• BA contaminated corona wire produces vertical white or dark stripes, not a repeating ghost image accompanied by unfused toner that smears when touched.
• CMedia can influence quality, but toner that smears on contact specifically means it was not heat-bonded, pointing at the fuser rather than at paper smoothness.

Glazed, dirty, or worn pickup and separation rollers lose grip, causing failure to pick, double-feeds, and frequent jams; cleaning or replacing them is the vendor remedy.

• AThe toner cartridge has no role in transporting paper from the tray, so replacing it cannot fix misfeeds, multi-feeds, or jams caused by the feed mechanism.
• CA driver governs how jobs are formatted and sent, not the physical pickup of paper, so reinstalling it will not resolve a mechanical feeding/separation problem.
• DThe fuser sits late in the paper path and bonds toner; failure to pick up paper or multi-feeding originates at the tray pickup and separation rollers, not the fuser.

A clogged air filter or blocked vents restrict cooling airflow, so the projector overheats and its thermal protection shuts it off; cleaning the filter and vents restores cooling.

• AA lamp at end of life trips the dedicated lamp indicator and may fail to strike, whereas a temperature indicator with auto shutoff points to a cooling/airflow problem instead.
• BA failing color wheel produces image artifacts or rattling noise, not a temperature-indicator thermal shutdown, so swapping it ignores the airflow restriction actually triggering the trip.
• CResolution and refresh settings have negligible effect on lamp/optical heat output, so changing them does not relieve the blocked airflow causing the thermal protection to shut the unit down.

A memory diagnostic (such as Windows Memory Diagnostic via mdsched) tests RAM outside the OS and confirms whether failing memory is causing the MEMORY_MANAGEMENT crashes.

• BReinstalling the OS wastes time and data if the fault is hardware, because failing RAM will continue to generate the same crashes after a fresh installation completes.
• CA failing PSU more typically causes sudden full power-offs or no-boot, and swapping it before testing memory replaces a working part while leaving suspect RAM unverified.
• DMEMORY_MANAGEMENT stop codes and app crashes point at system RAM rather than the display driver, so updating the GPU driver does not test or confirm the memory hypothesis.

A 169.254.x.x/16 address with no gateway is APIPA, which a host assigns itself only when no DHCP server responds, leaving it unable to route off-link.

• AA duplicate-address conflict involves a normal routable address and a Windows conflict warning, not a self-assigned 169.254 link-local address with no gateway populated.
• CA DNS failure still leaves a valid DHCP-assigned address and gateway; here the 169.254 address itself shows the client never obtained a lease, which is an addressing not a DNS issue.
• DA down gateway blocks routing but does not change how the client obtains its IP; the APIPA address specifically indicates the DHCP server, not the gateway, was unreachable.

Resume-from-sleep failures are commonly fixed by enabling 'Allow this device to wake the computer', disabling Fast Startup, and updating power-related and graphics drivers.

• AA weak battery causes short runtime or unexpected shutdowns, not a failure to resume from sleep while the system is clearly powered and the fans are running.
• BThe panel works after a normal restart, proving it is functional; a black screen only on resume points to power/driver state, not failed display hardware.
• DSleep preserves RAM contents and the system boots fine, so reseating memory targets the wrong subsystem; the fault lies in wake/power-management configuration and drivers.

Artifacts appearing right after a driver update typically stem from a conflicted or corrupt install; a clean driver installation removes leftover files and restores normal rendering.

• ACorruption that appears across many apps and began right after a driver change indicates a rendering/driver fault in the GPU stack, not a defect in the display panel itself.
• BArtifacts can stem from driver corruption, heat, or overclocking, and replacing hardware before ruling out a software cause discards a likely-good card without a confirmed diagnosis.
• CPage-file sizing affects system memory paging, not GPU rendering, so enlarging virtual memory has no bearing on display artifacts produced by a faulty graphics driver install.

Successful pings to the gateway and to a public IP prove Layer 3 connectivity works, so a failure only when resolving names isolates the fault to DNS configuration or reachability.

• BThe gateway cannot be down because the PC successfully pings both it and an external IP address; routing works, so the failure is specifically in name resolution.
• CAn APIPA address would block pinging the gateway and any internet IP, yet both succeed here, so the host clearly holds a valid routable address rather than a link-local one.
• DA duplex mismatch shows up as packet loss and slow throughput on pings too, but here ICMP to local and public IPs is clean, pointing to DNS rather than a link-layer mismatch.

A working monitor menu with 'No Signal' points to a wrong input selection or a loose/damaged cable; choosing the right input and reseating or swapping the cable restores the signal.

• AThe panel clearly works because its on-screen menu renders; 'No Signal' means no video is arriving, which is a cabling or input-selection issue rather than a failed panel.
• BSwapping the GPU is premature when the far more common causes are a wrong input source or a loose/faulty video cable, both of which should be ruled out before replacing hardware.
• DAn OS reinstall is irrelevant to a physical-layer 'No Signal' state and risks data loss while ignoring the likely cabling or input-source problem that is blocking the picture.

Only channels 1, 6, and 11 do not overlap in the 2.4 GHz band, so moving to the least-congested of these reduces adjacent-channel interference and improves throughput.

• AIncreasing power does not reduce contention or adjacent-channel interference and can worsen the shared-medium congestion, since all overlapping APs still compete for the same airtime.
• CWEP is deprecated and insecure and does nothing to relieve channel congestion; encryption choice is unrelated to the radio-frequency interference degrading the connection.
• DA 40 MHz channel consumes more of the narrow 2.4 GHz band and overlaps even more neighboring networks, increasing interference and typically reducing reliability in dense areas.

Swapping in a known-good adapter of the correct rating quickly proves whether a faulty charger, not the battery, is preventing charging before any part is replaced.

• AReplacing the battery before testing the charger discards a possibly good cell, because a failed or wrong-wattage adapter produces the very same 'plugged in, not charging' symptom.
• CA full OS reinstall is a drastic, time-consuming step that does nothing for a hardware charging fault and risks data loss while leaving a bad adapter or battery untested.
• DBoard replacement is an expensive last resort; the charging circuit should only be suspected after the far more common adapter, cable, and battery causes have been ruled out.

An accidental rotation hotkey flips orientation; changing Display orientation to Landscape (or the Ctrl+Alt+Up hotkey on Intel graphics) immediately restores the normal view.

• AThe panel is fine because it renders a sharp, correctly lit image; an inverted desktop is a software orientation state, not a physically mounted-backwards or failed panel.
• BA driver rollback is unnecessary work for an orientation setting the user accidentally toggled, and it will not reliably restore Landscape the way the display setting does.
• DA loose display ribbon causes flicker, lines, or no image, never a cleanly rendered but rotated desktop, so disassembling the laptop addresses the wrong layer entirely.

VGA carries each primary color on its own pin, so a bent pin or loose connector drops one color and tints the image; reseating, straightening pins, or swapping the cable restores it.

• ASoftware calibration cannot restore a color that is physically not arriving, and the fact that moving the connector changes the tint points to the cable or pins, not a profile.
• BSwapping the GPU is premature and costly when a bent VGA pin or loose connector, which the wiggle test already implicates, is the far more common cause of a lost color.
• CResolution and refresh changes affect timing and bandwidth, not which RGB pins make contact, so they cannot bring back a color dropped by a damaged or unseated VGA connector.

A printer that pings yet shows 'Offline' usually has 'Use Printer Offline' set or a stalled spooler; clearing that state and restarting the spooler releases the queued jobs.

• BThe interface clearly works because the printer answers a ping; an 'Offline' status here is a Windows print-subsystem state, not a failed network card needing replacement.
• CMoving the printer to another subnet would actually break reachability for clients on the original network and ignores that the device already responds to a ping.
• DLow consumables trigger a supplies warning on the panel, not an 'Offline' status with a ready printer, so swapping cartridges does not address the stalled queue.

Banding and a weak color after idle time are classic clogged-nozzle symptoms; a nozzle check confirms the gaps and a printhead cleaning cycle clears the dried ink.

• AInkjet printers have no fuser; that heated component belongs to laser printers, so ordering a fuser cannot address clogged nozzles on an inkjet that sat idle.
• BDraft mode uses fewer passes and faster carriage motion, which makes banding more visible rather than less, and it does nothing to clear the dried ink blocking nozzles.
• DWorn feed rollers cause misfeeds, multi-feeds, and skew, not evenly spaced color banding, so servicing the rollers targets a transport fault that is not present here.

Sticky clients cling to a distant AP while a closer one is available; trimming AP transmit power and setting a minimum-RSSI threshold prompts the client to roam to the nearer AP.

• ABoosting the far AP's power makes the sticky-client problem worse, because the device sees that signal as strong enough and refuses to release it and roam to the nearer AP.
• CWEP is obsolete and insecure and has no role in roaming decisions, which the client makes from signal strength, so this weakens security without fixing the sticky behavior.
• DSplitting one roaming SSID into separate names destroys seamless roaming and forces manual reconnection, which is impractical and does not address why the client stays stuck.

An access port carries a single VLAN, so a port left on the wrong VLAN hands the PC an address from that VLAN's subnet; reassigning the port to the correct VLAN restores access.

• AA solid link light and a successfully leased DHCP address prove the NIC is transmitting and receiving fine, so the wrong-subnet result is a switch configuration issue, not a dead card.
• BModern switches auto-negotiate MDI/MDI-X, and a wiring polarity issue would break link entirely rather than place the host in a valid but wrong subnet via DHCP.
• CA wrong DNS setting would still leave the host on the correct subnet and gateway, whereas an address from the wrong subnet shows the problem is which VLAN the port belongs to.

A drained coin-cell battery stops powering the real-time clock and CMOS memory, so the date and BIOS settings reset each time mains power is removed; a fresh cell restores them.

• BReplacing the whole board is excessive when the symptom set points squarely at a dead coin cell; the firmware itself is intact because the system boots and runs normally.
• CTime sync masks only the clock symptom while the BIOS settings still reset each cold boot, because the underlying coin cell can no longer retain firmware configuration.
• DA BIOS update does not give CMOS memory the standby power it needs, so settings and the clock will keep resetting until the depleted coin-cell battery is actually replaced.

A failed firmware update is exactly what vendor BIOS recovery exists for; the emergency key sequence or recovery USB reflashes a good image so the system can post and boot again.

• AAn OS reinstall cannot run because the firmware that initializes the hardware before any OS loads is corrupted; the machine never reaches a state where boot media is read.
• BThe timing pins to a failed firmware flash, not memory; swapping RAM ignores that the update was interrupted and that BIOS corruption is the documented cause of this no-display state.
• DA coin cell only retains settings and the clock; it cannot rebuild firmware erased by an interrupted flash, so replacing it leaves the corrupted BIOS image unrecovered.

Because RAID 0 has no fault tolerance, a single failed member loses the whole volume; the only path back is to rebuild the array and restore from a separate backup.

• ARAID 0 keeps no parity or mirror, so there is nothing on the surviving disk to rebuild from; expecting a parity rebuild misunderstands how striping without redundancy works.
• CA degraded-but-running mode exists for redundant levels like RAID 1 or 5; a RAID 0 stripe simply fails completely when any member drops, leaving no usable degraded state.
• DRe-cabling cannot reassemble interleaved stripes when half of every file is gone with the failed disk, so cable swapping does not recover a broken RAID 0 volume.

Moving the PC can unseat connectors, and a loose or faulty SATA data or power cable makes the drive vanish from firmware; reseating or swapping the cable is the first, cheapest check.

• AReinstalling Windows is impossible and pointless when firmware setup cannot even see the drive; a disk absent from BIOS is a connection or hardware issue, not a software one.
• BAn OS driver cannot help when the drive is invisible to firmware before Windows loads; a disk that BIOS does not detect must be addressed at the hardware/cabling layer first.
• CDisk Management can only act on drives the system already detects, and formatting would destroy data; neither applies to a disk that does not appear in firmware setup at all.

A refresh rate set far below the panel's capability produces visible flicker and eye strain; selecting the monitor's native higher refresh rate makes the on-screen image steady.

• BBacklight or inverter flicker fluctuates with brightness regardless of settings, whereas this flicker tracks an obviously low refresh rate, making a hardware replacement the wrong call.
• CReducing resolution does not raise the refresh rate that is actually causing the flicker, and it needlessly degrades image sharpness while leaving the 30 Hz setting in place.
• DTask Manager not flickering points away from a driver fault, and the visible 30 Hz setting identifies the cause directly, so a rollback addresses a problem the evidence does not support.

Windows keeps one default output, and audio is still routed to the PC speakers; selecting the HDMI monitor as the default playback device sends sound to the monitor's speakers.

• AA standard HDMI cable carries audio and video together on the same channels, so a working picture means the cable is fine; the issue is which output Windows is using.
• BAn OS reinstall is a heavy, data-risky step for a simple output-routing problem, and audio still functions through the PC speakers, proving the audio stack itself is healthy.
• DThe speakers have not been proven bad, and the most common cause is simply that Windows is still outputting to another device, so swapping the monitor is premature.

A device only appears for pairing while in discoverable mode and in range; placing the headset in pairing mode and re-adding it lets the laptop find and connect to it.

• AThe adapter shows normally and Bluetooth is on, so the driver is functioning; jumping to a reinstall skips the simpler, more likely cause that the headset is not yet discoverable.
• CWhile 2.4 GHz coexistence can affect throughput, it does not stop a device from appearing for pairing; the headset is missing because it is not in discoverable mode.
• DReplacing hardware that enumerates correctly and is powered on is unjustified; the symptom points to the peripheral not advertising itself, not to a failed internal radio.

The airplane icon and no listed networks after pressing function keys show the radio was switched off; re-enabling it with the Fn/wireless key or turning off airplane mode restores Wi-Fi.

• AOther users are connected through the same wireless network, so the access point is clearly up; the fault is local to this laptop, which is showing an airplane-mode indicator.
• BAn airplane-mode icon with the radio simply switched off is not evidence of failed hardware, so opening the laptop to replace the card is unwarranted before re-enabling the radio.
• CDHCP cannot assign any address while the radio is disabled and no SSIDs even appear, so an address renewal does nothing until the wireless function is turned back on first.

A link that flaps and follows the patch cable to another location signals an intermittent break or bad termination; testing and replacing the cable resolves the recurring drops.

• AThe fault following the patch cable to another desk points at the physical cable, not the driver, so reinstalling software ignores the strongest clue and is unlikely to help.
• BEvery other device on the same switch is stable and the problem moves with the cable, so the switch is exonerated and swapping it would be an expensive misdiagnosis.
• DHard-setting speed and duplex addresses throughput from a negotiation mismatch, not a link that physically drops and re-establishes, which a damaged cable explains far better.

A clean self-test with garbled jobs from the PC, starting after a Windows update, indicates a corrupt or incompatible driver; reinstalling the correct driver restores readable output.

• BThe printer's own self-test page prints perfectly, proving the formatter and engine are healthy; the corruption is introduced by the client's driver, not by failed printer hardware.
• CA bad cartridge causes faded, streaked, or blank output, not strings of wrong characters; the garbled content is a data-translation problem from the driver, not a supply issue.
• DReducing DPI changes image detail, not the page-description language the corrupt driver is mangling, so the printer keeps receiving garbled commands and keeps producing gibberish.

After implementing a fix the methodology calls for verifying full functionality, applying preventive measures where useful, and documenting findings, actions, and outcomes.

• ARe-theorizing is unnecessary because the cause is already confirmed and the fix worked; looping back to theory at this stage wastes time and skips the verification step that comes next.
• CClosing without verifying full functionality and documenting skips required final steps, risking an unrecorded recurrence and leaving no record for future troubleshooting.
• DEscalation belongs to the implement-or-escalate step and is pointless once the issue is already solved; the proper next move is to verify, prevent recurrence, and document.