Ok, notice the stress test is a mixed test, it tests CPU and RAM. But it doesnt really test CPU much, that's why you don't see it using 100% memory!

Change the test to small FFT's and watch your temperatures go up, this is a true heat test for your CPU.

Run the test for 5 minutes and then write the max temperature down,

increase Vcore to 1.47 (reading in Speedfan) and run the test for 5 minutes again and compare the temps.

This will demonstrate the effect of Vcore increase on temperatures.

Return the CPU to 1.4v (+-)

As you GRADUALLY increase Vcore, you will get to a point where the temperature starts to rise sharply, this is the critical voltage/thermal limit of your CPU and the test should be cancelled before the temperature gets beyond 60*. You don't need to do this now, this is simply for your information.

When you establish your critical voltage, never set it that high ever again, always bear in mind that that is the setting which will cause damage over time. It's best to back the voltage 2 notches from there and never go beyond it, you go back one notch to ease the stress and another notch to allow for hot days or long sessions on the PC where it gets much hotter.

So an example only, each CPU is different:

1.4v     =   38*      Standard Vcore
1.44     =   40*      
1.46v   =   42*
1.48v   =   44*      Recommended max Vcore
1.5v     =   46*
1.52     =   60+*   This is the critical Vcore

This is not a usual way to teach overclocking, but it is for your protection so you don't damage your CPU. I wanted to show you this first.

The same principles can be applied to your Vram should you wish to overclock/overvolt your ram somewhat. When the RAM gets hot during a Stress RAM test, that is the limit for Vram, and the voltage should be reduced as above.

There is no need to overclock the RAM, a divider can be used to lower the RAM's base speed to a fraction of the CPU bus speed.

If the RAM base speed is set to 400mhz, the ram follows the CPU bus speed 1:1  ,  hence, if the CPU bus is increased by 20mhz, the ram speed goes up by 20mhz, if the bus speed says 220mhz, the memory bus speed will say the same.

When a RAM divider (or ratio) is used, the memory bus no longer follows the FSB/CPU bus speed 1:1 , instead, the memory bus will be a fraction of the CPU bus.

Now, go grab this handy calculator and see how it works.  

http://www.hardwareanalysis.com/action/r/http://xtremesystems.org/forums/attachm...

The reason you use a memory divider is because your RAM is going to crash if it exceeds a speed much beyond 220mhz, so that limits our CPU overclock.

If we use a RAM divider of 166, this means we are setting our basic memory bus speed back to PC2700 standard speed, because we intend on increasing that speed using the Front Side Bus (or HTT). (The memory bus follows the FSB speed up as the FSB speed is increased.)

Here is an example:

RAM divider = 166          which gives us................

FSB or HTT  = 260

RAM speed = 216.6

CPU multiplier = 10

HT multiplier = 4

FSB x CPU multiplier = CPU core speed
260 x 10                  =  2600mhz or 2.6ghz

RAM speed = 216.666 x 2 = 433mhz DDR

FSB or HTT  = 260 x  4 (HT multiplier) = 1040mhz (2080 mhz DDR)



You could perhaps try the following settings and see if they work.............using the following settings with the divider gives you a 2.4ghz CPU with a standard 400mhz or PC3200 ram speed, in this way, you overclocked the CPU and FSB but not the ram.    

RAM divider = [166]

Vcore  = 1.425v (true Vcore as measured in Speedfan)

HTT =  240mhz

CPU multi = 10x

RAM  = 200mhz

HT multi  = 4x


Here is an example of a high overclock using a 166 memory divider, note the memclock and HTT are vastly different. Also note the low CPU multiplier (9) to keep my CPU within it's operating speed range. The idea of a RAM divider here is to create high bandwidth on the mainboard while keeping the CPU and RAM within operating frequency range. (unfortunately I didn't consider keeping the hypertransport speed within range  )



My PC crashed to blue screen directly after saving that pic, I was lucky to get that shot, here's why:

My HT multiplier was set in BIOS to 4x, this means that my true hypertransport speed was 4 x 311.82 = 1247mhz, well above the 1000mhz recommended limit!

Also, my system's chipset cannot have it's voltage increased as your's can, therefore I get instability over 300mhz, I'm not sure which one of these mistakes crashed me, but my money is on the HT speed. (I have gotten this mainboard to a FSB of 330mhz before).


http://www.dfi-street.com/forum/showthread.php?t=12960






You'll notice that a RAM divider is produced just by using a half CPU multiplier, this is a Quirk of the AMD64. This pic shows a RAM divider set by using a 10.5 CPU multiplier.

Quote:

In your last thread’s suggestion to try this, I found a “Memlock Value” of 166, with the help of  the correct manual I downloaded, coinciding with your “RAM divider” so I set it so.
The other thing in doubt was “RAM = 200mhz“ so I did nothing, and it may have been the sticks PC3200(200mhz) as shown in CPU-Z.

The results are :-

Temps STATIC: Cpu 29c, Chipset 34, 30c, 29c, 33c.
Temps with fs9 over LHR: CPU 39c, Chipset 36c, remote 54c, Local 41 & HD 34

Thanks Congo,
Calamity, I write mine in a notepat saved on desktop & paste in to replies, it has 20 pages of old notes by now.

I know you are busy at the moment with what seems like a terribly complex subject of SATA's, Arrays etc.

To tidy me up a bit for a while, just tell me which ones do you think in this manual page correspond to the 3-4-4-8  &  2-3-3-6 that chap sugested to try.
The perisher does'nt know, he was quoting somebody else.
The rest I think I figured out.

"......Set your ram to 266 for the purpose of excluding it from the cpu testing. Once you get your maximum CPU then you can increase the ram and the timings. Set your ram timings high as well. 3-4-4-8. It is spec'd out at 2-3-3-6 so once you get your CPU at maximum you will have lots of room to play with it.
Try these settings:
10x multi @ 240 --> 250 --> 260 --> 270
pci-e 100 mhz
ram volt 2.8
cpu volt 1.4375
pci sync 33.33......"

PS the top list are the "grayed out" left column below

I am now completely disorientated.
I will forget for the moment CAS, RAS etc.

Do'nt even remember what this one was about!? Please disregard.
"............ Tryed the FFTs,  
1st used Vcore 1.3375 to get true 1.39 &  
2nd used 1.325 for 1.47.  
CPU Temp Diff was 39c & 44c........... "

What I did try though was your sugestion below, and the results were as per Reply N0.18 above, with temps observed.

"......You could perhaps try the following settings and see if they work.............using the following settings with the divider gives you a 2.4ghz CPU with a standard 400mhz or PC3200 ram speed, in this way, you overclocked the CPU and FSB but not the ram.    
RAM divider = [166]  
Vcore  = 1.425v (true Vcore as measured in Speedfan)  
HTT =  240mhz  
CPU multi = 10x  
RAM  = 200mhz  
HT multi  = 4x ..............."

These are the actual Bios settings I put:
FSB=240, CpuMultplr=10, Vcore=1.3625, Hyprtr Mulplr=4x, VRam=2.60 Ram Divdr 166.

If you notice there the Speedfan Vcore1 shows 1.41, and achieved this by puting in Bios VCore 1.3625.
Is this what you are asking if "....I have voltage under correct control and is this demonstratable?......"?

The only tool I use is Speedfan and the Fan speed controlling is Unticked if you noticed.

All other Asus & Nvidia staff are uninstalled.

And am not sure I can huck all this at all really. Too old & the memory too poor.
Hate to waste your valuable time.

I tried to get to grips with it, but all instructions I found none is in sequence, bits and pieces and find difficulty in putting them in the right order.           luke

Just to show what a dud I am, please separate which value is used to O/Clock what, just the names.

i.e. for:
A. CPU - FSB, It's Multiplier, VCore ?...........etc

B. MEMORY - VRAM, MemClock ?..................etc

C. MOBO - ?

D. GRFX - ?

D. CHIPSET - ?

E. Anything else ?

What did it mean when I used FSB 240, on bootup it posted "DRAM Clocking 333", and with FSB 220 "Dram clocking 400" etc.

And the last real dud question, which are the "RAM" & "RAM Base Speed" you mentioned. I know the Ram Devider.

PS. I was going to ask ".....when you overclock, besides Benchmarks, FPS etc, what improvement do you actually SEE, say in FS9, the only one I use?......", but just now desided to run your suggested figures again to O/clock to 2.4 ghz and notice again the behaviour of FS9 over LHT.

Well with FSNav window plus two others of cockpit showing on the screen it did not have that slight jerk appearing when over the LHR's buildings at 500ft that I get when on defaults.
I guess this may be the answer on how 20% rported O/clock improves fs9. Is that all?

The temps observed over LHR were:
CPU      42c
Chipset 36c
Remote 58c  what on earth could that be?
Local     44c
HD        35c

Is this "Cooking" the components?

O/clock 2.4 ghz & static as I write this, Temps are 30c give or take 1c, same as when on defaults.

Mind you all these just for curiosity, I am runing the PC on defaults as fs9 is more than adequate for me as it is, and still have no case fan with side pannel open.

And BTW, which is correct, 2.40 GIGA hz showng in "My computer" properties, or MEGA hz showing elsewhere?

Thanks for all your efforts, I found it very interesting & I am hooked, when I recover and consolidate, curiosity will drive me to pester you more.               luke