Windows 10: BSOD after installing KB3197954

Discus and support BSOD after installing KB3197954 in Windows 10 BSOD Crashes and Debugging to solve the problem; Hello, I am currently facing an issue regarding a specific windows update (KB3197954). Let me first explain how this BSOD issue started. So back in... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by UltimateAntic, Nov 9, 2016.

  1. BSOD after installing KB3197954


    Hello, I am currently facing an issue regarding a specific windows update (KB3197954). Let me first explain how this BSOD issue started.

    So back in summer, I finished building my new rig and installed a clean copy of Windows 10 Pro (november update) on my PC. Everthing worked and I was very happy with it. Then, the Anniversary update was released. The upgrade to the new build went smooth and everthing was working fine. But then Microsoft released update KB3197954 which really screwed it up.

    Basicly, ever time when I turn on my system, windows will either keep BSOD'ing at either the boot screen or in the lock screen (sometimes it also BSOD's a few moments later after logging in). When the PC restarts after the BSOD, it happens again and again. Eventuelly after like 3 to 5 restarts, everthing will start working again and I will be able to use the system as if nothing was wrong with it. If I restart again, the pc will restart without any issues. But once I turn off the system and turn it on again next day, the occurance will re-occur again. It seems that this weird occurance happens only once each day.

    When I uninstalled the KB3197954 update, the weird BSOD's would stop. Unfortunately windows update automaticly reinstalled the update again which caused the BSOD's to reappear again. To top it off: the update would no longer show up in the list of updates to uninstall, meaning that I was stuck with it.

    So I decided to completely format the SSD and begin with a clean copy of the windows 10 anniversary edition. After installing Windows and the neccesary drivers, I installed all the updates including KB3197954 since I had hoped that the OS reinstall would have fixed any issue that might have caused this update to be so incompatible with my system. Unfortunately, all the BSOD's started occuring again after installing KB3197954, even after a full OS-reinstall.

    So I uninstalled KB3197954 and disabled Windows update through group policy. But when Microsoft released KB3200970, I decided to download KB3197954 and then install KB3200970 to see if the new update fixed the issue. But unfortunately, the BSOD's were still there.

    TL;DR Update KB3197954 caused my system to keep BSOD'ing at bootup.

    Attachment 109545

    So basicly, my question is how, why is KB3197954 causing my PC to keep BSOD'ing? I noticed that the BSOD's each give a different error message such as BAD_POOL_HEADER, BAD_MEMORY_MANAGEMENT, CRITICAL PROCCES DIED, KMODE_EXCEPTION_NOT_HANDLED.

    :)
     
    UltimateAntic, Nov 9, 2016
    #1

  2. Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB3197954) fails to install

    What happened when you tried this?

    Download and install Cumulative Update for Windows 10 Version 1607 for x64 based Systems (KB3197954)

    Microsoft Update Catalog
     
    Gerry C J Cornell, Nov 9, 2016
    #2
  3. need fix for cumulative update for windows 10 version 1607 for x64 systems (KB3197954 - Error 0x8e5e0152

    After endless failed attempts to install KB3194798, my HP desktop tried to install KB3197954 and this also failed. Then KB3201860 and KB3199986 installed successfully. Now I'm back in the loop of endlessly trying to install KB3197954 over and over again.
    It fails exactly the same way as KB3194798 did. Installs patches up to 30%, restarts, continues up to 100% and then says it was not successful and backs everything out and restarts. Come on guys, this is unacceptable!
     
    **** Wilkins, Nov 9, 2016
    #3
  4. BSOD after installing KB3197954

    UPDATE:

    Basicly, these random BSOD at bootups only occur during cold boots where the system hasn't been used for some time.

    However, sometimes instead of giving a BSOD, it will either randomly power off or give me a bootup error saying that a certain file was either missing or corrupt.

    Also, it seems that the windows update that I originally blamed, isn't the problem here since the BSODs now happen even if said update is uninstalled.
     
    UltimateAntic, Nov 13, 2016
    #4
  5. axe0 New Member
    Hi UltimateAntic,

    Apologies for the delay.

    Are you still in need of help?
     
  6. Yes I am still in need of help.

    What I've already tried:
    -Reinstall Windows
    -Run memtest86 (6 passses, no errors)
    -Reseat GPU and power cables.

    None of these had any effect.
     
    UltimateAntic, Nov 16, 2016
    #6
  7. philc43 Win User
    Could you rerun the Memtest86 from a cold start and make sure that you let it run for at least 8 passes. Only then can you rule out faulty memory.
     
    philc43, Nov 17, 2016
    #7
  8. BSOD after installing KB3197954

    UPDATE:

    Alright, today I tried the follwing approach:

    I disconnected the following hardware in order to see if the PC would behave normally with the minimum required hardware

    -GPU
    -All storage devices and optical devices except for the boot SSD
    -All case fans
    -Only 1 RAM stick instead of 2

    Results: PC coldbooted fine with no crashes or errors. This indicates that one of the follwing hardware I removed was causing trouble. So I decided to add 1 piece of hardware at a time and test the system

    The first hardware I reconnected was the RAM stick (lets call this memory stick #2). I started my PC again and suddenly it started BSOD'ing again at boot. So adding that memory stick made the system behave weird again. So what I did was remove all installed RAM sticks and then only reconnect memory stick #2 again to see if this memory module was defective. The system booted normally and seemed stable at first, but a reboot later, it BSOD'd.

    So I reconnected all the hardware back except for memory stick #2 and so far everthing seems stable. I will do a memtest86 on the possible defective memory stick tommorow to see if its defective.

    So I think that so far, I can conclude that BSOD's were being caused by either:

    -Defective stick
    or
    -Both RAM sticks not compatible in dual channel mode.
     
    UltimateAntic, Nov 17, 2016
    #8
  9. philc43 Win User
    That's great. Hope it continues to run well! Let us know how you get on.
     
    philc43, Nov 20, 2016
    #9
  10. Ztruker Win User
    Make sure you run memtest86+:

    ===================================================
    Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

    MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

    • RAM will accept and keep random patterns of data sent to it
    • There are no errors when different parts of memory try to interact
    • There are no conflicts between memory addresses

    Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.


    BSOD after installing KB3197954 [​IMG]
    Warning MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

    If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.


    BSOD after installing KB3197954 [​IMG]
    Note MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

    Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.
     
    Ztruker, Nov 20, 2016
    #10
  11. So, since one of my RAM modules causes the coldboot BSOD. I decided to start the pc with only the faulty RAM installed and ran memtest on it. I ran the test for 10 passes, but strangely no errors were discovered.

    I will run memtest on the other memstick as well later.
     
    UltimateAntic, Apr 5, 2018
    #11
Thema:

BSOD after installing KB3197954

Loading...
  1. BSOD after installing KB3197954 - Similar Threads - BSOD installing KB3197954

  2. BSOD after installing update

    in Windows 10 Software and Apps
    BSOD after installing update: I'm having a serious issue with Windows currently. I recently just built a new pc and have had nothing but issues with it since. I've tested it and it appears that as soon as I install update 22H2 KB5022834 , which is the most recent update, my computer endlessly produces...
  3. BSOD after fresh install

    in Windows 10 BSOD Crashes and Debugging
    BSOD after fresh install: Hi, I just fresh installed windows after having some previous errors, and now I seem to continually get this error:The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b 0x00000000c0000006, 0xfffff8073c4d0652, 0xfffffb0b9778e530, 0x0000000000000000. A dump...
  4. BSOD after clean installation

    in Windows 10 BSOD Crashes and Debugging
    BSOD after clean installation: Hello all, So i installed windows 10 on new ssd , and it stuck into BSOD loop. Kmode exception not handled is code . Updated all drivers, still getting BSOD. In Safe Mode , it runs ok. OS build 19043.928 , version 21H1 182704
  5. BSOD after installing 2004

    in Windows 10 Ask Insider
    BSOD after installing 2004: Hi everyone, I recently installed Windows 10 2004 using the Release Preview ring of the Insider program on my desktop PC. I am well aware of the risks and I am not complaining about that. Recently my computer keeps having BSODs that show the error kmode exception not...
  6. BSOD after SSD install

    in Windows 10 BSOD Crashes and Debugging
    BSOD after SSD install: I installed a new SSD, not in raid, that was meant to run my virtual machines for school. This was a few months ago and they have been happening frequently. A full restore of windows was completed yesterday and I deleted everything because I am done with school, the BSOD's...
  7. Windows 10 update (KB3197954) Continues to fail

    in Windows 10 Updates and Activation
    Windows 10 update (KB3197954) Continues to fail: I have continued to fail in updating the Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB3197954). I have tried to manually install it from the Catalog as well and it continues to fail. Link to my Onedrive for my System Log: Microsoft OneDrive -...
  8. CU KB3197954 error

    in Windows 10 Updates and Activation
    CU KB3197954 error: OS version 14393.321 This happens everytime at 11% progress. So far I've tried - System restore - WindowsUpdateDiagnostic tool - Emptied Windows/SoftwareDistribution/Download folder to no avail. What else could I do? [img] 68252
  9. Install after BSOD

    in Windows 10 Installation and Upgrade
    Install after BSOD: All of a sudden I have been getting BSOD/Rolling Reboot on a W10 system upgraded from W7. The only thing I could do is to do a fresh install. I tried using the repair disk, but repairs failed. So I finally tried the reset and was able to bring the PC back up, however the...
  10. Cumulative Update KB3197954 Windows 10 PC and Mobile build 14393.351

    in Windows 10 News
    Cumulative Update KB3197954 Windows 10 PC and Mobile build 14393.351: UPDATE October 27th 2016: KB3197954 has now been released to the general public (non-Insiders). [img] Information Microsoft has released a new cumulative update Windows Update to Windows 10 PC and Mobile. This will bring Windows 10 to Build 14393.351. This...
Tags: