The particular file is likely leading to your SSD freezing and triggering a BSOD.
The particular file is likely leading to your SSD freezing and triggering a BSOD.
Initially, my setup included a 5800X3D MSI B450 Tomahawk Max with 32GB RAM, 3200Mhz, Seasonic Focus Gold 1000W, and storage components like the Kingston KC2000 NVMe drive, Samsung 870 QVO, and WD Blue HDD. I saved game screenshots on the KC2000 drive and attempted to move them to the HDD. The process proceeded until around 87% completion when it abruptly froze, showing full disk activity in Task Manager but no progress. After waiting, a I/O error appeared, halting the transfer entirely. I retried multiple times, but the system still froze with identical symptoms. When I tried to move other files, they transferred smoothly, though selecting the problematic one caused the same issue—system unresponsiveness and a stuck 100% drive status. Eventually, a BSOD with "WHEA_UNCORRECTABLE_ERROR" forced a reboot. Post-reboot, the boot drive vanished from BIOS, which I interpreted as normal protection for the SSD. After power cycling, the drive reappeared, and the PC booted normally. Now, I’m hesitant to handle it again, fearing any contact could trigger the same problem. While the disk appears healthy (89% health, 100% spare, no errors), I’m unsure why this specific file is still causing trouble. Could the storage area have developed bad sectors over time? According to HWinfo, temperatures are stable at around 35°C with a peak of 45°C, and no warnings are present.
You're describing a situation where certain files or settings cause the operating system to behave strangely—slowing down Explorer, locking up the drive, and making it seem like everything is stuck. It sounds like the OS might be misinterpreting permissions or data placement, possibly leading to conflicts when you try to manage files via command lines. The concern about recurring issues if another file overwrites the same space is valid. It’s also worth noting that deleting files through the command line can sometimes trigger these problems again if the system isn’t fully cleared. Understanding what exactly is being written or modified in the drive area could help prevent this from happening.
Could be a simple issue, but it might have been severely damaged so even using it causes problems
I've noticed data issues in budget SSDs before and wonder if it's the same. To be safe, I'd back up any critical info. If Kingston provides an SSD tool, use it to verify the drive first. SMART reports can also be useful—interesting to know. I've seen SSDs have problems even without active alerts. A full surface read might trigger another crash on that spot. Generally, mistakes are inevitable, but you'd hope they fail more smoothly than this. It should identify bad sections and replace them during the next write. The issue could stem from corruption being too severe to handle quietly. For systems needing redundancy, it's better to risk a disk failure rather than risk corrupt data.