Ok I just got my rig set up yesterday and I am a newb OCer. I currently have no idea what all the different things in my BIOS mean for this ASUS board. I enable one thing and about 20 more things come up to configure....I read the OC guide for duals and quads but I am very lost atm and dont want to risk anything. Does anyone have any screenies of what should and shouldnt be on?

My specs ATM are:

Q6600 G0
Asus P5K-E WiFi
Xigmatek S-1283
Crucial Ballistix Tracer 2x2GB DDR2-800 4-4-4-12
XP Pro x64

Make sure you understand the bios options before installing the operating system. Check this site for your questions:

http://www.techarp.com/freebog.aspx

Your motherboard manual should explain the basic options also.

Howdy there! Welcome to Umbuto Land! (Once you OC to hi heaven!)

I have the same board as you, and the same.. chips.

Sooo... what are your goals? You just happen to have a handy configuration! My p5k-e wifi OCs better than my Formula, 780i, the 680i I had...

Anywho! Lets start here. Down Load Core Temp 64, HWMonitor 64, CPUz, GPUz, RivaTuner for 64 bit, ATI Tools for 64 bit.

Run core temp, then list the VID of your processor. Also, take note if the value moves at all. (It should be a fixed number) So all ya have to do is run a large program while watching the VID field in core temp. If it doesnt move, list it here!

With that set up I recommend lots of speed! LOL!

Get that junk, and get back to me, and we will get to work!

--Lupi!

Of course you'll also have to Update your Mobos Bios. It more than likely has a "new release" bios on it. And those blow, because they rush them out!

That will promote better OCing.

--Lupi!

Hey! AWESOME!

My VID is 1.3000v

Right now I'm messing around and am running @ 8x430 -> 3.44ghz

My CPU Voltage is like 1.425 I think. Running Prime95 right now and for a little under an hour. my Max Temps are 59 57 52 52 under full load.

I want to get the most speed I can. I plan to do a lot of gaming/video editing. I would like to keep max load temps around 65c max if possible, so far I think im running pretty cool for 1.425v....then again I have never OCed before!

I just BSOD...right at the 1 hour mark of Prime95 I'm now at 9x333 and DRAM @ 800

hehe, Retail chip you just bought? How long ago?

Thats a decent OC for that chip. Its a higher VID chip, so 3.6 will be about its maximum!

When you say your voltage is.. you mean VCore voltage set in the Bios?

Here is how that works, lol!

You set a VCore in the Bios, say 1.2375 like my q6700 in here right now!
When you get into windows it will list a different value. My p5k-e takes a 1.2375 BIOS VCore and VDrops it to 1.2000 in windows. Thats your IDLE windows voltage.
When you run a powerful program, its draws power into and from the CPU, so you get whats called VDroop as well. As it uses power, it has to drain some current and that VCore value reflects that while loaded.

So its BIOS VCore (1.2375) - VDrop (.375) = 1.200 in windows. VDroop makes that 1.168. Thats my LOADED VCore.

Thats the most important factor to remember. Loaded VCore is your target. That is what makes the difference when OCing. Because the chip will bomb out only when the power can no longer be translated into a defined high and low.

The loaded VCore has to be able to swing over a value for the logic gate to spit out a high logic. (a 1) or swing below a value to spit out a 0.
As you OC, you stretch that vcore swing to where it can no longer easily differentiate between a 1 or a 0. Adding VCore gives that wave a bit more power, and you want just enough so that at 100% usage, it can still tell between the two values.

To little and you get a zero where a one was supposed to be, and who knows what can happen at that point. System junk BSODs, Data files can be corrupted, etc. A single miscalculation can be bad, lol!

Man, its hard to shorten months of stuff into a few phrases.

--Lupi!

Yeah I got it less than a week ago from Micro Center.

So 3.6 will be max, lets get it! I have no idea what do to though.

Should I leave the VCore to auto for now? Then lower/raise accordingly?

Nope. Turn on Load Line Calibration! Disable speed step, and all other processor options but internal cache! Then set your NB voltage to 1.40-.45 for now. Up the FSB to 400, Select sync more or 1:1 for the ram, disable all the spread spectrum junk you can find. Up the Bios VCore to 1.5000, it will drop to like 1.4650, then should be .02 lower when loaded. We want about a 1.44-1.45 loaded VCore for 3.6 on that VID chip.

You may wanna disable transaction booster and static read whatever the hell. They lower timings of your RAM without telling you, hehe.

Save and re boot!

--lupi!

so...do what where? :X

I changed FSB Freq to 400.
DRAM Freq is now 801.
CPU Voltage is at 1.50v
NB Voltage is 1.40v
Load Line on.
PCIE Speed Spectrum is Disable.

I just changed all those things and am now idle @ 37 34 27 32

If you experience any problems, disable transaction booster, and static read control there.

You also may need to up the FSB termination voltage as well as CPU PLL Voltage to get prime stable.

The other processor options are under the tab Processor, once you exit that specific area of your BIOS. Disable them all, except for internal cpu cache.

Whats you Idle in Windows Vcore?

And when you note that, run prime small FFTs and prepare for your first BSOD! One of a few to come, lol!

Fire it up on all the cores. Watch the temps! Watch what the VCore goes down to. Use CPU Z to monitor real time changing of your VCore with x.xxx fields. 4 and not three like in HWMonitor, which should be open as well, to re verify the cores, and watch your voltages.

Core temp should also be open and noting temps. Windows task manager under performance should be up, so you can watch your cores and system responses.

What do ya need next?

--Lupi!

Idle VCore is 1.48v according to HW Mon, 1.480 CPUz.

Should I run prime Small or Large? Doesn't prime do all cores automatically?

Prime small FFTs, and it should! Thats good. So it will droop to like 1.46 or so! That may be just a tad to low. But gotta try it!

Get to work!

I'll be here for a few.

--Lupi!