Inside the lab follow MDrepairs on YouTube, TikTok & Instagram - visit our YouTube channel ↗

Data Recovery Guide

NVMe SSD Not Detected in BIOS: What Failed and What's Next

Updated November 17, 2026
In this article

An NVMe SSD missing from BIOS may have a connection, compatibility, power, firmware, controller, or NAND fault. It is not automatically empty or recoverable. If it holds your only copy, stop repeated power cycles, firmware updates, and repair utilities.

Modern encrypted NVMe SSDs cannot be recovered simply by removing their NAND chips. Recovery depends on restoring a viable original or specifically supported reading path. PC-3000's ability to connect an NVMe drive does not establish advanced firmware support for every controller.

Why an NVMe SSD Disappears from BIOS

BIOS or UEFI must detect the device before the operating system can use its normal storage interface. A drive may be absent because the slot is incompatible or disabled, a connection is damaged, or the SSD cannot initialize. A firmware or NAND problem can look similar to an electrical failure from the outside.

M.2 describes a form factor, not one universal protocol. An M.2 SATA device and an M.2 PCIe/NVMe device require compatible host support. Check the computer or enclosure documentation rather than assuming that physical fit proves compatibility.

Connection and power problems

A damaged connector, broken component, or inadequate power path can prevent an SSD from starting. If a basic compatible connection check is appropriate and you are comfortable handling the hardware, shut the system down first. Do not flex the PCB, probe live contacts, or repeatedly reseat a damaged drive.

Firmware and translator faults

The controller needs service information and mapping structures to expose logical sectors. Damage to these structures can cause a fallback identity, incorrect capacity, or no normal detection. Recovery depends on what survives and whether the exact controller and firmware have a supported method.

NAND degradation

Unreadable NAND can affect user data, service information, or both. A dead-looking SSD does not prove that its memory is intact. Bad blocks and uncorrectable errors can make extraction partial or impossible even when the controller responds.

Safe Checks Before Sending the SSD to a Lab

  1. Record the history. Note the actual model, what happened before failure, and any formatting, updates, encryption, or previous recovery attempts.
  2. Check compatibility. Confirm that the slot or enclosure supports PCIe/NVMe and the device's form factor. A BIOS boot menu is not always the same as the storage-device inventory.
  3. Check one known-good connection where appropriate. Avoid repeated testing if the SSD heats abnormally, disconnects, or has visible damage.
  4. Protect data before repairs. If the device returns, prioritize important files. If reads fail or it drops offline, seek controlled extraction rather than running repeated full scans.
  5. Keep the original parts. Do not discard or replace the SSD before the data question is resolved. A warranty replacement does not recover files.

Do not initialize a drive that suddenly appears as unallocated or the wrong size. Do not run CHKDSK, format, secure erase, PSID revert, or manufacturer production utilities as a recovery experiment.

Visible in BIOS but Missing in Windows

This is a different symptom from no hardware detection. The SSD may have a missing drive letter, a locked volume, damaged file-system metadata, unreadable sectors, or another storage-stack problem. A normal model and capacity are useful observations, but they do not prove healthy NAND.

For reliable sector access and logical damage, recovery software can work from a separate image. A normal software scan cannot read through an unsupported firmware fault or a controller that does not return user sectors. Our SSD not showing up guide explains this distinction.

How Professional NVMe Recovery Works

Electrical assessment and original-board repair

The lab checks power and controller behavior and identifies repairable board faults. Repair aims to obtain access to the data, not to certify the failed SSD for continued use. Preserve components and device-specific information required by the original encryption path.

Supported technological access

For certain controller and firmware combinations, PC-3000 SSD can use a compatible loader and technological mode. A controller must still function sufficiently to execute the supported operations and reach the NAND. The tool does not replace electrically dead silicon.

Virtual-translator reconstruction

A supported utility may reconstruct logical mapping from surviving information, allowing extraction outside the damaged normal translation path. This can help with particular firmware failures and, in limited supported cases, data that remains physically present after deallocation. It cannot reconstruct physically erased cells or missing cryptographic keys.

Controlled extraction

Where sectors can be read, a hardware-assisted workflow can manage timeouts, limited retries, resets, and progress maps. Priority-file extraction may be useful for unstable storage. The lab records unreadable areas and validates the requested files instead of equating a completed imaging task with a perfect result.

PC-3000, DeepSpar, Dolphin, and Raw-NAND Tools

Tool familyRelevant roleLimit to check
PC-3000 SSDSupported firmware access and virtual translationExact controller, firmware, NAND restrictions, and available recovery operations
DeepSparHandling unstable reads through supported storage interfacesNeeds a usable device path; does not decode removed encrypted NAND
Dolphin Data Lab SSD toolsDocumented loader/translator workflows for selected controllersA generic controller overview is not universal recovery support
PC-3000 Flash / Rusolut VNRRaw-NAND reading and reconstruction on supported flash devicesNot an encryption bypass for modern NVMe SSDs

ACE Lab's published list distinguishes controller and firmware support from ordinary imaging. Its Phison E18 entry is marked repair-only. Do not infer modern Samsung NVMe or WD in-house controller support from older SATA models or other controllers sold under the same brand.

Chip-Off Recovery for NVMe: The Hard Limit

On modern encrypted NVMe SSDs, removed NAND contains encrypted and controller-organized data. A perfect dump is not a usable file image. Reconstructing interleaving, error correction, and translation does not supply a missing encryption key.

This matters particularly when someone offers chip-off as the automatic next step after a Samsung NVMe controller dies. That is not a viable general promise. A donor controller of the same model does not automatically possess the original drive's required information.

Transferring necessary original components to a compatible board to repair damaged circuitry is a different procedure from reading NAND independently. Some legacy unencrypted SSD designs permit raw-NAND reconstruction, but that exception cannot be extended to modern encrypted NVMe devices. Read our chip-off guide for the distinction.

Bad Blocks, Heating, and Cooling

Controlled temperature changes sometimes improve reads from unstable NAND or electronics. A lab monitors the device and checks whether the reading result improves. Heating does not necessarily help, cooling does not necessarily help, and there is no universal temperature that restores a failed SSD.

Read-retry settings, when supported, adjust sensing behavior to help distinguish stored charge states. These are not the same as supply-voltage changes or XOR descrambling. None of these techniques bypasses encryption, restores overwritten data, or makes every unreadable region recoverable.

TRIM, NVMe Deallocation, and Deleted Files

NVMe deallocation tells the drive which logical blocks are no longer needed. The controller can stop exposing the previous contents before garbage collection physically erases them. There is no universal recovery deadline or guarantee that powering down leaves recoverable files.

A hardware failure is not proof that every live file was trimmed. Conversely, intact-looking NAND is not proof of recoverability. The original loss, subsequent operations, remaining data, and supported access must be considered together.

Recovery Cost and Turnaround

MDrepairs lists SSD/NVMe recovery at $1,000–$2,000+ depending on the case. The $100 diagnostic is credited toward a successful recovery. It is non-refundable once diagnostics start; donor drives or replacement parts you approve are non-refundable once ordered, even if recovery fails. You review and approve the recovery estimate before work starts. See current pricing and SSD recovery services.

Timing depends on the fault, parts, supported methods, and read stability. There is no higher-priced encrypted-chip-off tier that guarantees access. If the required controller or encryption path is irretrievable, the assessment may find that recovery is impossible.

Frequently Asked Questions

Can an NVMe SSD missing from BIOS be recovered?

Sometimes. A repairable connection or power fault may leave a route to the data, while unsupported firmware, damaged NAND, or a lost encryption path can prevent recovery. No-detection alone does not establish the outcome.

Can PC-3000 recover every NVMe drive?

No. Advanced recovery support depends on the controller, firmware, and sometimes NAND configuration. Being able to connect or image a responsive drive is different from supporting its internal firmware and translator.

Can you chip-off a Samsung NVMe if its controller is dead?

Independent raw-NAND chip-off is not a file-recovery fallback for modern encrypted Samsung NVMe SSDs. The necessary original or specifically supported reading and encryption path must remain recoverable.

Does a donor controller decrypt the original NAND?

Not simply because the model and firmware match. Device-specific encryption information may be required. Preserve the original electronics and obtain an assessment before donor work.

Should I try firmware updates or a freezer?

No. Do not experiment with firmware or household temperature treatments on your only copy. Preserve the complete device and seek assessment of a supported recovery method.

Technical References

Lost your data?
Let's assess your options.

Estimated turnaround: 4–6 weeks; timing may vary by case. Start with a free initial quote. The $100 lab diagnostic is credited on success; diagnostic and approved parts charges apply on failure.

Split the cost of your recovery with Affirm. Explore financing Subject to eligibility.

Devices recovered at our lab

These rows come from BenchKey, the ticket system we built for our own shop. Customer names, contact details and descriptions are left out.

Hard drive platter and head arm under green light at our Lincroft lab
An opened hard drive's platter and head arm sit under green inspection light at our Lincroft lab.
4.6 · 345 Google reviews$100 diagnostic, credited toward a successful recovery
Start your mail-in recovery