Windows 10 20H2 causes blue screen of death, Microsoft recommends a “rollback”

Windows 10 20H2

A few days ago we saw that the Windows 10 May 2020 Update was giving problems, and today we have been able to confirm that Windows 10 20H2 (November 2020 Update) not only It has not arrived without errors, but is giving major headaches to some users.

According to the Redmond giant, the Windows 10 20H2 update is causing two serious errors that cause two critical failures. We are going to see them in parts to better understand the situation in which this update is currently, although I already advance what I have told you on other occasions, it is better to postpone the semi-annual updates until we are totally sure that they have been «duly polished », And it is never a good idea to force it to update.

The first problem that Microsoft has confirmed is precisely the more serious of the two. This is an error identified as “DRIVER_VERIFIER_DMA_VIOLATION (e6) A driver being verified attempted an illegal DMA operation.” This fault occurs due to a compatibility problem that occurs with some PCIE NVMe SSDs, and inevitably leads to a blue screen of death. Microsoft has confirmed that it is working with Intel to resolve this issue, and has partially halted the rollout of this update.

Second, we have an error that forces a restart. When it occurs, the user is prompted to log out and restart the computer Due to a problem linked to the “MMC snap-in and local security authority process”. We might think that it is not serious, but this changes completely when we realize that after following the steps and restarting the computer, we tirelessly receive the same error message again.

What options do I have to resolve these Windows 10 20H2 issues?

Well unfortunately not many. Microsoft recommends do a rollbackIn other words, go back to the immediately previous version in case we have either of these two problems, since there is still no alternative, and it seems that it will still take a while for a patch to arrive that resolves both errors.

We can also manually remove update entering the corresponding Windows 10 path (Settings> Windows Update> View Update History).

Microsoft has built up a considerable history of serious bugs with the latest updates that They are not limited to Windows 10 20H2. Among them are from the classic blue screens to its black version, crashes, loss of Internet connection, failures in the start menu and loss of data in both some browsers and certain applications.

I think this simple summary explains, quite clearly, why it is advisable not to force semi-annual updates, and why we should wait a reasonable time before launching to update our operating system.




Please enter your comment!
Please enter your name here