What are you guys getting with this memory with 2 DIMMs in? Right now I am running 250 @ 2.5-3-3-0 really stable I believe.
Printable View
What are you guys getting with this memory with 2 DIMMs in? Right now I am running 250 @ 2.5-3-3-0 really stable I believe.
Zeus, i have now tried running memtest 86 and #5.
I now have a fan blowing over ram cuz i almost burned myself =)
Ram does not get that hot in any other bench or test i tried.
So you are giving your mem 3.1v uberman??
I have only gien it 2.8 so far. I didn't know how well they liked high volts. but yours seems to be doing ok.
I think I will give it 3.1v when I get home from school
I have having so much trouble with this memory. What DIMMs are you guys running your memory in? I am in 1 + 3. Or should I change it to something else?
I'm gonna RMA mine, got an RMA number already.
It runs hot, it makes my system not wanting to boot if i set DRAM drive strength below level 3 and it fails Prime at default timings and voltage at 208MHz!! (DDR416)
I hope my replacement will do a lot better. :)
isn't Level4 the "most relaxed" one for oc'ing?Quote:
Originally Posted by Zeus
How long should prime run until system is considered stable ?
24 hours should be long enough.Quote:
Originally Posted by Ubermann
Thats long and boring =)
Heres one cas 2.5 and 305FSB X 6 multi.
Primed for 1.5 hours then moving on.
Its simpleQuote:
Originally Posted by Ubermann
Either you do it with patience OR you get a nice BSOD while playing your fav game and lose your check point ;)
:up: so true... so true :lol:Quote:
Originally Posted by Samael
The point is to learn from your mistakes and to dont repeat them :explode: :lol: :explode:Quote:
Originally Posted by saaya
I need more time to screw with this and I need to learn what the hell each settings actually is in the BIOS, besides the obvious ones we always mess with.
Im just so happy i didnt try it for 24 hours cuz x7 multi wont pass any memtest =)
Dunno what to try..
ugp read this: http://www.ocforums.com/showthread.php?t=329627
WOW! Damn...I didn't know someone posted that! lol That's awsome. Thanks man!
Heres a link explaning every bios setting more deeply.
http://www.rojakpot.com/default.aspx?location=9
One and a half hour is good enough for me since i'm not a gamer, it's all too flashy for me. :D
305MHz with CAS2,5 is very nice! :up:
Today i've been RMA-ing mine, it failed Prime at 208MHz 2-2-2-5 with 2.7V :stick:
Now that was a real bad stick if you ask me.
Also, i couldn't get my head around this DRAM drive strength thing, setting it to level 2 or 1 resulted in a no post. :confused:
Not even the "detecting array" message.
I really hope my replacement will do as fine as yours but knowing me....hmmmm, we'll see. ;)
Too sad =(Quote:
Originally Posted by Zeus
Hope they are fast on switching the ram for you, we all hate waiting!
Its like having x-mas the 25:th December.
Oscar have some new bios (8/15) at:
http://www.dfi-street.com/forum/show...&threadid=1954
Has anyone tried it yet?
Im running it, notice no difference.
Some raid update i think it said.
I am running it now as well. I am seeing how far I can go at 2-2-2-5 with everything else at AUTO with MemTest. Test 5 seems to be the one that will give you errors. And then I am testing SiSoft Sandra Bandwidth and I am going to make a chart. I figure is the best way to start to see how far this memory can go. Is there a ny other test besides 5 I should do as well to test the MEM?
I think #5 is the absolute killer for ram.
If it survives that, then it survives anything.
No it doesn't.
Example:
230 1:1 2.5-3-3-7 Everything else on AUTO passes Test 5-7 but isn't SuperPi Stable.
Changed the TREF to 4708 Cycles and passes Test 5 and now is SuperPi Stable at 39s. And Sandra Bandwidth is at 3,509.
And When I tryed to load Windows at a Drive Strength of 4 I got "Detecting Array". So I switched it to AUTO and I now load into Windows.
Mine had a dislike for test 6, it was the test what made the RAM run the hottest.
Cas 3 errored in test 5 at 290 but it did fine at CAS 2,5. :confused:
I think if it passed ram test but not superpi then its you cpu that has wrong volt or is unstable in some way.Quote:
Originally Posted by ugp
Well, I have had my hands full lately with real life, but I finally got a chance to play with the memory again. I am having some problems getting the memory stable. I cannot pass memtest with both 512 modules without getting errors. I have tried stock settings, relaxed settings, 2.5 2 2 10 with all else set to auto, and voltages between 2.7 and 2.9. The memory still errors at 200MHz and on up. Odd thing is, both sticks will pass without errors if they are used by themselves, except in the second memory slot. I cannot get the machine to boot if I have a single stick in the second slot, but 1 and 3 are fine. I have a 90mm fan blowing directly onto the sticks, so they aren't overheating. I am going to do some more tests with each stick by itself to see if maybe one of the sticks is just not getting along with the system. I do wonder though, if it might be the DFI mobo causing the issues.
Good to see that others are having some success though. Hopefully, I can get things squared away stability wise and start having some oc'ing fun too.
Yeah it could be but I have a lot to play with until I finally find a stable point I am happy with. Sad part is I haven't even begun to try to find my highest CPU clock yes either. :(Quote:
Originally Posted by Ubermann
it's sad for an extreme ram to fail running at stock!Quote:
Originally Posted by Cohiba
good luck and wait for your nice results soon! :)
Well i have been messing around for some week now and im still trying =)
Girlfriend is very angry.
But, its a hobby and fun =)
Maybe she needs some oc and "tuning" as well :p: :D :p:Quote:
Originally Posted by Ubermann
Will tune her later, and if shes not happy by then i need another plan.
Maybe i put some Watt in her then shes very calm.
Adjust the pots inside the bread toaster and IEEEEEKKKKK!!
don't forget to vdimm her nippless :=)
Quote:
Originally Posted by Ubermann
Checks goldmemory screen (finally passing .5 G BH-5 @ 250/3.2Vdimm)
In 17 minutes max (will run test #5 all day @250FSB/3.1 Vdimm, fails GM in 5 mins @ same, (did it w/ errs during burnin @259/3.3 :flame: ) GM (20$) seems to mimmic windows performance more accurately, however need to test w/ both since sometime memtest passes and not GM or vice versa :brick: :wierd:
Ok so I have just tested 265 @ 3-3-3-10 @ v2.9 and Chipset @ v1.8 Times 8.
I tested SuperPi and got 41s.
I did Sandra Bandwidth and got 4,044GB/s
CPU Arithmetic scored 9,737.
I am not sure if this is stable.
But I had the usualy settings like bigtoe recommend...
TREF @ 4708 Cycles
TWCL @ 05 Cycles
DQS Skew Increase of 64
Max Async Latency of 08.0ns
Dymanic Counter Enabled
R/W Queue Bypass 04x
Bypass Max of 04x
32 Byte Granularity Disabled.
I shall run MemTest-86 and see how many errors I get. I don't exactly understand the program though. I ran it twice on a certain test and got one error and I had left the room and cam back and it didn't get any errors the second time around. Why in the hell does it do that?
For some reason girls don't like it when we pay more attention to our computers than we do to them. They get very jealous over a piece of machinary. I don't understand it lol. Just kidding. I know how that is though man. It is very easy to get caught up in messing with a PC. I have been doing the past 3 days all day.Quote:
Originally Posted by Ubermann
OK I have finally done some testing and I can't get this memory up past 255 1:1 with 2.5-3-3-10 1T? I did get it to boot at 260 once but it crashed soon after a Sandra run. I hit 7,200. I have the boards VDIMM maxed at 2.8? Any suggestions? I have the HT at 800 and the multiplier is at 9 to take those both out of the equation. On a side note I am running at 240 X 12 now with 2.5-3-3-10 1T and getting 7,300 in Sandra. I know I can get more out of this RAM but I don't know what is holding me back. Are there other memory settings I need to change?
i think she has already OCed too much and getting unstable!Quote:
Originally Posted by Samael
better prime test or mem test her... :D
He might need to give her the Touture test :DQuote:
Originally Posted by dav
Orgasm her to death and she'd be happy :p:
Here is my highest clock on the memory so far.
Next I am going to try to get it with a 9 multiplier so I can hit almost 2.4Ghz. Any suggestions on how much voltage I should use?
"single" channel? you got a stick of 1GB?Quote:
Originally Posted by ugp
no.. socket 754 doesnt have dual channel support..Quote:
Originally Posted by dav
ugp:i can run my mems at 265mhz with 2.5-3-3-10 and 2.8v prime95 stable..
so if u give the mems a bit more voltage u can maby run them at 270mhz.
I always run them @ v2.9 and I am still not stable. I am despiratly seeking answers to why. I have a good board I know I do. And a decent CPU. I dont understand why.Quote:
Originally Posted by Vitalizer
sorry didn't notice he's on 754.. :P
Try "tref" at 4672 instead.
Seems to be more stable there.
I have never been able to run ram at 300 and cpu at 2.4 and run any 3d benches.
Now it never fails.
Using the omega drivers most lately also.
APIC enabled.
Ehh, I like DNA Drivers. I bench higher with them. And I shall give that a shot. I posted on OCZs forum and I have Tony aka bigtoe helping me out. He said they should do 250 easily.
http://www.bleedinedge.com/forum/showthread.php?t=4689
Might want to check it out if he gives some tips :D
Seems to run fine at 2.5-3-3-0 at 285FSB.
"IdleCycle limit" and "R/W queue bypass" should be put to 8 with those timings.
Gives almost same results at 3dmark01 as 2.5-4-3-0 at 300FSB.
Another thing.
When going over to 3-4-4 then "read to write delay" need to be "3".
2.9volt seems to work best with ram.
Dram level 1 can and should be used on all settings.
Tref 4672 seems more stable then 4706.
This is one a single stick.
i cant run my cpu at 2.4ghz with 2 sticks in.. only with 1.. its very strange. so i have to run the cpu at 265x8.Quote:
Originally Posted by ugp
Thanks I'll give that a try real quick. I tested both DIMMs real quick and tried to max them out. I shall try it with this now.'Quote:
Originally Posted by Ubermann
EDIT: I gave it a try and this is what I came up with.
I tried each DIMM by itself in Slot 3 with settings of 2.5-3-3-0. TREF at 4672 Cycles and a Drive Strength of 1. The first stick that I was able to get 290 2.5-4-3-10 with got 124 Errors on test #5. The second stick that I was only able to get 280 2.5-4-3-10 (Those were a quick test by the way) I only got 56 errors.
I do not trust MemTest86 though. My memory pasted it with flying colors and kept getting memory dump errors unless that could be a CPU problem as well.
SP2 really sux when overclocking!
@Ubermann
Hey man want to have alittle contest?
Want to see who can get the most bandwidth out of stock speeds? (Being 200FSB)
If so feel free to copy and paste this as a template :p: :D
Since I am having trouble with OC I decided to start. I don't have anything to compare it to though...
Here is my results so far...
SiSoft Sandra Bandwidth: 3015MB/s
SiSoft Sandra Arithmetic: 9225 MIPS
SiSoft Sandra Multi-Media: 19,152 it/s
SuperPi: 44s
FSB BUS Frequency: 200
AGP BUS Frequency: 66
Clock Spred Spectrum:
LDT Downstream Width: AUTO
LDT Upstream Width: AUTO
LDT/FSB Frequency Ratio: AUTO
CPU/FSB Frequency Ratio: 10.0
CPU VID Control: 1.550V
CPU VID Special Control: AUTO
ChipSet Voltage Control: 1.6V
AGP Voltage Control: 1.5V
DRAM Voltage COntrol: 2.8V
DRAM Frequency Set (MHz): 200MHz 1:1
Command Per Clock (CPC): 1T
CAS Latency Control (TCL): 2
RAS# To CAS# Delay (TRCD): 2
Min RAS# Active Time (TRAS): 5
Row Precharge Time (TRP): 2
Row Cycle Time (TRC): AUTO
Row Refresh Cycle Time (TRFC): AUTO
Row To Row Delay (TRRD): AUTO
Write Recovery Time (TWR): AUTO
Write to Read Delay (TWTR): AUTO
Read To Write Delay (TWTR): AUTO
Refresh Period (TREF): AUTO
Write To CAS Latency (TWCL): AUTO
DQS Skew Control: AUTO
DQS Skew Value: AUTO
DRAM Drive Strength: AUTO
Max Async Latency: AUTO
Read Preamble Time: AUTO
Idle Cycle Limit: AUTO
Dynamic Counter: AUTO
R/W Queue Bypass: AUTO
Bypass Max: AUTO
32 Byte Granularity: AUTO
----------------------------------------------
SiSoft Sandra Bandwidth: 3015MB/s
SiSoft Sandra Arithmetic: 9219 MIPS
SiSoft Sandra Multi-Media: 19,152 it/s
SuperPi: 45s
FSB BUS Frequency: 200
AGP BUS Frequency: 66
Clock Spred Spectrum:
LDT Downstream Width: AUTO
LDT Upstream Width: AUTO
LDT/FSB Frequency Ratio: AUTO
CPU/FSB Frequency Ratio: 10.0
CPU VID Control: 1.550V
CPU VID Special Control: AUTO
ChipSet Voltage Control: 1.6V
AGP Voltage Control: 1.5V
DRAM Voltage COntrol: 2.8V
DRAM Frequency Set (MHz): 200MHz 1:1
Command Per Clock (CPC): 1T
CAS Latency Control (TCL): 2
RAS# To CAS# Delay (TRCD): 2
Min RAS# Active Time (TRAS): 10
Row Precharge Time (TRP): 2
Row Cycle Time (TRC): AUTO
Row Refresh Cycle Time (TRFC): AUTO
Row To Row Delay (TRRD): AUTO
Write Recovery Time (TWR): AUTO
Write to Read Delay (TWTR): AUTO
Read To Write Delay (TWTR): AUTO
Refresh Period (TREF): AUTO
Write To CAS Latency (TWCL): AUTO
DQS Skew Control: AUTO
DQS Skew Value: AUTO
DRAM Drive Strength: AUTO
Max Async Latency: AUTO
Read Preamble Time: AUTO
Idle Cycle Limit: AUTO
Dynamic Counter: AUTO
R/W Queue Bypass: AUTO
Bypass Max: AUTO
32 Byte Granularity: AUTO
----------------------------------------------
SiSoft Sandra Bandwidth: 3013MB/s
SiSoft Sandra Arithmetic: 9225 MIPS
SiSoft Sandra Multi-Media: 19,149 it/s
SuperPi: 45s
FSB BUS Frequency: 200
AGP BUS Frequency: 66
Clock Spred Spectrum:
LDT Downstream Width: AUTO
LDT Upstream Width: AUTO
LDT/FSB Frequency Ratio: AUTO
CPU/FSB Frequency Ratio: 10.0
CPU VID Control: 1.550V
CPU VID Special Control: AUTO
ChipSet Voltage Control: 1.6V
AGP Voltage Control: 1.5V
DRAM Voltage COntrol: 2.8V
DRAM Frequency Set (MHz): 200MHz 1:1
Command Per Clock (CPC): 1T
CAS Latency Control (TCL): 2
RAS# To CAS# Delay (TRCD): 2
Min RAS# Active Time (TRAS): 5
Row Precharge Time (TRP): 2
Row Cycle Time (TRC): AUTO
Row Refresh Cycle Time (TRFC): AUTO
Row To Row Delay (TRRD): AUTO
Write Recovery Time (TWR): AUTO
Write to Read Delay (TWTR): AUTO
Read To Write Delay (TWTR): AUTO
Refresh Period (TREF): AUTO
Write To CAS Latency (TWCL): AUTO
DQS Skew Control: Increase
DQS Skew Value: 64
DRAM Drive Strength: AUTO
Max Async Latency: AUTO
Read Preamble Time: AUTO
Idle Cycle Limit: AUTO
Dynamic Counter: AUTO
R/W Queue Bypass: AUTO
Bypass Max: AUTO
32 Byte Granularity: AUTO
----------------------------------------------
SiSoft Sandra Bandwidth: 3020MB/s
SiSoft Sandra Arithmetic: 9225 MIPS
SiSoft Sandra Multi-Media: 19,149 it/s
SuperPi: 45s
FSB BUS Frequency: 200
AGP BUS Frequency: 66
Clock Spred Spectrum:
LDT Downstream Width: AUTO
LDT Upstream Width: AUTO
LDT/FSB Frequency Ratio: AUTO
CPU/FSB Frequency Ratio: 10.0
CPU VID Control: 1.550V
CPU VID Special Control: AUTO
ChipSet Voltage Control: 1.6V
AGP Voltage Control: 1.5V
DRAM Voltage COntrol: 2.8V
DRAM Frequency Set (MHz): 200MHz 1:1
Command Per Clock (CPC): 1T
CAS Latency Control (TCL): 2
RAS# To CAS# Delay (TRCD): 2
Min RAS# Active Time (TRAS): 5
Row Precharge Time (TRP): 2
Row Cycle Time (TRC): AUTO
Row Refresh Cycle Time (TRFC): AUTO
Row To Row Delay (TRRD): AUTO
Write Recovery Time (TWR): AUTO
Write to Read Delay (TWTR): AUTO
Read To Write Delay (TWTR): AUTO
Refresh Period (TREF): AUTO
Write To CAS Latency (TWCL): AUTO
DQS Skew Control: AUTO
DQS Skew Value: AUTO
DRAM Drive Strength: AUTO
Max Async Latency: 08.0
Read Preamble Time: AUTO
Idle Cycle Limit: AUTO
Dynamic Counter: AUTO
R/W Queue Bypass: AUTO
Bypass Max: AUTO
32 Byte Granularity: AUTO
----------------------------------------------
SiSoft Sandra Bandwidth: 3017MB/s
SiSoft Sandra Arithmetic: 9225 MIPS
SiSoft Sandra Multi-Media: 19,151 it/s
SuperPi: 44s
FSB BUS Frequency: 200
AGP BUS Frequency: 66
Clock Spred Spectrum:
LDT Downstream Width: AUTO
LDT Upstream Width: AUTO
LDT/FSB Frequency Ratio: AUTO
CPU/FSB Frequency Ratio: 10.0
CPU VID Control: 1.550V
CPU VID Special Control: AUTO
ChipSet Voltage Control: 1.6V
AGP Voltage Control: 1.5V
DRAM Voltage COntrol: 2.8V
DRAM Frequency Set (MHz): 200MHz 1:1
Command Per Clock (CPC): 1T
CAS Latency Control (TCL): 2
RAS# To CAS# Delay (TRCD): 2
Min RAS# Active Time (TRAS): 5
Row Precharge Time (TRP): 2
Row Cycle Time (TRC): AUTO
Row Refresh Cycle Time (TRFC): AUTO
Row To Row Delay (TRRD): AUTO
Write Recovery Time (TWR): AUTO
Write to Read Delay (TWTR): AUTO
Read To Write Delay (TWTR): AUTO
Refresh Period (TREF): AUTO
Write To CAS Latency (TWCL): 5
DQS Skew Control: AUTO
DQS Skew Value: AUTO
DRAM Drive Strength: AUTO
Max Async Latency: AUTO
Read Preamble Time: AUTO
Idle Cycle Limit: AUTO
Dynamic Counter: AUTO
R/W Queue Bypass: AUTO
Bypass Max: AUTO
32 Byte Granularity: DISABLED
Working on making a "manual" for bios settings, taking selected info from
http://www.adriansrojakpot.com/Speed...uide_Index.htm
(hope they dont mind)
1. Command per clock
Common Options : Enabled, Disabled, Auto
Quick Review
This BIOS feature allows you to select the delay between the assertion of the Chip Select signal till the time the memory controller starts sending commands to the memory bank. The lower the value, the sooner the memory controller can send commands out to the activated memory bank.
When this feature is enabled, the memory controller will only insert a command delay of only one clock cycle or 1T.
When this feature is enabled, the memory controller will insert a command delay of two clock cycles or 2T.
The Auto option allows the memory controller to use the memory module's SPD value for command delay.
If the SDRAM command delay is too long, it can reduce performance by unnecessarily preventing the memory controller from issuing the commands sooner.
However, if the SDRAM command delay is too short, the memory controller may not be able to translate the addresses in time and the "bad commands" that result will cause data loss and corruption.
It is recommended that you try enabling SDRAM 1T Command Control for better memory performance. But if you face stability issues, disable this BIOS feature.
2. CAS Latency Time
Common Options : 2, 3 (SDR memory) or 1.5, 2, 2.5, 3 (DDR memory)
Quick Review
This BIOS feature controls the delay (in clock cycles) between the assertion of the CAS signal and the availability of the data from the target memory cell. It also determines the number of clock cycles required for the completion of the first part of a burst transfer. In other words, the lower the CAS latency, the faster memory reads or writes can occur.
Please note that some memory modules may not be able to handle the lower latency and may lose data. Therefore, while it is recommended that you reduce the SDRAM CAS Latency Time to 2 or 2.5 clock cycles for better memory performance, you should increase it if your system becomes unstable.
Interestingly, increasing the CAS latency time will often allow the memory module to run at a higher clock speed. So, if you hit a snag while overclocking your SDRAM modules, try increasing the CAS latency time.
3. RAS-to-CAS Delay
Common Options : 2, 3, 4
Quick Review
This BIOS feature allows you to set the delay between the RAS and CAS signals. The appropriate delay for your memory module is reflected in its rated timings. In JEDEC specifications, it is the second number in the three or four number sequence.
Because this delay occurs whenever the row is refreshed or a new row is activated, reducing the delay improves performance. Therefore, it is recommended that you reduce the delay to 3 or 2 for better memory performance.
Please note that if you use a value that is too low for your memory module, this can cause the system to be unstable. If your system becomes unstable after you reduce the RAS-to-CAS delay, you should increase the delay or reset it to the rated delay.
Interestingly, increasing the RAS-to-CAS delay may allow the memory module to run at a higher clock speed. So, if you hit a snag while overclocking your SDRAM modules, you can try increasing the RAS-to-CAS delay.
4. Min RAS# active time
Common Options : 4, 5, 6, 7, 8, 9
Quick Review
Like DRAM Act to PreChrg CMD, this BIOS feature controls the memory bank's minimum row active time (tRAS). This constitutes the time when a row is activated until the time the same row can be deactivated.
If the tRAS period is too long, it can reduce performance by unnecessarily delaying the deactivation of active rows. Reducing the tRAS period allows the active row to be deactivated earlier.
However, if the tRAS period is too short, there may not be enough time to complete a burst transfer. This reduces performance and data may be lost or corrupted.
For optimal performance, use the lowest value you can. Usually, this should be CAS latency + tRCD + 2 clock cycles. For example, if you set the CAS latency to 2 clock cycles and the tRCD to 3 clock cycles, the optimum tRAS value would be 7 clock cycles.
But if you start getting memory errors or system crashes, increase the tRAS value one clock cycle at a time until your system becomes stable
5. Row precharge time
Common Options : 2, 3, 4
Quick Review
This BIOS feature sets the number of cycles required for the RAS to accumulate its charge before another row can be activated. If the tRP timing value is too long, it will reduce performance by delaying all row activations. Reducing the precharge time to 2 improves performance by allowing a new row to be activated earlier.
However, the short precharge time of 2 may be insufficient for some memory modules. In such cases, the active row may lose its contents before they can be returned to the memory bank and the row deactivated. This may cause data loss or corruption when the memory controller attempts to read from the active row or write to it.
Therefore, it is recommended that you reduce the SDRAM tRP timing value to 2 for better performance but increase it to 3 or 4 if you experience system stability issues after reducing the precharge time.
6. Row cycle time
Common Options : 7, 8, 9, 10, 11, 12, 13
Quick Review
This BIOS feature controls the memory module's Row Cycle Time or tRC. The row cycle time determines the minimum number of clock cycles a memory row takes to complete a full cycle, from row activation up to the precharging of the active row.
Formula-wise, the row cycle time (tRC) = minimum row active time (tRAS) + row precharge time (tRP). Therefore, it is important to find out what the tRAS and tRP parameters are before setting the row cycle time.
If the row cycle time is too long, it can reduce performance by unnecessarily delaying the activation of a new row after a completed cycle. Reducing the row cycle time allows a new cycle to begin earlier.
However, if the row cycle time is too short, a new cycle may be initiated before the active row is sufficiently precharged. When this happens, there may be data loss or corruption.
For optimal performance, use the lowest value you can, according to the tRC = tRAS + tRP formula. For example, if your memory module's tRAS is 7 clock cycles and its tRP is 4 clock cycles, then the row cycle time or tRC should be 11 clock cycles.
7.row refresh cyc time?
8. Row to Row delay
Common Options : 2 cycles, 3 cycles
Quick Review
This BIOS feature specifies the minimum amount of time between successive ACTIVATE commands to the same DDR device. The shorter the delay, the faster the next bank can be activated for read or write operations. However, because row activation requires a lot of current, using a short delay may cause excessive current surges.
For desktop PCs, a delay of 2 cycles is recommended as current surges aren't really important. The performance benefit of using the shorter 2 cycles delay is of far greater interest. The shorter delay means every back-to-back bank activation will take one clock cycle less to perform. This improves the DDR device's read and write performance.
Switch to 3 cycles only when there are stability problems with the 2 cycles setting.
9. Write Recovery Time
Common Options : 1 Cycle, 2 Cycles, 3 Cycles
Quick Review
This BIOS feature controls the Write Recovery Time (tWR) of the memory modules.
It specifies the amount of delay (in clock cycles) that must elapse after the completion of a valid write operation, before an active bank can be precharged. This delay is required to guarantee that data in the write buffers can be written to the memory cells before precharge occurs.
The shorter the delay, the earlier the bank can be precharged for another read/write operation. This improves performance but runs the risk of corrupting data written to the memory cells.
It is recommended that you select 2 Cycles if you are using DDR200 or DDR266 memory modules and 3 Cycles if you are using DDR333 or DDR 400 memory modules. You can try using a shorter delay for better memory performance but if you face stability issues, revert to the specified delay to correct the problem.
10. Write to Read Delay
Common Options : 1 Cycle, 2 Cycles
Quick Review
This BIOS feature controls the Write Data In to Read Command Delay (tWTR) memory timing. This constitutes the minimum number of clock cycles that must occur between the last valid write operation and the next read command to the same internal bank of the DDR device.
The 1 Cycle option naturally offers faster switching from writes to reads and consequently better read performance.
The 2 Cycles option reduces read performance but it will improve stability, especially at higher clock speeds. It may also allow the memory chips to run at a higher speed. In other words, increasing this delay may allow you to overclock the memory module higher than is normally possible.
It is recommended that you select the 1 Cycle option for better memory read performance if you are using DDR266 or DDR333 memory modules. You can also try using the 1 Cycle option with DDR400 memory modules. But if you face stability issues, revert to the default setting of 2 Cycles.
11. Read to Write Delay
Common Options : 1 Cycle, 2 Cycles
Quick Review
This BIOS feature controls the Write Data In to Read Command Delay (tWTR) memory timing. This constitutes the minimum number of clock cycles that must occur between the last valid write operation and the next read command to the same internal bank of the DDR device.
The 1 Cycle option naturally offers faster switching from writes to reads and consequently better read performance.
The 2 Cycles option reduces read performance but it will improve stability, especially at higher clock speeds. It may also allow the memory chips to run at a higher speed. In other words, increasing this delay may allow you to overclock the memory module higher than is normally possible.
It is recommended that you select the 1 Cycle option for better memory read performance if you are using DDR266 or DDR333 memory modules. You can also try using the 1 Cycle option with DDR400 memory modules. But if you face stability issues, revert to the default setting of 2 Cycles.
12. Refresh Period
Common Options : 7.8 µsec, 15.6 µsec, 31.2 µsec, 64 µsec, 128 µsec, Auto
Quick Review
This BIOS feature allows you to set the refresh interval of the memory chips. There are three different settings as well as an Auto option. If the Auto option is selected, the BIOS will query the memory modules' SPD chips and use the lowest setting found for maximum compatibility.
For better performance, you should consider increasing the Refresh Mode Select from the default values (15.6 µsec for 128Mbit or smaller memory chips and 7.8 µsec for 256Mbit or larger memory chips) up to 128 µsec. Please note that if you increase the Refresh Mode Select too much, the memory cells may lose their contents.
Therefore, you should start with small increases in the Refresh Mode Select and test your system after each hike before increasing it further. If you face stability problems upon increasing the refresh interval, reduce the refresh interval step by step until the system is stable.
Where did you find that?
Will try find info on all setting and finish it later.
And yes ugp i gonna see what max i can get stock setting 200x10 in a while =)
Oh sweet thanks man. Yeah I have given up for the time being...need a break from it.
Might be your -CO cpu that holds you back, but im still noob so its a guess.Quote:
Originally Posted by ugp
I have thought that was well too.
I can't seem to get any higher than 3020MB/s
But I am also testing this with 2 DIMMs
EDIT: I take that back I jsut got 3027MB/s.
FSB BUS Frequency: 200
AGP BUS Frequency: 66
Clock Spred Spectrum:
LDT Downstream Width: AUTO
LDT Upstream Width: AUTO
LDT/FSB Frequency Ratio: AUTO
CPU/FSB Frequency Ratio: 10.0
CPU VID Control: 1.550V
CPU VID Special Control: AUTO
ChipSet Voltage Control: 1.6V
AGP Voltage Control: 1.5V
DRAM Voltage COntrol: 2.8V
DRAM Frequency Set (MHz): 200MHz 1:1
Command Per Clock (CPC): 1T
CAS Latency Control (TCL): 2
RAS# To CAS# Delay (TRCD): 2
Min RAS# Active Time (TRAS): 5
Row Precharge Time (TRP): 2
Row Cycle Time (TRC): 12
Row Refresh Cycle Time (TRFC): 14
Row To Row Delay (TRRD): 2
Write Recovery Time (TWR): 3
Write to Read Delay (TWTR): 1
Read To Write Delay (TWTR): 1
Refresh Period (TREF): 200MHz 3.9us
Write To CAS Latency (TWCL): AUTO
DQS Skew Control: AUTO
DQS Skew Value: AUTO
DRAM Drive Strength: AUTO
Max Async Latency: 7
Read Preamble Time: 5
Idle Cycle Limit: 16
Dynamic Counter: ENABLED
R/W Queue Bypass: 8x
Bypass Max: 4x
32 Byte Granularity: AUTO
That is what I used...Alot of it was set to AUTO but I pulled up A64 Tweaker and got the settings it assigned.
And also it was a 43s SuperPi time.
Even at stock speeds I still scored 7144 on 3DMark03. Not bad if you ask me :D
I would like to understand OCZ Platinum Rev. 2's timings and FSB range, perhaps someone have tried and can comment.
Q1 : What is the lowest timings these DDR can do at FSB 233 & 250MHz 1:1 DC on i865PE/i875P? Does the chipset bootstrap (133/166/200MHz) play a part?
or
Q2 : Is it possible to attain 2-2-2 or 2-3-3 on i875P at 1:1 DC FSB 233/250MHz on chipset bootstrap 133/166MHz? I know it's a messy situation, I apologise... Any comments appreciated.
Thank you.
Regards,
pokipoki
I get 3144 in sandra at 200x10
ugp choose 166 instead of 200mhz at "Refresh Period (TREF): 200MHz 3.9us"
And you gain almost 100meg in sandra.
Poki dunno if someone here run them with intel.
Very nice post about settings ubermann
Will ask jess if i can use hes recommended settings for bios in that "guide"
I want to know the optimal settings for best performance/bandwidth that the EL Plat Rev 2 will handle.
Thanks for the reply. So, bootstrap does play a part even for AMD or is it just Sandra? I asked at OCZ forums about i875P performance a few days ago, maybe they missed it.Quote:
Originally Posted by Ubermann
Sorry, I'm not familliar with AMD platform, but is strap 166MHz officially supported? Could Sandra mislead results on an unsupported bootstrap?
Regards,
pokipoki
Poki i really dont know anything about intel.
Im new to overclocking and dont even know what bootstrap is.
Can you explain what it is ?
If you mean Refresh Period (TREF) then you can choose from 100 to 200mhz on this board with different value on each.
Im trying to learn A64 and this ram.
Google and logic is your friend =)
What is your max fsb with 2 sticks ?
I can do some benches at that fsb and mess with timings and bios to try find some optimal setting.
But not sure if that result would be same with 2 sticks.
Quote:
Originally Posted by ugp
Which 166? There are a few different ones to choose from..Quote:
Originally Posted by Ubermann
Try the 166 7.8us
I am having trouble finding my max overclock without any errors in MemTest-86 :( This is why this sucks so bad. I can hit 290 one 1 stick and 280 on another stick without errors in MemTest-86 but I get memory dump errors in windows before it even finishes loading to my desktop. I do not understand it at all.Quote:
Originally Posted by Ubermann
Alright I'll give it a shot after this DVD finishes burning...
Quote:
Originally Posted by Ubermann
You run XP SP1 ?
What chipset volt ?
I am running SP2 and I am using v1.6Quote:
Originally Posted by Ubermann
What is the best TRC & TRFC?
Use Chipset 1.8 (put a fan blowing on it, i never seen it go over 50c with 1.9v) and throw SP2 in the garbage.
I cant even boot win with my settings and SP2.
Thanks for the reply. Short question, on AMD - what's the highest FSB you can run on 2-2-2-5? and 2-x-x-x? Thanks againQuote:
Originally Posted by Ubermann
regards,
pokipoki
A cas on 2 wont bring it higher the 220fsb i think.
Never tried 2-3-3 and such, will do it now.
Raising chipset voltage did bugger all for me.
I could boot at 420HTT with just 1,6V on the chipset, 1,7 or higher didn't make any difference.
Uber,
Did you try all dimm slots individual?
For me slot 1 appeared to be worse than 2 and 3.
I have been able to do 220 @ 2-2-2-5 with 2DIMMsQuote:
Originally Posted by pokipoki
What does the Chipset voltage actually do?
Poki 250 "seems" stable, 255 gives errors in PI.
Check pic if you want some info that you can use.
Zeus i need 1.8 volt to go beyond 280 i think.
Win wont boot else.
And really high fsb and low chipset volt gimme the "drive array" if i remember correctly.
@Ubermann
Thank you for your efforts. I appreciate it.
Best Regards,
pokipoki
i use 1.6v with my board.. doesnt help to give it more.Quote:
Originally Posted by Ubermann
I just tested 250 @ 2.5-4-3-10 with an 8x muliplier. I have figured out that it is my CPU that is causing my system to be unstable. 250x8.0 gives me 2.0GHz and I survived MemTest-86 and SuperPi 32M and completed it in 39m 44s. First time I have ever ran that. Not sure if that is good or not. I am guessing it isn't. But atleast I got 250 stable now with 2 DIMMs. I shall try for alittle more.
Here is my 250FSB Screen.
Going to try for 2.5-3-3-10
I do run 1.8 volt on cpu to get it stable near 2.4 gig.
This cpu isnt good at all for overclocking.
Its seems to be good for high FSB only.
Whats max you got in 3Dmark01 with that ATI ? (unstable or whatever)
*Edit is it in the sig ?*
22,644 is the highest I have ever gotten.
I have gotten 7,311 on 3DMark03 @ 441/375. Those clocks are the same for 3DMark01SE. I can't even get 3DMark01SE to even run anymore. It fails to load.
Reinstall windows maybe =)
I do it ones every week lately i think.
Nah I just reinstalled it. I got 7,157 on 3DMark03 with only 2GHz:D
I dont think i can beat that with mine =(Quote:
Originally Posted by ugp
Your 9800 Pro can do alot man! What do you have it clocked at right now? I bet you can get 7k easy. You just need to tweak it alittle. My 9800 Pro I had will do 450+ on the GPU and I can't remember on the Memory. But what you should do to it is take an AMD Barton Heatsink and slap it on there. Use zip ties. It works. That is what my friend Jeff has going on with my old card and it works nicely.
I slapped one of the sensors from my case and my RAM runs 37C or so during normal usage. (ie. Web browsing and chatting). It that about right? Can you guys post what your temps are on yours?
EDIT...my RAM is @ 250FSB right now...
Tried all "Write cas latency"
Seems like Auto,1 and 5 works.
The rest gives blank screen.
But killing powersupply and tapping Insert key will take you back to bios instead of clear cmos.
Never thought about it before =)
Yeah my friend showed me that and it makes the board BOOT safe settings and then you can go into BIOS like normal and all your settings are still there. Because I have a lot of sh*t disabled and all. And it is a pain to go back and do it all over again each time.Quote:
Originally Posted by Ubermann
Only works on ps/2 keyboard it seems.
That I had noticed as well. I have the Cordless MX Duo set but I have both PS/2 plugged in instead of just the USB. Seems to work alittle better that way.Quote:
Originally Posted by Ubermann
OK, things are looking a bit better now as far as my setup goes. I installed a 90cm fan to blow on the DIMMS, and I re-flashed my bios with the 10/05 version. I went ahead and heatsinked/fanned any mosfet that was getting warm as well. So far I can get 243~245 stable with 2x512 modules running at 1:1 with my multiplier at 10. I can get 250, but it isn't completely stable. I am pretty sure if I play around with the RAM settings some more I can squeeze a little closer to 250 stable. I went ahead and flipped my XP-90 around as well so that the heat pipes face the DIMMS and get some of that RAM cooling goodness too. I know I changed a lot more than one variable here, but whatever it was has sure improved stability.
LOL! Damn you have done alot to it...what components are you using with your DFI? Please post I would like to know...
Sure, no problem:
AMD 64 3400+ CG
OCZ PC3200 Plat Rev2 1 gig (obviously :D ) cooled with 90mm fan
XP-90 w/90mm Panaflo
Vantec iceberq copper NB chipset cooler (using the smaller copper sinks on the other mosfets cooled by a 70mm fan)
550 Watt TTGI SS w/dual 80mm fans
120mm Panaflo intake fan
120mm Panaflo exhaust fan
80mm side intake fan
Got any pictures? And you should be able to get that RAM stable @ 250. Look at mine in my specs...tell me if you can tighten the timings any? Or is you can improve bandwidth with any of the other settings this board has to offer...
Are there any 1gig sticks of this ram ?
Not that I know of anyway...I am not sure if they are going to make any. I do know 1GB sticks do not overclock worth the sh*t! :p:Quote:
Originally Posted by Ubermann