Understanding the 'Unlocated' Error
The term "Unlocated" in Windows event logs or BIOS screens indicates that the operating system or firmware cannot physically communicate with the storage device at its expected address. For the Kingston SUV400S37120G, which is a SATA-based SSD, this often happens when the motherboard’s SATA controller is not properly initialized during the Power-On Self-Test (POST). When the system attempts to boot from a drive it cannot see, it may hang indefinitely while waiting for a timeout, leading to the observed 30-minute freeze.
This issue is distinct from simple corruption; it is a hardware enumeration failure. If the drive were corrupted but detected, you would likely see BSODs or file system errors, not a complete halt before the OS loads. The fact that this started after installation suggests a configuration mismatch between the new drive and the existing system firmware.
Verifying BIOS/UEFI Configuration
The most common cause for this specific symptom is incorrect SATA operation mode. Many modern motherboards default to RAID or Intel RST (Rapid Storage Technology) modes, which can conflict with standard Windows installations if the correct drivers are not present in the initial boot environment. You must ensure the SATA mode is set to AHCI.
- Restart the computer and enter the BIOS/UEFI setup (usually by pressing Del, F2, or F10 during startup).
- Navigate to the Advanced or Storage Configuration section.
- Locate the SATA Mode or SATA Operation setting.
- Change the setting from RAID or IDE to
AHCI. - Save changes and exit. Note: Changing this setting on an existing Windows installation can cause a Blue Screen of Death (BSOD) because the kernel expects different drivers. Since your system is already freezing, you may need to boot from a Windows USB installer and repair the boot sector or reinstall if necessary.
If the system uses an M.2 slot via an adapter, check our guide on Using M.2 Drives on a PCIe X16 Adapter Card to ensure the adapter is not causing electrical or signaling issues that prevent proper enumeration.
Updating Chipset and SATA Drivers
Windows 11 includes generic drivers, but they may not support the specific power management states of newer SSDs. Outdated chipset drivers can cause the SATA controller to fail waking up from low-power states, resulting in long hangs during reboot.
Download the latest chipset and SATA AHCI drivers directly from your motherboard manufacturer’s website, not just through Windows Update. Install them, then perform a clean shutdown. During the next reboot, monitor the BIOS screen to see if the Kingston SSD is listed under the SATA ports. If it appears here but still fails in Windows, the issue is likely software-related.
Checking Drive Firmware
Kingston occasionally releases firmware updates to fix compatibility issues with certain motherboards. Use the Kingston SSD Manager tool or visit their support page to check if a newer firmware version is available for the SUV400S37120G. Applying a firmware update can resolve communication timeouts that manifest as "Unlocated" errors.
Disabling Fast Startup and Sleep States
Windows Fast Startup saves the kernel session to disk to speed up boot times. If the SSD has a glitch in how it handles hibernation files, this feature can cause massive delays during reboot. Disable it to test stability:
- Open Control Panel and go to Power Options.
- Click Choose what the power buttons do.
- Click Change settings that are currently unavailable.
- Uncheck Turn on fast startup (recommended).
- Save changes and restart.
Additionally, disable SATA Link Power Management in the Advanced Power Plan settings. This prevents the drive from entering deep sleep states that some older controllers struggle to wake from.
Testing with Legacy BIOS Settings
If you recently switched from an older system or cloned a drive, legacy BIOS settings might be interfering. Ensure UEFI is enabled if your motherboard supports it, and that CSM (Compatibility Support Module) is disabled unless specifically required for older peripherals. See our article on Can't Install Windows on SSD with Old Legacy BIOS? if you suspect legacy mode conflicts are preventing proper drive detection.
Diagnostic Steps if Problem Persists
If the above steps fail, the drive itself may be defective or incompatible with the specific motherboard revision. Test the SSD in another computer to confirm it enumerates correctly. If it works elsewhere, the issue lies with your original motherboard’s SATA port or controller. Try using a different SATA cable and connecting to a different SATA port on the motherboard. If the problem follows the drive to another PC, replace the unit under warranty.
Frequently Asked Questions
Why does my SSD show as 'Unlocated' only sometimes?
This intermittent behavior usually points to a loose SATA cable or a failing power connector rather than a total drive failure. Check all physical connections and try reseating the drive in a different SATA port to rule out a bad port on the motherboard.
Can I use RAID mode instead of AHCI to fix this?
No, switching to RAID mode without installing the appropriate Intel RST drivers before changing the setting will likely cause a BSOD. AHCI is the standard mode for single-drive consumer setups and offers better compatibility with Windows 11 native drivers.
Does enabling System Restore fix the 'Unlocated' error?
No, System Restore operates within the Windows environment and cannot fix hardware enumeration failures that occur before the OS loads. The "Unlocated" error happens at the firmware level, so restoring previous system files will not make the drive visible during boot.
Is the Kingston SUV400S37120G compatible with Windows 11?
Yes, this drive is fully compatible with Windows 11. However, compatibility requires correct driver installation and BIOS settings. If the drive is not detected, the issue is environmental (motherboard/cables) rather than OS incompatibility.
How long should a reboot take if the SSD is healthy?
A healthy SSD on Windows 11 should boot in under 30 seconds. A 30-minute freeze indicates a critical timeout waiting for a device response. Normal reboots should never exceed two minutes, even with slow HDDs.