vgbaron wrote on Oct 11
th, 2008 at 1:23pm:
Good Morning Nick -
Success at 6!
Tried 5 but locked up.
[img]
[img]
I can't say I understand it but I'm getting a feel for the relationship between the parts.
Let me see if I can get my 71 year old brain cells around this:
What we just did is between the memory, the mobo and the FSB and is not dependant upon the CPU other than it determines the FSB max.
So, when the Q9650 arrives and I try to kick the FSB up to 450, my main concern is keeping this memory at 1066 and the vCore lower.
Question about memset - since I 'saved' the settings, I'm getting the "error" sound on boot - no problems, no messages, nothing in the event viewer. The settings have taken because the Everest bench is the same. Can/should these settings be done in the BIOS or leave well enough alone.
Thanx!
Vic
Error sound on boot is normal. Just ignore it
The tRD value can be set in the BIOS however as many clockers have discovered when Windows boots and the BIOS initializes to hardware through the ACPI system you can in some cases lock with a lower tRD set in the BIOS even though the system is stable once Windows is fully BIOS aware..
The setting that controls tRD is Ai Transaction Booster under that seting after MANUAL is selected should be a list.
Ai Transaction Booster: Manual
Common Performance Level: XX <---- this value sets tRD
Pull-In of CHA PH1: Disabled
Pull-In of CHA PH2: Disabled
Pull-In of CHA PH3: Disabled
Pull-In of CHB PH1: Disabled
Pull-In of CHB PH2: Disabled
Pull-In of CHB PH3: Disabled
This setting has changed somewhat since I last saw this BIOS and if it still functions the same as it did in the past... yours SHOULD show 08 as it did in MemSet before you manually changed it. You can set this to 06 (or what ever you found stable in Memset)
Unfortunately tREF (Refresh Period) is NOT available in the BIOS. That setting is explained here:
http://forums.avsim.net/dcboard.php?az=show_mesg&forum=197&topic_id=43631&mesg_i...Unfortunately there is no way to change that in the BIOS so the only way to tweak it is using MemSet
I boot with memset as well as most pros who clock. If you ever had a problem getting into Windows because of a SAVED memset adjustment simply enter SAFEMODE and delete the save.
So my suggestion is to just use MemSET to make the 2 changes and ignore the error sound… think of it as letting you know you are booting MemSet CORRECTLY
You will need to fly with the current settings and make sure the system remains stable. If it does after a few weeks I think its safe to say you are set. If not, you may need to back the PL down (actually up) to 7 which should cure any intermittent lockups.
As for understanding what you are doing....
That’s easy... go back up and look at the 3 benchmarks you posted... if you notice the latency has dropped 10ns from the 60's into the 50's. The read speed on the memory has increased by 977MB/s and the L2 latency has dropped from 3.8 to 3.3ns
What you have done is accessed the true ability of the memory and northbridge of the motherboard, increased the communication ability between the CPU and memory and also made the flow of data take LESS pauses though latency reduction.
When you install the new processor you should not need to change anything other than:
Vcore
FSB
CPU STRAP
The CPU STRAP at 333 when the FSB is 450 SHOULD display a memory option of 1066-1080
All other values should remain the same however, I would SUGGEST you go ahead and DELETE the memset save and start out clean BEFORE you install the new processor... start over by getting things trimmed in JUST LIKE YOU DID in this thread... start with CPU/FSB and getting it stable at 450x9 in Vcore.
NOTE: P Quad processors should NOT exceed 1.36-1.4v vcore even if they are running COOL. Damage can occur to the proc.
However what you will discover is the processor you selected should run 4050 on a 1.28-1.32v vcore. As you know, lower is better.
You may need to raise the NB voltage to 1.55.. especially when working out the tRD (PERFORMANCE LEVEL) stability.. that is something you will need to address as it unfolds in stability testing but the goal will be to return the system to the PL6 setting if possible and also do not forget the highest tREF value from the dropdown as well.
Fly FSX after you go through the setup list for XP and O&O... I am sure you will see a difference in how the system ran in the past and how it runs now.
If you have any questions, shoot them to me and when you get your new proc feel fee to fire off any question you may have
Pages: 
