KB5003690 BSOD

Anonymous
2021-06-24T12:44:33+00:00

Not so fast! On installing this update.

Installed KB5003690 (tried) on five rigs. Three no issue, one refused to install, and worst of all one started BSOD constantly after installing. Removed from that rig and all was fine and returned to normal. Reinstalled KB5003690 to verify this was the issue and yes, the BSOD issues returned, again uninstalled and all returned normal again. I'm satisfied in saying that KB5003690 is / was the issue.

Heidi-Ann

Scientific Frontline

Rig with issue

Edition Windows 10 Home

Version 20H2

Installed on ‎10/‎21/‎2020

OS build 19042.1055

Experience Windows Feature Experience Pack 120.2212.2020.0

Processor AMD FX(tm)-8320 Eight-Core Processor 3.50 GHz

Installed RAM 8.00 GB

System type 64-bit operating system, x64-based processor

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

93 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2021-07-08T22:18:53+00:00

    I ran Who Crashed to diagnose my dump files, and it consistently identified system service exception BSOD, ntkrnlmp.exe as the problem. I uninstalled my Nvidia drivers then reinstalled them, then tried installing 4945, and again with the same failure.

    Question: Is this only happening to machines with GeForce drivers, or it it affecting AMD/ATI graphic drivers as well? BTW, my 1st Gen i7 laptop with Intel graphics handles the update with no issues.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-07-08T21:55:36+00:00

    for 16 hours everything was fine - and i begun to relax, thinking the problem might be solved by now. but 5 minutes ago my pc crashed again with a bsod. i can`t believe that. uninstalled KB 5004945 immediately. so do not feel too comfortable - i think, the bsod issue no longer occurs that often as with KB5003690. but it is still there...

    This is so annoying. And still no comment by Microsoft...

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-07-08T19:37:46+00:00

    With the others success, I installed the new 5004945 and so far no problems 1 hour in. It wouldn't run more than 2-3 minutes before. I wonder if something additional in this new cumulative update had to be paired with the problematic quality update.

    Many thanks to Microsoft to helping us all figure this out ./ end sarcasm.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-07-08T19:08:13+00:00

    24hours+ without BSOD on 5004945

    Was this answer helpful?

    0 comments
  5. Anonymous
    2021-07-08T16:05:44+00:00

    And now they found out that the emergency patch to fix the security flaw doesn't even work!

    Recommendation is not to install if you have issues or not. It doesn't work.

    You can read more at several geek sites such a Beta News.

    Only if you have pre-configured your machine to use Point and Print policy and configured to not show the elevation warning. Which should only affect Pro and Server editions, as its a non-standard (none-out-the-box) group policy settings.

    99% of machines will not have this enabled (not that i have access to these numbers, but im guessing 99%+++ of machines dont need it, or users even knowing about it).

    For Windows home users (and pro users who dont want to mess group policy for some reason, you can create these and set the value as follows (tho this should NOT be needed, and you have no reason to do so unless you have some sort of idea/understanding of what you are doing, i will not and would not be doing it personally).

    HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Printers\PointAndPrint

    NoWarningNoElevationOnInstall = 0 (DWORD) or not defined (default setting)

    NoWarningNoElevationOnUpdate = 0 (DWORD) or not defined (default setting)

    Was this answer helpful?

    0 comments