Use this beta of RealTemp to confirm the temps on the processor

http://www.xtremesystems.org/forums/showpost.php?p=3471705&postcount=2735

link is in the post

Confirm the readout on the Palm matches Realtemp. If it does under a full load the Palm readout is correct.. if it doesnt, use the reading in RealTemp instead

There has been some discussion about i7 and the temps sensors out there. Coretemp will not read the i7 CPU correctly and even some BIOS have been said to report temps incorrectly

As for clocking it.. what you said is that simple... raise BCLOCK, vcore if necessary, confirm the memory is running the correct or close to the correct speed and the temps under full load are in order..

thats it


As for it it will be stable without raisng vcore.. that is problematical and I cant guess about it... If its not stable then start bringing vcore up in values of .05 till it trims in. Most should be able to run a 940 at 1.35-1.40v Vcore  @ 4GHz however that varies from system to system. The name of the game is get the CPU to the highest speed stable at the lowest Vcore possible and that is part of clocking. Its a trial and error setting.



Load testing is done with the software OCCT v2.0.1

Run the 1 hour automatic text and watch the temps under full load. FSX will never get the processor that hot which means if it passes that load test stable and below max temp spec, your safe and clocked correctly

Great Thanks again NickN.  Your help here is invaluable !

I did try RealTemp and the readout seems consistent with my palm.

Now, 2 more questions:
1) Just to clarify, vcore is CPU voltage, right ?
2) Can I get to 3.4 on stock cooling ?

I will use occt to my testing.

Hopefully this will help me eliminate some stutters when FPS locked at 30.  At 25 no stutters but as smooth....almost there.

you cant damage the CPU unless it hits 100c

The lower value is what we use becasue the thermal limiting system will kick in right around 80-85c and slow the processor down to keep it cool

If you were hitting those 80c+ temps and did not change Vcore (set to AUTO) and only running 3190 then I suspect the heat sink may not be sitting on the CPU correctly.. thermal compound was too thick, PSU is too weak (would eliminate that if a decent 750watt unit is installed) or the tower airflow is very poor with a high room ambient temp

Ok, I just installed a Thermalright 120 and my temps are great.

Need some help here.

I increased the bclock to 155
Set the multiplier to 22
Set vcore to 1.225v

passed occt with temps below 60c.

How do I know if my RAM is running ath the right speed ?

CPUz tells me it is running at 465mhz with FSB/DRAM ration of 2:6 and NB frquency of 2480mhz.

Do I need to play with the RAM settings in the bios ?

Looking forward to your help.

Guys, I just got an unexpected Christmas boner..ah, I mean bonus

and I'm seriously thinking of taking that + selling off my MB, CPU, RAM (done!) to get one of these i940s.  

-Jim

fvjuke wrote on Dec 31^st, 2008 at 12:03pm:


Did you shut down TURBO MODE and ALSO the CPU TM Function in the BIOS before setting up the clock? If not kill the CPU advanced TM crap and turbo mode and it should be stable

hmmmmmm

I would think that would have been stable

You may want to go over to the OCZ forums and post this to Tony or one of the other devs.. I am not sure what they are suggesting for QPI/Dram voltage on those sticks..  they may want that a bit higher than 1.35v for their product

I assume you made sure the DRAM Timing was correct by the stick spec

Is this the memory in use?

OCZ3G1600LV6GK

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


If so your timing is too high which means the memory is running too slow

8-8-8-24  @ 1.65V

I would set it for 2T first.. establish the clock/stability and then try 1T and verify the stability

and yes, please use the OCZ forum and ask about clocking this product. I do not use it and can not advise without researching it myself and unfortunately I do not have time right now

OCZ is great about assistance in setting up a proper clock on their product

I would think 1.35v QPI/DRAM and a 1.65v DRAM would be correct with a 1.32-1.4v Vcore (lower is better) however they may suggest a higher QPI

To be quite honest... many time you DO NOT need to change anything off of AUTO other than the memory timing/speed, DRAM Voltage and Vcore and just work Bclock leaving everything else on AUTO but that can vary

Post over at OCZ and see what they have to say

I am saying those are the correct timings and voltages if you are using the memory I posted.. yes

and if 1.66v DRAM voltage is stable over 1.65.. thats OK just no higher

fvjuke wrote on Jan 2^nd, 2009 at 12:37pm:



If its that 3x1GB product then it should be 7-7-7-24

its only 3GB instead of 6.. the 6GB modules would be 8-8-8

fvjuke wrote on Jan 2^nd, 2009 at 12:37pm:




Ulf B

Any updates on the latest version of the bios?

I am having all sorts of issues with just anout the same gear......
my stuff idles 48c and I am blowing 80c under the latest OCCT within a few minutes. And can someone tell me where in the bios is "turbo"? I have been searching for it to disable..but no joy.
thx

Can you please look over where I'm at with this?

I have all the bios settings written down:

Under Manual in AI Tweaker:
CPU Ratio:22
BCLK:180
PCIE:100
DRAM:1443
UCLK:Auto
QPI Link Data Rate: AUTO

All Auto down to DRAM BUSS VOLTAGE: 1.66
The rest Auto.

Dram 1st 4:
8
8
8
24

This was the same as before but now it reads 1T versus 2t in my other post.

Under Advanced:
Freq: 3.98
Bclk: 181 Mhz

Cache L1: 128 kb
Cache L2: 1024 kb
Cache L3 8192 kb

Ratio Actual value: 22
CPUID: 106A4

CPU Ratio Setting: 22
C1E: Disabled
Hardware Prefetcher: Enabled
Adjacent cache line prefetcher: Enabled
Intel  Virt Tech:Disabled
CPU TM Function: Disabled
Execute Disable Bit: Enabled
HT: Disabled
Active Processors: Enabled
A20m: Disabled
C State: Disabled

That's all the bios settings in mine. I have seen other items from other posts but not on my mobo...maybe a different flash or the Palm version? I dunno.

This setup is just under 4 gigs, and can't pass more than a few minutes of OCCT load test.

Turbo V has now been disables from the startup. I was under the assumpion that was in the bios...hence my other post....learning as I go, but it is finally starting to make sense.

Note: At out of the box speeds I was idling at = +50c

I pulled the 120 Thermalrite and followed your description on the thin coat of thermal paste (artic freeze) I didn't have the balls to shand down the processor lid....thought about it...too small.

After resetting the heat sink...temp at idle dropped to 40c. Clocked up to 3.96 I sit around 50c but not able to get past the load test. Sink is seated nice and tight....fan spins the right direction!! With the numbers I posted is this a thermal issue? This case is a mini climate center.
Thx

Your guidence on a stable 4 gigs is appreciated

[quote author=NickN link=1229353222/15#26 date=1232680899]QPI/DRAM VOLTAGE 1.35v

DRAM VOLTAGE: 1.65 or 1.66v

you have temp problem.. LOAD LINE CALIBRATION: ENABLED
and work Vcore to the lowest point where it is stable with the QPI/DRAM voltage I listed above

Somewhere between 1.34 and 1.40v

If you can not get it to run stable at 80c or less your cooling solution is not doing the job.. either alignment or not flat  

Also, ambient temp where you are will effect the high end.. if its warm it will be harder to keep it 80c and under quote]

Have a look at this:


As you can see...I barley made it, but why the big difference in core temps between Real Temp and OCCT? Which one is accurate? It was like that the entire load test. It seems like I am just barley able to make 4 gigs...Was kinda hopin for 4.2
Do you see anything wrong?
Thanks

Hi,

Intresting article from AnandTech about the difference between different batches of Core i7 920 processors regarding overclocking potential: http://www.anandtech.com/cpuchipsets/intel/showdoc.aspx?i=3502

My own newbie experience with overclocking 940 on a P6T Deluxe board is that it was very easy getting the cpu up to 3.8 GHz with a VCore voltage at 1.27. My cooler is small and not that efficient (Zalman CNPS9500 AT) but the temps stay under 82C running OCCT v2.0.1. The temp readings match Real Temp 2.90 with TjMax set to 100). To be able to reach 3.9 GHz I had to raise the VCore voltage pretty much (don't remember the exact figures but it was close to 1.35V) to get it stable, but the temp increased too much.

At the 3.8 OC I run my OCZ 1600 3x2GB sticks at  1520MHz 7-7-7-24 T1. Multiplier at 20 and BCLK at 190. Very good benchmarks with SiSoftware Sandra Lite  

Nick,

Thank you for the info that I might pass OCCT but still fail in FSX. I raised the vcore a notch, 1.40, and am now stable at 4Gh.

You were also very right about 'heavy metal' in your earlier guidelines to the i7; I have never flowm the LvLD 767 with frames locked at 30 and auto and scenery at max with a fluid ride.

system: i7 920@4Gh
            Mushkin 1600 7-8-7-7-20
            Raptor 150 MB drive
           260 EVGA card
           Noctua cooling
           Antec 900 case
           Max temp under OOCT load: 74C, room@70F

Your knowledge is much appreciated.

Jack S



PS followed the posts last night - nice to see the individual is not around!!!

So I assume you are fine now Jack?


you dais you are stable @ 4Ghz.. and that includes FSX now?

Nick,

Yes, thank you for checking. Frankly, I think the load temp was fairly good  due to my following your thermal paste suggestion: spread onion skin thin with razor blade. 

  Jack

PS: Your suggestion to RMA the original Mushkin RAM was also dead on; they replaced it very fast.

J,

Thanks for the reply. I am locked at 20 with the 920 but I guess you read my mind.

I'm using 20x197=3.5 Gh and the RAM is at 1573 so I'm pretty close. The 4.0 Gh turned out to be unstable in FSX but so far she seems to be stable and I ran RealTemp in the background as a check - max was 63C.

I may have one of the chips AnandTech talked about.

I was also able to drop the vcore to 1.36 which helps with the temp.

I do believe a 940 is in my future somewhere - wish I had read Nick's suggestions sooner but $ were/are an issue.

Jack