NickN - an opinion?

[NickN]

OK

I have not worked with the Nvidia boards.. but the deal is this setting


CPU Load Line Rate

Which is not the same as LLC or CVD and is a direct setting of the change on droop

I would need to research that setting to see what effect it has on vdroop and Vcore and I would not change that unless you know what to set it for.. I dont have time to look it up right now but I am sure that setting is the target

Whn you get home.. check that in the BIOS and tell me what the scale is for the setting

The deal with Vdroop is NEVER exceed the Vcore for the proc by Intel spec and you should be fine..

[vgbaron]

Understood - VID for my Q6600 is 1.5.

I'll check the settings tonight and let you know.

I appreciate your taking time from your Gex workload to help.

Thanx!

[NickN]

let me know what yours is set to as well as the option list

[vgbaron]

Currently running p30 bios - latest is p33 with these fixes:

This BIOS is ONLY for the EVGA 680i SLI Motherboard

P33 BIOS is available now, the major highlights are listed below:
Added support for new Penryn dual core CPUs

Added FSB-overclocking support to the new Penryn FSB-1066/1333 CPUs
Fixed compatibility issues of OS + ACPI
Fixed restoring disabled device states & fan speeds after suspend/resume
Fixed PCI and PCIe compatibility issues
Added device functionality improvements (includes GPUs & Sound cards)
Fixed SATA / MAC / USB compatibility issues

Added support for auto-overvoltaging when overclocking <----??
Improved nTune compatibility
Improved memory compatibility

I'm thinking one thing at a time but JIC there's something that jumps out at you to require an update prior to anything further.

Vic

[vgbaron]

Murphy's Law abounds - the CPU Load Line Rate setting is not in my BIOS. I've posted on EVGA's forum asking if it is available in the current BIOS but no answer yet.

Also read a 3 page thread on people with the same mobo having the same freezing issues as myself. Unfortunately, no resolution.


fyi -
BIOS vCore setting is 1.537
BIOS vCore reading is 1.481
CPUz vCore reading is 1.496

[NickN]

Thats HIGH

you should not need to run that high to clock a Q6600


BIOS update sounds like the direction this needs to go. If you have never done one, be advised they can be dangerous but as people like Brett Henderson will tell you they can also be a godsend due to the fixes and settings that may become available



I always keep my BIOS updated to the latest official version (not beta version) and there are cases where a BIOS update can make a system run worse where the user, just like drivers, needs to find the BIOS that works best for them.

My advice would be to update the BIOS. There are tools they give you to do that in Windows which I never, ever use. There is usually a DOS boot method which is always better and its also always best to manually reset the CMOS by the jumper on the motherboard after powering down from a BIOS flash .. it means all the BIOS settings are wiped but its the best way to be sure the new BIOS initiates correctly.

[vgbaron]

I've done a few flashes thru the years - agree about the DOS method.

So you're saying flash the BIOS, after reboot power down and jumper the BIOS on the mobo and start from scratch.

Any opinion on using the 'auto' voltage function for o/c?

Thanx!

[NickN]

I've done a few flashes thru the years - agree about the DOS method.

So you're saying flash the BIOS, after reboot power down and jumper the BIOS on the mobo and start from scratch.

Any opinion on using the 'auto' voltage function for o/c?

Thanx!

Yep.. always jump the reset on the mobo after a BIOS flash..  Once cleared and the jumper is placed back to normal, boot up, enter the EXIT menu.. hit LOAD SETUP DEFAULTS and F-10 Save and Exit, then reboot enter the BIOS and start fresh

Auto overvoltage is typcially a liquid or LN2 clockers tool. I would not use it on air

What you are looking for is control stability over the Vdroop. The new BIOS may have addressed stability issues too

[vgbaron]

Guess I'm going to have to go thru the whole clock procedure again. Set the FSB to 400 and it crashed in 8 seconds.

I'm puzzled tho - I've set the vCore to 1.45 in the BIOS yet it only shows 1.41 - isn't that large for vDroop?

400 has been easy in the past so I'm slowly bumping the vCore and testing - 1.41 doesn't cut it.

[NickN]

Guess I'm going to have to go thru the whole clock procedure again. Set the FSB to 400 and it crashed in 8 seconds.

I'm puzzled tho - I've set the vCore to 1.45 in the BIOS yet it only shows 1.41 - isn't that large for vDroop?

400 has been easy in the past so I'm slowly bumping the vCore and testing - 1.41 doesn't cut it.

I have seen .10v variances in Vdroop in the past.. its really a 'by board design' thing as there is a standard they use for the circuit design from Intel but nothing set in stone with it for all boards.

Make sure the memory voltage/timing is correct.. you could be hitting memory walls and not CPU

[vgbaron]

Good point about the memory. I just set it to what I had before

2.2V as recommended by Mushkin and 5-5-4-12 2T

Probably should do as I did last year - leave the memory at default until I get the CPU clock right.

its PC6400 DDR2 #991535 1066

[vgbaron]

ok, system is stable - settled at 3.623 and 1.44. A tad lower than original clock (3.645) but vCore is lower too. Memory back where I had it and so far so good.

Appreciate your help, as usual, especially that I know you have a full plate right now.

Have a virtual beverage of your choice, on me!



Vic

[NickN]

ok, system is stable - settled at 3.623 and 1.44. A tad lower than original clock (3.645) but vCore is lower too. Memory back where I had it and so far so good.

Appreciate your help, as usual, especially that I know you have a full plate right now.

Have a virtual beverage of your choice, on me!



Vic

The best you are going to do stable without extreme cooling and pushing the vcore way up on a Q66 is 3.6GHz so if its running a tad higher consider yourself lucky


Memory being able to keep up in timing and speed is by product and its design... that purchase can be expensive and its expensive for a reason. Going from CAS 5 at 1066 to a stable CAS 4 costs. At the same time going from CAS 5 1066 to CAS 5 1140 costs too

http://forums.avsim.net/dcboard.php?az= ... 4141&page=

[vgbaron]

Understood - think I'll leave well enough alone.

One last question tho - any benefit/problem with enabling Speedstep after clock is done?

Thanx,

Vic

[NickN]

Understood - think I'll leave well enough alone.

One last question tho - any benefit/problem with enabling Speedstep after clock is done?

Thanx,

Vic

I dont

Some do

It depends on if it remains stable. My opinon on that is I dont want to find out 2 hours into a flight.. and its not making the proc or the board live any shorter or longer but thats just me

its a power consumption issue, not lifespan

all you can do is try it