OK  gig is using a slightly different method of CPU STRAP to memory..

There are differences in how this board will work compared to Asus boards.

Here is what I would like you to do in order to investigate a bit and confirm a few things since what they say in the manual and what really appears on the screen in the BIOS can be different especially if they have upgraded the BIOS since the manual and changes the programming math of the BIOS

You will not SAVE these settings at this time.. I just want to know if they are working the numbers as the manual suggests...

Enter the BIOS and find:

CPU Host Frequency (Mhz) and raise it to 450

Now.. the available Memory Frequency (Mhz) at this FSB will be based on

(G)MCH Frequency Latch - Same as CPU STRAP in ASUS

System Memory Multiplier - Available values depend on Latch setting


Here is the deal.. we are looking for 1066... those sticks you have are not clocking sticks however they may have some overhead in them. If they do I doubt it will be much higher than 1090 @ 5-5-5 so what you are looking for is DDR2 1066 or just slightly above in Memory Frequency (Mhz) @ 450-460FSB

When looking for this value, first lock the

(G)MCH Frequency Latch to 333

Latch freq is the NB strap, basically, internal NB timings. Lower is tighter. The separate MCH Latch settings in the Giga boards are are not redundant you can pick mem ratio and the strap in the mem section at the same time but with the LATCH set to a value it limits the values under System Memory Multiplier to ones that only function with the LATCH of 333.

(G)MCH Frequency Latch to 333 - remains a constant

Now, work the CPU Host Frequency (Mhz) (start at 450 and go up but try to keep it as close to 450 as possible without going UNDER), the System Memory Multiplier and check the Memory Frequency (Mhz) ... you are looking for a Memory Frequency of 533MHz or also known as DDR 1066 (533x2)

Now.. once you find the FSB and memory multiplier that gets you as close to 1066 as possible without going UNDER but without going too far OVER (try for 1080max if that is the best you can do) then verify the following


Standard Timing Control
CAS Latency Time: 5
tRCD: 5
tRP: 5
tRAS: 15



If this all checks out and you have established a 1066-1080 memory speed @ that timing.. then you are ready to clock

At this point you can cancel out of the BIOS and remember the settings you found above and let me know what values you ended up to get 1066 (or close) with for


CPU Host Frequency (Mhz)

System Memory Multiplier

and what the final Memory Frequency (Mhz) ended up at

This will tell me what to post for voltages to stabilize the clock attempt and keep you safe


To recap, the goal in this exercise is to find the Memory Frequency (Mhz) which will place the memory as close to DDR2 1066 (533Mhz) as possible on 5-5-5-15 timing with a locked (G)MCH Frequency Latch set to 333 and a CPU Host Frequency (Mhz) of at LEAST 450Mhz or slightly higher


NOTE 1: If you find the memory speed is sitting at 1080-1090 @ 450MHz and you can not get it lower without reducing CPU Host Frequency (Mhz) to below 450.. tell me where FSB sits below 450 to place memory at 1066 as I may go that route instead


NOTE 2: Setting (G)MCH Frequency Latch to AUTO instead of 333 may allow a 1066 memory speed at 450MHz.. check this too although I would prefer (G)MCH Frequency Latch be locked at 333

Brett_Henderson wrote on Jan 23^rd, 2009 at 2:09pm:



Windoze is reading the full 8.5x multiplier... probably a BIOS glitch

I need to remember how to activate that 1/2 multiplier and lock it on.. not sure if Gigabyte does it automatically or not



Just to make sure... you ARE using this CPU cooler, correct?

http://www.ocztechnology.com/products/cooling_products/ocz_vendetta_2_cpu_cooler

Thats the Vendetta2

or is it just the 1st release Vendetta?

http://www.ocztechnology.com/products/cooling_products/ocz_vendetta_cpu_cooler


The primary difference is the fan size.. as I recall the V1 is a 92mm fan and the V2 is a 120mm and there were a few other minor tweaks. So let me know about that because that may affect the settings.. you can always strap a 120mm PWM 4 pin fan to the Vendetta1 and get basically the same cooling result down the road

OK so 444MHz CPU Host Frequency (Mhz) is 1066

OK so here are the options.. and its based on if the memory will run 1080 stable

All of the tests will have the following DISABLED

Limit CPUID Max. to 3
CPU Enhanced Halt (C1E)
C2/C2E State Support
C4/C4E State Support
CPU EIST Function
Virtualization Technology

I left the TM function enabled for you for thermal protection. What I posted should lock the processr at the full 8.5x multiplier

Same settings @ 450 placing the memory @ 1080

The CPU Vcore will be problematical and you may need to work this a bit. I estimate 1.28-1.32 will be the range however that may be stable a bit higher or a bit lower than the range

Lower is cooler and always better. 1.38v will be your max and do not exceed it

Start at 1.28v

CPU Termination will be set to 1.25v. This can end up a bit higher as well with a max on 1.35 however I would work that in up by starting at 1.25 then move to 1.28, 1.30, 1.32, 1.34 testing for stability. To be quite honest I dont see this needing to be any higher on the clock we are looking at than 1.28v

CPU PLL will be set to 1.50v and leave it


MCH Core: This is the northbridge voltage and may need to be adjusted from AUTO for higher FSB. Lets start at 1.3v with the possibility of this needing 1.35 or 1.40, or 1.45

start at 1.30

DRAM Voltage will be set to 2.1v and no higher as per the spec from Corsair

Leave everything else on AUTO



Ok.. F-10 save and exit.. she should boot


NOTE: it is possible the system may boot into Windows and be unstable in load tests. At that point you need to do some voltage tweaking.. the same tweaking you would do if the system did not boot at all as I outline below:

If it fails to boot or fails in Windows under stress then enter the BIOS and bring up the Vcore and the MCH Voltage slightly and try again

VCORE 1.28

and

MCH CORE 1.35

If still fails in load tests or no boot it is very possible this memory simply will not do 1080 and that is the problem. To do a quick check enter the BIOS at that point and raise DRAM VOLTAGE to 2.2v leaving everything else as it was and F-10

If it boots then the memory is the issue. At 2.2v you are pushing the outer limits of the spec and although it can be run like that it is past what Corsair specs for the memory and could shorten its life however you can NOT go above 2.2v

If you would rather run the 2.1 spec then the only option is to back down the CPU Host Frequency (Mhz)

At that point lest set the voltages back to the original list I posted above and set the CPU Host Frequency (Mhz) to 444 which makes the memory speed 1066 and boot up

I would think that would be stable but if not, its the same drill as above.. start with Vcore and MCH CORE first and if after you have raised those to to VCore 1.32 and MCH CORE 1.40 you still are unstable post to me and let me know


Now, when in Windows do not use the system properties to see the CPU Speed and the memory speed and timing, use CPUz

At 450x8.5 you should have a CPU speed of 3825MHz

At 444x8.5 you should have a CPU speed of 3774MHz

Both are nice clocks


but





This would be a setting of 471MHz CPU Host Frequency (Mhz) and adjusted memory speed for as close to 1066 as possible using the method mentioned above. Check your multiplier ranges at that HOST speed and see if 1066 comes up close to or around 471MHz. Even if you end up a touch slower than 1066.. like 1045 it may be worth the 4GHz clock.


Same deal on the voltages.. you may find you will run just fine at 4003.5MHz

So thats how its done


Now, temps

no matter what speed...

http://www.ocbase.com/download.php?fileext=exe

You need to check for temps and stability in such clocks. I typically use the software OCCT and run the 1hr automatic test. I enter the settings for OCCT and make sure the CRASH or FAIL temp is set to the Tjunction of the processor.. in your case this is 80c

Fire up the test with ReatTemp or Coretemp up on the screen.. there will be a 1 minute prep period then the test will start.. temps will go sky high and that is what we want

As long as the 1hr test passes and your temp remains below 80c you are set on that clock

Now, if you are stable and temps look good you do not need to make any changes however.. if Vcore will drop a tad and stability remain a constant then the proc will run cooler. I estimate you wont get much lower than 1.25 no matter what and in the case of 4GHz it may or may not run less than 1.3v. Some do, some dont.

The next step is to run FSX and make sure you are stable in 3D. If not let me know and we can go from there

The 2 primary settings you will be messing with for stability are

VCORE

On the 4GHz clock this may need to be 1.36 but many manage a 4Ghz clock at 1.28v. do not exceed 1.38 and temps must be under 80c in load tests no matter what voltage

MCH CORE

MCH may need to come up to as high as 1.50 but do not exceed that without checking with me

you get the idea now...


when you get that stable and its up in the 3.7 to 4GHz range.. FSX will sing for you

I just noticed this board may have these settings


CPU Clock Ratio
Fine CPU Clock Ratio

If it does make sure it is set to

CPU Clock Ratio [8X]
Fine CPU Clock Ratio [+0.5]


Sorry I missed that!


You can also just work with 8x..   that is a way you can find stability as well by reducing CPU speed if you find the CPU is unstable


The trick is figuring out if its

the CPU

the Northbridge

or
the memory

causing stability... thats why we work the voltages back and forth, up and down to find the stable lowest point for each

Dont get frustrated.. it may take a bit of playing and a few posts to lock it down


As for the memory, I just checked to be sure.. Corsair only warrantys those sticks to 2.1v so anything above that is pot luck. Some run them at 2.2 (never higher) and never have a problem but that is a risk. running 2.2 for a boot and stability check is fine.. running it long term is what can be dangerous

QUACK QUACK QUACK

gets 'em every time

he he he


Yea.. I left that out on purpose   sorry, call it a hazing for the  clocking fraternity



Thats fine Brett.. as long as voltages are within the limits I posted and the temps are solid.. you are fine and I know you can do better on the clock.

When you are ready for a memory purchase let me know. Those hybrid DDR2/DDR3 boards can be a bit finicky about memory though

You should be stable as long as the memory is @ 1066 and 2.1v.. but it may require higher MCH Core and Vcore with a touch of VTT to run the higher FSB

Those E0 95 and 9650 chips will do 4GHz on the right boards pretty easy

DDR3 1600
Brett_Henderson wrote on Jan 24^th, 2009 at 4:44pm:



LOL!!


i7 DDR3 is not the same as the 1st generation DDR3 used in that board... and the memory you posted is a bit too bold for that board

If you purchase DDR3 now it can not be used for i7 so dont go spending a bundle.

In DDR3 @ 400MHz I would go with these:

http://www.newegg.com/Product/Product.aspx?Item=N82E16820146777


@ 1.9v they will also do 1T instead of 2T COMMAND RATE (faster) and I can show you a way to pop a bit more out of them too using a tool called MEMSET which will access the northbridge and set the tRD (MCH READ DELAY) down to 6 which will boost their ability again..


That board is a hybrid so I can not be confident of its stability tweaking as mentioned however those sticks are really nice and even if you could not tweak them as I posted should do the job a lot cheaper





EDIT: Posted the wrong memory... edited the link for 2x2GB

Brett_Henderson wrote on Jan 24^th, 2009 at 5:11pm:


If you have any questions while toying with settings shoot them to me


Also.. in case you have not seen it.. I did post a FSX tuning guide for settings and config tweaks

http://www.simforums.com/forums/forum_posts.asp?TID=29041

It covers just about all the bases including the use of Nhancer


hmmmmm.... in your area I can think of a few well known NFL boys who I would not want to upset