Failing Storage, Failing Memory and Hardware Safety
Where you are: Module 8 — Computer and Hardware Troubleshooting · Lesson 8.3 · Based on Chapter 8 (§8.5–8.6 and the Safety First box) of Dr. Tahseen Al Doori's Troubleshooting Essentials.
What you'll be able to do
- Recognise the warning signs of failing storage and failing memory.
- Explain why a suspected failing drive is backed up before any troubleshooting.
- Describe how memory is tested and how a faulty module is isolated.
- Follow the complete safety routine before opening any computer.
Watch: Failing Storage, Failing Memory and Hardware Safety
The video contrasts two fictional machines: one with a drive that has begun to click, one that crashes at random. It shows why the order of actions matters so much with storage, how memory faults are tested and isolated, and the safety routine that comes before any of this work. Keep these questions in mind:
- What is S.M.A.R.T., and where does its information come from?
- Why can troubleshooting a failing drive make things worse?
- How would you find which of four memory modules is faulty?
Back up first, troubleshoot second. If storage failure is suspected, back up immediately and stop unnecessary use: every operation on a failing drive can make recovery harder. Do not run disk repairs such as chkdsk /f or fsck, defragmentation or repeated restarts on a drive that may be failing and holds the only copy of important data. If a backup is not possible, escalate (Module 13); data recovery is specialist work.
Failing storage (§8.5)
Storage is where every file lives, so a storage fault is the one most likely to cause permanent loss. The book lists these warning signs:
- clicking or grinding noises from a hard disk;
- very slow file access;
- files that become corrupt;
- disk errors in the event log.
Health can be checked with the drive's S.M.A.R.T. status using manufacturer tools. S.M.A.R.T. stands for Self-Monitoring, Analysis and Reporting Technology: the drive keeps its own records of errors and wear and can report when it predicts trouble. A S.M.A.R.T. warning is strong evidence; weigh it together with the other signs (noises, slowness, corrupt files and log errors) rather than relying on any single reading.
The book's rule is unusually firm, and it reverses the normal order of the methodology. In most problems you identify, theorise and test before acting. With suspected storage failure, protecting the data comes before diagnosis:
- Back up immediately the files that matter most, most important first.
- Stop unnecessary use. Do not install tools, run scans or leave the computer working on large tasks.
- Only then investigate: S.M.A.R.T. status, event log errors, the drive's connection.
- Escalate if the backup fails or the data is critical.
Why? A failing hard disk may be physically damaged. Every read, write and repair attempt makes it work harder, and a repair tool rewrites the file system on a device that may not survive the process. This is principle 6 from Module 2, protect what matters, applied where the stakes are highest.
Beyond the book (2026 note): On Windows 11, Microsoft shows drive health under Settings > System > Storage > Advanced storage settings > Disks & volumes, then Properties for the drive, including estimated remaining life, available spare and temperature; Microsoft notes that Windows monitors only NVMe solid-state drives this way, not SATA SSDs or hard disks, and urges you to back up if a warning appears. On a Mac, Apple advises that if Disk Utility reports a disk is about to fail, you should back up your data and replace the disk, because it cannot be repaired. Sources: What to do about a critical warning for a storage device — Microsoft Support · Repair a storage device in Disk Utility — Apple Support
Failing memory (§8.6)
Memory (RAM) holds the programs and data the computer is using right now. When a memory module is faulty, data can be corrupted silently as it passes through, so the symptoms look random:
- random crashes;
- error screens (on Windows, often with memory-related stop codes);
- corrupted files;
- failure to boot.
Because these symptoms overlap with software faults, test the theory rather than assume it. The book names two tools:
- Windows Memory Diagnostic, built into Windows.
- MemTest86, a separate memory-testing tool; follow its publisher's instructions.
On desktops, isolate a faulty module by testing with one module at a time. This is remove-and-restore from Module 6: with four modules installed, remove all but one, test, then swap. The module that fails the test, or the configuration in which crashes return, identifies the faulty part. Each swap means opening the case, so the safety routine below applies every time. Where memory cannot be removed, as in some laptops, a confirmed memory fault is a repair for the manufacturer or a qualified technician.
Beyond the book (2026 note): Microsoft's current steps for Windows Memory Diagnostic: save your work, press Windows key + R, enter mdsched and select OK, then choose Restart now and check for problems (recommended). The test runs automatically after the restart; Standard tests run by default and Extended tests (selected with F1, applied with F10) are more thorough but slower. Results appear in a notification after you sign in, or in Event Viewer, where event ID 2001 means no memory errors were detected. On a Mac, Apple Diagnostics checks hardware: on Apple silicon, hold the power button until Options appears, then hold Command (⌘)-D; on an Intel Mac, hold D at start-up. Sources: How to fix Error 0xA: IRQL_NOT_LESS_OR_EQUAL — Microsoft Support · Use Apple Diagnostics to test your Mac — Apple Support
While you are learning, run memory and hardware diagnostics on a training machine. They take the computer out of use and restart it, and on a computer that may also have a failing drive, backing up the drive comes first.
Hardware safety (Chapter 8 Safety First box)
Before opening any computer, follow the book's routine in full, every time:
- Shut down properly (not sleep).
- Unplug the power cable.
- Remove the battery where possible.
- Press the power button to discharge any remaining charge.
- Wear an anti-static strap, connected correctly, to protect components from electrostatic discharge.
- Do not open equipment under warranty without authorisation.
And from Chapter 7: never open power supplies or monitors, because they can hold dangerous charges even when unplugged. From Chapter 13: burning smells, smoke, sparks, swollen batteries, exposed wiring or water near electricity mean stop and escalate.
Worked example
(Fictional scenario.) An architect's desktop has started making a faint clicking sound, and opening project files takes minutes instead of seconds. One file would not open this morning.
- Recognise the pattern: clicking, very slow access and a corrupt file are three of the book's four warning signs.
- Protect first: the technician stops all other work and copies the current projects to an external drive, newest first. The copy is slow but completes.
- Investigate: the manufacturer's tool reports a S.M.A.R.T. warning, and the System log shows disk errors going back a week.
- Plan and implement: the drive is replaced and the data restored from the new backup. No repair tool was run on the failing drive.
- Verify and document: the architect opens his projects at normal speed; the ticket notes that the event log warnings had been present for a week, and monitoring for disk errors is added (prevention, Module 12).
Try it
A planning exercise; do not run disk repairs or open your computer.
- Write your personal failing drive plan: which three folders you would back up first, where to (and whether you have a working backup today), and who you would escalate to.
- Find where your system shows drive health (manufacturer tool, Windows Disks & volumes, or Disk Utility) and record what it reports, without running any repair.
- Write the six-step safety routine from memory, then check it against the book's list.
Completion criteria: a dated backup plan naming folders, destination and escalation contact; a recorded drive-health reading or a note that none is available; and a correct six-step safety routine.
Knowledge check
A hard disk has started clicking and files open very slowly. What should you do first?
What does S.M.A.R.T. provide?
A desktop with four memory modules crashes at random. How does the book suggest isolating a faulty module?
Which step is part of the book's safety routine before opening a computer?
Answers explained — 1: the book's rule is back up first, troubleshoot second; repairs, defragmentation and repeated restarts all make a failing drive work harder. 2: S.M.A.R.T. is the drive's self-monitoring and reporting; memory testing and startup lists are different tools. 3: one module at a time is remove-and-restore; the power supply, SFC and a reinstall do not test individual modules. 4: the safety routine is shut down, unplug, remove the battery, discharge and wear a strap; staying plugged in, opening a power supply or removing the strap are all unsafe.
Key takeaways
- Failing storage shows as noises, very slow access, corrupt files and disk errors in the log; check S.M.A.R.T. status.
- Suspect storage failure: back up first, troubleshoot second, and stop unnecessary use.
- Failing memory causes random crashes, error screens, corrupt files and boot failures; test with Windows Memory Diagnostic or MemTest86 and isolate one module at a time.
- Before opening any computer: shut down, unplug, remove the battery, discharge, wear an anti-static strap, respect the warranty.
Sources
- Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), §8.5–8.6, Chapter 8 Safety First box, §7.5, §13.1, Glossary (S.M.A.R.T.)
- What to do about a critical warning for a storage device — Microsoft Support
- Repair a storage device in Disk Utility — Apple Support
- How to fix Error 0xA: IRQL_NOT_LESS_OR_EQUAL — Microsoft Support
- Use Apple Diagnostics to test your Mac — Apple Support
