G3258 won't overclock

[LTC8K6]

Asus B85M-G R2.0 board. Got the board and the chips back in October 2014.

BIOS was 2008.

I bought an i3-4360 with the board. A little later I bought a G3258 and installed it in the board. I had it up to 4.8Ghz.

I got bored with that and I took the G3258 out and put the I3-4360 in, and used the system as my Win10 Insider test mule, to run the different Win10 builds.

G3258 was just sitting on a shelf in it's original packaging after that.

Had no problems at all with the system.

Fast forward to a couple days ago. I decided to see what the 3258 could do with the CPU-Z bench, since it would run at a relatively high clock speed.

Well, it won't anymore.

If I set the multiplier to anything over 32, Win10 won't run. I see Windows just start to load, then BEEP, and restart, in a loop.

I can break in to the loop with the delete key, and get to the BIOS. If I don't break in, the loop continues.

BIOS was the same, 2008.

Set the multi to 32, and Windows boots right up.

It's as if Windows does not like me overclocking the chip.

At 3.2Ghz, the chip runs cool, even under the Intel Burn test.

I did load the latest BIOS, but there was no behavior change.

The i3 still works fine, as does an E3 1231 V3 Xeon.

It really seems to be that multiplier setting.

 

[LTC8K6]

I see in some other threads, that this may be a microcode problem or possibly a deliberate change to the microcode?

 

[jpiniero]

Yeah only Z mobos are supposed to be allowed to OC. Microsoft/Intel likely fixed this loophole with the updated microcode.

 

[Dufus]

If you can boot into W10 without overclock then try taking ownership of "Windows\System32\mcupdate_GenuineIntel.dll" (security tab in properties) and rename it mcupdate_GenuineIntel.dl_ or whatever. Then try rebooting with your overclock.

 

[LTC8K6]

If you can boot into W10 without overclock then try taking ownership of "Windows\System32\mcupdate_GenuineIntel.dll" (security tab in properties) and rename it mcupdate_GenuineIntel.dl_ or whatever. Then try rebooting with your overclock.

Yeah that seems to be the solution, but this is a windows insider preview build, so I am not going to bother.