Corsair XMS3200 Overclocking

Cheetah Designs

Cheetah Designs

Cheetah Designs

Associate
Joined
10 Jul 2006
Posts
2,423
Hi there,

I gut got a 2GB Corsair RAM kit. (XMS3202v2.1).

I have already overclocked my CPU and the FSB is at 289. (opteron 165)

Now i have heard that you get a performance fall if you are not running it 1:1. I am guessing that is not possible with this ram, so I was wondering what the best settings for the best perfromance were to try.

So if anyone has this RAM, could you tell me some settings to try?

Thanks.
 
Cheetah Designs said:
Hi there,

I gut got a 2GB Corsair RAM kit. (XMS3202v2.1).

I have already overclocked my CPU and the FSB is at 289. (opteron 165)

Now i have heard that you get a performance fall if you are not running it 1:1. I am guessing that is not possible with this ram, so I was wondering what the best settings for the best perfromance were to try.

So if anyone has this RAM, could you tell me some settings to try?

Thanks.
Click to expand...

Using a memory divider is fine on the A64 platform, the performance hit is minimal (nothing like on socket A). You'll never get your memory to 289Mhz, and CPU speed is everything, so stick with using a divider.
 
Cheetah Designs said:
Should i try and get as high FSB as possible, even if it means changing the timmings?
Click to expand...

Its a difficult question, usually the answer is yes, but its best to bench the alternatives with superpi 1mb and see which is faster. The performance difference is likely to be slight whatever your RAM settings are though, as S939 isn't very limited by memory bandwidth.
 
Cheers.

Ok, I will test with both.

It is possible to change the timmings in windows or do i need to do it via bios?

Thanks.

EDIT:

Also, what is the standard testing setting for Super PI that most people use?

I also have a Dual core so should i run two instances of it?
 
Last edited:
Just run a single SuperPi 1Mb test, which ever setting has the faster time is the best in all likely hood. Though you try the more intensive tests like 4 and 8Mb just to be on the safe side.

Download an app called A64 Tweaker to set RAM timings in Windows, great little took.
 
I am havign trouble telling which settings are which?

My ram is rated to run at 2-3-3-6. But what are they?

It doesn't explain this very well in the sticky, it just has terms but doesnt say which is which.
 
Corsair lets you put so much voltage through your memory before the warranty is void, but off the top of my head I can't remember. (They can't really tell unless you put stupid volts through it)

What speed is your memory running at? Those speeds are only guaranteed for 200Mhz (400Mhz).
 
I cant get it to boot windows at anything above 144FSB (Divider 1:2)

Thats with auto timmings or the timmings: 3-3-3-8

Have tried up to 2.9V so far.

But for some reason it seems to boot fine at 200FSB with everything auto.
 
Hehe, I think i'm right in saying that divider is the wrong way around, your 144FSB = 288 FSB? Try running 1:1 at 200 FSB :)
 
Well the divider is at half is what i meant.

So I was running 289FSB, but the ram was running at 144. Or am i totally off on the logistics of how it works?

I can get it to boot fine at 200FSB fine on what it thinks is stock which is 3-6-6-8 2.6V but not 2-3-3-6 2.8V

Motherboard is DFI NF4 Ultra-D
 
Last edited:
Hi there,

A development:

I have reset all my settings so that the ram is running 1:1 at 200FSB.

I have managed to get it to boot and clears memtest at 2-3-3-6 at ~2.8V.

Is it the fact that its on a divider that means it can't clock properly?

Thanks.
 
You were running the divider the wrong way around :p Whatever your FSB, your memory was double that 1:2 divider. Seems like your memory was working perfectly.

Keep it at 1:1, loosen your timings and slowly increase the FSB to see what speed you can get out of the modules :)
 
subxero said:
You were running the divider the wrong way around :p Whatever your FSB, your memory was double that 1:2 divider. Seems like your memory was working perfectly.

Keep it at 1:1, loosen your timings and slowly increase the FSB to see what speed you can get out of the modules :)
Click to expand...


I deffinatly wasnt. I can 110% vouch for that. The RAM was running at half the FSB, which when it was 289FSB it was 144FSB for the RAM. That i know for sure. So it must be something to do with the divider.

EDIT:

This is confirmed by CPU-z aswell.
 
Last edited:
When you're running on a divider slacken the ram timings max async latency and preamble time to 9 and 8 respectively, can help stabilise the memory a lot.
 
You must log in or register to reply here.
Back
Top Bottom