Whether the hardware has an influence is currently unclear. Most are Kingston A400s with Phison S11 controllers and 2D TLC NANDs, but there was also a Kingston V300 with Sandforce controller and MLC NANDs, which certainly has a completely different TRIM behavior than the Phison-fired ones. At first I suspected a faulty TRIM behavior in combination with chkdsk and the fact that the system reboots immediately after completion.īut they are not identical SSDs. They are all Kaveri systems with ASUS A68HM-PLUS motherboard and Kingston SATA SSD running in AHCI mode with the Windows standard AHCI driver.

In the forum, the affected person gives some characteristics of the affected devices. After that, the systems booted again after installing the SSD as a Windows disk in the original PCs. These could be corrected with chkdsk in offline mode. The /f option of chkdsk probably destroyed the NTFS file system.įurther analysis of the RAW partition with chkdsk in offline mode revealed errors with a corrupted 'file 9' and an error in the BITMAP attribute of the Master File Table. When analyzing the affected disks (SSDs) on a working system, it could be determined that the logical Windows drive on the disk was detected only as a RAW partition. The affected person was able to observe this on seven computers with Windows 10 20H2. The blue screen shown in the screenshot above appears with the stop code NTFS File System (it shows a NTFS FILE SYSTEM stop code, see here for an English version of the BSOD). Stop error NTFS File System, Source: -Forum The guy was able to prevent the re-boot from the other computers, after the seventh machine failed.

The affected person had seven systems, that can no longer boot after the file system check including repair. In the scenario described above, things went very badly wrong. The intension is to check the Windows drive for damage and (with the /f switch) immediately perform a repair. The administrator, who did the manual update install, decided to execute the following command after finishing the update installation: In a school, several systems with Windows 10 20H2 already installed should be manually updates to the current update status (Windows and Office updates). The problem was initially described by Nero24 in the German forum (the affected person contacted me via email). They all pointing to a strange bug, obviously brought to systems with cumulative update KB4592438. I've been contacted by several German blog readers by email and via comments within my German blog (thanks for that).

Chk ntfs