Technical > Overclocking / Modding > [OC] Overclocking Question on i7 2600k

reply to ikyuaoki

Re: [OC] Overclocking Question on i7 2600k

Very nice! Mine is AMD quad core, that my motherboard does do combines both hypertransport bus and memory bus in summary of about 36GB/sec or 37GB/sec total of bandwidth, in reality I saw that my real memory bandwidth is up to 17GB/sec after I cracked up the CPU/memory controller integrated up up to close to 300Mhz clock frequency range so my games loads so faster flawless without any single packet error showing up I get...

I went run "winsat mem -v" in command prompt and saw that benchmark that says it is 17GB/sec. that really wowed me

EDIT I had to aligned the NB bridge to be sure at 2.3Ghz clock so I can get archieved up to 17GB/sec of an memory bandwidth meets.

Hmm, seems I wasn't as stable as I thought. I spent most of the day organizing all my home videos (removing dups, copying the ones my wife hadn't yet copied from her laptop, etc).

So I went to start converting them all to AVC (h.264/aac) and it only made it to like video 51 of 594 when my box rebooted itself. I was sitting at 4.5 GHz turbo and a Vcore of 1.27, but I guess I'll need a few more mv. I'm trying 1.29, though most of the guides I saw recommended 1.23-1.27 for a 4.5 GHz turbo.

*edit* BTW, the temps weren't anywhere near as hot as when I was running multiple instances of mprime (prime 95 for *nix). high 40's to 51-52 TOPS. So it wasn't a temperature issue. Unfortunately it did not panic the FreeBSD kernel, it appears to have just rebooted. So I think it was just the CPU going *poof* - at least, something that was so sudden/severe that the OS didn't even see it, it just went bye bye heh.

Does this sort of thing (just immediate reboot versus an OS crash) indicate I just need more Vcore?

FWIW, I'm on video 81 of 594 now with a 1.29 Vcore and it seems fine so far... *knock on wood*

You don't want to increasing the CPU Vcore up, as far as your Vcore setting is fine, that is no problems for you, don't fix anything if it isn't broken... I set my own Vcore to 1.275 volt from the default 1.300 volt, to keep my processor cooling while in operation of overclocking to 3.4Ghz state from the original 3.0Ghz default...

The OP crashed... how can you tell him do not fix what aint broken... it is broken...

Also you have an AMD chip... so lol all your settings vcore... all mean nothing...

As for the OP... I would try more vcore but we need to know your settings... windows gives error... I only know how to go off those...

Yeah, unfortunately I wasn't watching the screen when it crashed, so I don't know if it panic'd or just rebooted. With my previous hardware, I know that when I was tweaking the Vcore, it would spontaneously reboot when my Vcore was too low, so that's why I bumped it up by 20mV. I can post my BIOS settings later when I can get back into the BIOS, but the only thing I really changed was the CPU Vcore and the RAM voltage (1.5 V for these dimms). Everything else I think were basically defaults. I think there were a couple of other things that changed, but I was using a guide (I'll see if I can find the link) and I followed those settings to a T.
--
"Women. Can't live with 'em, pass the beer nuts." -Norm

reply to pflog
Try put to restore back to the default CPU Vcore and RAM voltage settings. Also if you are doing overclocking your CPU and bridge chipset, so just try put it back to default clock frequencies. if that works for you at default settings, there is no reason for you to adjust it over it because your OS gets crashed so easily.

Thank you anyway, but I have to disagree with your advice entirely.

My OS "doesn't gets crashed so easily", it wasn't the OS's fault I was overclocking and not giving the CPU enough voltage to operate properly at that frequency.

After bumping it up to 1.29 Vcore, it happily went through and converted all 594 videos in a row with the full 4.5 GHz turbo. So I think I found my sweet spot. I could try 1.275-1.285 but since I'm not seeing that much increase in temps from 1.27 to 1.29, I'm going to leave it alone.
--
"Women. Can't live with 'em, pass the beer nuts." -Norm

What default CPU voltage it was runs at? and I guess you have a monsterious heatsink with bunch of heatpipes integrated.

I don't know for sure what the default voltage is but I did find this:

You likely just need more vcore despite what the guide says you may have a crappy chip (oc wise) you are on the right path... shoot her up with a little more vcore...

Unless you oced your ram... or bclock... it really can only be vcore... or pll, vtt, etc...

Nope, left the bclk and ram alone I am running the RAM at 1600 (spec'd) and with the spec'd timings.

I was able to get through converting all 594 home videos with ffmpeg/x264, so looks like 1.29v is my sweet spot
--
"Women. Can't live with 'em, pass the beer nuts." -Norm

I think you're doing good with your vcore, you can add a little more if you need to.

But since you're using all 4 DIMM slots, I would add a little more to it than the stock 1.5v. to help the IMC a bit.
I have mine currently at 1.5125v. I incremented it by 0.00625v at a time.

Hmm, ok thanks for the tip. If I notice any further instability, I'll try giving the RAM a little more voltage
--
"Women. Can't live with 'em, pass the beer nuts." -Norm