It is now reported that the latest Windows 11 update is causing SSDs to become non-functional after a large data write, and it seems to have affected several drives.
Many SSDs Are Becoming Non-Functional After Large Data Writes
`Well, Microsoft's updates with their OS have brought in new problems for PC gamers several times in the past, and it seems like your SSDs might not be safe this time. In a deep dive by an X user @Necoru_cat, it is revealed that after the 'KB5063878' security update on Windows 11 that dropped a few days ago, storage drives reportedly malfunction while large files are being written to them at once. The user himself spotted the trouble when he was updating Cyberpunk 2077 with the new security update.
Before we dive into the specifics of the report, it is essential to note that these details have emerged from internal testing and benchmarking, and neither SSD manufacturers nor Microsoft has verified the SSD failure issue since it is a new one with the recent security updates. It is claimed that problems within the SSDs could appear if there's approximately 50GB of continuous writing, and there are similar issues within HDDs as well, hence this isn't just specific to one storage drive.
After a long instance of data write, the OS doesn't recognize the SSD, and if the PC is restarted, the drive's partition is no longer accessible. The affected SSDs are based on pretty much every major controller out there such as from SMI, Innogrit, Samsung, Phison, and WD.
According to a list compiled by NichePCGamer, here are the SSD drives that until now have been reported to be influenced by the issue after installing the latest security updates;
- Corsair Force MP600
- Phison PS5012-E12 controller-equipped SSD
- KIOXIA EXCERIA PLUS G4
- Fikwot FN955
- SSD with InnoGrit controller
- Maxio SSD
- KIOXIA M.2 SSD
- SanDisk Extreme PRO M.2 NVMe 3D SSD
For now, the issue isn't as widespread as it hasn't been reported across public forums, but the security update might have something to do with SSDs failing to perform after data writes. Our best reasoning for the problem is likely from a storage driver or kernel-level regression that came with the update, which mishandles long sequential writes, ultimately leading to controller lock-up, which makes the drive disappear and is not recognizable by the OS.
We are gathering more updates and reports on the issue. However, we advise users to avoid long sequential write instances, especially if their drive is on the above-mentioned list.
About the author: Muhammad Zuhair is a hardware and technology reporter for Wccftech, specializing in the semiconductor industry and the complex interplay between technology, manufacturing, and geopolitics. His coverage focuses on the corporate strategies and technological roadmaps of industry giants like TSMC, NVIDIA, Samsung, and Intel. Zuhair's expertise lies in deconstructing complex topics such as fabrication nodes (e.g., 2nm process), the economic impact of policies like the CHIPS Act, and the strategic development of AI infrastructure from NVIDIA, AMD and Intel.
Follow Wccftech on Google to get more of our news coverage in your feeds.
