← Article Library

Info & Help · Hardware Troubleshooting

Is Your SSD or NVMe Drive Failing? How to Investigate Boot Problems

By MR Techworks · Published

Boot loops, missing files and freezes can suggest storage trouble, but they can also originate in RAM, Windows, drivers or power delivery. A careful diagnosis avoids guessing—and protects the data you may still be able to recover.

Western Digital SN850X NVMe SSD drive, front view
Actual NVMe storage device, shown for illustration; this photograph does not indicate drive failure.

What symptoms make a drive suspicious?

Repeated read errors, unexpected file corruption, inconsistent disk detection and boot failures can be signs of storage trouble. Some faults appear only intermittently and may not show in a short test.

A computer becoming stable after replacing a drive supports further investigation, but it does not prove the original SSD was the only cause. Always check what actually changed.

Check disk health without stressing it

On a working Windows installation, an elevated PowerShell session can use Get-PhysicalDisk to list device health and operational status. Get-PhysicalDisk | Get-StorageReliabilityCounter may reveal wear, temperatures or error counts when the hardware reports them.

A 'Healthy' status and missing counter values are not conclusive. Driver support and SSD firmware differ; a manufacturer's diagnostic tool may expose more detailed health information.

Rule out similar failures

Memory problems can corrupt data and mimic storage failures. A loose connection, motherboard slot, power issue or unstable firmware setting can also produce I/O symptoms. Compare a known-good drive and test RAM separately when possible.

Write down each change and the resulting behavior. Swapping several components at once makes the root cause much harder to establish.

Protect files before aggressive tests

If the disk intermittently disappears or repeatedly fails reads, prioritize backup or professional recovery assessment rather than intensive write benchmarks. Avoid repeatedly running repair utilities on an unstable drive without considering the possibility of worsening file loss.

A successful clone may save an operating system, but it does not certify the source hardware. A failed clone may reflect damaged sectors, adapter problems, encryption or other compatibility restrictions.

A diagnostic order

First, document errors and protect accessible data. Second, verify whether UEFI/BIOS consistently detects the SSD. Third, check supported health metrics and relevant Windows error logs. Fourth, test other likely causes such as RAM and power.

Only then decide whether replacement, firmware repair or Windows recovery is justified. If the data is irreplaceable, seek data-recovery advice before repeated attempts.

Sources and further reading

Original MR Techworks guidance based on Microsoft technical and support documentation. External text has not been copied.

Reviewed November 13, 2026. Recovery options and interface wording can vary by Windows version.

Browse more technology guides · Get local help