Fast & Flashy 2GB from Corsair ---> TWINX2048-4400PRO OCing report!!!

[Redbeard]

Here are some numbers you guys might be interested in.

I tested 20 sets of TWINX2048-4400PRO modules on three boards. DFI NF4 SLI-D (0329 BIOS), Asus A8N-SLI Premium (1009 BIOS), and the Asus A8N32-SLI Deluxe (1103 BIOS).

These modules had all passed our internal screening, and on all three boards, they were 100% stable in SuperPi @ 32M, CPU Burn-In, and would complete a full benchmark of PCMark2k5, Sandra, and Everest, not to mention Memtest at 275 MHz at 3-4-4-8 2T timings.

(Processor used was an Athlon64 X2 4200+)

I then tested them with 3DMark2001 as it has been the best estimate of 3D stability with this IC.

Here are the results

DFI NF4 Ultra-D: 17/20 passed
A8N-SLI Premium: 20/20 passed
A8N32-SLI DLX: 18/20 passed (2 failed were of the 3 that failed on DFI board)

As a result, we recognized that there was a problem and we've raised the screen a bit. After raising the screen (which cut down on our yields slightly), I tested another 20 modules in the same systems and got 20/20 to pass.

We are still selling this part at 2T at 275 MHz, but anything with a lot number starting with 0618 or later should get the newer parts.

If you have older parts that do not meet the spec, give us a call and we will RMA them for you and get you a set that does meet the spec.

Thanks to Deathspawner and some other guys from here that have helped us nail down this issue. I still feel confident that this is the highest frequency DDR1 memory around in 2GB kits.

[Deathspawner]

Thanks Redbeard for conducting all of that testing. My head would be spinning after swapping over twenty kits.

It's interesting to note that the A8N-SLi board ran -every- kit just fine.

I love these modules.. especially now that they can handle 275MHz with 3-3-2-0 timings. 1T timings is also a huge bonus, but can't be expected on every kit.. maybe -that- part is pure luck.

[Slammin]

Sucks that I didn't stick to my guns and ask Corsair to send me some good sticks.

<rant mode=ON>
Should one have to do this?
<rant mode=off>

272 on the ram. That's all I wanted.

Oh well, glad everything is all sorted now.

[PRJ]

Hi

I need some help with timings for these memmory on a DFI SLI-D mobo running on 0406BTA Bios with a 4800+ Toledo X2 @ 2 x 2.90 GHz CPU @ divider 180 = DDR526

What i do know is this, and if you would help me fill out the blancks for best timings possible...

DRAM Frequency (Mhz)= 180
Command per clock (CPC)= Enabled
CAS Latency control (TCL) =
RAS# TO CAS# delay (TRCD)=
MinRAS# active time (TRAS)=
Row precharge time (TRP)=
Row cycle time (TRC)=
Row refresh cycle time (TRFC)=
Row to row delay (TRRD)=
Write recovery time (TWR)=
Write to read delay (TWTR)=
Read to write delay (TRWT)=
Refresh period (TREF)=
Odd Divisor Correct=
DRAM bank enterleave=


DQS skew control=
DQS skew value=
DRAM drive strength=
DRAM data drive strength=
Max async latency=
DRAM responce time=
Read preamble time=
Idlecycle limit=
Dynamic counter=
R/W Queue bypass=
Bypass max=
32 byte granalarity=

[Deathspawner]

I need some help with timings for these memmory on a DFI SLI-D mobo running on 0406BTA Bios with a 4800+ Toledo X2 @ 2 x 2.90 GHz CPU @ divider 180 = DDR526

You can refer to Redbeard or my post that includes some settings. I would leave everything at default, except manually set your CAS-tRCD-tRP-tRAS. I would try throwing your DRAM Response to Fastest, and your DRAM Drive Strength to Normal 4 (Level 8). You can adjust your Data Drive a little bit too.. maybe Level 1 or 2.

[PRJ]

#105

Thanks for the tip I'll try this out

Im am currently running these settings...

DRAM Frequency (Mhz)= 180
Command per clock (CPC)= Enabled
CAS Latency control (TCL) = 3
RAS# TO CAS# delay (TRCD)= 3
MinRAS# active time (TRAS)= 8
Row precharge time (TRP)= 3
Row cycle time (TRC)= 10
Row refresh cycle time (TRFC)= 16
Row to row delay (TRRD)= 2
Write recovery time (TWR)= 2
Write to read delay (TWTR)= 1
Read to write delay (TRWT)= 3
Refresh period (TREF)= 3072
Odd Divisor Correct= Disabled
DRAM bank enterleave= Enabled

DQS skew control= Auto
DQS skew value= 0
DRAM drive strength= Normal 3
DRAM data drive strength= Level 2
Max async latency= 8ns
DRAM responce time= Normal
Read preamble time= 6ns
Idlecycle limit= 256
Dynamic counter= Disabled
R/W Queue bypass= 16x
Bypass max= 7x
32 byte granalarity= Disabled

See anything that i could tweak? ( TRP can't go down to 2 ) But anything else?

Thanks

PRJ

[Deathspawner]

See anything that i could tweak? ( TRP can't go down to 2 ) But anything else?

Change your tRCD to 2, you should have -no- problems there. Is there a reason you manually set your Async Latency? I usually leave that at Auto.

Also.. what speeds are you running on your mem? 275?

[PRJ]

Hi again

I'll reboot in a sec and try it out. I have set Async Latency manually sert because of timings found on other brands of memory with same IC's. I had some links, but these links are lost for now.

The memory are running 290 x 10 Divider 180 = DDR526

PRJ

[PRJ]

It could´nt boot with tRCD @ 2 even with Async Latency @ Auto.

Hmm... my previus pair, before RMA could TRP go down to 2

Greeting and goodnight

PRJ

[Deathspawner]

Lol, sorry. My head is o.O today.

tRP at 2 should be fully possible, so I do not know why you are having issues. Maybe an RMA is in order. tRCD at 3 is basically the limit on these modules. Sorry for the confusion.

Change your CPC to disabled and see if you are still having problems. These modules are clocked for 2T timings, and you are using 1T. Either way, these modules should be doing better than they so, so I recommend an RMA.

[PRJ]

I just ordered another RMA on these sticks, so I hope these new ones can clock a bit higher, or at least at lower timings.

Succesesfull DDR526 timings would still be nice...

PRJ

[Redbeard]

I just ordered another RMA on these sticks, so I hope these new ones can clock a bit higher, or at least at lower timings.

Succesesfull DDR526 timings would still be nice...

PRJ

Were these TWINX2048-4400PRO?

You don't happen to remember the lot code on them or anything do you? It should start with 05 or 06.

[PRJ]

Were these TWINX2048-4400PRO?

You don't happen to remember the lot code on them or anything do you? It should start with 05 or 06.

Yes, they are TWINX2048-4400PRO lot code 06142661

Waiting for the new set to arrive, hope for a better pair.

"Deathspawner" is refering to you, about timings on these sticks. What timings would you use @ DDR526?

PRJ

[Westley]

Here are some numbers you guys might be interested in.

I tested 20 sets of TWINX2048-4400PRO modules on three boards. DFI NF4 SLI-D (0329 BIOS), Asus A8N-SLI Premium (1009 BIOS), and the Asus A8N32-SLI Deluxe (1103 BIOS).

These modules had all passed our internal screening, and on all three boards, they were 100% stable in SuperPi @ 32M, CPU Burn-In, and would complete a full benchmark of PCMark2k5, Sandra, and Everest, not to mention Memtest at 275 MHz at 3-4-4-8 2T timings.

(Processor used was an Athlon64 X2 4200+)

I then tested them with 3DMark2001 as it has been the best estimate of 3D stability with this IC.

Here are the results

DFI NF4 Ultra-D: 17/20 passed
A8N-SLI Premium: 20/20 passed
A8N32-SLI DLX: 18/20 passed (2 failed were of the 3 that failed on DFI board)

As a result, we recognized that there was a problem and we've raised the screen a bit. After raising the screen (which cut down on our yields slightly), I tested another 20 modules in the same systems and got 20/20 to pass.

We are still selling this part at 2T at 275 MHz, but anything with a lot number starting with 0618 or later should get the newer parts.

If you have older parts that do not meet the spec, give us a call and we will RMA them for you and get you a set that does meet the spec.

Thanks to Deathspawner and some other guys from here that have helped us nail down this issue. I still feel confident that this is the highest frequency DDR1 memory around in 2GB kits.

does the 3500LL pro facing same problems?

[Deathspawner]

does the 3500LL pro facing same problems?

I am not Redbeard, but I can say that they don't. I had great success with the first revision 3500LL PRO, and have just used two seperate newer revisions that clocked -amazingly-.

284MHz 3-3-2-0 is game stable with the 3500LL PRO I've been using. You can check out my related thread here if you are interested.

[Redbeard]

Yes, they are TWINX2048-4400PRO lot code 06142661

Waiting for the new set to arrive, hope for a better pair.

"Deathspawner" is refering to you, about timings on these sticks. What timings would you use @ DDR526?

PRJ

I've not done benchmarks with tRAS, but the other benchmarks are 3-3-2-8 and seem to work fine at anything around 265-270. I know Deathspawner runs his at 3-3-2-0 but I honestly don't know if that would make any performance difference at all.

tRAS is one of those things that I haven't played with a whole lot, but the last time I did, it made very little difference on DDR1 modules.

If you can't get the modules to do 275 MHz hopefully the replacements will work for you.


And to the question about our 3500LLs, our 3500LLs are built with the same ICs that the 4400PRO is built with, so they will perform similarly. However, the 3500LLs usually have a lower top-end (because they are screened only at 2-3-2-6 and there is very little correlation between that and 3-3-2-8 at the high end) and the 4400PROs may not do 219 MHz at 2-3-2-6 because they are screened only at 3-4-4-8 internally.

[Westley]

I am not Redbeard, but I can say that they don't. I had great success with the first revision 3500LL PRO, and have just used two seperate newer revisions that clocked -amazingly-.

284MHz 3-3-2-0 is game stable with the 3500LL PRO I've been using. You can check out my related thread here if you are interested.

thanx for ur info, and thanx for redbeard too.

well, i hv mine doing 260, screen shot right here
i have never touch the highest, due to my proc limit.

[Deathspawner]

Very nice man! I am surprised your 146 can't hit 2.75GHz though.

[Westley]

Very nice man! I am surprised your 146 can't hit 2.75GHz though.

well, this is not my opty result.
now using a 0516 fpaw 3200+
the 146, is using on another machine

[PRJ]

I Got the memory back the day before yesterday, and booted fine. Then ran 275 / 1:1 / 3.0-4-4-8 / 2.80 and succesfully passed 3DMark03 : : So these do work at rated speeds and timings.:

Then i decide to play around with timings and used timings from this thread...

http://www.xtremesystems.org/forums/...&highlight=prj

Timings....

http://www.clockmehigh.com/ddr/Corsa...-3-3.0_32M.png

Tryed to run Sisoft Sandra where the system crashed and could'nt reboot. I Cleared mos and still could'nt boot. Then i tryed booting with my old memory and flashed bios just to be shure. This didn't help the "new" memory. They will not boot at all. I noticed that one of the sticks did'nt light up yellow at power on, and expeckt that it's default.

Whats gone wrong here, what do I do? RMA costs me arround 50 U.s. Dollars in shipping.

Greatings PRJ

[Deathspawner]

Try booting with one stick at a time. That way you will know for sure if it's a problem with one stick. That sucks you ran into a problem that quickly though..

[pcmoddingmy]

Guys, below is my test results with the 2GB 4400PRO kit:

Here's a screenshot of the pair doing 275MHz at CL3-4-4-8-1T with only 2.8V (rated spec). And yes, it was 3D stable! My test bench consists of an Opteron 144, DFI LP UT RDX200 CF-DR motherboard, GeForce 6800GS with a 600W SilverStone ST60F power supply. The memory batch code is 0613190-9 and it is a v1.1 kit.

Okay... here's the money shot:

Note: DRAM DS = 2 and DRAM DDS = 1 was selected in BIOS.

Despite the fact that a number of users having issues getting these modules to run DDR550 at 1T and 3D stable, we had no issues whatsoever running em' on my setup. In the screenshot, it was running Prime Blend stress for 3hours. I'll continuously stress them for another 21hours to complete the 24hour Prime stress

Previously, I had issues running these modules on the Abit AN8 SLI motherboard and looks like the RDX200 (or CFX3200) might be the right motherboard for the job.

Edit: Prime stress reaching almost 6 hours now...

[PRJ]

Try booting with one stick at a time. That way you will know for sure if it's a problem with one stick. That sucks you ran into a problem that quickly though..

Hi

I'll try booting with only one stick, it's just a shame

Never thought that timings could kill memory....?

PRJ

[Deathspawner]

Never thought that timings could kill memory....?

If a module is indeed dead, then it wouldn't be the timing that killed it. It would just be a huge coincidence. If your computer boots fine with other modules, then chances are one is dead, but at least if you can find the problematic one, you will know for sure.

[Westley]

juz now try 275mhz, well, my 3500ll pro manage to do it.
but, it will be too extreme, my proc need more than 1.6v