Random BSODs/Crashes after Latest Cumulative updates (1703).


  1. Posts : 5
    Windows 10 1703
       #1

    Random BSODs/Crashes after Latest Cumulative updates (1703).


    I have been getting BSODs and crashes after the latest cumulative updates for 1703 (KB4023057, KB4033631, KB4074592, KB4073543). This was the only change that happened to my PC since the crashes started, so I figured they were the culprit.

    I uninstalled all of those updates and the problem seemed to go away. I was able to play without crashes or BSODs for multiple days. As expected, W10 forced the updates back on a day or two ago. Once again, I started BSODing again.

    I am able to identify and prevent the updates from coming again using WUSHOWHIDE. My question is--if I block these security and cumulative updates from WUSHOWHIDE, will I still receive future cumulative/security updates? Or will this prevent all future updates from coming? I'd like to be able to receive future updates, but definitely want to skip these for now since they are giving me problems.

    Thanks.
      My Computer


  2. Posts : 14,903
    Windows 10 Pro
       #2

    Hi Declio,

    Welcome to 10Forums.

    It depends on if future updates require those updates you're blocking, there's also a chance those updates will be replaced with other updates that may or may not cause trouble.

    You're sure all those updates cause this problem, not just one of them?
      My Computers


  3. Posts : 5
    Windows 10 1703
    Thread Starter
       #3

    axe0 said:
    Hi Declio,

    Welcome to 10Forums.

    It depends on if future updates require those updates you're blocking, there's also a chance those updates will be replaced with other updates that may or may not cause trouble.

    You're sure all those updates cause this problem, not just one of them?
    Hello,

    I'm not certain which one (or all) of the updates are causing the issue. I went with the nuclear option both times and removed all of them. I would have to guess that it is the cumulative update and not the security one (hope not at least!). To be honest though, I'm not sure I would like to spend the time uninstalling one at a time.

    If I continue to have issues with updates in the future, I may do a clean install of 1709. I had lots of gsync/multiple monitor problems with the latest version of the FCU, so I reverted to 1703 which has been performing fine. It has probably been long enough since I've tried 1709 to give a fresh install another go, but for now I will stick with 1703 and update this thread if I get any new information in the future.

    Thanks!
      My Computer


  4. Posts : 14,903
    Windows 10 Pro
       #4

    Speaking from personal experience with 1709, I would encourage you to skip 1709. I've had some issues with 1709 due to for me unwanted changes that are implemented such as extra load on the boot time because they think it's convenient to open the last closed app immediately after logging in, loading chrome with 25 tabs actually makes me wait longer for the system to load. Another one is the forced installs about 3D stuff which is completely useless for me and caused performance/stability issues.
      My Computers


  5. Posts : 5
    Windows 10 1703
    Thread Starter
       #5

    So the one update that I could not block with wushowhide came back today-- it is KB407592. It installed itself and I again started experiencing BSODs.

    This is very frustrating since it doesn't appear that I can block this update with wushowhide (it doesn't show up in the list--all of the other updates that came on that same day did show up in wushowhide and i successfully blocked them) and I'm on Home edition of windows so I don't think I have any other way to block W10 updates?

    The strange part about this particular update is that in my update history, it shows as the cumulative update (2018-02 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4074592))

    However, when I go to the uninstall screen, it shows as a "security update." I'm not sure why it's showing up as different things on each screen.

    The only thing I have found googling this update is this article which does point out some BSOD issues: Windows 10 Cumulative Update KB4074592 Issues

    Can I do anything else to block this particular update?
      My Computer


  6. Posts : 31,651
    10 Home x64 (22H2) (10 Pro on 2nd pc)
       #6

    Declio said:
    The strange part about this particular update is that in my update history, it shows as the cumulative update (2018-02 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4074592))

    However, when I go to the uninstall screen, it shows as a "security update." I'm not sure why it's showing up as different things on each screen....
    That is perfectly normal, it's just the way Microsoft do it. The uninstall screen in part of Control Panel and it uses an older style of naming than the newer Settings app. In fact, if you open a command prompt and type the SYSTEMINFO command you'll see an even older naming convention, they are all listed as 'Hotfix(s)'.

    The key identifier is the KB number, uninstall the 'security update' with the correct KB number and you are uninstalling the cumulative update.

    Can I do anything else to block this particular update?
    I see from your post on another thread here that you are having problems hiding this particular update, you're not seeing it listed in wushowhide. You cannot hide an update that is already installed, only updates that are 'available for this PC' can be hidden. This may be because windows update is sneaking it in again before you have a chance to hide it. I would first set a metered connection to prevent this, then uninstall KB4074592. After the reboot use wushowhide immediately, you should see it listed then and be able to hide it.

    Of course, the preferred solution would be to fix the BSOD that KB4074592 causes on your machine. If you leave it installed and follow the Blue Screen of Death (BSOD) Posting Instructions after a BSOD there are some knowledgeable experts here (others, not me) who can analyse it for you and suggest solutions.

    Edit: KB4077528 was superseded by KB4077528 on 22 February. This newer cumulative update may have fixed the problems that caused your BSOD.
    Last edited by Bree; 28 Feb 2018 at 19:33.
      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 11:07.
Find Us




Windows 10 Forums