If your SSD has stopped showing up in your computer entirely — not just failing to boot, but not appearing in BIOS, Windows, or even a USB enclosure — it's tempting to assume the worst. The good news is that in most of these cases your data isn't gone; it's just become inaccessible through normal means. The bad news is that getting it back usually requires professional-level diagnostics, not consumer software.
Two very different failure types
When an SSD stops being detected, the root cause almost always falls into one of two categories — and the distinction matters a lot for what recovery looks like:
- NAND failures — the actual flash memory chips are degrading. This happens gradually through normal wear, bad blocks, or uncorrectable errors, and is more common in drives that have seen heavy write cycles over their lifespan. (More on this in our guide to NAND degradation.)
- Controller failures — the chip that manages communication between the drive and your computer has stopped functioning correctly. This can be firmware corruption, a damaged power management IC (PMIC), a failed voltage regulator, or physical damage to the controller itself.
Controller failures tend to be more dramatic — the drive goes completely dark, with zero response from the BIOS or operating system — while NAND issues often show up more gradually, sometimes with warning signs first (SMART alerts, slow performance, occasional read errors).
The PMIC question
One failure mode we see fairly often involves the PMIC — the component responsible for regulating and distributing power to the rest of the drive, including the controller and memory chips. A damaged or shorted PMIC can prevent the controller from ever completing its boot sequence, which looks identical to a dead controller from the outside: no detection, no response, nothing.
Diagnosing which component is actually at fault requires more than plugging the drive in and hoping. In the lab, this typically means:
- Measuring current draw during power-on to rule out (or confirm) a short
- Checking whether downstream components, like onboard memory, are receiving power at all
- Thermal imaging the board to spot components running hotter than they should
- Probing individual voltage rails to see whether power is reaching the controller cleanly, or sagging and failing before it gets there
Why the encryption layer raises the stakes
On many modern SSDs, encryption keys are fused directly into the controller silicon. If the original controller can't be revived or repaired, that encryption can make the data permanently inaccessible — even though the raw data is technically still sitting on the NAND chips. This is one of the biggest reasons SSD recovery differs so much from traditional hard drive recovery, and why board-level repair (rather than a simple chip-off) is often the first and best option when the controller itself is salvageable. It's the same hardware-bound-key problem we cover for self-encrypting drives.
A word on "guaranteed recovery" claims
You'll find labs online claiming they can recover any Samsung SSD, controller failure or not. Be cautious of this. Samsung's firmware architecture is proprietary and largely locked down, and FTL (Flash Translation Layer) mapping support across recovery tooling is genuinely limited for many Samsung controller generations — especially newer ones. Some older SATA-era models (like the 840 and 850 series) have decent tool support for rebuilding a corrupted FTL. Many newer NVMe controllers do not, and firmware-level access simply isn't available industry-wide, regardless of what a lab advertises.
This doesn't mean recovery is impossible — board-level repair (replacing a failed PMIC or voltage regulator to bring the original controller back online) is often achievable and doesn't depend on firmware access at all. But if the controller itself needs firmware reconstruction rather than a hardware fix, be skeptical of any lab promising a guaranteed outcome before they've actually diagnosed the drive. It's the same honest principle we apply to every case — see our page on data recovery challenges.
What this means if your drive won't show up
If your SSD has stopped being detected:
- Stop powering it on repeatedly. Two or three attempts is enough information — beyond that, you risk making things worse.
- Don't run diagnostic or repair software against a drive that isn't detected at all. There's nothing for that software to act on, and some tools can make assumptions that cause additional damage.
- Get a professional evaluation before assuming the worst. Controller and PMIC failures are often recoverable through board-level repair or firmware-level reconstruction — but only if the drive hasn't been further stressed by repeated power cycles or DIY attempts.
Every drive that comes through our lab gets a full diagnostic before we tell you anything definitive about recoverability. If you're dealing with a drive that's stopped responding, we're happy to take a look.
SSD not detected — FAQ
My SSD isn't detected in the BIOS at all — is my data gone?
What's the difference between a controller failure and a NAND failure?
Can any Samsung SSD be recovered, like some labs claim?
Should I keep power-cycling an SSD that won't show up?
SSD gone dark and undetected? Start with a free evaluation — we'll diagnose it properly before saying anything definitive.
Request free evaluation →