● UK tech experts · info@vividrepairs.co.uk
Vivid Repairs
A 3.5 inch hard drive connected to a SATA power cable on a dark workbench with a PSU visible in the background
Fix It Yourself · Troubleshooting

intermittent HDD detection

Published 10 September 202612 min read
As an Amazon Associate, we may earn from qualifying purchases. Our ranking is independent.

Your drive was there yesterday. Now it's gone. Reboot and it's back. Reboot again and it's gone. Intermittent HDD detection is one of the most frustrating faults you'll deal with because the drive isn't dead, it's just unreliable, and that ambiguity makes people panic and RMA things that didn't need replacing. Nine times out of ten, this is a cable, a connector, or a dodgy PSU branch. Let's sort it properly.

TL;DR

Intermittent HDD detection is almost always caused by a loose SATA cable, an overloaded PSU rail, or a SATA 3.3 PWDIS pin-3 incompatibility. Reseat cables, swap to a different PSU branch, check SMART data, and only RMA after you've confirmed the fault follows the drive across known-good hardware.

⏱️ 13 min read ✅ 80% success rate 📅 Updated August 2026

Key Takeaways

  • Intermittent HDD detection is rarely a dead drive. Start with cables and connectors.
  • A PSU branch shared with power-hungry devices can drop voltage during spin-up, causing the drive to disappear.
  • SATA 3.3 pin-3 PWDIS incompatibility stops some newer drives from spinning up on certain PSU cables.
  • Windows power settings can cause a drive to vanish after sleep. Set 'Turn off hard disk after' to Never.
  • If the drive clicks or beeps, stop power cycling it and back up your data immediately.
  • Only prepare for RMA after diagnostics confirm the fault follows the drive, not the cables or system.

At a Glance

  • Difficulty: Intermediate
  • Time Required: 30 to 45 mins
  • Success Rate: 80% of cases resolved before RMA

What Actually Causes Intermittent HDD Detection?

Here's the thing: a drive that comes and goes is almost always a power or connection problem, not a dead drive. The most common culprit is a SATA power or data connector that isn't seated properly. These connectors have a notoriously poor locking mechanism and they work loose over time, especially if the drive has ever been moved or the case has been transported. A connector that looks fine can still have enough play in it to cause an intermittent fault, particularly during spin-up when the drive draws its peak current.

PSU rail issues are the second big one. When a drive spins up from cold it pulls a surge of current, sometimes 2A or more for a 7200rpm drive. If that SATA power branch is already feeding other devices (optical drives, multiple HDDs, case fans via adapters), the voltage can dip just enough to trigger the drive's internal protection circuitry. The drive then enters a fail state and won't respond until the system is fully powered off and back on again. A simple reboot often won't clear it because the PSU rail never fully de-energises during a warm restart.

Then there's the SATA 3.3 PWDIS issue. This one catches a lot of people off guard. The SATA 3.3 specification added a power-disable function on pin 3 of the power connector. Some newer PSUs assert a signal on that pin that tells compatible drives to stay powered down. Older drives ignore it. But some drives, particularly certain WD models, will not spin up at all when that signal is present, causing what looks exactly like intermittent HDD detection. The drive appears in BIOS sometimes (when the signal isn't asserted) and disappears other times. You can read more about the SATA power connector pinout and this specific behaviour over at Tom's Hardware.

Finally, there's a genuine internal drive fault. If the drive's read/write heads, motor, or controller board are failing, you'll see the same intermittent pattern. The difference is that a hardware fault follows the drive. Swap it to a different system with different cables and the problem persists. That's when you know the drive itself is the issue and RMA is the right call. But you need to rule everything else out first, because sending a perfectly good drive back and waiting two weeks for a replacement is a waste of everyone's time.

Windows power management can also be a factor, though it's more of a software-layer issue than a hardware one. If the OS is configured to spin down the hard disk after a period of inactivity, and the drive then fails to spin back up correctly after a resume or sleep cycle, it can look like the drive has vanished. This is particularly common on systems where the drive is already marginal on power.

Intermittent HDD Detection Quick Fix: Reseat and Swap Cables

1

Reseat SATA Cables and Move to a Different PSU Branch Easy

  1. Full power-off first
    Shut Windows down completely. Don't restart. Hold the power button until the system is off, then unplug the power cable from the wall socket. Wait 30 seconds so the PSU capacitors discharge fully. This matters because a warm restart doesn't always clear a drive's fail state.
  2. Reseat both SATA connectors
    Open the case and locate the SATA data cable (thin, L-shaped connector) and the SATA power cable (wider, 15-pin connector) at the drive end. Pull both out completely and push them back in firmly until they seat without wobble. Do the same at the other end: the SATA data cable at the motherboard port, and the power cable at the PSU modular socket if accessible.
  3. Move to a different SATA port and power branch
    Plug the SATA data cable into a different port on the motherboard (avoid port 0 temporarily, try port 2 or 3). For power, use a completely separate cable run from the PSU rather than a daisy-chained connector. If your PSU has two SATA power cables, use the one that isn't feeding anything else.
  4. Boot and verify in BIOS first
    Before loading Windows, enter BIOS/UEFI (usually Del or F2 at POST) and check that the drive appears in the storage or SATA configuration page. If it's there consistently across two or three reboots, the cable or branch was the issue.
If the drive now appears consistently in BIOS across multiple cold boots, you've found it. The fault was a loose connector or a shared PSU branch dropping voltage during spin-up.
Avoid SATA power splitters during testing. A splitter adds resistance and reduces the current available to the drive during spin-up. Use a direct cable run from the PSU for any diagnostic work.

More Intermittent HDD Detection Solutions: Software and Power Settings

2

Fix Windows Power Settings Easy

  1. Open Power Options
    Press Win + R, type powercfg.cpl and hit Enter. Click Change plan settings next to your active power plan, then Change advanced power settings.
  2. Set hard disk to never turn off
    Expand the Hard disk section and set Turn off hard disk after to 0 minutes (which Windows displays as Never). Click Apply and OK.
  3. Disable sleep temporarily for testing
    If the drive only disappears after the system wakes from sleep or hibernate, disable sleep entirely for 24 hours. Go back to Power Options, set Sleep after to Never for both battery and plugged in. If the problem stops, you've isolated a power-state transition fault rather than a hard hardware failure.
If the drive stops disappearing after changing these settings, the root cause was Windows spinning the drive down and it failing to spin back up correctly, likely because of marginal power delivery.
3

Update Storage Drivers and Check Event Viewer Medium

  1. Check Event Viewer for disk resets
    Press Win + X and open Event Viewer. In the left panel, go to Windows Logs > System. Filter by event sources: look for disk, atapi, storahci, or iaStorAVC. Repeated warnings or errors from these sources around the time the drive disappeared are a strong indicator of cable, power, or controller instability rather than file-system corruption.
  2. Update chipset and SATA controller drivers
    Go to your motherboard manufacturer's support page (Asus, MSI, Gigabyte, ASRock, etc.) and download the latest chipset driver and SATA/storage controller driver for your board model. Install and reboot. Outdated controller drivers can cause intermittent HDD detection that looks identical to a hardware fault.
  3. Run a clean boot to rule out software conflicts
    Press Win + R, type msconfig, go to the Services tab, tick Hide all Microsoft services, then click Disable all. On the Startup tab, open Task Manager and disable all startup items. Reboot and test. If the drive is stable in clean boot, a third-party storage filter or startup application is interfering.

If you're seeing this fault on a system that also has other storage oddities, like slow boot times or files occasionally going missing, it's worth reading our guide on HDD performance problems alongside this one, as the two issues sometimes share the same root cause.

Advanced Intermittent HDD Detection Fixes: Diagnostics and PWDIS

4

Run HDD Diagnostics and Check SMART Data Medium

  1. Download a SMART monitoring tool
    Get CrystalDiskInfo (free, widely trusted) or the manufacturer's own tool: SeaTools for Seagate drives, Western Digital Dashboard for WD drives. Install and open it while the drive is currently detected.
  2. Check the critical SMART attributes
    Look specifically at: Reallocated Sectors Count (ID 05), Current Pending Sector Count (ID C5), and Uncorrectable Sector Count (ID C6). Any non-zero value in these three is a serious warning. A drive with reallocated sectors is actively failing and should not be trusted with important data. CrystalDiskInfo will flag the overall health as Caution or Bad if these are elevated.
  3. Run the manufacturer's short and extended tests
    In SeaTools or WD Dashboard, run the Short Drive Self Test first (takes 2 minutes). If it passes, run the Extended Test (can take 1 to 4 hours depending on drive size). A failure at any point during these tests is solid grounds for RMA. Screenshot or save the results before contacting the manufacturer.
If the drive is clicking, grinding, or beeping during any of these tests, stop immediately. Do not run further tests. Power the system down and focus on recovering your data before anything else. Repeated power cycling of a mechanically failing drive can make data permanently unrecoverable.
5

Test for SATA 3.3 PWDIS Pin-3 Incompatibility Advanced

  1. Identify whether your drive is affected
    This issue primarily affects certain WD Blue and WD Green drives (and some other manufacturers) when used with newer PSUs that implement the SATA 3.3 power-disable feature on pin 3 of the SATA power connector. Check your drive's model number against the manufacturer's spec sheet or known compatibility lists. If the drive is a WD model from around 2015 onwards, it's worth checking.
  2. Test with a compliant cable first
    The cleanest fix is to use a SATA power cable that does not assert the pin-3 signal. Some older PSU cables or third-party cables don't implement SATA 3.3, which means pin 3 is simply not connected or carries +3.3V passively. Try a different cable from an older PSU or a known-compatible replacement.
  3. Pin-3 tape fix as a last resort
    If you've confirmed the drive model is affected and you don't have a compliant cable, you can carefully cover pin 3 on the SATA power connector (the third pin from the left on the 15-pin connector, in the 3.3V group) with a small strip of electrical insulating tape. This prevents the power-disable signal from reaching the drive. This is a well-documented workaround, not a hack, but do it carefully and verify the tape doesn't interfere with adjacent pins.
The SATA 3.3 PWDIS issue causes the drive to not spin up at all on affected boots, rather than spinning up and then dropping out. If your drive spins up (you can hear it) but then disappears from the OS, this specific fix probably isn't your issue. Focus on the PSU branch and cable solutions instead.
6

Test the Drive in a Second System Medium

  1. Move the drive to a different PC
    Connect the suspect drive to a completely different computer using that system's own SATA cables and PSU. Boot into BIOS and check if the drive appears consistently. Then boot into Windows or a live Linux environment and run CrystalDiskInfo or the manufacturer diagnostic tool again.
  2. Interpret the result
    If intermittent HDD detection stops in the second system, the fault is with your original PC's cables, PSU branch, or motherboard SATA controller. If the fault continues in the second system across known-good hardware, the drive itself is at fault and you should prepare for RMA with your diagnostic results as evidence.
A drive that behaves perfectly in a second system is almost certainly a PSU or cable issue in the original machine. Don't RMA a healthy drive.

For systems where the motherboard SATA controller itself might be the weak link, our motherboard SATA controller troubleshooting guide covers how to test and isolate a faulty controller port, which can cause symptoms identical to intermittent HDD detection even when the drive and cables are fine.

One more thing worth saying clearly: if your data matters and the drive is behaving erratically, back it up before you do anything else. Run your diagnostics, yes, but get a copy of your important files onto a different drive first. Don't let the troubleshooting process become the thing that costs you your data.

If you've worked through all of this and the fault turns out to be the PSU rather than the drive, our PSU failure symptoms guide walks through how to properly diagnose a failing power supply before replacing it.

Preventing Intermittent HDD Detection

Most of these faults are preventable. Here's what actually makes a difference, in order of importance:

1. Use quality cables and avoid splitters. Cheap SATA power splitters are the single biggest cause of marginal power delivery to HDDs. If you're running multiple drives, use a PSU with enough native SATA power connectors to give each drive its own direct lead. A modular PSU makes this easy.

2. Keep each drive on its own PSU branch where possible. Don't chain your HDD on the same power run as optical drives, multiple SSDs, and fan controllers. The cumulative current draw during spin-up is what causes voltage dips on that rail.

3. Mount the drive properly. A drive that vibrates in a loose bay will eventually work its SATA connectors loose. Use all four mounting screws and rubber grommets if your case supports them.

4. Monitor SMART health regularly. CrystalDiskInfo can run in the system tray and alert you when SMART attributes change. Catching a reallocated sector count starting to climb gives you time to back up and replace the drive before it fails completely. The Microsoft support page on power options is also worth bookmarking if you want to fine-tune how Windows handles storage power states.

5. Keep BIOS and storage drivers updated. Motherboard vendors occasionally release BIOS updates that fix SATA compatibility issues, particularly with newer drive models. Check your board vendor's support page every few months.

6. For newer drives, verify SATA 3.3 compatibility upfront. Before you install a new HDD, check whether your PSU implements pin-3 PWDIS and whether the drive model is known to be affected. Five minutes of research saves a lot of head-scratching later.

Intermittent HDD Detection Summary

Intermittent HDD detection is almost never the drive itself, at least not to begin with. Start with the physical stuff: reseat the cables, move to a different PSU branch, and use a direct cable run. Then sort the software side: set Windows to never spin the drive down, update your storage drivers, and check Event Viewer for reset events. If you're on a newer drive with a SATA 3.3-capable PSU, check the PWDIS pin-3 situation before you do anything else. Run SMART diagnostics and manufacturer tests to get a proper picture of drive health. And only once you've confirmed the fault follows the drive across known-good cables, ports, and a second system should you start the RMA process. Do it in that order and you'll sort it without sending back a perfectly good drive.

Frequently Asked Questions

This usually points to a marginal SATA power or data connection, an overloaded PSU branch dropping voltage during spin-up, or a drive entering a protective fail state until fully power-cycled. Reseat and swap cables and ports first to isolate the cause before assuming the drive is dead.

Swap the data and power cables and move to a different SATA port and PSU branch. If the problem disappears, it was the cable or branch. If the fault follows the same drive across known-good cables and a second system, the drive itself is likely at fault and you should prepare for RMA after running diagnostics.

Yes, on some newer drives. If pin 3 power-disable signalling is present on your PSU cable, the drive may refuse to spin up. Test with a compliant SATA power lead or carefully isolate pin 3 with a small strip of insulating tape if you confirm the drive model is affected. Check the manufacturer spec sheet to verify.

Not before diagnostics. Run the manufacturer HDD diagnostics tool and check SMART data, then test the drive in another known-good system or with a known-good PSU. Only prepare for RMA once the fault clearly follows the drive regardless of cables, ports, and system.

Stop power cycling it immediately. Clicking or beeping combined with intermittent HDD detection is a serious warning sign. Back up any data you can access right now, then stop. Continued power cycling of a mechanically failing drive risks making data unrecoverable.