Windows 10 broke the blue screen of death bug again? Here’s the solution

Windows 10 broke the blue screen of death bug again! Every Windows 10 update seems to always bring some inexplicable problems, and this time is no exception. Not long ago, Microsoft released the December cumulative update KB4592438 for Windows 10.

Some users found that Windows 10 20H2 will cause a blue screen of death after running the ChkDsk disk scan tool, and the blue screen message displays the error message “NTES_FILE_SYSTEM”. From this point of view, this is a blue screen caused by the file system.

Windows 10 broke the blue screen bug again, the blue screen information displayed “NTES_FILE_SYSTEM”

ChkDsk is a command that many Windows 10 players are very familiar with. It is used to repair disk errors. Common uses include entering “chkdsk /f” in CMD to repair U disks and so on. ChkDsk is a very common technique, and Windows 10 system will run it regularly to fix certain problems. This time Windows 10 will trigger a blue screen because of it. If it is triggered by the system automatically running ChkDsk, the user may not even know what is going on, and suddenly encounter the blue screen.

ChkDsk is a very commonly used command. It is reported that even when using a virtual machine, the error can still be reproduced, and in the most serious cases, it may even cause file system damage and fail to boot!

In fact, this is not the first time Microsoft has recently overturned a memory-related issue. After the Windows 10 20H2 update was pushed, many users encountered the blue screen of death. After investigation, Microsoft believed that this was due to some devices using old, incompatible drivers and Thunderbolt ports that caused NVMe SSD errors. In response,

Microsoft made the KB4586853 patch and pushed it to users with the cumulative update in December. However, the old problem has just been solved, and the new ChkDsk problem has followed one after another. Microsoft also quickly provided a solution this time, let’s see how to do it.

First of all, if you have triggered the bug, but the system can still boot normally, you can download the latest patch released by Microsoft and install it to suspend the problem.

Download link: https://download.microsoft.com/download/f/d/b/fdbe1bf5-677f-41da-b2a5-

b0143f33d11d/Windows%2010%20(20H1)%20Known%20Issue%20Rollback%20121920%2001. msi

This is a special rollback group policy that is used to temporarily prevent the system from automatically running the ChkDsk scanning tool and avoid triggering the blue screen of death.

And if it has been unable to boot due to this bug, you need to fix it through the following steps:

• After the system fails to boot several times, it will enter the advanced boot mode, as shown in the figure below.

• Click “Continue”-“Advanced Options” and find “Command Prompt”.

• Enter the following command line in it:

chkdsk /f

• Next, the system will repair the file system in safe mode, and restart the computer after completion.

In general, this is a bug that can be confusing, but in fact, it cannot be fixed. I hope Microsoft will fix the problem fundamentally soon.