Your '100% Health' SSD score is a trap: The hidden signs of silent data corruption

SSDs have a lot of behind-the-scenes error correction. That's fantastic, but it also means they can fail at 100% health, and you'll be none the wiser.

Sometimes, the warning signs of a failing SSD, or even just file corruption, are subtle enough that you won't notice them until it's much too late. Here's what you need to watch out for and what to do if any of these happen to you.

SSDs aren't error-proof

Trusting them too much can backfire.

SSDs do a lot of silent cleanup behind the scenes. Error correction (ECC), wear leveling, and spare blocks are all housekeeping tasks that your SSD tackles on a daily basis to make sure it runs well. Filling your SSD close to full adds another layer of work for the drive, too.

The scary part is that an SSD can look like it's absolutely fine as it works its way through these tasks, but there might be cracks underneath the surface that aren't obvious at a glance.

It all comes out when it hits an error it can't correct.

Many people (myself very much included) use tools like CrystalDiskInfo to track SSD health and try to prevent disaster. They're good, but the 100% health number can be a trap , too. On most drives, it's mainly a wear indicator, not a promise that all of your data is intact. You can have a drive that reports healthy life remaining while still throwing read errors, integrity errors, or behaving inconsistently.

What file corruption really looks like

Blink and you might miss it.

Corruption can really sneak up on you. It rarely shows up as a dramatic failure. Instead, you'll deal with annoying stuff that's easy to forget about when it's over: an archive you can't extract, a failed installation, a crash or a freeze here and there, or a project that seems to have some files missing. Running into an error just once makes it easy to blame it on the software, but it could instead be an indication that your SSD is having a bad time.

Archives are a big tell because they verify their own contents. If you see errors cropping up while extracting, that's a sign that the copy you just made might not be intact. The same goes for apps like game launchers or backup tools, as those tend to do verification checks and will catch mismatches quicker than you might.

Another symptom of corruption is when files copy just fine, but still don't work on the destination drive. This is perhaps the worst kind, because the transfer completes, the file size looks right, and everything looks fine until you try to open it later. If a file works on the source drive but breaks after copying it over, that could be a corruption problem that you're dealing with.

The weakest link isn't always the SSD

Look at the big picture if there are no obvious faults.

When it comes to internal SSDs, your data has a long way to travel, and something can go wrong during any of the "stops" on its journey.

Data travels through the RAM, the CPU, drivers, and the storage controller before it ever lands on the drive.

Any instability along that path can result in a corrupted file that appears to be perfectly fine until you try it. As a result, the SSD might be where you spot the problem, but not necessarily where it started.

How can you tell where the problem really lies? Unfortunately, you'll just have to troubleshoot. SATA SSDs (which aren't super relevant anymore, but hardly obsolete) can misbehave due to issues with cables or ports, leading to communication errors. NVMe drives aren't immune to similar annoyances, such as a slightly loose M.2 stick or a poorly seated SSD and/or heatsink can lead to timeouts and resets.

The biggest clue is system stability. If you're overclocking your CPU or your RAM or undervolting, something else might be struggling, leading to errors along the way. Transferring, encrypting, or compressing large files will put your system under load, exposing problems that may not show up in day-to-day use.

Portable storage adds a second failure chain

A lot more can fail when the SSD is outside your PC.

Up until now, I've talked about the quiet ways an internal SSD can fail you, but what about portable SSDs? Oh, those can fail, too, and often in more spectacular ways than their M.2 NVMe counterparts.

Portable SSDs rely on more than just the drive itself. They also depend on the USB bridge controller, firmware, a cable, and a port or a hub. That's why some portable SSDs can be shockingly slow , and why putting NVMes in enclosures is often a waste of money ; the failure chain is a lot longer when there are even more elements that come into play.

We're not talking about catastrophic failure here, though. Any one of those could glitch during file transfer and create file corruption that you might not be aware of.

Power is a big part of it. If the port can't deliver stable power during long writes, or a hub is splitting power across multiple devices, you can get brief disconnects. The SSD might seemingly pick up the transfer where it left off, but in reality, something could be wrong.

To avoid these issues when using portable drives, try to use the most reliable accessories you have on hand, and plug directly into your PC instead of a hub. The back panel ports are always a better choice than the front panel, which may add some extra latency.

How to catch corruption early

Keeping your files safe doesn't have to be a full-time job.

File corruption will sometimes produce warnings, but other times, you'll just be doing your thing, trying to access a file or an archive, and something will be broken. Fortunately, there's a way to avoid that.

You can't fully save your SSD (or any storage media) from dying, but you can largely save your files from the worst disasters.

First, for transfers, make sure to verify important files and archives before you delete the original. Don't just assume it's fine. Try to run the file on the destination drive, and only if everything is as it should, delete the source. For big folders, you can spot-check a few large, important files with a hash (PowerShell Get-FileHash) and make sure the source and destination files match.

---

If you keep seeing corruption symptoms, stop using the drive for writes; it might not be safe. Instead, consider backing up all your files (the 3-2-1 rule is a good one to follow) and try to see whether the drive behaves differently in another PC or enclosure. That can sometimes help catch the culprit if it's not the drive itself.