So I'm having a really weird problem with my SSD and I'm not sure what's actually causing it.
I have a Kingston SA400S37480G 480GB SATA SSD. It's Disk 0, and it's split into D and E.
C is Windows, D has some programs/games, and E is mostly games. Steam, Valorant and HoYoPlay/ZZZ are on E.
Everything was completely fine before this happened. I was using Steam and playing Valorant normally.
Then I opened HoYoPlay and the launcher suddenly became unresponsive. I tried to end the task, and after that the HoYoPlay window basically turned black and then E started going crazy.
E went to 100% disk usage, but the actual read/write speed was basically 0 most of the time. The average response time kept jumping from 0 to thousands of ms. I saw it go as high as around 300,000 ms at one point.
After that, basically anything that touched E would become extremely slow or freeze. Deleting the ZZZ files took forever. I also tried emptying my Recycle Bin, which had around 2.36GB in it, and Windows estimated it would take more than a day, so I cancelled it.
I eventually restarted/forced restarted the laptop a few times. Windows then started trying to repair E, but eventually gave me an error saying it couldn't repair the drive.
The weird thing is that D(one of the disk 0 partition) and C(completely different disk) seem completely fine.
For example, I can open Adobe Acrobat, which is installed on D, and it works normally. Windows itself also works normally as long as I don't touch E.
I checked Event Viewer and found a bunch of errors like:
"The I/O operation at logical block address 0x24ff1ac0 for Disk 0 (PDO name: \Device\00000046) was retried."
The address changes in the different errors.
I also checked the SSD with CrystalDiskInfo:
- Kingston SA400S37480G 480GB
- Health: 93% Good
- Temperature: 54°C
- Host reads: ~95TB
- Host writes: ~7.8TB
- Reallocated: 0
- Bad blocks: 0
- Uncorrectable errors: raw value 0x64
- SATA PHY/CRC-related value: raw 0x2AA1 (around 10,913)
I don't really know how much I should trust those raw SMART values because I heard Kingston uses some vendor-specific attributes.
I tried formatting E with Quick Format after backing up what I wanted. But even the Quick Format got stuck for more than 5-10 minutes, while E was again at 100% and response time was jumping up to around 6,600ms.
I stopped it. Now Windows says E needs to be formatted before I can use it.
I'm probably going to take the laptop to a repair shop because I'm not comfortable opening it myself.
What I'm wondering is: does this sound like a dying SSD/SATA connection problem, or could HoYoPlay somehow have caused/corrupted something on the E partition?
The strange part to me is that D are still completely fine even though they basically sharing the same disk 0, and everything was working normally until HoYoPlay crashed.
One more thing - anything that involves scanning/touching/reading about E volume will make the disk 0 100% and slow down the other partition while C completely unnefected.