G.Skill 2GBHZ 1GX2 DDR580 PI 32M Done

[QuikSilver]

Well I ordered a pair of these yesterday, hopefully I can get them pretty high without killing them

[Jupiler]

I got my pair in on friday, and couldn't wait to see how they'd perform, specially after reading André's and Major's results with them.
So off I went and started directly at 270Mhz, 3-4-4-8, with André Yang"s timings. Memtest ran fine without any errors.
Upped it to 275Mhz, same settings, still no problems. SuperPi 1M was ok, no error.
Then 280Mhz, same thing, no problems whatsoever.
I decided to bump it up to 285Mhz, and run some Prime95 "Blend" test, which use lots of ram.
Prime 95 ran fine for about 2 hours, no errors or so.

All in all, I'm very impressed with the performance of the sticks.
Never thought my sticks would manage this.

[D4nnyOcean]

probably not a compatiblity issue. over at dfi-street some ppl got quite a few doa sticks, might be where he got his info from.

Cool. Just ordered some. I'll post my results shortly after they arrive.

[FlyBoyGeo]

I recommend Dfi NF4 bios 702-1 or 704-1 for best overclock

G.S.T

I'm working on my sticks now. You tested them in your review thread with 510-1 BIOS, but you now recommend the 702-1 or 704-1 for the best overclock now?

Thanks

[thinkingbear]

How much "real world" performance am I lossing by keeping this ram and running 2T?

1T vs. 2T command rate thread for A64's

From the thread:

GuitarDaddy System: CPU - Winch@2548Mhz | Memory- 2-3-2-7 X @232Mhz

SuperPI 8m 1T- 6:03m
SuperPI 8m 2T- 6:09m
1T is 2.4% faster

Aguamark3 1T- 58156
Aguamark3 2T- 57985
1T is 0.3% faster

3dmark 03 1T- 6908
3dmark 03 2T- 6872
1T is 0.5% faster

HL2 1T- 97.5fps
HL2 2T- 95.5fps
1T is 2.2% faster

X2 the threat 1T- 87.4fps
X2 the threat 2T- 85.8fps
1T is 1.9% faster

Doom3 1T- 85.9fps
Doom3 2T- 84.3fps
1T is 1.9% faster

[GSKILL TECH]

I'm working on my sticks now. You tested them in your review thread with 510-1 BIOS, but you now recommend the 702-1 or 704-1 for the best overclock now?

Thanks

long time ago i think
i am now using 702-1 bios for testing, it gives a bit more mhz out

[FlyBoyGeo]

long time ago i think
i am now using 702-1 bios for testing, it gives a bit more mhz out

I am going to try out 702-1 thanks.

[Nettwerk]

Got my HZ set yesterday and this ram acted like a fool with the 623 bios (only would boot with the ram in a certain slot/unstable at stock speed). I flashed to 704-bta and it runs great now

http://img359.imageshack.us/img359/3...ll2gbhz9az.jpg

[Jaco]

mine are als doing very well , this is the easiest RAM I've worked with.


Didn't try higher yet ! But very happy so far.

[bachus_anonym]

mine are als doing very well , this is the easiest RAM I've worked with.
http://users.telenet.be/taye/pics/GS...8%202048MB.jpg

Didn't try higher yet ! But very happy so far.

That's quite nice, Jaco! I bet you could still find few extra MHz somwhere in there

[Jaco]

thanks, bachus.
I ran some benchies at 285Mhz , superPI 16M / 3D01 /3D03 /Aqua /renderbench ... but not (prime ) stable yet. Could be the MC maxed out , haven't figured it out completely. With these settings ,I have like 3760MB/s in Memtest that's maybe too much for the memorycontroller.

[NeezyDeezy]

I was running bios 623-3 on my dfi lanparty ultra-d, but I could only get about 253 mzh. As soon as I'd raise it to 254 I'd get errors in memtest.

So I heard about using 702-1 with this ram. After setting that up, I can now get exactly 256mzh max! I was really expecting more. My settings are 3-4-4-8 at 2.64v. Even ignoring the fact that some people are getting 280 or more, I am really disappointed to be getting errors at 257 because I bought this ram for its acclaimed OC.

[Jaco]

Neezydeezy ,
can you post an A64 tweaker screenshot.
Maybe an incorrect setting holding you back.

[ccokeman]

I have found that mine performs best at 2.7v. No real improvement above that.

[blazin-asian]

*sigh* this is so depressing. seeing everyone at 280+ and i cant even get 270 stable. ive tried all a64 settings posted by:

AndreYang
Jupiler
Nettwerk (what kind of cooling are you using?)
Jaco

this sucks. my current BIOS is:

DRAM FREQUENCY SET: 200 (1:1)
COMMAND PER CLOCK: ENABLE (1T)
CAS: 3
TRCD: 4
TRAS: 8
TRP: 4
TRC: 7
TRFC: 18
TRRD: 2
TER: 2
TWTR: 2
TRWT: 3
TREF: 3684
TWCL: 1
DRAM BANK INTERLEAVE: ENABLE

DQS SKEW CONTROL: AUTO
DQS SKEW VALUE: 0
DRAM DRIVE STRENGTH: 8
DARM DATE DRIVE STRENGTH: 3
MAX ASYNC LATENCY: 8 NS
DARM RESPONSE: NORMAL
READ PREAMBLE TIME: 5NS
IDLECYCLE LIMIT: 256
DYNAMIC COUNTER: ENABLE
R/W QUEUE BYPASS:16
BYPASS MAX: 7
32 BYTE GRANULARITY: DISABLE

and here a link to a64: here

any suggestions people? thanks.

EDIT: cant even pass memtest at 265

[AndreYang]

*sigh* this is so depressing. seeing everyone at 280+ and i cant even get 270 stable. ive tried all a64 settings posted by:

AndreYang
Jupiler
Nettwerk (what kind of cooling are you using?)
Jaco

this sucks. my current BIOS is:

DRAM FREQUENCY SET: 200 (1:1)
COMMAND PER CLOCK: ENABLE (1T)
CAS: 3
TRCD: 4
TRAS: 8
TRP: 4
TRC: 7
TRFC: 18
TRRD: 2
TER: 2
TWTR: 2
TRWT: 3
TREF: 3684
TWCL: 1
DRAM BANK INTERLEAVE: ENABLE

DQS SKEW CONTROL: AUTO
DQS SKEW VALUE: 0
DRAM DRIVE STRENGTH: 8
DARM DATE DRIVE STRENGTH: 3
MAX ASYNC LATENCY: 8 NS
DARM RESPONSE: NORMAL
READ PREAMBLE TIME: 5NS
IDLECYCLE LIMIT: 256
DYNAMIC COUNTER: ENABLE
R/W QUEUE BYPASS:16
BYPASS MAX: 7
32 BYTE GRANULARITY: DISABLE

and here a link to a64: here

any suggestions people? thanks.

EDIT: cant even pass memtest at 265

maybe your HZ is not good. I am MSU student, too. You can come to my home. I can help you test again.

[blazin-asian]

maybe your HZ is not good. I am MSU student, too. You can come to my home. I can help you test again.

im testing them individually to see how they fair. together they cannot pass 260 on memtest, but 1 has passed 260 and failed 270. trying 265 now.

EDIT: both stop at 262 MHz. im gonna RMA em and hopefully newegg will give me a better pair.

260 x 11 until tomorrow i guess.

[palehorse]

im testing them individually to see how they fair. together they cannot pass 260 on memtest, but 1 has passed 260 and failed 270. trying 265 now.

EDIT: both stop at 262 MHz. im gonna RMA em and hopefully newegg will give me a better pair.

260 x 11 until tomorrow i guess.

what excuse are you going to give them? they'll probably test them and send the same pair back since they do 250, as advertised.

It's worth a try, but i suggest you place a tiny mark with a sharpie on each stick just to see if they send the same ones back! lol...

[GSKILL TECH]

im testing them individually to see how they fair. together they cannot pass 260 on memtest, but 1 has passed 260 and failed 270. trying 265 now.

EDIT: both stop at 262 MHz. im gonna RMA em and hopefully newegg will give me a better pair.

260 x 11 until tomorrow i guess.

well this is not a really good idea to do....

[-.-PhanTom-.-]

Hmmmm, it would seem that these sticks generally perform better in DFI Ultra/SLI than in the DFI Expert?
Which CPU's are you guys using in your Ultra/SLI mobos? .... my bet says NOT Dualcore Opteron....
Seems DFI Expert+dualcore Opteron is a bad mix for these sticks?
Hoping that a BIOS update or custom made BIOS can fix this "issue" with this hardware combination....
Just wonder if it is Expert+RAM alone, or if the funky memory controller of the dualcore Opterons (well atleast the 170s) also plays a part....

[blazin-asian]

what excuse are you going to give them? they'll probably test them and send the same pair back since they do 250, as advertised.

It's worth a try, but i suggest you place a tiny mark with a sharpie on each stick just to see if they send the same ones back! lol...

i have the serial #'s written on a sticky sitting on my desktop. newegg doesnt do testing on site and they will most likely just give me new ones. as long as they can higher then 262 then i guess its ok. hoping for 270+ though.

*crosses fingers*

[Onepagebook]

oh ya, from newegg handpick or the way you teach me how to

[s7e9h3n]

i have the serial #'s written on a sticky sitting on my desktop. newegg doesnt do testing on site and they will most likely just give me new ones. as long as they can higher then 262 then i guess its ok. hoping for 270+ though.

*crosses fingers*

Ummm....that's not very ethical....

[bachus_anonym]

EDIT: both stop at 262 MHz. im gonna RMA em and hopefully newegg will give me a better pair.

i have the serial #'s written on a sticky sitting on my desktop. newegg doesnt do testing on site and they will most likely just give me new ones. as long as they can higher then 262 then i guess its ok. hoping for 270+ though.
*crosses fingers*

This is the 1st and last time I'm saying that to you... What you're trying to acomplish is not gonna gain you any friends here and may very likely lead to your short career on XS. You RMA stuff if it's defective!!! Do you understand that? If you don't like your HZ, sell it and get another pair or different RAM, please. Think about it before you start another sentence about your "RMA idea" This is against XS Forum Rules and I would appreciate it If you familiarized yourself with those now...

[blazin-asian]

This is the 1st and last time I'm saying that to you... What you're trying to acomplish is not gonna gain you any friends here and may very likely lead to your short career on XS. You RMA stuff if it's defective!!! Do you understand that? If you don't like your HZ, sell it and get another pair or different RAM, please. Think about it before you start another sentence about your "RMA idea" This is against XS Forum Rules and I would appreciate it If you familiarized yourself with those now...

sorry. i didnt think this would be such a touchy topic so i'll end it. as for only RMAing stuff that is defective, thats not true. ive returned my Corsairs just because i was unsatisfied by them. talked to newegg rep and told them they didnt do what i needed them to do and they took it back even though i had them for over a month.

there are several people helping me on XS and i really appreciate it, but ive had some people tell me that my HZ were "bad". THATS why i decided to do this. didnt mean to stir up any trouble so once again, i apologize.