Carecat posted:

My 2500K is sitting at 1.361V with a 47x. It gets to an eyebrow raising 1.396v and 78c peak in IBT on normal which makes me hesitate to try it on maximum.

Economic Sinkhole posted:

Which sensors should I be paying attention to? I am trying to overclock my 3750K with an Asus P8Z77-V Pro. HWiNFO lists a temp for each core, CPU package and a under Nuvoton NCT6779D it also lists CPU, often much lower than other temps given.

Agreed posted:

Stability test the stock setup first. There is nothing more frustrating than doing everything right while overclocking your computer and getting endless blue screens, failed tests, etc. - only to drop it all back to stock, run the same tests, and it turns out you've got a bum stick of RAM, or the processor's defective and won't run at stock clocks.

Step zero of overclocking is do everything you would do to test the stability of an overclock to your stock-settings assembled computer.

Quick list (you don't get the joys of using the computer during this period but you can either have your cake or eat it, and it's a good idea to make sure the cake isn't spoiled first):

Memtest 86+, at least one full iteration but preferably a few. You want to work the integrated memory controller, the motherboard's pathways to the RAM, and of course the RAM itself. If you get errors, consider a slight bump to RAM voltage. If it's still unstable, slight voltage bump (as in, one increment, two max) to VCCIO. If you still get errors, probably bad RAM.

Prime95 in admin mode, blend, for a first-go to establish stability I would say a solid 24 hour run isn't overkill. You're trying to prove beyond a shadow of a doubt that the basis of your system from which you'll be overclocking is stable. 9 hour or 12 hour Prime95 runs are fine for a lot of stuff, but you want ultimate confidence here, so let it roll.

I guess you could test with IntelBurnTest, but that seems really silly for establishing stock performance. That is, after all, the "quick check" of overclocking - 10-20 Standard stress runs in admin mode will usually let you know if your processor's thermal performance is acceptable at the clock and voltage, and 2-3 runs in Maximum stress gives the whole processor&RAM interface a nice workout without cooking your stuff, ideally. But it's a tool to save time later, for a base system stability confirmation you should stick to the golden tools above and ignore the shortcut tools like IBT or OCCT.

Factory Factory posted:

After your OS is patched and stable. Technically, you can do it beforehand if you have stress testing programs on a LiveCD, but that's pretty hard to arrange. You don't want to risk instability while you're patching, or you could severely gently caress up your OS install. You also don't want any unpatched-software crashes messing with figuring out whether the hardware is stable or not.

An overclock is one you'll still want to stability test in a perfect world, but it should also have an excellent chance to just work. And you can always set an easy overclock now and tweak later.

Zenzirouj posted:

Great, thanks guys! I ended up spending the evening with an icky gross GIRL so I didn't have time to do anything, but tonight is the night.

Agreed posted:

You got nothin' scrub I'mma new dad (incoming red title text: SHUT THE gently caress UP ABOUT BEING A NEW DAD YOU DICK) and that means as soon as this little dude learns to move around and mess with god damned everything I am probably going to have to give up my 200mm fan mounted on a mesh-cut side panel fan that I got from Corsair for free and put on the solid side panel that I got from Corsair for free.

Truly changing moments. My airflow

Carecat posted:

Motherboard is a Gigabyte Z77-D3H. Bought an overclocked bundle from Scan so I didn't set it up. I was looking at VID which was 1.36-1.38. The vcore is 1.428V

Kind of not surprised now that it rebooted itself before getting to bios around six times before it started today. Changed to the unclocked profile. Looked like everything was on auto except the multiplier and voltage.

CPU was manually set to 1.425V, CPU VTT at 1.1. BLCK is 100. Everything else is on auto. Not sure what I paid for other than a 24 hour stress test and a kamikaze vcore setting.

Dogen posted:

Did you cut the mesh out? Can't see that mattering.

Dogen posted:

Just for reference, my wife's best friend has a 14 month old that crawls around and is pulling up, and the baby's pop has a 650D with the window just sitting on the floor. Worst I think that has happened is she has accidentally turned off the computer (she likes the lights )

Factory Factory posted:

Economic Sinkhole posted:

Thanks. It looks like Asus's Ai fan control thing uses the Nuvoton CPU temperature to decide how fast to spin the fans. It lags behind the Digital Thermal Sensors by a lot, showing up to 40C cooler than the other ones at times. Should I be using the Ai fan control or something else?

Factory Factory posted:

Voltage shouldn't be increasing at load; it should be decreasing. Do you have LLC pumped up to max or something?

tijag posted:

This is a good question. Although for me I'm not sure it matters. I have got my i5-3570k OC'd to 4.5ghz on all 4 cores with OCCT going for 10 minutes without any errors.

That's long enough for me to be comfortable with the OC.

highest temp was 64C on one of the 4 cores. Offset voltage is +.060.

I'm thinking later [after a few weeks] I'll check it again, and if it's still looking pretty good I might try to push the voltage a bit more and get to 4.7ghz. My CPU VCORE voltage was 1.16v at the highest. It idles at 0.98V.

This is a good start right?

Dogen posted:

Pretty darn good temps for 4.5, yeah.

Agreed posted:

Stability test the stock setup first. There is nothing more frustrating than doing everything right while overclocking your computer and getting endless blue screens, failed tests, etc. - only to drop it all back to stock, run the same tests, and it turns out you've got a bum stick of RAM, or the processor's defective and won't run at stock clocks.

Step zero of overclocking is do everything you would do to test the stability of an overclock to your stock-settings assembled computer.

Quick list (you don't get the joys of using the computer during this period but you can either have your cake or eat it, and it's a good idea to make sure the cake isn't spoiled first):

Memtest 86+, at least one full iteration but preferably a few. You want to work the integrated memory controller, the motherboard's pathways to the RAM, and of course the RAM itself. If you get errors, consider a slight bump to RAM voltage. If it's still unstable, slight voltage bump (as in, one increment, two max) to VCCIO. If you still get errors, probably bad RAM.

Prime95 in admin mode, blend, for a first-go to establish stability I would say a solid 24 hour run isn't overkill. You're trying to prove beyond a shadow of a doubt that the basis of your system from which you'll be overclocking is stable. 9 hour or 12 hour Prime95 runs are fine for a lot of stuff, but you want ultimate confidence here, so let it roll.

I guess you could test with IntelBurnTest, but that seems really silly for establishing stock performance. That is, after all, the "quick check" of overclocking - 10-20 Standard stress runs in admin mode will usually let you know if your processor's thermal performance is acceptable at the clock and voltage, and 2-3 runs in Maximum stress gives the whole processor&RAM interface a nice workout without cooking your stuff, ideally. But it's a tool to save time later, for a base system stability confirmation you should stick to the golden tools above and ignore the shortcut tools like IBT or OCCT.

tijag posted:

Is there any consensus on what is 'safe'?

Agreed posted:

Nope. Right now it's just based off of VID and watch-and-see with the extreme overclockers at other places. Remember that we were initially told 1.5V was safe for Sandy Bridge, and sure, some chips that are extraordinary can take that with high-end cooling, but it turns out it cooks other chips right away regardless of cooling (destroys them internally) and Intel amended to 1.38V as a ballpark safe figure.

I kind of have my doubts that they themselves know what the actual safe 24/7 voltage is for Ivy Bridge at the moment, two lithographic changes (one really huge in terms of its potential effects) at once? That's basically alchemy, no poo poo, there's a lot of guesswork involved in process shrinks and new process transitions. Who knows how many spindowns were involved in making Ivy Bridge chips that function? Intel is less forthcoming, it seems, about process issues than GPU makers are (but then Intel fabs their own chips, nVidia and ATI can both say "TSMC " when shareholders get antsy).

Factory Factory posted:

EIST-type jumps aside (from a low-power state ~1.00V to load), the way Vdroop works, a more intense load should result in a lower Vcore than a less intense load (e.g. IBT is more intense than Prime95). If the Vcore goes up instead of down, that means something is counteracting Vdroop, at that something is LLC.

For example, I have LLC completely disabled on my board, and I Prime95 at 1.366V VID and 1.32 +/- .08 Vcore. IBT has the same VID, but 1.312V Vcore flat.

Hiyoshi posted:

So what you're referring to is the voltage difference between an intense 100% load and a light 100% load rather than the difference between a 0% load and 100% load, correct?

Hiyoshi posted:

So what you're referring to is the voltage difference between an intense 100% load and a light 100% load rather than the difference between a 0% load and 100% load, correct?

zenintrude posted:

am I going to be able to OC using this as easily/stably as the ASUS boards

quote:

and is there a good tutorial for its BIOS I should look at?

Agreed posted:

Nope. Right now it's just based off of VID and watch-and-see with the extreme overclockers at other places.

Factory Factory posted:

That particular board has a weaker VRM design. Overclocker-type boards are the -GDxx models. With it, you may have to settle for a lower frequency, but maybe also not if you're overclocking Ivy Bridge and end up temperature-limited.

Factory Factory posted:

Actually, you can get pretty darn far leaving the voltage at stock. I think AnandTech's sample hit 4.4 GHz at the default 1.05V Vcore. I would not worry in the slightest up to 1.1V, and I personally would feel absolutely safe at 1.25V, maybe 1.3V.

Agreed posted:

Right now, be a touch conservative with voltage, but be very wary of heat. Until we know more, that is the best indicator that everything is fine, or not.

Agreed posted:

Power delivery adjustments in the VRM phases happen at between 300mhz and 500mhz for Asus Intel boards, for example.