Introduction
I was originally using an Intel i5-6500 CPU, but after switching to an AMD Ryzen 2700, frequent system freezes started occurring.
Symptoms
During these freezes, I observed that the disk usage in Task Manager was at 100%, while both read and write rates were at 0. The SSD is a generic Lexar Hades 512 GB. In Event Viewer, there were numerous events with ID 129.
Suspecting Hardware Issues
After repeatedly changing SATA ports and reconnecting power cables, the freezes persisted.
Searching for Related Issues Online
Online searches mostly pointed to the root cause being Windows 10’s AHCI driver issues and SSD firmware problems.
Solution Approach 1: Replacing the AHCI Driver - Ineffective
To replace the AHCI driver, I tried downloading chipset drivers from both AMD’s official website and ASUS’s official website, and manually replaced the driver in Device Manager so that it showed as an AMD SATA driver. I also tried various motherboard drivers, but testing proved ineffective, and the problem remained unsolved.
Solution Approach 2: Converting the Drive to RAID Format - Ineffective
To convert to RAID format, I reinstalled Windows, but during the installation process, Windows could not recognize the SSD. According to AMD’s official English manual and official RAID drivers, I manually loaded the RAID drivers, but Windows still couldn’t see the SSD during installation. After multiple attempts, it remained undetected. This might be because volume mode RAID is not supported with only one drive. I abandoned this approach.
Solution Approach 3: Modifying the Registry, Disabling MSI - Ineffective
https://www.pconline.com.cn/win10/739/7395324.html
In essence, when using the StorAHCI.sys driver in certain AHCI modes, some SSDs may not be able to complete input/output operations correctly in “Message Signaled Interrupt” (MSI) mode, ultimately resulting in system freezes with disk usage showing 100% in Task Manager. Of course, the solution is simple: just disable it (MSI Mode) directly in regedit.
4. Click Cortana, type “regedit” to launch the Registry Editor, navigate to “HKEY_LOCAL_MACHINE\System\CurrentControlSet\Enum\PCI\xxxxx\Device Parameters\Interrupt Management\MessageSignaledInterruptProperties” (where “xxxxx” is the “device instance path” you just recorded);
5. Finally, change the “MSISupported” key value in the right pane from 1 to 0;
Testing proved this ineffective.
Solution Approach 4: Changing Power Settings - Ineffective
Setting the PCI-Express setting to OFF, testing proved ineffective.
Solution Approach 5: Changing LPM - Effective
http://www.sohu.com/a/204645459_493865
The content is as follows:
Most SSDs we use today support some power-saving features, such as DIPM/HIPM/Device Sleep.
When a state change request is initiated by the host, we call it HIPM (Host-Initiated LPM), and when it’s directly initiated by the device, we call it DIPM (Device-Initiated LPM). What are they requesting? Requesting to slow down, save energy, or enter Device Sleep.
Both HIPM and DIPM rely on the computer’s LPM technology support. LPM, or Link Power Management, is a function at the physical layer of the SATA interface that can divide the link between the host and storage device into three states: Active state, Partial state, and Slumber state. The goal is to reduce the physical layer bus transmission speed, thus achieving power-saving effects.
LPM is generally enabled by default.
So is enabling LPM good for SSDs?
1. The host sends an HIPM state change command, but due to differing SSD device standards, it may not be well-supported, causing compatibility issues leading to stuttering or drive disconnection;
2. The host sends HIPM state change commands too frequently, causing the SSD device to not respond in time, resulting in stuttering;
3. After LPM is enabled, it increases SATA bus transmission delays, causing high-speed SSDs to become blocked and stutter;
4. Conflicts between the SSD’s internal DIPM and the host’s requested HIPM cause stuttering.
Often, SSD-induced computer stuttering and sudden drive disconnections are caused by LPM.
LPM can help SATA devices achieve power-saving effects. However, it also affects SSD performance.
So, for the sake of power saving, are you willing to pay the price of losing SSD performance?
HDD power consumption is around 10-25W. Perhaps LPM was originally only intended for HDDs.
SSD startup power consumption: 0.1W1W (2W), maximum power consumption: 510W, average power consumption: around 4~5W.
Does our power supply care about these few watts from the SSD? Do we care about this bit of electricity cost? Should we even care!
If SSDs don’t need LPM, which harms SSD performance, can we turn it off?
Save as “.reg” format.
Click to run. It will automatically write to the registry, changing the LPM power settings.
If your SSD is experiencing severe stuttering or disconnections, you can try this method.
The main reason for SSD stuttering and disconnections is that the SSD is too poor quality. Indeed, with SSD prices constantly rising today, it’s very difficult to buy a good SSD at a relatively low price.
After testing, this was effective
Solution Approach 6: Changing BIOS Settings, Enabling SATA Hot Plug Functionality - Recommended
https://www.aiweibk.com/5795.html
After enabling the Hot Plug attribute in the motherboard BIOS settings, there will be a side effect: the SSD’s LPM power saving will be turned off as hot-plugging is enabled, thereby avoiding data loss during hot-plugging or loss of response when reconnecting.
If your SSD and motherboard have compatibility issues causing intermittent stuttering, try enabling the Hot Plug option in the motherboard BIOS settings to disable LPM power saving, which might solve the problem.
After testing, this was effective
Conclusion
Why was there no problem with Intel before, but problems arose after switching to AMD? I suspect it’s because the original Intel motherboard was inferior and didn’t support SATA LPM, while Windows 10 has LPM enabled by default. The generic SSD doesn’t support LPM well, so even though its firmware supports LPM, serious issues can occur. Since the motherboard didn’t support LPM, even with Windows enabling LPM, the problem didn’t manifest.
Now with a new motherboard that supports LPM, compatibility issues with the SSD have emerged under default settings. LPM functionality needs to be manually disabled.