Results 1 to 5 of 5

Thread: Windows 10 KB4100347 update breaks Broadwell-E overclocking

  1. #1
    HEXUS.admin
    Join Date
    Apr 2005
    Posts
    27,488
    Thanks
    0
    Thanked
    1,695 times in 588 posts

    Windows 10 KB4100347 update breaks Broadwell-E overclocking

    It is possible to uninstall this Spectre Variant 2 patch if you wish.
    Read more.

  2. #2
    Member
    Join Date
    Mar 2015
    Location
    Darwen
    Posts
    102
    Thanks
    0
    Thanked
    3 times in 3 posts
    • Potbellieddwarf's system
      • Motherboard:
      • MSI X99A XPower Gaming Titanium
      • CPU:
      • i7-6850K @ 4.4GHz (Full custom watercooling)
      • Memory:
      • 32GB 3000MHz DDR4 Corsair Dominator Platinum C15 (8 x 4GB)
      • Storage:
      • 256GB Samsung NVME M2 (OS), 6 other 2.5" SSD's for game files, 2TB Seagate HDD (Storage)
      • Graphics card(s):
      • MSI GTX TITAN X (Maxwell) & EVGA Titan X SC(Maxwell) in SLI(Both are fully custom watercooled)
      • PSU:
      • SeaSonic P-1050XP3 1050W Platinum
      • Case:
      • Thermaltake Tower 900 (White) Full custom watercooled loop with twin pump
      • Operating System:
      • Windows 10 Pro
      • Monitor(s):
      • Asus 34" ROG Swift PG348Q
      • Internet:
      • SKY Fibre Pro 80 Mb Broadband (80 download & 20 upload)

    Re: Windows 10 KB4100347 update breaks Broadwell-E overclocking

    I am having no problems with overclocking my Broadwell-E i7-6900K on my MSI X99A XPOWER GAMING TITANIUM motherboard.
    I have checked and update KB4100347 is installed.
    I have even tried changing my overclock settings and everything is working fine.
    Not sure if I am lucky or if it doesn't affect MSI motherboards.
    <a href="http://eu.playstation.com/psn/profile/potbellieddwarf/"><img src="http://mypsn.eu.playstation.com/psn/profile/potbellieddwarf.png" border="0" /></a>

  3. Received thanks from:

    mtyson (24-09-2018)

  4. #3
    Registered User
    Join Date
    Sep 2018
    Posts
    1
    Thanks
    0
    Thanked
    0 times in 0 posts

    Re: Windows 10 KB4100347 update breaks Broadwell-E overclocking

    I have the same problem on my MSI X99S SLI Krait Edition and an Intel Core i7 6900K running just 3.7GHz instead of my overclock of 4.2GHz.
    I uninstalled the KB4100347 update and then I downloaded the win update tool here (the prevent-driver update tool doesn't work for it, it has to be this one)-> https://support.microsoft.com/en-us/help/3183922/how-to-temporarily-prevent-a-windows-update-from-reinstalling-in-windo
    It allowed me to find the KB4100347 on the win update list and block it from being downloaded and installed. It works without issues. The update doesn't appear anymore when I run windows update and the pc runs at 4.2GHz again.

    My wifes PC running with MSI X99S Gaming 7 and a Core i7 5960X@4.1GHz isn't affected by this update.

  5. #4
    Registered+
    Join Date
    Sep 2016
    Posts
    20
    Thanks
    0
    Thanked
    1 time in 1 post

    Re: Windows 10 KB4100347 update breaks Broadwell-E overclocking

    I also was affected by this bug, Asus Rampage V Edition 10 and 6950X OC to 4.4 Ghz, when update is installed working at 3.5 ghz instead of 4.4 ghz. I unistalled this update and blocked it using https://support.microsoft.com/en-us/...lling-in-windo 2 weeks ago.

  6. #5
    Admin Saracen's Avatar
    Join Date
    Jul 2003
    Posts
    18,325
    Thanks
    995
    Thanked
    3,170 times in 2,253 posts

    Re: Windows 10 KB4100347 update breaks Broadwell-E overclocking

    A classic example of why auto-installing updates, when MS want to, is a non-starter for me. But at least this one simply hit performance .... sometimes. What's utterly unacceptable is MS deciding I need an update, with the result being something I need, right now, not working until I've spent hours trying to work out how to un-bork my machines .... while, either a deadline looms or an editor/client is screaming at me.

    No thanks, MS. Before I do any updates, I clone the drive(s) and do a dry-run on the copy. Only if everything works fine do I update a live system. And I need to do updates whrn it suits me, in a known quiet time, not when you or your systems decide my PC is "ready".

    Though it's not the only reason, that alone kills W10 for me.
    Noli nothis permittere te terere.


Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •