I'm beginning to get REALLY annoyed

[vgbaron]

makes sense - I'll get at it tomorrow

I'll put in the corsair and see if I can get it set at 400x9 1600 and then kick it up to 450 and go from there

[vgbaron]

ok corsair stable at 400x9 7-7-7-20 PL7 2T

going to kick it up to 450 8-8-8-24-pl7 2t with same voltages and see what happens.

[vgbaron]

failed memtest after 1/2 hour. will add GTL settings -40mv

[NickN]

What is the current NB voltage?

you may need to raise NB voltage a bit and there was a NB GTL in use as well as CPU GTL as I recall

I would probably work NB voltage if CPU GTL still fails and set GTL back to AUTO until I confirm a safe NB high end is not stabilizing the memory

If a high NB voltage such as 1.6 has no effect then I would try GTL

[vgbaron]

Set GTL -40 and NB GTL +60

NB voltage was/is 1.51

memtest stable at 41 minutes.

I'll try OCCT a this setting and see what happens. If it fails, I'll reset GTL's to auto and kick up NB

[NickN]

Thare ya go!


Now you're on the right track



just work them numbers.. we know the GTL is correct for the VTT so if it got stable on that then I would leave GTL and if you see any hiccups raise NB a touch with GTL set

I would only set GTL back to auto if memtest failed the same as before

If after all is said and done its more stable with the GTL then leave it and work NB but do keep in mind the GTL AUTO is an option with NB tapped up too.

there is nothing set in stone.. its a matter of working the variables and do remember a touch of Vcore may also help too..




..and one other thing.. dont stress about 1T @ 1800. Thats the last thing to go for and at 1800 and above its not as critical to hit. 2T is fine

[NickN]

Vic

As I posted in that other thread.. make sure

DRAM STATIC READ/WRITE CONTROL are both DISABLED

DRAM STATIC READ CONTROL (not write which always remains DISABLED) will actually provide a touch of a boost however if you can get 1T and 1800 stable with it DISABLED, that would be the first choice.

Always set up the clock with it DISABLED and after everything else is confirmed check with it ENABLED. You may find ENABLED can cause strange interrmittant lockups though

[vgbaron]

OCCT and Memset stable after 1 hour.

Tried PL6 - lockup - didn't even try 1T

Do latency and read values seem low or am I thinking of PL6/1T?

Also - noticed on reboot that windows 'sound' is scratchy - seem to recall a post by you about possible cause - can't locate it.

[vgbaron]

woops - saw your last post - both were set on auto. I guess I should disable both and retest?

[vgbaron]

ok OCCT stable 1 hour with both disabled

trying IT

[NickN]

Yes.. DISABLED for both

only ENABLE DRAM STATIC READ after EVERYTHING else is established but do be aware.. if you get any lockups thats the first thing you will disable



also

MAKE SURE


CPU SPREAD SPECTRUM
PCIE SPREAD SPECTRUM

and both DISABLED

see if sound is not scratchy after that.. can help a high clock too

1T will pull you down into the 48ns range if it will run stable and remember that MUST be set in the BIOS not MEMSET!

you are reading at dang near 11 grand.. dont knock that

[vgbaron]

ok - that's a little better!

[vgbaron]

STatic Read Enabled - seems to make a difference.

Still have some static with windows opening sound but all other osunds are just fine.

Will wait until XP64 is installed and see what happens.

Final settings:

450x9
333 strap
1800 8-8-8-24-1T PL7

GTLVref -40mv
NBGTL - +60mv

Vcore 1.31
PLL 1.51
Vtt 1.28
NB 1.52
Vram 2.0
ChaVref +25mv
ChBVref +25mv
SB 1.51
SB 1.06

[NickN]

hmmmmm

Windows boot sound being scratchy and all other sounds OK would indicate the issue is some kind of switch taking place. As Windows boots its initializing ACPI systems and that could be an indication of a resource share not quite worked out at the time of sound init

That may resolve itself on another Windows install as Windows will make the assignments as it is being installed clean.

DRAM STATIC READ ENABLED is allowing higher functions of DDR3 memory which typically in a clock you really do not need but it does provide a bit of a boost if ENABLED.

You may find that to be unstable in FSX use when the NB is really getting hammered. Thats the first setting to DISABLE if you see any problems like that


Now..

ChaVref +25mv
ChBVref +25mv

Not sure that is needed. Reset those to AUTO and see if its still stable. IF so leave them on AUTO but do note them in case you see anything in 3D stress and can try them again lock down stability

Everything else is looking right on the money.

Once you establish everything then you need to go through that BIOS on all screens and write down all the settings



NOTE: When you do switch to the 64bit OS (or before you install it) you need to enter the ADVANCED CHIPSET area and find the setting MEMORY REMAP FEATURE. It needs to be ENABLED for a 64bit OS, DISABLED for 32bit OS

[vgbaron]

Understood!

Moving right along  :)