“Our test lab got the problem replicated and confirmed that the problem is a Windows Update KB4100347 that includes a new Intel microcode, this is included in this latest major update.
The primary solution for this is to restore this version of the current Windows update to the previous version. Even though this is installed through the build update, this should still appear in the list of installed updates.This problem is coming up with a BIOS update to fix this problem, but this is not yet ready for an official release.”

3 users thanked author for this post.

Hopefully Asus plans to rectify this with BIOS updates as per MSI and EVGA ðŸ˜‰

For many years Asus, MSI and Abit were my preferred choice of motherboard brands (for clients and ourselves). On a personal level, performance tweaks to hardware was a major factor at purchase phase to achieve better overall performance boosts on Intel CPU’s.

Since the introduction of W10, overclockers, gamers and end-users are susceptible to MS methodology of patching and upgrades that causes a great disturbance in various communities.

I can only sympathize with those overclockers affected and truly feel saddened by the inadequate one direction MS has chosen. Needless to say, years later, my overclocking art is now consigned to history.
Fun was had..

| W8.1 Pro x64| Linux x64 Hybrids| W7 Pro x64 O/L| XP Pro O/L No problem can be solved from the same level of consciousness that created IT - AE

1 user thanked author for this post.

I’m hearing that Inspectre can help disabled the baked in ‘protections’ and/or mitigations that once was associated with a KB update.Â However, I know nothing of this app. I’m reading that Inspectre detects both meltdown/spectre and can disable them.Â Once disabled and you reboot you will notice another CPUID. And your CPU OC should return to normal.