Overclocking help with 2600K

xisor

Member
Apr 5, 2010
28
13
81
I have a 2600K and a gigabyte Z68 motherboard, and no matter what i do i cant get it to boot at 4.8ghz (bluescreen). I have it booted and stable at 4.69ghz (102x46) atm, and am curious about temperatures.

I have a hyper212+ and intelburntest puts my temps in the upper 80s-low 90s, handbrake encoding HD h.264 puts them in the mid 70s, am i ok or do i need to back off my clocks?

4.4ghz intelburntest puts temps in the low - mid 80s, everything else in low 70s. Is something wrong with my hyper212+ installation, or is this normal ranges for the cpu at these particular clocks?

Idle around 33 - 38c regardless of clock settings (yay for sandybridge being able to use EIST and Cstates etc when overclocked, unless thats whats holding back my overclocking?)

1.4vcore 1.9pll and 1.1vcc, are these dangerous?
 
Last edited:

RobertR1

Golden Member
Oct 22, 2004
1,113
1
81
Your temps seem a bit high.

Also, some chips are better than other. Your chip might not be able to hit 4.8ghz. I believe 1.35v is generally considered the "safe" voltage for these chips.

My 2600k can hit 4.8ghz just using the auto OC on my mobo but I'm not comfortable with my temps in the high 80's and having my vcore 1.4+

right now, I'm sitting at 4.6ghz, with 1.3v and temps are nice n low in the 60's.

This is a on a Hyper 212+ 1 fan config using MX-4 thermal compound.
 

xisor

Member
Apr 5, 2010
28
13
81
Your temps seem a bit high.

Also, some chips are better than other. Your chip might not be able to hit 4.8ghz. I believe 1.35v is generally considered the "safe" voltage for these chips.

My 2600k can hit 4.8ghz just using the auto OC on my mobo but I'm not comfortable with my temps in the high 80's and having my vcore 1.4+

right now, I'm sitting at 4.6ghz, with 1.3v and temps are nice n low in the 60's.

This is a on a Hyper 212+ 1 fan config using MX-4 thermal compound.

im hitting low 70s at 4.4ghz now, but VID is usually at 1.3911 under 100% load in prime, its much lower than that when not at 100% usage, is this dangerous? i have voltage set to auto in bios now, at 4.4 it just works, raise the multi and the wattage limit and done (at 100% load it goes way over the 95 watt default, around 120 - 140 watts)
 

MisterMac

Senior member
Sep 16, 2011
777
0
0
im hitting low 70s at 4.4ghz now, but VID is usually at 1.3911 under 100% load in prime, its much lower than that when not at 100% usage, is this dangerous? i have voltage set to auto in bios now, at 4.4 it just works, raise the multi and the wattage limit and done (at 100% load it goes way over the 95 watt default, around 120 - 140 watts)

Classic mistake or rather...my mistake.


Set it way lower.


Set Phase to Extreme and Duty Control to Thermal/tprobe preference.
(Thermal/Tprobe keeps heat in check, and shouldn't be switched unless you got monster cooling imho)

Set Load Line Calibration between medium/extreme (lower = less heat, but more unstability, so find your spot).

Manually set vcore to 1.32-1.35

Enable PLL Overvoltage

Multiplier 47x.


I'm on a Push/pull Antec 620 Kuhler loop - with a 4.7 Ghz, 1.32 Vcore @ high 60's with a 2500k.

Could probably push higher for mid 70's, but like this so far for stability :p


Earlier i just used auto and boom ... heat 85-86c on 44X.... absolutely atrocious.
Auto also OVER VOLTS by so much... creates much more heat than needed.


so tweak it abit :)
 

choliscott

Senior member
Mar 11, 2010
206
0
76
I just got my 2600k & Asrock Z68 Extreme 3 MB & I'm using an H60 as the cooler. I was able to hit 4.6 with 1.37v & LLC set for high (not auto).

When I ran prime, my temps ran in the mid 80's, so I lowered it back to 4.5ghz, & I am able to run that with 1.30v.

Not sure if on your chip, but mine 4.5 seems to be the highest with the lowest voltage. When I run Prime at this speed, I have about low to mid 70's, otherwise it's in the low 40's

I have a 2600K and a gigabyte Z68 motherboard, and no matter what i do i cant get it to boot at 4.8ghz (bluescreen). I have it booted and stable at 4.69ghz (102x46) atm, and am curious about temperatures.

I have a hyper212+ and intelburntest puts my temps in the upper 80s-low 90s, handbrake encoding HD h.264 puts them in the mid 70s, am i ok or do i need to back off my clocks?

4.4ghz intelburntest puts temps in the low - mid 80s, everything else in low 70s. Is something wrong with my hyper212+ installation, or is this normal ranges for the cpu at these particular clocks?

Idle around 33 - 38c regardless of clock settings (yay for sandybridge being able to use EIST and Cstates etc when overclocked, unless thats whats holding back my overclocking?)

1.4vcore 1.9pll and 1.1vcc, are these dangerous?
 

Idontcare

Elite Member
Oct 10, 1999
21,110
64
91
1.4vcore 1.9pll and 1.1vcc, are these dangerous?

Why 1.9V for the PLL? 1.8V is stock, and from what I've read your OC is supposed to become more stable if lower the PLL voltage, not raise it.

Enable PLL Overvoltage

This is what is keeping you from higher clocks. You must "enable" the "PLL overvoltage" in your BIOS (which is not the same as manually overvolting the PLL).

Don't worry about the actual temperatures you hit while running Intelburntest, the point of running IBT is to take your rig into a regime that will create an accelerated stability test environment, provided you are not throttling because that would invalidate the stress test itself.

If your rig can remain stable for the ~1hr or so of IBT at those elevated temps then you are reasonably assured your rig will remain stable for weeks and months when operating 10C cooler while running your every-day apps.

Tcase for these chips is spec'ed at 72.6°C, and the DTS temp will be higher than Tcase, so if your DTS temp is at or below Tcase while fully loaded with your everyday apps then you know your long-term cpu lifetime will be fine (assuming you aren't running silly stupid Vcc >1.5V or something like that).
 

xisor

Member
Apr 5, 2010
28
13
81
Why 1.9V for the PLL? 1.8V is stock, and from what I've read your OC is supposed to become more stable if lower the PLL voltage, not raise it.



This is what is keeping you from higher clocks. You must "enable" the "PLL overvoltage" in your BIOS (which is not the same as manually overvolting the PLL).

Don't worry about the actual temperatures you hit while running Intelburntest, the point of running IBT is to take your rig into a regime that will create an accelerated stability test environment, provided you are not throttling because that would invalidate the stress test itself.

If your rig can remain stable for the ~1hr or so of IBT at those elevated temps then you are reasonably assured your rig will remain stable for weeks and months when operating 10C cooler while running your every-day apps.

Tcase for these chips is spec'ed at 72.6°C, and the DTS temp will be higher than Tcase, so if your DTS temp is at or below Tcase while fully loaded with your everyday apps then you know your long-term cpu lifetime will be fine (assuming you aren't running silly stupid Vcc >1.5V or something like that).

Ok so, i want to enable PLL overvolting but leave it set to auto, manually set VCC and Vcore voltages (is 1.1 a safe level by the way for VCC?) leave bclk alone and then... what exactly? i couldnt get it to boot at 4.8 with just a vcore change, so what should i be doing? 4.4 is rock solid even at auto voltage (which is giving me 1.3911v under load with intelburntest on very high profile) 4.6 is stable with the vcc increase and manually setting 1.4v, i dont know if its even WORTH pushing further than 4.4, will i see any appreciable real world increases from 4.8 vs 4.4 in 1. gaming 2. rendering (such as with maya) and 3. video encoding?
 

MisterMac

Senior member
Sep 16, 2011
777
0
0
Ok so, i want to enable PLL overvolting but leave it set to auto, manually set VCC and Vcore voltages (is 1.1 a safe level by the way for VCC?) leave bclk alone and then... what exactly? i couldnt get it to boot at 4.8 with just a vcore change, so what should i be doing? 4.4 is rock solid even at auto voltage (which is giving me 1.3911v under load with intelburntest on very high profile) 4.6 is stable with the vcc increase and manually setting 1.4v, i dont know if its even WORTH pushing further than 4.4, will i see any appreciable real world increases from 4.8 vs 4.4 in 1. gaming 2. rendering (such as with maya) and 3. video encoding?

Dont overclock the PLL manually, just set it to overvoltage enabled - so uh yes, what your doing.
but forget VCC.


Focus on LLC, Duty control, Phase Control & Manuel vCore voltage(offset).

Listen to what we're telling you.


1,39 is WAY TOO much voltage needed for 99% of the chips for 48x (imho).


Set it MANUALLY boot up, if boot run prime for 20 mins.
If no crash, up multiplier.

If crash/no boot up vCore on offsetmode.


If your real persistent, after you found out your vCore during load/idle you can change from offset to fixed mode and try that.

Your like ignoring everything people say and just messing and setting.

1.35 with tprobe/extreme phase + high LLC should get you bootable and stable for prime 95 with 46/47 perhaps 48.
 
Last edited:

xisor

Member
Apr 5, 2010
28
13
81
Dont overclock the PLL manually, just set it to overvoltage enabled.


Focus on LLC, Duty control, Phase Control & Manuel vCore voltage(offset).

Listen to what we're telling you.


1,39 is WAY TOO much voltage needed for 99% of the chips for 48x (imho).


Set it MANUALLY boot up, if boot run prime for 20 mins.
If no crash, up multiplier.

If crash/no boot up vCore on offsetmode.


If your real persistent, after you found out your vCore during load/idle you can change from offset to fixed mode and try that.

Your like ignoring everything people say and just messing and setting.

1.35 with tprobe/extreme phase + high LLC should get you bootable and stable for prime 95 with 46/47 perhaps 48.


Im not ignoring what you guys are saying, however im having stability issues at 4.6, and even when i set my vcore to 1.32 at 4.4 (stable btw) it gives it MORE voltage on its own when i put a load on it, right back up to 1.3911, any way to STOP it from providing more voltage than specified under load? as for duty control and phase control, there are no such settings anywhere in my bios, what else might they be called? likewise with tprobe or extreme phase. there is NOTHING called anything remotely similar to that anywhere in the gigabyte bios.


EDIT: I may have been following some bad advice before, i was using the turbo multiplier for my overclocking as reccomended by sites like guru3d, which apparently also ramped up the vcore when it went from stock to the "turbo" speed, as well as screwed around with other things, im going to run some tests here at 4.6 and hopefully its stable at 1.35vcore now and booted fine, lets burn the chip and see whats up!

EDIT2: Well its stable, but temps hit 85c during a 10 minute burn. Vcore is still going beyond what i manually specified, is this SUPPOSED to happen? it hit 1.413v when i loaded it up with IBT on very high mode. Going to try some rendering as its the most cpu intensive thing ill be doing with the thing real world, see what temps and vcore do. EDIT3: Confirmed stable, no issues at 4.6, temps in realworld (handbrake 1080p encoding and luxrender rendering software) hover around 70 - 75c, am i good at 4.6 now?
 
Last edited:

IndyColtsFan

Lifer
Sep 22, 2007
33,655
688
126
OP, I am currently using the auto overclock feature on my system (see below) and just ran Prime95 for 10 or 15 minutes. I'm at 4.4 Ghz with 1.3 V and 2 of the cores are hitting about 80 degrees with max being 83 degrees. Idle is in the low to mid 30s depending on core.

i7-2600K
Asus P8Z68-Pro
16 GB of DDR3-1600 RAM
Xigmatek RS-1283 recycled from my last system

I'm not sure what to think of these temps to be honest. All the core temps are within 7 degrees and from what I read, that is pretty normal variation so I think I have the heatsink mounted properly. I can probably live with those temps.
 
Last edited:

MisterMac

Senior member
Sep 16, 2011
777
0
0
Looking at Gigabyte, do you have a UEFI bios or an oldskool one?

I don't see the features on OC'ing guides with Gigabyte.


Any gigabyte owner wanna help here ? Are those settings just not tweakable on Gigabyte boards?
 

RobertR1

Golden Member
Oct 22, 2004
1,113
1
81
Why 1.9V for the PLL? 1.8V is stock, and from what I've read your OC is supposed to become more stable if lower the PLL voltage, not raise it.



This is what is keeping you from higher clocks. You must "enable" the "PLL overvoltage" in your BIOS (which is not the same as manually overvolting the PLL).

Don't worry about the actual temperatures you hit while running Intelburntest, the point of running IBT is to take your rig into a regime that will create an accelerated stability test environment, provided you are not throttling because that would invalidate the stress test itself.

If your rig can remain stable for the ~1hr or so of IBT at those elevated temps then you are reasonably assured your rig will remain stable for weeks and months when operating 10C cooler while running your every-day apps.

Tcase for these chips is spec'ed at 72.6°C, and the DTS temp will be higher than Tcase, so if your DTS temp is at or below Tcase while fully loaded with your everyday apps then you know your long-term cpu lifetime will be fine (assuming you aren't running silly stupid Vcc >1.5V or something like that).


Would you mind providing more info on Tcase. I saw the link and it stated 72.6. When using RealTemp and running IBT, if the temps are spiking from 70's to low 80's, what impact does that have on the chip? Are we running it well past spec at that point?

Also on the OC front, if I gather what you're saying, to obtain OC on SandyBridge K series, you should:

Enable PLL
Reduce Load Line Calibration from max (where it fluctuates voltage the most) to medium
Manual set the voltage offset

On the manual volate offset. If the goal is to get a stable OC at 1.35v, I'd set the offset to be +0.1v since the base voltage is 1.25v?

If the offset allows for 1.35v, won't having PLL enabled bump the vcore up as needed during the testing phase?

Finally, my temps on the 212+ can shows upto an 8c diff between the cores. Should I reset the heatsink and reapply the thermal compound? I'm using MX-4 so I dont' think the compound is the issue.
 

Screech

Golden Member
Oct 20, 2004
1,203
7
81
For temps, you might want to check your case has positive pressure.......Throwing a second intake fan onto my case keeps everything generally cooler as a result.
(2600k but only at 4.2 right now, gigabyte z68a, zalman performa cpu cooler (1x 120mm fan) - intel burn test never gets above 75 C, and any real program doesn't go above 55).

Ninja edit: I believe Tcase is the max temp that should be allowed to be measured on the middle outside of the cpu lid. IE you can have a core that is hotter but in theory as long as the temeprature on the outside middle of the cpu lid does not go above Tcase you are not running out of spec. However it goes without saying that if you exceed Tcase dramatically on any core you are likely running the risk of going out of spec there as well. We can assume that the measured Tcase (if you could measure it) should be cooler than the hottest core as heat flows from hottest to coldest, so if your cores are below the set Tcase you should easily be in the green; if you are at Tcase with a stressing program (burntest, etc) you are probably OK as most of the time youll never really get to that point with a normal program (unless you run prime95 24/7 for some reason), but if you are high above it (mid 80's for example).....eh.....I'd definitely check you have adequate cooling and everything.

Ninja edit #2: Was going to explain further but IDC has a way better post than mine so read his instead.
 
Last edited:

Idontcare

Elite Member
Oct 10, 1999
21,110
64
91
Would you mind providing more info on Tcase. I saw the link and it stated 72.6. When using RealTemp and running IBT, if the temps are spiking from 70's to low 80's, what impact does that have on the chip? Are we running it well past spec at that point?


TJmax is set to protect your cores, and it is 98C. Tcase is set to protect the socket and the surrounding electronics.

There is a thermal gradient that exists between the point where the heat is generated (the xtrs and the wires) and the physical location where Tcase is spec'ed.

Because the DTS are located closer to the source of the heat generation than the Tcase location, we expect the DTS temp to be a more accurate representation of the temperature experienced by the CPU IC itself, which is also why the TJmax value is higher (98C) than Tcase (72.6C).

We can't easily measure Tcase, it requires milling a divet in the surface of the IHS and placing a thermocouple there, sandwiched between the IHS and the HSF.

But we can use our knowledge of the heat equation to rationalize that the Tcase temp will always be less than the DTS temp, and if the DTS temp is anywhere close to the TCase max spec then we are reasonably assured the actual Tcase temp is below the spec limit for max Tcase temp.

Your chip can spike in temps all the way up to TJmax and still be fine, that is why TJmax is TJmax. If it wasn't ok to hit TJmax then Intel would have set TJmax to a lower temp to begin with.

What you don't want to do is hit TJmax while appreciably over-volting...unfortunately without a Vmax spec we really have no basis for establishing a working Vmax.

Arrhenius equation guides us to roughly expect the chip's lifetime to double for every 10C we can reduce its operating temps. The chip will have been engineered to have a certain intrinsic lifetime if operated at TJmax provided the thermal gradient is such that the TCase max is honored.

Operating 88C instead of 98C will double the chip's expected lifetime. 78C will double it yet again. 68C yet another doubling.

But raising voltage has the opposite effect. Raising voltage reduces lifetime expectations in the same sort of logarithmic effect (voltage lowers the activation barrier, kind of like a catalyst).

So raising your voltage ~3% will reduce the chip lifetime by a factor of ~2x.

If your chip is supposed to last 10yrs if subjected to near-98C operating temps at 1.35Vcc but you take it down to ~68C operating temps (expected lifetime becomes 40yrs) but you raise the voltage to 1.44V (~6% over the stock volts) then your lifetime is back to being an expected 10yrs.

However, if you are running 1.44V and your operating temps are more like 78C than 68C then your expected lifetime would be only 5yrs...and if your temps end up being in the 80's at that voltage then you can expect your chip to last maybe 2-3 yrs.

Also on the OC front, if I gather what you're saying, to obtain OC on SandyBridge K series, you should:

Enable PLL
Reduce Load Line Calibration from max (where it fluctuates voltage the most) to medium
Manual set the voltage offset

On the manual volate offset. If the goal is to get a stable OC at 1.35v, I'd set the offset to be +0.1v since the base voltage is 1.25v?

Yes.

If the offset allows for 1.35v, won't having PLL enabled bump the vcore up as needed during the testing phase?
That's not what the "PLL overclock enabled" means or does. It is the phase-loop-lock circuits used by the circuits in the system agent to do its job, apparently these circuits limit the overclockability of the core logic circuits unless the mobo is allowed to overclock them transparently to us users. The downside is, reportedly, that your desktop rig might not wake up if it goes to sleep, required a hard-boot.

Solution to that is to not set your power-plan to allow the rig to go to sleep. Have it either idle or hibernate, just no sleeping.

Finally, my temps on the 212+ can shows upto an 8c diff between the cores. Should I reset the heatsink and reapply the thermal compound? I'm using MX-4 so I dont' think the compound is the issue.

It's unavoidable owing to the asymmetry of the sandy bridge chip itself. The thermal diffusion mechanics pretty much make it an unavoidable reality.
 

RobertR1

Golden Member
Oct 22, 2004
1,113
1
81
Idontcare,

Thanks a ton for that explantion and the details. Very much appreciated. I"ll play around with manual voltages and report back. If that temp variance is normal, then I'll save myself the trouble of redoing the heatsink.
 

BonzaiDuck

Lifer
Jun 30, 2004
16,652
2,034
126
. . .
. . .
We can't easily measure Tcase, it requires milling a divet in the surface of the IHS and placing a thermocouple there, sandwiched between the IHS and the HSF.

. . . . .

Solution to that is to not set your power-plan to allow the rig to go to sleep. Have it either idle or hibernate, just no sleeping.. . . .

. . . Then there's the "next-best" option of milling the divet on the surface of the HSF-base -- with a lower-than-"real" TCASE. And the slight problem that the effectiveness of the HSF will be slightly reduced . . . If one were to mill the IHS, and with the risks of so doing, I can't imagine what sort of milling device might be required. I'm not sure that a dentist's drill has a bit that can mill copper. I'll have to ask my dentist-PC-enthusiast . . . At least, with the HSF-base, a dremel cutting-wheel might be useful. IF . . . you can keep it steady, that is . . .

On the PLL-overvolt issue and the sleep-state, I didn't realize that hibernate continues to work properly. Interesting -- if you're correct about that . . .
 

Idontcare

Elite Member
Oct 10, 1999
21,110
64
91
. . . Then there's the "next-best" option of milling the divet on the surface of the HSF-base -- with a lower-than-"real" TCASE. And the slight problem that the effectiveness of the HSF will be slightly reduced . . . If one were to mill the IHS, and with the risks of so doing, I can't imagine what sort of milling device might be required. I'm not sure that a dentist's drill has a bit that can mill copper. I'll have to ask my dentist-PC-enthusiast . . . At least, with the HSF-base, a dremel cutting-wheel might be useful. IF . . . you can keep it steady, that is . . .

Best of luck :thumbsup:

On the PLL-overvolt issue and the sleep-state, I didn't realize that hibernate continues to work properly. Interesting -- if you're correct about that . . .

Hibernate completely shuts down the system. From the perspective of the BIOS, rebooting a system that has been hibernated is no different than rebooting a system that was shutdown.

The difference only comes into play when the boot image is inspected on the boost disk, that is when it loads the hibernate image versus a fresh-reboot of the OS.

The issue with PLL overvolt enable and "sleeping" is that sleeping involves power-states and the dynamic modulation of them...this is where the system agent gets confused. No confusion exists when the cpu is cold-booted as is the case with a resume from hibernate.
 

xisor

Member
Apr 5, 2010
28
13
81
A status update, 4.6 boots, but i got a BSOD randomly after a few hours of use, so im still not quite sure whats going on, is my chip just not able to handle 4.6? am i doing something wrong? im not sure what to do here... 4.4 again is 100% rock solid. How much of a performance difference is there realworld between 4.4 and 4.6 or 4.8 on these chips?
 

MisterMac

Senior member
Sep 16, 2011
777
0
0
A status update, 4.6 boots, but i got a BSOD randomly after a few hours of use, so im still not quite sure whats going on, is my chip just not able to handle 4.6? am i doing something wrong? im not sure what to do here... 4.4 again is 100% rock solid. How much of a performance difference is there realworld between 4.4 and 4.6 or 4.8 on these chips?


No one with a Gigabyte OLDSKOOL bios can help this fella out?

Maybe you need asrock/asus with the DIGI VRM+ designs to scale that high?


It seems your getting alot of overvolting to stay stable.

Even my 2500k can easily overclock 4.4.


Come on anandtech, must be a SB guy with a Gigabyte board?
 

RobertR1

Golden Member
Oct 22, 2004
1,113
1
81
Yes.


That's not what the "PLL overclock enabled" means or does. It is the phase-loop-lock circuits used by the circuits in the system agent to do its job, apparently these circuits limit the overclockability of the core logic circuits unless the mobo is allowed to overclock them transparently to us users. The downside is, reportedly, that your desktop rig might not wake up if it goes to sleep, required a hard-boot.

Solution to that is to not set your power-plan to allow the rig to go to sleep. Have it either idle or hibernate, just no sleeping.



It's unavoidable owing to the asymmetry of the sandy bridge chip itself. The thermal diffusion mechanics pretty much make it an unavoidable reality.

Getting some weird results. On my mobo (asrock z58 extreme 4 gen3), I did the following:

multiplier to 47x
Vcore: offset, +0.10v
LLC: 1 (least amount of voltage fluctuation)
PLL: Enabled. Max add +0.05v

However in CPU ID, my vcore is maxing out at 1.46v I don't get it. I though the max would be 1.25 + 0.1 + 0.05 = 1.40v

What am I missing? I have all power saving settings and such enabled in the bios.
 

xisor

Member
Apr 5, 2010
28
13
81
No one with a Gigabyte OLDSKOOL bios can help this fella out?

Maybe you need asrock/asus with the DIGI VRM+ designs to scale that high?


It seems your getting alot of overvolting to stay stable.

Even my 2500k can easily overclock 4.4.


Come on anandtech, must be a SB guy with a Gigabyte board?

my chip wants 1.3911V at 100% load, and regardless of what i set the voltage to manually it still hits that voltage when i run IBT or Prime, i cant figure out why it keeps upping the vcore automatically.
 

Idontcare

Elite Member
Oct 10, 1999
21,110
64
91
Getting some weird results. On my mobo (asrock z58 extreme 4 gen3), I did the following:

multiplier to 47x
Vcore: offset, +0.10v
LLC: 1 (least amount of voltage fluctuation)
PLL: Enabled. Max add +0.05v

However in CPU ID, my vcore is maxing out at 1.46v I don't get it. I though the max would be 1.25 + 0.1 + 0.05 = 1.40v

What am I missing? I have all power saving settings and such enabled in the bios.

Sorry to say but I am at a loss here, you got me stumped. If I had your mobo I could possibly pursue it further, but I don't. Hopefully another member here will be able to chime in.
 

BonzaiDuck

Lifer
Jun 30, 2004
16,652
2,034
126
Sorry to say but I am at a loss here, you got me stumped. If I had your mobo I could possibly pursue it further, but I don't. Hopefully another member here will be able to chime in.

Ditto. I've had two different models of Gigabyte boards for an earlier CPU (775) generation -- one that retailed for $85 and the other around $140 (although ask a TRUE wine-aficianado whether price is a reliable indicator of anything, especially if you put a new bottle back and keep it below 60F for four years). Both boards were stellar for what we used them for.

I read reviews of Z68 boards which I found before choosing my ASUS -V-Pro, and some which I found after. I think somewhere there was a Tech-Report comparison. Between ASRock (really ASUS), the ASUS boards and the Gigabyte boards, some of the latter may have been lacking in comparison. That was an impression I got, and impressions are not a basis for final conclusions, but . . .

Best of luck
:thumbsup;

I'm probably going to ponder this for another several weeks. I still want to extend my mobo's fan-control features to handle a more powerful fan or fans -- possibly allowing a temperature reading to spin them up from 0 rpm. The controller I have comes highly recommended for per-channel wattage and the use of both analog and digital sensors, but the software that comes with it won't read the SB sensors. So I have to use at least an analog sensor on the CPU to do that, or it's a no-go.

As I already said once: Perfectionists are their own undoing. For the noise levels coming out of the system at this time, I shouldn't bother with this. Maybe it's a manifestation of "obsessive-compulsion." Dunno.
 
Last edited: