Running my Q6600 (B3) @ 9x333 and 1.32V, looking to go higher

georgio440

Member
Aug 10, 2007
38
0
0
Hi guys, I recently purchased my Q6600 which is cooled by a Zalman 9700 and an Antec 900. It is currently running at 9x333MHz (3.0GHz) with a 1:1 DRAM ratio (which means my RAM is running at 667 instead of 800). I am considering raising the FSB to 400 from the current 333, which would bump me up to a nice 3.6GHz, and my RAM would be running at 800MHz again. With this, I have some questions. Do I need to over-volt? Is it unsafe to raise my CPU frequency up to 400MHz from 333MHz? The Q6600 is very stable right now @ 3.0GHz, but with the heatsink and case I have, I feel like I can be doing more, plus the whole RAM speed issue. I am new to OC'ing, so any help is appreciated. I'll just say that I will be ecstatic if I can run at 9x400MHz with my RAM back up to 800MHz. Thanks in advance.
 

myocardia

Diamond Member
Jun 21, 2003
9,291
30
91
First of all, you aren't going to be able to run that Q6600 @ 3.6 Ghz, using air cooling, since it's a B3 stepping. And secondly, your RAM's speed makes absolutely no performance difference, as long as it's running 1:1. Well, so little difference, it makes no difference. And last of all, welcome to anandtech.
 

zach0624

Senior member
Jul 13, 2007
535
0
0
A couple of factors determine wether or not you reach 3.6ghz. First from what I understand the G0s run the coolest getting maybe 200mhz more than a b3 but most don't get past 3.4ghz. Swtethan was lucky and has a great chip and mobo too reach 3.6. Also anything over 3ghz will probably need more volts. Check out swtethan's quad overclock thread for some voltage ideas. It would be great if you posted your temps and mobo so it is easier for people to evaluate your overclock. Just remember that what ever overclock you get past 3ghz that is still over 12 totalghz if you multi task (you know run seti@home, encode, play games, all while coordinating the US's nuclear arsenal)
 

georgio440

Member
Aug 10, 2007
38
0
0
Well, I'm not at home right now so I do not remember my exact temps, but I have an Abit IP35-E motherboard. Everything seemed to be running cool (using RM Clock and Speedfan), but I haven't really stress-tested it yet.
 

georgio440

Member
Aug 10, 2007
38
0
0
Oh, now that I recall, the CPU was running at 31C @ idle (according to speedfan's temp reading in the taskbar).

And another question: What would I have to bump my voltage up to if I were to run at 8x400 or 9x400?
 

Capitalizt

Banned
Nov 28, 2004
1,513
0
0
Try 8x400. You will probably need 2.0 for your RAM and 1.35-1.36 for the cpu.

If that doesn't boot, you may need to set the "FSB Term" voltage to 1.4 manually. I couldn't get my e6600 to boot with a 400FSB without doing that..



 

georgio440

Member
Aug 10, 2007
38
0
0
FSB Term? I don't recall seeing that option, but maybe I'm just not remembering correctly. Other than that, thanks for the advice.
 

BonzaiDuck

Lifer
Jun 30, 2004
16,884
2,192
126
"FSB Term" or termination voltage is the CPU's FSB voltage -- also called (on some boards) the VTT or CPU_VTT voltage.

Bumping it up to 1.4V should help. If you see that certain kinds of problems are occurring -- you lose the mouse, the screen seems locked up and the "G-0-GO-0-G . . . " isn't flashing in Windows, if you have to punch the reset button, raising the VTT voltage may help. And of course it would be nicer if all errors resulted simply in the ORTHOS red "STOPPED" screen.

Try to contain your ambition on this matter. There are several ways to OC, and it's just my opinion that people are too hot-to-trot on getting the CPU to run fast. If you have decent memory, you might focus your attention equally on the FSB and DDR2 speeds -- because it is a bottleneck -- although a lesser one.

I suggest you read the intel specs on the processor, and we've published a link several places in threads here and on "Cases and Cooling" for a C2D Temperature Guide at TomsHardware.com. Of course, it is dated material for not explciitly covering the quad core processors, but the general ideas apply. The Intel spec on the B3-Q6600 will tell you the TCase temperature where the processor begins to throttle. I'd say it's a good idea to limit your over-clocks to a point where the individual core (TJunction) temperatures are all below 70C at a room ambient approaching 80F degrees.

The cooler, the better.

On the matter of voltage. Overclocking involves an acceptance of some risk. It is possible to OC these processors to some limit while keeping the VCORE below the manufacturer "Maximum" spec or the recommended "operating range." For the B3 Q6600, the Intel "Maximum" on the box's label shows "1.35V."

How did Intel decide on this number? They don't want any RMA returns under warranty. So they would choose a Maximum spec that almost completely eliminates any chance of failure for the full warranty period. So think of this number as suggesting a probability distribution that the unit is likely to fail, and that none or hardly any of the distribution's tail crosses the line below 1.35V.

This might also suggest that bumping up the voltage 1%, 2%, 5% or even to an arbitrary limit of 10% will not risk damage to the processor OF ANY SIGNIFICANT DEGREE, although moving up the ladder of percentage notches increases the odds against CPU longevity.

Motherboard BIOS's provide a scale of manual voltage settings. When you choose one of these voltage levels for VCORE, there are certain things to be said about it. First, it may deviate from the measured or monitored value in software. Second, it may vary from the actual voltage measured with a multi-tester. Third, if it comes close to what is shown under BIOS setup "Voltage Monitor" or Windows monitoring software, it will be the idle voltage value. You will want to be interested more in the load voltage, and there is a generally understood voltage "droop" phenomenon, so if you set the VCORE at 1.42V, the load voltage may show as 1.35 or 1.36, or some number closer to 1.42.

I would think that the load voltage is the number you'd want to use in determining how much in percentage terms you've exceeded the "Maximum" spec.

Since any increase in voltage increases temperature, try to increase your voltage just enough to get a stable setting, perhaps push the speed and voltage just a tad farther, find out what voltage and speed setting causes ORTHOS "STOPPED" errors and adjust to eliminate instability, and then back off the speed slightly from a voltage you've proven stable. That is -- keep the voltage setting, but reduce the speed setting slightly.
 

georgio440

Member
Aug 10, 2007
38
0
0
Wow, thanks for the huge write up. I'll read up on it again when I get home. I think I'm just going to run it @ 8x400 and bump up the FSB term to play it safe. Honestly, a 3.2GHz Q6600 is plenty.
 

Chronoshock

Diamond Member
Jul 6, 2004
4,860
1
81
Originally posted by: georgio440
Also, check out this thread. I don't know what kind of cooling this guy has, but he says he went straight to 3.6GHz on a B3. I'm not familiar with "compression" and all the "thread testing," however. Can someone clarify?

http://discussions.hardwarecen...howthread.php?t=177456

The compression refers to the user running 7-zip, a compression program, to stress test his rig.
He got 3.6GHz on a B3 stepping Q6600 using water cooling, not air like you are.
 

georgio440

Member
Aug 10, 2007
38
0
0
Hey guys, just got home. I OC'd it up to 8x400, which gives me an estimated 3.2GHz (obviously). However, when I log into Windows, Vista says that my CPU is running @ 3.6GHz. Any explanation for this? Need urgent assistance! Thanks in advance.
 

KingGheedora

Diamond Member
Jun 24, 2006
3,248
1
81
Try running one of those programs like CPUZ to check the speed. Also, what speed is listed on screen when you first boot up?
 

BonzaiDuck

Lifer
Jun 30, 2004
16,884
2,192
126
Vista, ORTHOS and other software may assume that the effective multiplier is the stock multiplier of 9, and make calculations based on that assumption to give inflated speed reports.

Even for Microsoft, with their vast resources and minions, it's logical that they would overlook this because the OS is marketed to a majority of users who don't know from VCORE or "multiplier," and who would probably be horrified at just the thought of opening their OEM box to install an expansion card without assistance.