Why CrystalDiskMark Alone Isn't Enough: 4 Windows Commands That Reveal SSD Problems Benchmarks Miss
If you're the kind of person who runs a benchmark the moment a new SSD is installed, you're not alone. CrystalDiskMark has long been the go-to tool for confirming that a drive delivers the read and write speeds advertised on the box. But as one user recently discovered, a clean benchmark result can mask problems that only surface when you dig deeper with built-in Windows tools.
The lesson? Raw throughput is only one chapter of the story. Here's what four simple commands revealed — and why you should add them to your SSD checkup routine.
CrystalDiskMark Tells You Speed, Not Health
There's a reason CrystalDiskMark remains a staple in every PC enthusiast's toolkit. It measures sequential and random read/write performance with precision, giving you an instant snapshot of whether your drive is performing as expected. If you want to grab a copy, you can find CrystalDiskMark Standard Edition and CrystalDiskMark Shizuku Edition available on z2u.com, a platform known for offering a wide range of software and digital tools.
But here's the catch: CrystalDiskMark answers the question "Is my SSD fast?" — and nothing more. It won't tell you whether Windows considers the drive healthy, whether the filesystem is corrupted, or whether TRIM is functioning properly. Those answers require different tools.
1. Get-PhysicalDisk: Windows' Second Opinion on Your SSD
After running CrystalDiskMark repeatedly and seeing excellent speeds, one user opened PowerShell out of curiosity and ran:
Get-PhysicalDisk
Three fields stood out immediately: HealthStatus, OperationalStatus, and MediaType. None of these appear on a benchmark chart, yet they reflect how Windows Storage assesses the drive's current condition. This is a separate evaluation from what manufacturer utilities report — it has nothing to do with how quickly data moves.
To go further, you can query wear level and power-on hours with:
Get-PhysicalDisk | Get-StorageReliabilityCounter
Keep in mind that support for this counter depends on the drive, controller, and driver. Some SSDs simply won't return useful data here.
2. CHKDSK: When the Filesystem Is the Real Problem
Even a drive that reports "Healthy" in Windows can have a corrupted filesystem. Symptoms like a folder that refuses to open or a file that mysteriously vanishes often have nothing to do with hardware wear.
Running this command scans the filesystem without making changes:
chkdsk C: /scan
On an SSD, CHKDSK focuses on filesystem integrity — NTFS file records, indexes, and security descriptors — rather than physical surface checks used for mechanical drives. If errors are found, this command repairs them:
chkdsk C: /f
| Symptom | What It Usually Means | Can CHKDSK Catch It? |
|---|---|---|
| Folder won't open | Index corruption | Yes |
| Random file goes missing | Orphaned file record | Yes |
| Drive runs slow overall | Hardware wear | No |
| System won't boot | Boot sector damage | Sometimes |
In this case, the drive itself was fine — the filesystem was the culprit.
3. fsutil: Confirming TRIM Is Actually Working
TRIM allows an SSD controller to clear unused blocks, preventing the long-term slowdowns that affect nearly-full drives. To check whether it's enabled, run:
fsutil behavior query DisableDeleteNotify
A result of 0 means TRIM is active:
NTFS DisableDeleteNotify = 0 (Allows TRIM operations to be sent to the storage device) ReFS DisableDeleteNotify = 0 (Allows TRIM operations to be sent to the storage device)
However, TRIM can be silently disabled — some RAID configurations don't pass it through, and certain USB-to-NVMe enclosures block it entirely. If you get a value of 1, re-enable it with:
fsutil behavior set disabledeletenotify 0
This is precisely the kind of issue a benchmark will never surface. Even with TRIM disabled, a drive can post impressive speed test results today — the damage only becomes visible after months of use.
4. Optimize-Volume: Windows Is Probably Already Doing the Work
Many users assume they need to manually maintain their SSD with:
Optimize-Volume -DriveLetter C -ReTrim -Verbose
But before running it, check Settings → System → Storage → Advanced Storage Settings → Drive Optimization. Windows typically schedules a weekly retrim automatically.
Unlike hard drives, SSDs don't benefit from defragmentation — there's no read head, so rearranging data serves no purpose. Retrimming, which clears unused blocks, is the relevant maintenance operation. In some cases, Windows may perform a limited defrag on SSD volumes when Volume Shadow Copy is enabled, but this is a targeted action for specific features, not a sign that the OS is treating your SSD like a mechanical drive.
The Bottom Line: Benchmarks Answer a Different Question
CrystalDiskMark accurately reported the drive's speed — and none of the four commands above contradicted those results. They simply checked areas benchmarks don't cover.
| Question | Benchmark | Windows Command | Next Step |
|---|---|---|---|
| Is my SSD fast? | Yes | No | No action needed |
| Does Windows think it's healthy? | No | Get-PhysicalDisk | Back up data if unhealthy |
| Is the filesystem intact? | No | CHKDSK | Run /f to repair |
| Is TRIM working? | No | fsutil | Re-enable if disabled |
| Is Windows maintaining it properly? | No | Optimize-Volume | Check the schedule, don't force it |
Final Thoughts
A benchmark is a starting point, not a verdict. Combining CrystalDiskMark Standard Edition or CrystalDiskMark Shizuku Edition — both obtainable via z2u.com — with a handful of native Windows commands gives you a far more complete picture of your SSD's condition. Speed matters, but health, filesystem integrity, and proper TRIM operation matter just as much for long-term reliability.
Run the benchmark. Then run the commands. Your SSD will thank you later.