ClockGen (CG-NVNF4) corrupted

[luke]

Has anybody had similar corruption of Clockgen for nF4?

In foto, the left one as used to show up with AN8-sli mobo, and the right hand one corrupted and unusable, after mobo exchanged for A8N 32 sli.

With / without firewals.

Redownloaded & un/reinstalled it several times.

PS Get Values applied for both.

Any help appreciated.

[congo]

Look at your signature and I think you'll find the answer.

You don't have an NForce4 SLI chipset, your's is different.

You might get a reply from them saying they are working on a new version of clockgen hopefully.

Edit: Ah, I saw your other thread. Fixed huh?

[luke]

Unfortunately not, please see new thread over at:

http://www.simviation.com/cgi-bin/yabb/ ... 1138345100

luke

[congo]

Q. What is GPU?  

A. Graphics processing unit. Your video cards processor.


Q. Last night I rechecked Bios and nearest to HTT is :
"Over Voltage Hypertransport" [Disabled]  or Enabled, with no figures to set.

A. This is a setting that is missing on my board, it enables volt increases for the hypertransport link allowing massive overclocks. Leave it disabled until you have expert knowledge of overclocking.


Q. DDR Vcore [Auto] ....2.6V, 2.65.........to 3.2

A. Normally called Vram. Set this field to manual if your ram is unstable at high overclocks, increasing ram voltage will yield stabilty at higher speeds. There is a danger of burning out your RAM if you use this. There are special RAM testing and burn in programs for getting the most out of your RAM.

Most RAM for these rigs is 2.6V, but you can probably go to 2.75V without harming anything. Ground yourself to the case and feel the ram chips with the back of your fingers to see if they are hot while flying in FS9 or using some intense benchmarking utility. If they are hot, do not increase Vram.


Q. DDR Clock Skew  [Auto] ....Normal, Advanced, 150 - 900pc

A. I wouldn't have a clue except that it's an advanced overclocking option, leave it at default until you know for sure what it does.


Q. 1T / 2T Memory Timing 1T / 2T

A. this is a basic RAM command rate timing. The boys at the overclocking sites will tell you that 1T is a must. Well, that's just a load of BS with these boards. I can get better performance using 2T with my RAM, and in fact, it's been documented by several people that these asus boards are unstable at 1T in many high speed configurations (ie. When memclock goes much over 240mhz).

Use 1T under 240mhz but if you tighten the other ram timings you may find 2T will need to be used. Proof of performance needs to be carefully tested with a benchmark utility to find which configuration is the best.


Q. Vcore Voltage      [1.472v] ....Ignore

A. Definitely do not ignore this setting. The Vcore you have set there is VERY high for Stock cooling. You should see sharp temperature rises while Simming or benchmarking. Be careful. Only increase Vcore from standard 1.4V if your rig is unstable at the overclock, and increase it in very small increments until stabilty is reached. I would leave it at stock speed until you have crashes or benchtest failures.


Q. I am stuck, unless any of the other variable factors in the Bios that I can see, can be used instead of the elusive HTT,  like:
1. CPU FSB [200] goes up by 1, 2, 3 ......to 500

A. CPU FSB is the same as HTT. This is what you are winding up with the slider in Clockgen.

2. Processor Voltage (for setting VCore) starts at 1.735,
is Set at [1.425] ....1.4375, 1.45, ....to 1.5625

A. This is different from the info you provided above for Vcore (you said it was 1.472v). You have to be accurate or I'm wasting my time replying ok?

3. Adjust PCIE Freq Set [100]

[luke]

Thank youuuuu,
Firstly, what you saw there is what comes up as default. I have not changed anything, and will only do when satisfied that I fathomed what you experiensed people say.

The GPU bit, I should have said

[luke]

Since previous thread, after a couple of B...up with failed bootups & restarts, I altered the Bios items

[congo]

You should see CPU temp in the sensor section as well as GPU, look up a bit.

The CPU temp is only high when it's doing work, So you need a util that reads in real time, everest does it, but your speedfan seems to be picking it up.

Your Vcore is too high, drop it so your hardware monitor in BIOS and speedfan shows 1.4v or close to that.

You may find you have to set 1.34v to get 1.4v, it's strange but your mobo is sending the CPU too many volts.

This may be explained........... many users whined about not having enough voltage so there were bios files produced that used a ratio to increase the actual voltage well over the setting voltage in bios. I'm not sure if this is your case, but it

[luke]

You realise ofcource that the settings I put were not from a consious efford, more rather out of a flook, to arrive at 2.4ghz.

But Everest again says O/clock 10% as with 2.2ghz.

I do'nt know about instability, but PC was normal, fs9 flew well, and did not noticed any improvements in my heavy clouds etc. Just as before I would say.

Heavy multitasking is not affected either.

Will try, but do not remember to have seen Vram.

My corrupted ClGen comes up like this below, and mine as per your last one. So different. I keep setting Clgen up just to see, even if it is unusable. Hoping these interrilations would be same if it was working & applied.
Is,nt there any other similar progr. for windows?

So you reckon it is because of the x16 of my chipset?
No word from ClGen people yet.

Also Everest Temps are of Computer > Sensor. Has nothing else. Unless the mobo corrupted this one too.

PS. would you say that "Voltage Control" in Clgen refers to CPU VCORE? I get confused as I find everything is referred too differently at different places.

[congo]

10% is a modest overclock, you aren't going to notice it much, this was simply to help you understand without frying anything. FS9 may be limited by your Graphics card
if you measure no difference there.

Vram can be adjusted, you listed the setting above and I replied explaining it..

There may be a similar utility to clockgen, I had an nVidia made overclocker for nForce2 boards that was similar.


The A8N32 SLI x16 chipset is fairly new, it depends on 3rd party developers as to whether they build utils for it or not, have you looked on your mainboard install disk for overclocking utils? I try to avoid any tool that works "automatically" though, as they are more junk running in the background and you have limited control over them.

It's possible that the sensors in your board are quite different to what Everest can read, the version of everest you have is now discontinued and no longer supported, they went payware about the time your chipset came out. Your board is definitely not on the support list for clockgen

Voltage control in Clockgen is Vcore (CPU) control.

Did you manage to get your Vcore under control?



Also, you are posting illegal size bitmaps in the forum!

SHAME ON YOU !      

[luke]

Tahnx for the info.

I put in the figures you said:
Vcor 1.337, FSB 220, Cpu Multplr 11, VRam 2.7, Hypertr.Multplr. 4.
It gave Cpu Spd 2419mhz, but fs9 was rather Jerky.

Then entered:-
Vcor 1.450, FSB 240, Cpu Multplr 10.5, VRam 2.60, Hypertr.Multplr. 4,

[congo]

Your Vcore is set to high!            It's reading 1.5v !

Drop it so your tools read it as 1.4v or just go back to automatic settings, your gonna fry yer CPU luke, I tried to warn you about voltage settings and ease you into this, but you're moving too fast before you understand it.

This is why I posted the clockgen thread to begin with, so people could learn before they jumped in, unfortunately your system isn't compatible with the version of Clockgen you downloaded. They just released a new version, you might try that.

Your friend is right, he is showing you how to get max overclock, if I did that, I would not be your friend !

You don't have enough knowledge to do it safely yet.
A complete understanding of the chipset, BIOS and it's relevant settings is required.

I advise you to set everything back to auto for now, then check the Vcore, if it's higher than 1.4v, reduce the Vcore in Bios until the sensors read 1.4v, then report back here, I'm not going to help you fry yer CPU, get Vcore under control first, then I can help you more.

I'm not trying to show you how to overclock your system, just how to understand it so that you can.

[luke]

I was writing this when your last thread arrived.

Apreciate a lot your concern and WARNINGS.

1. As mentioned before, any settings I try only stay up to the readings after StressPrime & a quick few seconds to check temps with fs9 & multitasking then back to defaults.
The case is open in front of me continusly feeling the Cpu Heatsink, sticks, chipset & pipes, and the 6600gt. They were never hot to the touch, just worm as discribed on each O/clock try.

2. Made a mistake referring to Temps in last foto as "StressPrime gave Ts as per foto."

Those as foto shows were with fs9 running, all maxed, full cloud & moderate rain.

The AFTER StressPrime test teps are, in this foto.

That test's CPU Usage never goes past 3 - 4%, in fs9 are 100% constantly. Would'nt that be a better test? after seeing the StreePrime ones are low?; or am I confused again. Wont be the least surprised.

The VCore is 1.4125 default. To O/clock lowered it to 1.335, nearest to 1.34 as you said, giving Cpu Speed 2.1.

There are some facilities here, maybe relating to this?.
Advance > Jumper Free
Over V NB core [Disable] or Vcore to +1.3
Over V SB

[congo]

Your Vcore is still showing 1.5volts, you haven't lowered it yet!

You need to get the Vcore voltage down to 1.4v before anything else.

There probably isn't any real danger in the short term, I just want you to demonstrate that you can control the Vcore accurately before we move on.

The stressprime test is not going to help you yet, we will come to that one day  

[luke]

Thanx again Congo,
I think I tried to explain this before, but with VCore at 1.335 during the test shows 1.50 & before/after it 1.39.

It is terrifying that I could burn my

[congo]

[quote]Thanx again Congo,
I think I tried to explain this before, but with VCore at 1.335 during the test showed 1.50 & before/after it shows 1.39.

It is frightening that I could burn my