Session 6: Storage, Memory & Boot Faults

The messages a machine shows before Windows loads are the firmware telling you what it could not do, and learning to read them is most of this session. 'No bootable device' or 'Boot device not found' means the firmware found no drive with a working boot sequence — which can be a disconnected drive, a changed boot order in the firmware, a corrupted boot record, or a failed drive. These have very different fixes, so you check the simplest first: is the drive detected in the firmware at all?

Beep codes are the firmware's alternative to a display. A pattern of beeps on a machine with no picture identifies the fault — commonly one long and two or three short for a memory fault, or a repeating pattern for a display fault. The meaning is specific to the firmware manufacturer, so you look up the pattern for that board rather than guessing. A spinning fan and no display usually points to RAM, the board, or the GPU. Endless restart loops often indicate faulty RAM or a corrupted operating system.

The discipline is to write the message down exactly, or photograph it. Customers describe errors loosely — 'it says something about a disk' — and the exact wording distinguishes a boot-order problem from a dead drive. Photograph the screen before doing anything else; it costs nothing and it is frequently the whole diagnosis.

A drive can be working and still failing, which is why you test rather than assume. Every modern drive reports its own health through S.M.A.R.T. — Self-Monitoring, Analysis and Reporting Technology — which tracks reallocated sectors, pending sectors, power-on hours and temperature. A drive with reallocated or pending sectors is degrading and will fail; how quickly is unpredictable, which is exactly why you do not wait.

Read S.M.A.R.T. with a free tool, or on Windows with `wmic diskdrive get status`, which returns OK or Pred Fail. For a mechanical drive, also listen — a clicking or grinding noise is a head or bearing failure and the drive must be treated as a data-recovery case immediately, not a repair case. Continuing to power a clicking drive can destroy the data permanently, and this is the single most important rule in this session.

An SSD reports differently: it has no moving parts to listen to, but it has a finite write endurance and reports its remaining life. The practical rule for both: if a drive shows any sign of degradation, back up the data first and replace the drive. There is no repair for a failing drive, only replacement — and the value you provide is getting the data off before it is gone.

Faulty RAM produces the most confusing symptoms in computing: random blue screens, restarts under load, files that corrupt for no reason, an operating system that fails to install. Because the symptoms are random, the only reliable approach is to test rather than to guess.

Two methods. Windows Memory Diagnostic runs from a restart and checks the installed memory, reporting errors afterwards — it is built in and adequate for a first pass. For a thorough test, MemTest86 boots from a USB stick and runs a long series of patterns, which is the professional standard; let it complete at least one full pass, ideally several, because some faults only appear after the memory has warmed or after many passes.

The physical approach complements it: with multiple sticks, test one at a time in one slot, which isolates both a bad module and a bad slot. And reseat first — a poorly seated stick causes exactly these symptoms and costs thirty seconds to rule out. The sequence is: reseat, then test each stick individually, then test each slot. That finds the fault without buying anything.

A corrupted boot sequence is common after a failed update, an improper shutdown or a malware infection, and it is usually repairable without touching the user's files. The sequence: boot from a Windows installation USB, choose Repair your computer rather than Install, and use the Startup Repair tool first, which fixes many cases automatically. If that fails, the command prompt in the recovery environment lets you rebuild the boot records with the `bootrec` commands — rebuilding the boot configuration data and rewriting the master boot record.

The critical rule is that you do not reinstall Windows as a first response. A reinstall overwrites the operating system and, depending on the choices made, can destroy the user's files. It is the last resort after boot repair has failed and after the data has been recovered. A technician who reaches for a reinstall first is a technician who destroys data, and customers remember that permanently.

Related and often confused: a changed boot order in the firmware produces the same 'no bootable device' message as a dead drive, and it is fixed in seconds by putting the correct drive first. Check it before assuming anything is broken — particularly after a battery replacement or a CMOS reset, which can reset the boot order as a side effect.

When a drive is failing, the order of operations determines whether the data survives. Stop using the machine immediately. Every write to a failing drive reduces the chance of recovery, and continuing to boot it, or attempting a repair, or running a disk check on a mechanically failing drive can finish it. This is the rule that separates a recovered family photograph archive from a lost one.

The safe sequence: power down, remove the drive, connect it to a healthy machine through a USB adapter as a secondary drive rather than booting from it, and copy the most important files first — documents, photographs, anything irreplaceable — before attempting a full copy. Copy, never move; the original stays untouched until you are certain. If the drive is mechanically clicking, stop and refer it to a professional data-recovery service; no software will help and continuing makes it worse.

Then be honest about what you can and cannot do. Software recovery from a logically damaged but physically healthy drive is well within your scope and is a genuinely valuable service. Physical recovery — opening a drive in a clean room, swapping heads — is a specialist discipline requiring equipment you do not have, and referring it out is the correct professional answer. Customers respect a referral; they do not respect a technician who takes money and destroys the drive.