Intermittent BSOD's, since installing KB5004945


  1. Posts : 45
    OS Name Microsoft Windows 10 Home
       #1

    Intermittent BSOD's, since installing KB5004945


    Hi-

    After I installed KB5004945, I started experiencing intermittent BSOD's, with varying failure codes, such as: 0x00001000CDCCDD, 0x0000000000000000002 and 0xFFFFF802461498BE, etc. When this occurs I reboot and run (RUN IN POWERSHELL AS ADMIN. DISM /online /cleanup-image /restorehealth and sfc /scannow.) to clean up the problem. My system is currently running w/o any difficulties, until next time... Any help is truly appreciated, Thank you.

    Edition Windows 10 Home
    Version 21H1
    Installed on ‎10/‎20/‎2020
    OS build 19043.1083
    Serial number YJ00S33M
    Experience Windows Feature Experience Pack 120.2212.3530.0
    Intermittent BSOD's, since installing KB5004945 Attached Files
      My Computer

  2. axe0's Avatar
    Posts : 14,858
    Windows 10 Pro
       #2

    Please run driver verifier using the following settings for 48 hours.
    • Special Pool
    • Force IRQL checking
    • Pool Tracking
    • Deadlock Detection
    • Security Checks
    • Miscellaneous Checks
    • Power framework delay fuzzing
    • DDI compliance checking



    Warning: driver verifier could cause boot issues and/or performance issues.



    Resetting driver verifier options (recommended in this order)
    1. In normal mode open an administrator command prompt and enter the below command
    2. In safe mode open an administrator command prompt and enter the below command
    3. On 3 boot failures, you'll boot automatically to the recovery options,
      • click Troubleshoot
      • go to the advanced options
      • choose command prompt
      • enter the below command

    4. Boot with the recovery media, see above 4 steps in option 3.
    5. Via the recovery options or recovery media, select a restore point prior enabling driver verifier

    Code:
    verifier /reset


    Crashed when running driver verifier
    1. Reset driver verifier
    2. Boot in normal mode if necessary
    3. Follow Blue Screen of Death (BSOD) Posting Instructions to provide the requested logs




    Extra information about driver verifier
    When you run driver verifier, there are two things you're looking out for
    1. Driver verifier won't find any driver violating something and thus in the time you need to run it there won't be a crash
    2. Driver verifier will find a driver violating something and thus the system will crash.

    The end result of driver verifier is either of the two, but when driver verifier finds something your system will BSOD.


    Driver verifier essentially validates selected drivers on selected actions, this validation adds some delay to actions performed in the background which results in a performance decrease that many people notice. This is called stress testing drivers and depending on quite a few factors this performance decrease is worse for some than for others, and some won't even notice a difference.

    Depending on the drivers selected, it is possible that some of the selected drivers are so-called 'boot' drivers, meaning they load when your system is booting. If these drivers don't pass a validation check, your system will crash, but since the drivers are loading at boot, your system will basically be in a boot loop. That is one of the risks involved and the most important one. Of course, there are various methods to recover from it.

    If you want visual confirmation that driver verifier is actually running, copy/paste the following command in powershell or command prompt

    Code:
    verifier /query
    If the command gives a result similar to this, it means driver verifier is running.


      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 10:42.
Find Us




Windows 10 Forums