Why Is My SSD Not Detected in BIOS September 2026 Guide

Your SSD is not detected in BIOS because of a loose or faulty SATA/M.2 connection, incorrect BIOS settings (wrong SATA mode, disabled ports, or CSM/UEFI conflicts), outdated BIOS firmware, power supply issues, or a failed SSD controller. Most detection failures are caused by connection or configuration problems, not hardware death.

I have helped dozens of people troubleshoot this exact issue across forum threads, Discord channels, and in-person PC builds. The panic when a drive full of data vanishes from BIOS is real, and I understand the urgency. Over the years, I have seen every variation of this problem, from a simple loose cable that took 10 seconds to fix, to an NVMe drive that needed a BIOS rollback after a botched update.

If you are asking why your SSD is not detected in BIOS and how to fix it, this guide walks you through every possible cause and solution in order of likelihood. You do not need advanced technical knowledge. I will define every term, provide exact BIOS key combinations for your motherboard brand, and give you a symptom-to-cause-to-fix table so you can skip straight to the fix that matches your situation.

Most people resolve this issue within the first three steps. But I have also included advanced troubleshooting sections for edge cases that other guides skip entirely, including Intel RST/VMD driver conflicts, CMOS resets, the power cycle trick for a locked SSD controller, and how to tell if your SSD is actually dead versus just misconfigured.

Quick Summary: SSD Not Detected in BIOS

Before diving into detailed troubleshooting, here is a quick-reference summary of the most common causes and the fastest fixes. I recommend scanning this list first, then jumping to the detailed step that matches your symptom.

The 5 most common reasons your SSD is not detected in BIOS:

1. Loose or faulty SATA cable or M.2 not seated properly (most common, easiest fix)
2. Wrong SATA mode set to IDE or RAID instead of AHCI in BIOS
3. SATA port or M.2 slot disabled in BIOS settings
4. Outdated BIOS firmware that does not support your NVMe drive
5. Intel VMD (Volume Management Device) blocking NVMe detection on Intel 11th Gen and newer platforms

Quick-fix flow: Check cables first. Then enter BIOS and verify SATA mode is set to AHCI. Confirm the specific port or slot is enabled. If you have an NVMe drive on an Intel platform, check for VMD settings. Still nothing? Update your BIOS or test the drive on another computer.

When to stop DIY troubleshooting: If the SSD is not detected on any computer, in any BIOS, with any cable, and makes no sound or shows no signs of life, it may have a failed controller or NAND flash. At that point, professional data recovery or a warranty replacement is your next step.

Why Is My SSD Not Detected in BIOS? (Root Causes)

Understanding why your SSD is not detected in BIOS starts with knowing how the detection process works. When you power on your computer, the BIOS or UEFI firmware performs a Power-On Self-Test (POST). During POST, the motherboard scans all connected storage interfaces, including SATA ports and M.2 slots, looking for devices.

For a SATA SSD, the motherboard sends a signal through the SATA data cable to the SSD’s controller chip. The controller responds with identification data, including the drive model, capacity, and serial number. For an NVMe M.2 SSD, the motherboard communicates through PCIe lanes directly to the drive’s controller.

If anything breaks this communication chain, the BIOS cannot see the drive. Here are the 10 root causes I encounter most frequently, ranked by how common they are:

1. Loose or Faulty SATA Cable Connection

This is the number one cause I see, especially with 2.5-inch SATA SSDs. SATA cables can work loose from vibration, temperature changes, or simply being bumped during other maintenance. I have also seen cables that look perfectly fine on the outside but have an internal wire break that causes intermittent connectivity.

Seagate’s official knowledge base specifically recommends keeping SATA cables under 1 meter in length and checking for bent pins at the connectors. A cable that worked for years can silently fail, and the SSD will simply vanish from BIOS without warning.

2. Incorrect SATA Mode (IDE Instead of AHCI)

BIOS offers multiple SATA operating modes: IDE (also called Legacy), AHCI, and RAID. SSDs require AHCI mode to function properly. IDE mode is an old compatibility standard designed for mechanical hard drives, and many motherboards default to it for backward compatibility.

If your BIOS is set to IDE mode, the SSD may not be detected at all, or it may be detected but perform terribly. AHCI enables Native Command Queuing and hot-swapping, both essential for SSD operation. I have seen users spend hours chasing phantom problems only to discover a single BIOS toggle was set wrong.

3. Disabled SATA Port or M.2 Slot

Many modern motherboards, particularly from MSI and ASUS, ship with certain SATA ports or M.2 slots disabled by default. Some motherboards also share lanes between M.2 slots and SATA ports, meaning if you populate an M.2 slot, it may disable SATA ports 5 and 6 automatically.

This is one of the most confusing issues for new builders. The drive is physically installed correctly, but the BIOS has the port turned off. Reddit users on r/buildapc frequently report this with MSI motherboards that require manually enabling SATA ports in the BIOS storage configuration menu.

4. Outdated BIOS Firmware

Older motherboards may not support newer NVMe SSDs out of the box. If your motherboard was manufactured before the NVMe drive you are trying to install, the BIOS may simply lack the firmware to communicate with it. A BIOS update is often the only fix.

I have personally encountered this with Gigabyte H81-series motherboards that needed a firmware flash before they could see any NVMe drive. The SSD was perfectly healthy, but the BIOS was too old to know how to talk to it.

5. Intel VMD Blocking NVMe Detection

This is the hidden cause that no competitor covers. On Intel 11th Gen (Tiger Lake) and newer platforms, the BIOS includes a feature called VMD (Volume Management Device). When VMD is enabled, it intercepts PCIe storage traffic and routes it through Intel’s Rapid Storage Technology driver instead of letting the BIOS see the drive directly.

If you install Windows without the Intel RST driver, or if VMD is enabled but the driver is missing, your NVMe SSD will be completely invisible in BIOS. The fix is either disabling VMD in BIOS or loading the correct Intel RST driver during Windows installation.

6. CSM/UEFI Compatibility Conflicts

CSM (Compatibility Support Module) is a BIOS feature that allows legacy BIOS booting for older operating systems. When CSM is enabled, it can interfere with NVMe SSD detection because NVMe requires UEFI boot mode. Several users on Tom’s Hardware forum report that simply toggling CSM off immediately made their NVMe drives visible.

Secure Boot can also cause issues. If Secure Boot is enabled and your SSD’s bootloader signature does not match what the BIOS expects, the drive may appear in storage information but not in the boot priority list.

7. Power Supply Issues

SSDs require clean, stable power. A failing power supply or a loose SATA power connector can cause the SSD to drop offline intermittently. I have seen cases where an SSD was detected after running Windows repair but vanished again after a full shutdown, which traced back to a failing PSU that could not maintain stable voltage on cold boot.

Power surges and outages are a major culprit. A user on the Microsoft Community forums reported their NVMe SSD stopped showing in BIOS entirely after a power outage during gaming. The surge likely damaged a component on the SSD’s power delivery circuit.

8. M.2 Not Fully Seated

M.2 NVMe SSDs are notoriously tricky to seat properly. The drive goes in at a 30-degree angle and is secured with a single tiny screw. If the drive is not pushed fully into the slot before screwing it down, the gold contacts will not make a complete connection.

I have built dozens of PCs and still double-check M.2 seating every time. The drive can look flush with the motherboard but still not be making contact. Remove the screw, pull the drive out, push it firmly back in until you feel it stop, then secure it.

9. Corrupted Partition Table or RAW File System

Sometimes the SSD is detected by the hardware but not usable because the partition table is corrupted. In Disk Management, the drive will show as RAW or unallocated. The BIOS can see the hardware, but the storage information is unreadable.

This is a logical failure, not a physical one. The data is often still there, but the filesystem metadata is damaged. You can usually fix this by reinitializing the drive and assigning a drive letter, though you may need data recovery software if the drive contained important files.

10. Failed SSD Controller or NAND Flash

This is the worst-case scenario and the least common. SSDs use a controller chip that manages data flow between the computer and the NAND flash memory chips. If the controller fails, the SSD may produce no response at all when the BIOS queries it.

NAND flash degradation can also cause “sudden death syndrome,” where the drive works normally one day and is completely invisible the next. If the drive is not detected on any computer with any cable, the controller or NAND has likely failed.

Symptom-to-Cause-to-Fix Quick Reference Table

Use this table to jump directly to the fix that matches your situation. I compiled these from real forum cases and my own troubleshooting experience.

Symptom	Most Likely Cause	Fix
SSD never showed up (new installation)	Cable not seated, port disabled, or M.2 not pushed in fully	Reseat cable or M.2, enable port in BIOS
SSD was working, suddenly vanished	Loose cable, SATA cable failure, or power surge damage	Replace SATA cable, check power supply
SSD shows in Storage but not in Boot Priority	CSM enabled, Secure Boot conflict, or no EFI partition	Disable CSM, switch to UEFI mode
SSD detected sometimes but not after cold boot	CMOS battery dying, failing PSU, or intermittent cable	Replace CMOS battery, test PSU, replace cable
SSD not detected after BIOS update	BIOS update changed SATA mode, CSM, or VMD settings	Reset BIOS to defaults, reconfigure AHCI mode
New NVMe M.2 not detected on older motherboard	BIOS too old to support NVMe or M.2 slot	Update BIOS to latest version
SSD works as external USB but not internally	Motherboard SATA port, M.2 slot, or BIOS setting issue	Drive is healthy, fix motherboard-side configuration
SSD not detected on any computer	Failed controller, dead NAND, or firmware crash	Power cycle trick, then professional data recovery

Common Signs Your SSD Is Not Being Detected

SSD detection problems manifest in several different ways. Knowing which symptom you have narrows the possible causes dramatically. Here are the signs I look for when diagnosing this issue, along with what each one typically means.

“No Bootable Device Found” error on startup. This is the most common sign. The BIOS has completed POST and looked for a bootable drive, but found nothing. This means either the SSD is not detected at all, or it is detected but has no bootable partition.

SSD appears in Storage Information but not in Boot Priority. The BIOS can see the hardware, but it does not consider the drive bootable. This usually points to a CSM/UEFI conflict, a corrupted EFI partition, or Secure Boot blocking the bootloader.

SSD was working yesterday, gone today. Sudden disappearance typically means a cable came loose, a power surge damaged something, or the SSD controller crashed. Check connections first.

SSD detected intermittently. If the drive shows up sometimes but not others, especially after cold boot versus warm reboot, look at the CMOS battery, the power supply, and the SATA cable quality. One user on the Microsoft Community forums reported their Gigabyte H81M-S1 detected the SSD after running Windows repair but lost it again after a full shutdown, which traced to a combination of CMOS battery failure and an aging power supply.

SSD works in an external enclosure but not internally. This is actually a strong diagnostic clue I see frequently on Reddit. If the drive works when connected via USB to SATA adapter, the SSD itself is healthy. The problem is on the motherboard side: dead SATA port, disabled M.2 slot, or BIOS configuration issue.

BIOS detects the SSD but Windows installer cannot see it. The drive shows up in BIOS Storage Information but the Windows setup screen says no drives were found. This is almost always a missing storage controller driver, particularly Intel RST/VMD on modern Intel platforms, or a RAID mode that requires a driver loaded from a USB flash drive during installation.

SSD makes clicking or beeping sounds. Unlike mechanical hard drives, SSDs have no moving parts and should be completely silent. Any sound from an SSD indicates a hardware failure, typically a short circuit or a failing power delivery component. Stop using the drive immediately.

Step-by-Step Fixes for SSD Not Detected in BIOS

Now we get to the core of this guide. I am going to walk you through 10 fixes in order from simplest to most complex. Work through them sequentially. Most people resolve the issue within the first three steps.

Step 1: Reseat All Physical Connections

Power off your computer completely and unplug the power cable from the wall. Wait 30 seconds for residual charge to dissipate. Open your case and locate the SSD.

For a 2.5-inch SATA SSD, unplug both the SATA data cable and the SATA power cable. Inspect the connectors for bent pins, corrosion, or damage. Reconnect both cables firmly until you feel them click into place. Try using a different SATA port on the motherboard and a different SATA cable entirely.

For an M.2 NVMe SSD, unscrew the retention screw and gently pull the drive out of the slot. Inspect the gold contacts on the drive for any damage or debris. Align the notch on the drive with the key in the M.2 slot, insert at a 30-degree angle, and push firmly until the drive is fully seated. Secure with the screw, but do not overtighten.

I cannot count how many times this single step has fixed the problem. One builder I helped spent three hours troubleshooting only to discover their SATA cable had an internal wire break that was invisible from the outside.

Step 2: Enter BIOS and Check Storage Information

Power on the computer and immediately start tapping your BIOS key. The exact key depends on your motherboard brand. I have included a complete reference table in the next section, but the most common keys are Delete and F2.

Once in BIOS, look for a menu called Storage, Storage Information, SATA Configuration, or NVMe Configuration. This menu lists all storage devices the BIOS can see. If your SSD appears here, the hardware connection is good and the problem is likely a boot configuration issue. If it does not appear here, continue with the physical and BIOS-level fixes below.

Step 3: Set SATA Mode to AHCI

While still in BIOS, navigate to the SATA Configuration or Storage settings. Look for an option called SATA Mode, SATA Controller Mode, or Storage Controller. The available options are typically IDE (or Legacy), AHCI, and RAID.

Change this setting to AHCI. This is the correct mode for all modern SSDs. IDE mode is for ancient mechanical drives and will either prevent detection or cause severe performance problems. RAID mode is only needed if you are running multiple drives in a RAID array.

Important warning: if Windows was installed with IDE mode and you switch to AHCI, Windows may blue screen on boot with an INACCESSIBLE_BOOT_DEVICE error. You need to enable AHCI in Safe Mode first or change the registry setting before switching. The reverse is also true. If you are installing a fresh copy of Windows, always set AHCI before starting the installation.

Step 4: Enable the Specific SATA Port or M.2 Slot

In the same SATA Configuration menu, many motherboards allow you to enable or disable individual SATA ports. Scroll through ports 0 through 6 and make sure the port your SSD is connected to is set to Enabled, not Disabled or Auto.

For M.2 slots, look for a setting called M.2 Configuration, NVMe Configuration, or Onboard Devices Configuration. On some ASUS and MSI boards, the M.2 slot must be explicitly enabled before the BIOS will scan it. Also check whether the M.2 slot shares lanes with SATA ports. On many motherboards, populating the M.2 slot disables SATA ports 5 and 6.

This is an easy fix that catches many people off guard. The drive is installed perfectly, but the motherboard is simply not looking for it.

Step 5: Disable CSM and Enable UEFI Mode for NVMe Drives

If you are using an NVMe M.2 SSD, CSM (Compatibility Support Module) can block detection. CSM is designed for legacy BIOS booting and does not fully support NVMe drives. Find the CSM setting, usually under Boot or Advanced settings, and set it to Disabled.

When you disable CSM, the BIOS switches to full UEFI mode. NVMe drives require UEFI to be detected and to appear in the boot priority list. Multiple users on Tom’s Hardware forum have reported that this single toggle immediately made their NVMe SSDs visible after hours of frustration.

Also check Secure Boot settings. If Secure Boot is enabled and your drive’s bootloader is unsigned or does not match the Secure Boot keys, the drive may appear in storage information but not in boot priority. Try disabling Secure Boot temporarily to test.

Step 6: Check Disk Management for Unallocated Space

If the SSD is detected in BIOS but not visible in Windows, the issue is often at the OS level. Right-click the Start button and select Disk Management. Look at the bottom section for your SSD.

If the drive shows as Unallocated, it needs to be initialized and formatted. Right-click the unallocated space and select New Simple Volume. Follow the wizard to assign a drive letter and format the drive with NTFS or exFAT.

If the drive shows as RAW, the partition table is corrupted. You can right-click and format it, but this will erase all data. If you need to recover data from a RAW drive, use recovery software like TestDisk or PhotoRec before formatting.

If the drive shows as Online but has no drive letter, right-click the partition and select Change Drive Letter and Paths. Assign an available letter and the drive will appear in File Explorer.

Step 7: Initialize the SSD with the Correct Partition Style

In Disk Management, if the SSD prompts you to initialize, choose GPT (GUID Partition Table) for modern systems running UEFI BIOS. Choose MBR (Master Boot Record) only if you are running a legacy BIOS system from before 2012.

GPT supports drives larger than 2TB and is required for UEFI booting. MBR is the older standard and has limitations. If you select the wrong one, you can always reinitialize, but existing data will be lost.

Step 8: Update Your BIOS Firmware

If you have an older motherboard and a newer NVMe SSD, the BIOS may simply be too old to support it. Visit your motherboard manufacturer’s website, find your exact model number, and download the latest BIOS version.

Flash the BIOS according to the manufacturer’s instructions. This usually involves putting the BIOS file on a USB flash drive and using the BIOS flash utility built into the motherboard. Some modern motherboards support BIOS Flashback, which lets you update without a CPU or RAM installed.

Do not interrupt a BIOS update under any circumstances. A power failure during flashing can brick the motherboard. Connect a UPS if possible and never update during a storm.

Step 9: Try the Power Cycle Trick for a Locked SSD Controller

If the SSD controller has crashed or locked up, the power cycle trick can sometimes revive it. This technique is recommended by BLR Tools and has worked for many users with SSDs that suddenly stopped being detected.

Here is how to do it safely:

1. Disconnect the SATA data cable from the SSD, but leave the SATA power cable connected.
2. Power on the computer and let it sit at the BIOS screen or “no bootable device” error for 30 minutes. This provides continuous, clean power to the SSD without data transfer activity.
3. After 30 minutes, power off the computer completely.
4. Reconnect the SATA data cable to the SSD.
5. Power on and enter BIOS to check if the SSD is now detected.

The theory behind this trick is that the SSD controller can enter a locked state where it stops responding to commands. Continuous power without data activity can reset the controller and clear the lock. This does not always work and does not fix physical damage, but it is worth trying before paying for professional recovery.

Safety warning: do not touch the SSD while the computer is powered on. Do not attempt this on a laptop with an internal battery without first disconnecting the battery. Static electricity can damage components, so ground yourself by touching the metal case before handling the drive.

Step 10: Test the SSD on Another Computer

This is the definitive diagnostic step. Remove the SSD from your computer and connect it to another system. For SATA SSDs, use a different SATA cable in a different computer. For NVMe drives, use a USB NVMe enclosure or install it in another compatible motherboard.

If the SSD is detected on the other computer, your original system has a problem. It could be a dead SATA port, a motherboard fault, a BIOS issue, or a power supply problem. The SSD itself is fine.

If the SSD is not detected on any computer, with any cable, in any BIOS, the drive has likely suffered a hardware failure. Proceed to the section on dead SSDs below.

Motherboard BIOS Key Quick Reference Table

One of the most frustrating parts of troubleshooting is simply getting into BIOS. Different motherboard manufacturers use different keys. Here is a comprehensive reference table I have compiled covering every major brand.

Manufacturer	BIOS Key	Boot Menu Key	Notes
ASUS (motherboards)	Del or F2	F8	Some models also support Esc
Gigabyte	Del	F12	Some boards use F2 for Q-Flash
MSI	Del	F11	Click BIOS interface
ASRock	F2 or Del	F11	Some models use F6 for Instant Flash
Dell	F2	F12	Some Dell laptops use F12 only
HP	F10	F9	Press Esc repeatedly for startup menu
Lenovo	F1 or F2	F12	Some ThinkPads use Enter then F1
Acer	F2 or Del	F12	Some models require Ctrl+F2
Intel (reference boards)	F2	F10	Visual BIOS interface
Custom/Generic	Del or F2	F12 or Esc	Try Del first, then F2

Start tapping the BIOS key immediately when you power on. Do not wait for the logo screen, because on fast-booting systems you may have less than 2 seconds. If you miss it, the system will boot to Windows or show a “no bootable device” error. Just restart and try again.

SATA SSD vs NVMe M.2 SSD: Different Causes, Different Fixes

SATA SSDs and NVMe M.2 SSDs use completely different interfaces, and the causes of detection failure differ significantly. If you are troubleshooting, knowing which type you have narrows the problem immediately.

SATA SSDs (2.5-inch or M.2 SATA): These connect via SATA cables or M.2 SATA slots and use the same protocol as mechanical hard drives. Detection issues are usually related to cables, SATA mode settings, or port configuration. The SATA data cable is the single most common failure point. If the SSD is detected sometimes but not always, swap the cable before doing anything else.

NVMe M.2 SSDs: These connect directly through PCIe lanes and do not use cables. Detection issues are typically related to BIOS firmware, M.2 slot configuration, CSM/UEFI settings, or Intel VMD. NVMe drives are more sensitive to BIOS version because the BIOS must understand the NVMe protocol. On older motherboards, NVMe support may require a BIOS update.

Issue Type	SATA SSD	NVMe M.2 SSD
Most common cause	Faulty or loose SATA cable	CSM enabled or BIOS too old
BIOS mode required	AHCI (works in both UEFI and CSM)	UEFI only (CSM must be off)
Connection check	Two cables (data + power)	Single M.2 slot, no cables
Firmware dependency	Low (SATA is universally supported)	High (BIOS must support NVMe protocol)
Slot sharing	Each port is independent	M.2 may disable SATA ports 5 and 6
Intel VMD issue	Not applicable	Common on Intel 11th Gen+

One important detail: some M.2 slots support both SATA and NVMe drives, while others are NVMe only. Check your motherboard manual to confirm which type of M.2 drive your slot accepts. Installing a SATA M.2 drive in an NVMe-only slot will not work, and the drive will not be detected.

PCIe lane conflicts are another common issue. Some M.2 slots share PCIe lanes with the graphics card slot. If your GPU is running at x8 instead of x16 because the M.2 slot is using lanes, both devices may have reduced performance. Check your motherboard manual for lane allocation details.

Intel RST and VMD Driver Conflicts (Hidden BIOS Issue)

This section covers the most under-documented cause of NVMe SSD detection failure. No major competitor guide covers this, and it affects a huge number of modern Intel systems.

What Is Intel VMD?

Intel VMD (Volume Management Device) is a hardware controller built into Intel 11th Generation (Tiger Lake) and newer chipsets. VMD sits between the NVMe SSD and the rest of the system, managing all PCIe storage traffic. It is designed to enable Intel Rapid Storage Technology features like RAID and SSD caching.

The problem is that when VMD is enabled in BIOS, the NVMe SSD is hidden from the standard BIOS storage scan. Instead of seeing the drive directly, the BIOS sees a VMD controller. The actual NVMe drive is only visible if the Intel RST driver is loaded.

If you are trying to install Windows and the setup cannot find your NVMe drive, VMD is almost certainly the cause. The drive is physically fine, the connection is correct, but the Windows installer does not have the Intel RST driver to see through the VMD layer.

How to Disable VMD in BIOS

The fix is straightforward. Enter BIOS and look for a setting called VMD Controller, VMD Setup, or Intel RST/VMD. This is usually under Advanced, Storage, or Onboard Devices Configuration.

Set the VMD controller to Disabled. Save and exit BIOS. Your NVMe SSD should now appear in the standard Storage Information menu and in the Windows installer without any additional drivers.

On some motherboards, particularly from ASUS and Gigabyte, VMD is enabled by default on 11th Gen and newer platforms. This catches many builders off guard because the drive works on older Intel or AMD systems but vanishes on a new Intel build.

When You Actually Need Intel RST Drivers

If you are running NVMe drives in a RAID array, or if you want Intel-specific features like SSD caching with Optane memory, you need VMD enabled and the Intel RST driver installed. In that case, download the latest Intel RST driver from Intel’s website, extract it to a USB flash drive, and load it during Windows installation by clicking Load Driver on the disk selection screen.

For most users with a single NVMe SSD, disabling VMD is the simplest and most reliable solution. You lose RAID features but gain straightforward BIOS detection.

SSD Not Detected After a BIOS Update

This is one of the most frustrating scenarios because the update was supposed to improve things, not break them. I have seen this happen many times, and the cause is almost always a settings change that the BIOS update applies automatically.

When you update your BIOS, the update process typically resets all BIOS settings to factory defaults. This means your SATA mode may revert from AHCI to IDE, CSM may be re-enabled, VMD may turn on, and individual SATA ports may be disabled. The SSD has not changed, but the environment it operates in has.

How to fix it: After any BIOS update, immediately enter BIOS and check three things. First, verify SATA mode is still set to AHCI. Second, check that all SATA ports and M.2 slots are enabled. Third, disable CSM and VMD if you are using NVMe drives.

If the BIOS update introduced a bug that breaks SSD detection, you may need to roll back to the previous BIOS version. Most motherboards support BIOS rollback through the same flash utility. Download the older BIOS version from the manufacturer’s website and flash it using the USB method.

Some motherboards have a dual-BIOS feature with a backup chip. If the main BIOS is corrupted, the backup takes over automatically. Gigabyte calls this feature Q-Flash Plus, and ASRock calls it BIOS Flashback. Check your manual for the specific procedure.

One scenario I have seen repeatedly: a user updates their BIOS to the latest version, and suddenly their NVMe drive that worked fine for months disappears. The newer BIOS version has a bug in its NVMe implementation. Rolling back one or two versions resolves the issue. Always read the BIOS changelog before updating and check forum threads for reports of storage regressions.

Advanced Troubleshooting: CMOS Reset and BIOS Rollback

If the standard fixes have not worked, it is time for more advanced techniques. These methods reset the motherboard’s state to resolve deep-seated configuration corruption.

CMOS Battery Reset

The CMOS battery is a small CR2032 coin-cell battery on the motherboard that maintains BIOS settings when the computer is powered off. A dying or dead CMOS battery can cause intermittent SSD detection issues because the BIOS settings reset on every cold boot.

The Microsoft Community case study I mentioned earlier, involving a Gigabyte H81M-S1 motherboard, is a perfect example. The user’s SSD was detected after running Windows repair but vanished after a full shutdown. The cause was a dead CMOS battery that caused BIOS settings to reset, which changed the SATA mode and port configuration.

How to reset CMOS:

1. Power off the computer and unplug the power cable.
2. Open the case and locate the CMOS battery (a silver coin-cell, usually CR2032).
3. Use a small flathead screwdriver to gently pop the battery out.
4. Wait 5 minutes to ensure all residual charge dissipates.
5. Press and hold the power button for 10 seconds to discharge capacitors.
6. Insert a fresh CR2032 battery (they cost about $2 at any pharmacy).
7. Reconnect power, boot into BIOS, and reconfigure your settings.

Alternatively, many motherboards have a dedicated Clear CMOS jumper or button. Check your manual for the exact location. Using the jumper is faster than removing the battery but achieves the same result.

When to Flash or Roll Back BIOS

BIOS flashing should be a last resort, not a first step. I recommend trying it only if:

• Your motherboard is too old to support your NVMe SSD (needs newer firmware)
• A recent BIOS update broke SSD detection and rolling back fixes it
• The manufacturer’s changelog specifically mentions storage fixes
• You have exhausted all other troubleshooting steps

Before flashing, verify you have the correct BIOS file for your exact motherboard revision. Installing the wrong BIOS can permanently brick the board. Check the revision number printed on the motherboard itself, not just the model name, because different revisions sometimes use different BIOS files.

Electrostatic Protection Warning

Whenever you open your computer case, be aware of electrostatic discharge (ESD). Static electricity can damage SSD controllers, motherboard components, and RAM. The Microsoft Community response on this topic specifically warns about ESD as a cause of SSD damage.

Ground yourself by touching the unpainted metal case of the computer before touching any internal components. Work on a hard surface, not carpet. Wear cotton clothing, not synthetic fabrics that generate static. If you have an anti-static wrist strap, use it.

What to Do If Your SSD Is Physically Dead

If the SSD is not detected on any computer, with any cable, in any BIOS, and the power cycle trick did not work, the drive may have suffered a hardware failure. Here is how to confirm the diagnosis and what to do next.

Signs of Physical SSD Death

An SSD with a failed controller or NAND flash degradation typically exhibits one or more of these signs: it produces no response when connected (no LED, no detection, no sounds), it was working perfectly and then suddenly vanished with no warning, or it was exposed to a power surge, liquid, or physical trauma.

SSDs can also fail gradually. Warning signs before total failure include frequent crashes, files that become corrupted, extremely slow read/write speeds, and the drive disappearing after extended use only to reappear after cooling down. If you see these signs, back up your data immediately.

Check SMART Data with CrystalDiskInfo

If the SSD is still detectable on some boot, run CrystalDiskInfo to check the drive’s SMART (Self-Monitoring, Analysis, and Reporting Technology) data. CrystalDiskInfo is the most recommended diagnostic tool across Reddit and tech forums. It reads the drive’s internal health sensors and reports remaining lifespan, error counts, and temperature data.

If CrystalDiskInfo shows a Caution or Bad status, the SSD is failing. The specific SMART attributes to check include Reallocated Sector Count, Uncorrectable Error Count, and SSD Life Remaining. Any non-zero reallocated sector count indicates the NAND flash is degrading.

Seagate also offers SeaTools, a free diagnostic tool that can test both Seagate and non-Seagate drives. SeaTools for DOS runs outside of Windows and can perform more thorough testing than Windows-based tools. Run the short test first, then the long test if the short test passes.

Data Recovery Options

If the SSD contains important data and is no longer detectable, you have several options. For logical failures (corrupted partition table, RAW file system), data recovery software like TestDisk, PhotoRec, or commercial tools may recover files even when the drive appears dead in Windows.

For physical failures (dead controller, NAND degradation), software tools will not help. The SSD needs professional data recovery. Companies like DriveSavers, Ontrack, and Secure Data Recovery specialize in SSD recovery by removing the NAND chips and reading them directly on specialized equipment.

SSD data recovery is more expensive than HDD recovery because it requires chip-off techniques and proprietary controller decryption. Expect costs ranging from $500 to $2,500 depending on the drive and the extent of the damage.

Warranty Replacement

Most SSDs come with a 3 to 5 year warranty. Samsung, Crucial, Western Digital, Kingston, and Seagate all offer warranty service through their websites. Check the manufacturer’s warranty portal with your drive’s serial number to see if it is still covered.

If the drive is under warranty, you can get a replacement. However, warranty service does not include data recovery. If you need the data, you must attempt recovery before sending the drive in, because the manufacturer will likely refurbish or destroy the original unit.

FAQ’s

Conclusion

Figuring out why your SSD is not detected in BIOS and how to fix it comes down to a systematic process: check physical connections first, verify BIOS settings (AHCI mode, enabled ports, CSM off for NVMe), look at Disk Management for unallocated or RAW drives, and test the SSD on another computer as a definitive diagnostic. The vast majority of detection failures are caused by simple cable or configuration issues, not hardware death.

If you have worked through all 10 steps and the drive is still invisible on every system, the SSD controller or NAND flash has likely failed. Check your warranty status, try the power cycle trick as a last resort, and consider professional data recovery if the drive contains irreplaceable files. For future protection, always keep current backups, use a quality power supply with surge protection, and monitor your SSD health with CrystalDiskInfo so you catch problems before they become emergencies.