Skip to main contentSkip to navigation
Rossmann Repair Group logo - data recovery and MacBook repair

NVMe SSD Not Detected in BIOS? 5 Diagnostic Steps Before You Give Up

Quick Answer: If your NVMe SSD is not detected in the BIOS after reseating and testing in another system, the controller has likely failed. Software cannot fix this. Professional recovery uses hardware tools like PC-3000 to bypass the controller and extract data directly from the NAND. Cost: $200-$1,500 at Rossmann Repair Group.

When your NVMe SSD disappears from the BIOS and Windows Disk Management, the motherboard has lost communication with the drive's controller. Software cannot fix a drive that is not presenting itself to the system. Follow these diagnostic steps to determine whether you have a simple connection issue or a hardware failure requiring professional recovery.

No Data, No Fee. Call (512) 212-9111

Louis Rossmann
Written by
Louis Rossmann
Founder & Chief Technician
Updated 2025-01-15
1

Reseat the Drive

Power off the computer. Remove the M.2 retaining screw with a Phillips screwdriver. Pull the drive straight out of the slot. Clean the gold edge connector with 90%+ isopropyl alcohol and a lint-free cloth to remove any oxidation or dust. Let it dry for 30 seconds, then reseat the drive firmly until the connector is fully inserted and the screw holes align.

A loose or partially seated NVMe drive is the most common reason for a BIOS detection failure that is not caused by hardware damage. The M.2 connector uses a high-density layout with up to 75 pin positions. Even a fraction of a millimeter of misalignment... A fraction of a millimeter of misalignment is enough to lose signal integrity on the PCIe lanes.

2

Check the M.2 Standoff Position

M.2 drives come in four standard lengths: 2230, 2242, 2260, and 2280. The number represents the width and length in millimeters. Most desktop and laptop NVMe drives are 2280 (22mm wide, 80mm long), but compact laptops and the Steam Deck use 2230.

If the standoff is in the wrong position, the screw forces the PCB to flex at the connector end. This can crack solder joints on the controller or NAND packages, or prevent the gold fingers from seating at the correct depth. Verify the standoff is in the hole that matches your drive's length before screwing it down.

Common mistake: Some motherboards ship with the standoff pre-installed at the 2260 position. A 2280 drive screwed into a 2260 standoff will flex upward at the far end, lifting the connector pins out of the slot.

3

Check Disk Management vs. BIOS

This step determines whether you have a software problem or a hardware problem. Boot into your BIOS/UEFI setup (typically by pressing F2, DEL, or F12 during POST) and look for the drive in the storage or NVMe device list.

Visible in BIOS, Not in Windows

The drive hardware is functional. The issue is a missing partition table, an uninitialized disk, or a file system Windows does not recognize. Open Disk Management (diskmgmt.msc). If the drive appears as "Unallocated" or "Not Initialized," this is recoverable with software tools or by assigning a drive letter. Do not format if you need the existing data.

Absent from BIOS Entirely

The motherboard cannot detect the drive at the hardware level. No operating system, driver, or software tool can access a device the BIOS does not see. This points to a connection problem (Steps 1-2), a dead M.2 slot (Step 4), or a failed controller/power component on the SSD itself (Step 5).

4

Try a Different Slot or System

Test the drive in a second M.2 slot on the same motherboard if one is available. Many motherboards have two or more M.2 slots, and they connect through different PCIe lanes. A failed PCH lane or a dead slot does not mean the drive is bad.

If no second slot is available, test the drive in a different computer. You can also use an external M.2 NVMe USB enclosure, though some enclosures do not support all NVMe drives. If the drive appears in the second system's BIOS, the original motherboard slot is the problem, not the SSD.

If the drive fails to appear on any system, proceed to Step 5.

Common False Alarms Before Assuming Failure

M.2 SATA vs. M.2 NVMe Keying Mismatch

M.2 is a physical connector, not a protocol. An M.2 drive can be SATA or NVMe, and they use different pin configurations (keys). NVMe drives have an M-key notch (a single gap on the right side of the connector). SATA M.2 drives have a B+M key (gaps on both sides). Most modern motherboard M.2 slots support only NVMe. Plugging an M.2 SATA drive into an NVMe-only slot produces zero detection in BIOS; the drive is not broken, it is in the wrong slot.

Check your motherboard manual. Slots labeled "M.2 (PCIe)" or "M.2 (NVMe)" do not accept SATA drives. Slots labeled "M.2 (PCIe/SATA)" accept both. If you have a SATA M.2 drive in a PCIe-only slot, moving it to a compatible slot or using a SATA adapter will restore detection.

PCIe Lane Allocation and BIOS Settings

On many consumer motherboards, M.2 slots share PCIe lanes with SATA ports. Enabling a second M.2 NVMe drive disables SATA ports 5 and 6. Some boards disable an M.2 slot entirely when a SATA device is connected to a shared port. This is documented in the motherboard manual under "M.2 / SATA sharing" or "Storage Configuration."

If your NVMe drive was working and disappeared after adding a new SATA device (or vice versa), check BIOS storage configuration. Intel platforms route some M.2 lanes through the PCH; AMD platforms route the primary M.2 slot directly from the CPU. The CPU-direct slot is always available. PCH-routed slots depend on what else is connected to the chipset.

5

This Is a Controller Failure

If the NVMe SSD is absent from BIOS on multiple systems after reseating and verifying the standoff, the controller chip or a power regulation component on the SSD PCB has failed. The drive is not communicating on the PCIe bus at all.

No software, driver update, or BIOS setting will fix this. The controller is the processor that manages all communication between the NAND flash and the host system. When it fails, the drive becomes electrically invisible to the motherboard. Your data is still stored on the NAND chips, but nothing can read it through normal channels.

Professional recovery path: Tools like the PC-3000 SSD utility can interface with the controller at the firmware level, bypass the failed initialization routine, and extract data directly from the NAND. In cases where the controller is completely dead, chip-off NAND reading may be an option for older drives without hardware encryption.

Common NVMe controllers that fail this way include Samsung Elpis and Phoenix (found in the 970 EVO, 980 Pro, 990 Pro), Phison E12/E16/E18, and Silicon Motion SM2262EN/SM2264. Each requires a controller-specific recovery procedure.

Free evaluation. $200-$1,500. No data, no fee.

What Not to Do

Once you have confirmed the drive is invisible to the BIOS on multiple systems, stop troubleshooting. The following actions risk making recovery harder or impossible.

  • Do not flash BIOS updates hoping it will detect the drive. A BIOS update changes your motherboard firmware. It cannot fix a dead SSD controller.
  • Do not use a heat gun or "reflow" the SSD. Heating an NVMe drive damages the NAND flash chips. NAND is temperature-sensitive, and uncontrolled heat degrades the charge stored in the cells, reducing recovery odds.
  • Do not repeatedly power cycle the drive. Each power-on attempt forces the controller to attempt initialization. On a partially failed controller, this can cause further damage to the firmware area stored on NAND.
  • Do not open the SSD or desolder components. NVMe SSDs have no user-serviceable parts. Removing the controller or NAND packages without the right equipment and firmware knowledge destroys recovery options.

NVMe SSD Recovery in the Lab

SSD Recovery Pricing

NVMe controller failure recovery follows our standard SSD recovery pricing tiers. Free evaluation, firm quote before work begins. No data = no charge. Call (512) 212-9111.

Service TierPriceDescription
Simple CopyLow complexity$200

Your drive works, you just need the data moved off it

Functional drive; data transfer to new media

Rush available: +$100

File System RecoveryLow complexityFrom $250

Your drive isn't showing up, but it's not physically damaged

File system corruption. Visible to recovery software but not to OS

Starting price; final depends on complexity

Circuit Board RepairMedium complexity – PC-3000 required$600–$900

Your drive won't power on or has shorted components

PCB issues: failed voltage regulators, dead PMICs, shorted capacitors

May require a donor drive (additional cost)

Firmware RecoveryMedium complexity – PC-3000 required$900–$1,200

Your drive is detected but shows the wrong name, wrong size, or no data

Firmware corruption: ROM, modules, or system files corrupted

Price depends on extent of bad areas in NAND

Advanced Board RebuildHigh complexity – precision microsoldering and BGA rework$1,200–$1,500

Your drive's circuit board is severely damaged and requires advanced micro-soldering

Advanced component repair. Micro-soldering to revive native logic board or utilize specialized vendor protocols

50% deposit required upfront; donor drive cost additional

Hardware Repair vs. Software Locks

Our "no data, no fee" policy applies to hardware recovery. We do not bill for unsuccessful physical repairs. If we replace a hard drive read/write head assembly or repair a liquid-damaged logic board to a bootable state, the hardware repair is complete and standard rates apply. If data remains inaccessible due to user-configured software locks, a forgotten passcode, or a remote wipe command, the physical repair is still billable. We cannot bypass user encryption or activation locks.

All tiers: Free evaluation and firm quote before any paid work. No data, no fee on all tiers (advanced board rebuild requires a 50% deposit because donor parts are consumed in the attempt).

Target drive: The destination drive we copy recovered data onto. You can supply your own or we provide one at cost. All prices are plus applicable tax.

Frequently Asked Questions

Can data be recovered from an NVMe SSD that is not detected in BIOS?
In most cases, yes. When the NVMe controller fails, the NAND flash chips still retain the stored data. Professional recovery tools like PC-3000 can interface with the controller at the firmware level, bypass the failed initialization, and extract data directly. For drives with completely dead controllers, chip-off NAND reading is an option on older drives without hardware encryption.
Why did my NVMe SSD suddenly stop being detected?
The most common cause is controller or PMIC (power management IC) failure. NVMe controllers are sensitive to power events: surges, unstable PSU output, and sudden shutdowns during firmware operations. The controller dies, the drive disappears from BIOS, but the NAND retains the data. Less common causes include a failed M.2 slot on the motherboard or physical damage to the edge connector.
Is an NVMe SSD that shows in BIOS but not in Windows recoverable?
Yes, and this is a better scenario than not appearing in BIOS at all. If BIOS detects the drive, the controller is functional. The issue is at the partition or file system level: corrupted partition table, raw/uninitialized state, or file system damage. This is often recoverable with software tools without needing professional hardware intervention.

NVMe drive missing from BIOS?

Free evaluation. $200-$1,500. No data, no fee. Ship your drive to our Austin lab.