Windows 10 20H2 causes blue screen of death



[ad_1]

A few days ago we saw that the Windows 10 May 2020 update was giving problems and today we were able to confirm that Windows 10 20H2 (November 2020 update) not only did not arrive without errorsrather, it is giving some users major headaches.

According to the Redmond giant, the Windows 10 20H2 update is causing two serious causing errors two critical failures. We will see them in part to better understand the situation in which this update is currently found, although I have already anticipated what I have told you on other occasions, it is better to postpone the six-monthly updates until we are absolutely sure that they have been “duly refined” , And it’s never a good idea to force the update.

The first problem Microsoft has confirmed is the more serious of the two. This is an error identified as “DRIVER_VERIFIER_DMA_VIOLATION (e6) A driver being tested has attempted an illegal DMA operation.” This error occurs due to a compatibility issue this occurs with some NVMe PCIE SSDs and inevitably leads to a blue screen of death. Microsoft has confirmed that it is working with Intel to address 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 off and restart the computer Due to an issue related to the “MMC snap-in and local security authority process”. We might think it’s not serious, but this completely changes when we realize that after following the steps and restarting the computer, we tirelessly get the same error message again.

Windows 10 20H2

What options do I have to fix these Windows 10 20H2 problems?

Well unfortunately not many. Microsoft recommends do a rollback, i.e. to revert to the immediately previous version in case we have either of these two problems, as there is still no alternative, and it seems it will take a while for a patch to arrive that fixes both errors.

We can too manually remove the update by entering the corresponding Windows 10 path (Settings> Windows Update> View update history).

Microsoft has amassed a remarkable history of serious bugs with the latest updates that They are not limited to Windows 10 20H2. Among these are from the classic blue screens to its black version, crashes, lost internet connection, errors in the start menu and data loss in both some browsers and certain applications.

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

[ad_2]
Source link