Limits SSD 2.5" drives to 50% storage space.
Limits SSD 2.5" drives to 50% storage space.
Hello, I recently assembled a new PC at the end of last year. It features just an M.2 SSD with a Crucial P3+ 2to, where Windows 11 is installed. Since then, whenever I download large files—usually games or updates—I experience frequent freezes lasting about ten seconds until the download finishes. This is quite frustrating. In the Task Manager, under the Process tab, the disk usage stays at 50% and never goes beyond it. Someone mentioned this might be normal after the SSD reaches half capacity. Currently, I have 747GB free on a 1.81TB drive. I turned off the write-caching policy. The Crucial storage expert confirmed the SSD is in good condition and has the latest update. I forced Gen4 mode on the M2_1 slot. Running chkdsk and sfc scannow via Command Prompt showed everything is fine. What should I try next?
Performance is disappointing. Maybe switch to a different M2 slot or simply reinsert the SSD. Speeds at the random end are lower than what an HDD would achieve.
Thanks for the update. The SSD setup remains consistent, but performance is still lagging compared to previous tests. I tried another M.2 slot and saw noticeable improvement (referenced below), though it’s still slower than what was achieved earlier. The speed page you shared provides more details. I’m still limited to 50% on Windows, and I haven’t found a fix for the slowdown. Could the issue lie with the motherboard itself? Are there other factors I should investigate before reaching out to MSI warranty support?
Yes, it didn't assist. I used the CPU lane initially (m2_1). This morning I switched to m2_3 for testing.
I understand why your disk space stays at 50% and can't exceed it. It seems you recently installed a second 2.5" SSD. The task manager displays the combined usage, showing one drive idle and the other at full capacity. That explains why the total reaches 50%. If I add more drives, the usage will surpass that limit. I’m sorry for the inconvenience, but this appears to be an issue with your M.2 SSD.