Benefit at running Q6600 multiplier at x9 instead of x8

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
I didn't look at that last time, but I just ran it for another 15 minutes, and the lowest it got was 1.320.

Before starting Prime it was 1.440.

Do I need to bump up Vcore? Should I keep the NB voltage where it is?
 
You'll have to test to find that out. Okay, what I mean was this, at your current settings, boot into windows and look at CPUz and see what it says, if its berserkly low, like 1.1xxxx you need to make sure speed step is disabled, and EIST if its in there.

if its more like 1.4xx thats fime, just note what it idles at, and then run primes small ffts on all the cores for 30 seconds, and watch to see what the lowest CPUz shows it as, it maf flicker to one, and then another, and back... just remember the lowest value and mention it here.

--Lupi

 
The lowest value is 1.320. What's my next step to make this thing more stable?

And regarding SpeedStep... The only way to bring up the option is to set the cpu multiplier to Auto, if I set it to 8, the option goes away to disable it, but i did set mult to Auto, disabled SpeedStep, and then put the mult back to 8.
 
Sorry for another hijack....

@Luip, what about 1066mhz memory, 4GB. I currently have my Q6600 @ 3.0ghz with the stock 9x multiplier, so 333FSB. The memory is running at 1067 I think :heink: Im honestly too scared to put the FSB @ 400, and im not too savy with the RAM timings/multipliers, whatever its called (1:1, 1:1.2, all that) its currently at 5:8. Im using an ASUS V-60 cooler, and the CPU peaks at around 55c after running Age of Conan for multiple hours or Prime95. The voltage is set to 1.3V, ive left it alone and often wondered if it would be safe to lower it eventhough the BIOS says it might not have enough juice, im also unaware of what will happen if I undervolt.
 
Because this thread has been double hi-jacked (lol) I want to make sure we can pick up where we left it...

The lowest cpuz value is 1.320. What's my next step to make this thing more stable?
 
im sure is getting ever more popular.lupi has got a formula to work out the required voltage to achieve certain speed.i cant remember off my head.you will have to wait for him.

but whats the vcore you set in BIOS?and whats the windows idle vcore in CPU-Z and loaded vcore.
 
I have my q6600 overclocked to 3.0, had it overclocked to 3.4 stable but my brother accidently reseted my cmos. I have it 1.2125V in bios, vcore idle is 1.192V. If I remember correctly for loaded vcore, its just a little below the vcore idle.
 
@ Shadowthor, if its a true 1.2000 VID chip, then it will take about 1.3200 or so for 3.6, thats the benefit of a Low VID there.

And in boards with high VDrop and droop! 1.2000 I think is the lowest factory VID for the old series.

@Spathotan You want to set your front side bus as high as possible, if your ram can take the sync mode. Its pretty straight forward to me, if you data pathway is 333, and your trying to push anything more through it, it would have to wait for a new cycle to xfer that data, and therefor makes it slow.

As far as what would happen if you under volt your Processot. If its right on the verge of stability, minor programs will fail, like pre fetch, super fetch, windows explorer, junk like that, maybe a frozen program, and if the voltage is off enough, you'll get the occasional BSOD.

Just use Prime 95 small fft torture test on all cores and watch with CPUz the current core value, and let it run for a few hours, then lower the VCore a notch and do it again until you Blue screen, then raise it by one and test for 8 hours.

That 1.320 is the LOADED value. Thats the only critical voltage. When I say will do xxx at 1.3200 Thats the loaded value. Your board has Load Line Calibration, turn it on!

Then what you do is manually set it to stock, and manually enter in 1.2000 as the VCore value in the bios. Then boot into windows and look at CPUz and note the lowered value, then also run prime 95 small ffts on all the cores for 30 seconds and note the second value as the VCore is reduced further. The total reduced number needs to be around 1.3200.

Once you add those two up and know how your mobo will apply the initial from Bios to windows VDrop, and then the in windows but fully loaded VCore with VDroop applied now as well. The end number is the final Loaded Value!

--Lupi
 
To the original poster! To make it more stable, its all in the VCore, a 1.3250 VID will need around 1.45 while LOADED with prime 95 small FFTs. Thats what causes most of your problems, read above post, Test for your VDrop and VDroop by manually entering a Bios setting, then loading windows and seeing where its now idling, then load it up with Prime 95 small ffts and see where its finally reduced to. For 3.6 you will need to get it to where its reduced only to around 1.45

Remember, to us.01 isnt $hit, but to your chip, thats a huge amount.

If you have the FSB already stable at 400, just add the VCore, and up the multiplier, and all should be well!

--Lupi