I7 6850K problem.

[Vlad Tepes]

Hi! 

I've been looking everywhere for an explanation of why my cpu started behaving the way it now does, or maybe it's the motherboard playing tricks on me, not sure. I will try to explain.

At the start it was no problem to get a stabil overclock using XMP and sync all cores 4.4Ghz at 1.285V using BCLK 100 x 44 .

Now it isn't accepting anything using bclk 100, I have to use bclk 125 x 34 .

I can set it in bios and at the boot up screen it says 25% overclock but in windows it's back to basic xmp profile maxing out at 4Ghz.

Can you damage your cpu in such a way that this could accrue? 

I did the mistake of using asus ai suite 3 to auto tune my system. It applied the voltage 1.61V on the vcore........

Could this be why I'm now seeing this problem? 

When I now try using the 4way optimisation I get a blue screen before it even start the process.

But running bclk higher than 100 seems to work just fine.

Passing cinebench at 4250Mhz and no crashes while gaming.

 

System specs are following

 

Asus Rog strix x99 gaming (bios 1903) 

Intel i7 6850K 

Noctua DH15

32Gb 3000Mhz corsair vengeance (4 sticks)

Intel m.2 500Gb 

2x Samsung 256Gb Evo something something SSD.

2x Asus strix 1080Ti OC HB SLI. 16x pcie.

Evga nova 3 1300W PSU 

 

 

 

 

[X_X]

Have you tried ownership of C:\Windows\System32\mcupdate_GenuineIntel.dll, renaming it to something like *.dl_ then rebooting and see if the problem still exists?

 

If no different you can rename the file back to it's original name.

[Vlad Tepes]

16 hours ago, X_X said:

Have you tried ownership of C:\Windows\System32\mcupdate_GenuineIntel.dll, renaming it to something like *.dl_ then rebooting and see if the problem still exists?

 

If no different you can rename the file back to it's original name.

I will try that, never heard about it but i will give it a shot 

[Vlad Tepes]

Just placed a order of a i9 9900K instead, this crappy x99 shit is hitting the bin! 

[X_X]

The file you renamed is the file that contains microcode updates and a few months back it was a microcode update that broke overclocking on Broadwell-E.

 

https://forums.evga.com/Latest-Intel-MicroCode-breaks-Overclocking-on-BroadwellE-m2857370.aspx

 

https://hexus.net/tech/news/cpu/122477-windows-10-kb4100347-update-breaks-broadwell-e-overclocking/

 

and so on. By renaming the file the microcode update should not have taken place thereby restoring OC'ing. Sorry it didn't work out for you.