4670K wont overclock

[Digitalle]

Built a new system at the weekend:

• 4670k
• Asus Gene VI
• H100I
• Seasonic G-550
• Corsair pro 1600

The first few days the the auto-over clock set it to 3.8 @ 1.2v without me touching anything. I decided to try and get a bit more, and somehow now I cannot get the cpu to run past clock speeds. Either by inputting the multiplier manually or letting the board do it itself like before. Screen shots:

Other information:

• Bios updated to latest version
• Reset cmos and removed the battery
• Also tried it with another 4670k that I have, same issue
• Please help

 

[OracIe]

So when you let the board do an autoclock to 3.8, does that work? If so, at what voltage?

 

[alex_123_fra]

So what happens when you set OC to manual and change the multiplier in extreme tweaker?

 

[Digitalle]

So when you let the board do an autoclock to 3.8, does that work? If so, at what voltage?

So what happens when you set OC to manual and change the multiplier in extreme tweaker?

Neither works. If i let the board use the optimised defaults it says in the bios that its going for the 3.8 but when it boots its still at 3.4.

When I do it fully manual mode, say set the multiplier to 42 and the vcore to 1.2, it boots and in cpuz the core shows as 1.2 but the multiplier never changes from 3.4.

 

[Digitalle]

Some more details:

At first the auto overclock/turbo boost was working fine at 3.8 at 1.2v

I then switched to manual mode push the overclock myself and it sitting fairly stable at 43x at 1.3v within my 80oc temp limit at full stress. I wasn't too happy with the 1.3v though so I wanted somewhere around 1.25 regardless of speed, just stable.

That's when this starting happening. I think I switched the turbo mode boost off in the bios, then re enabled it. That is the only thing I can think of that changed during the time I was working with it.

I also installed a new OS on a second drive today to rule out any software issues. Nothing changed.

 

[alex_123_fra]

How did you flash the latest bios version? If you didn't use bios flashback, I would do this and start again. In the interest of experimentation to find the route cause, try the bios just before the latest.

 

[Digitalle]

How did you flash the latest bios version? If you didn't use bios flashback, I would do this and start again. In the interest of experimentation to find the route cause, try the bios just before the latest.

The very first thing I did even before I installed an OS was flash the bios use the flashback feature of the ROG boards.

Yesterday to experiment I flashed them back to the previous bios, with no change. I then flashed back to the most recent version today again. Still nothing.

All the time using the flashback feature as apposed to the one done from the OS itself.

 

[Digitalle]

As you can see I really have exhausted all areas of experimentation before coming on here just in case I missed anything obvious. I have literally tried everything, all I really can do now is try and determine what is at fault. It seems to be the Mobo, but I cant really rule out anything, like the cpc, ram, psu etc. That's what is really annoying me. '

 

[alex_123_fra]

You can run windows diagnostics to ensure the CPU and RAM are ok (or memtest on a usb stick for the latter), but I highly doubt they are the cause.

If the mobo is somehow locking you out, then it really sounds like that is the cause and I would consider RMAing. Is there any code showing up on the board?

 

[Digitalle]

Yeah iv been all over the ROG forums for the past few days and after running through pretty much everything they have suggested RMA seems to be the way to go. I'm a little sad really, I build pc's for friends, family and work all the time, and never have an issues like this. Every single time I build myself one things go wrong.

I will run both windows diagnostic tool and memtest in the mean time, since the computer is completely usable, just to make sure. I wouldn't be so bothered but I purposely bought a high tier mobo/cooling system so I could overclock as much as I could, so I'm definitely not not letting the issue go.

No code shows up other than A0 i think it is which means everything is fine from its point of view.

 

[alex_123_fra]

Agree you should definitely not let it go. Got to be the board unless Intel somehow managed to put the world's first 4670 (non K) into a 4670k shell and box!

Your retailer should sort it quickly. If it was OCUK and it is within 14 days, you'll be swapped even faster.

Have to say I haven't had any issues with any Asus ROG boards ever but these things do happen. MSI and Gigabyte boards have been less reliable for me.

 

[kaku]

Last thing I can think of is the power management settings in Windows. It's a long shot, but it's the only other thing I can think of that affects processor speeds.