trtw = 1 is a no fly zone for me :p: i couldn't get into windows with that setQuote:
Originally Posted by esdee
Printable View
trtw = 1 is a no fly zone for me :p: i couldn't get into windows with that setQuote:
Originally Posted by esdee
Quote:
Originally Posted by Agent-JCDenton
it's propably the IMC, ive seen this several times,
let me guess, the unbuff under memtest was >3300MB/s?
Yeah, when trfc = 1 I get >3300 unbuffered in memtest. I couldn't boot into windows with that set even with my VX.
Here's 260 1.5-2-2-5 @ 3.45v not much difference from 2-2-2-5, Trrd has been changed to 1.
http://homepage.ntlworld.com/najmudd..._1.5-2-2-5.jpg
nice!
i think they are tweaked down as much as they can get (stupid IMCs)
now go bench :D
Jus tried some mushkin xp4000 redlines at the same speed and the sucked. they were only memtest stable at 2-2-2-5, with the rest of the settings left similar to the GH, and they were only stable at that speed with trfc at 3 (and you can guess how ugly the unbuffered bandwidth looked).
I'll continue tweaking the GH, its still got a lot of life in it.
I haven't tested FSB at 3.5-3.6v. Hopefully those voltages will allow for 265Mhz+.
But i'll work on that 2moro :D
Quote:
Originally Posted by Agent-JCDenton
remember that Mushkin Redline use UTT Ch5, thus trfc MUST be set to >14
i tried it at 15 and nothing, i'll give it another shot this weekend, the GH is keeping me entertained.Quote:
Originally Posted by esdee
250Mhz 1.5-2-2-0, trrd set to 0 as well. I still can't get trtw = 1 and boot into windows.
http://homepage.ntlworld.com/najmudd..._1.5-2-2-0.jpg
Nice... that's my experience as well. These GH are holding tighter timings, VERY tight timings in fact.... considerably tighter than other UTT out there!
C
Thanks Charlie,
The GH is certainly performing well even at "low" voltages, jus tested 1.5-2-2-0 at 3.2v and that was stable too. a quick question, does read preamble and idle cycle limit have a huge effect on the overall bandwidth? i'm only getting 7.2K in sandra at the moment...trying to bump that up.
Is this RAM gonna be AMD oriented as Mushkin REDLINE? becouse i saw only test with AMD?
I thought CH-5 has less pins.Quote:
Originally Posted by kakaroto
Hmmm... BRUTAL mem b/w for 9x multi and "only" 271mHz!!!
These G.Skill GH hold their timings REALLY tight!!! Nice stuff.
3.7Vdimm
DFI nF4 Ultra-D
BIOS 0510-2
Yellow Slots
http://www.xtremesystems.org/forums/...chmentid=30803
Nice clocks charlie.
Jus testing the mushkin redlines and i reckon i almost have them stable at 270Mhz...jus need a few more tweaks and i'll be happy. i've learnt a few more tricks to try on the G-Skill GH from using the mushkins. I've found a few more trefs that my winnie likes :D. will report back soon.
For some strange reason, after testing my Mushkin's and sticking my GH back in i can't get 260Mhz stable even at the settings i'd used before :rolleyes:
But i was able to get 1.5-2-0-0 a try and was able to boot into windows at 200 x 11. those timings were good until 210Mhz (very unstable, but could post and run memtest). 1.5-2-0-0 seems to show 100MB of more bandwidth than at 1.5-2-2-2. Tried 1.5-1-0-0 and 1.5-1-1-1 but no post.
http://homepage.ntlworld.com/najmudd..._1.5-2-0-0.jpg
Now to try and get 260Mhz stable again....
OMG this stuff OWNZ. amd shld never adopt to DDR2 cos it sucks.
If they have to i wonder if they'll offer CPUs in two flavours, DDR & DDR2, coz i still can't see any reason to go for DDR2 at the moment. I think they should skip the entire generation and go DDR3.Quote:
Originally Posted by NickS
I hate you guys get the better GH tan mine. :slapass:
Are all of these sticks guarunteed to run 250 @ 3.3 volts? I was trying to decide between these and some OCZ Bh-5, as I need some low latency goodness and am looking to do it with as little voltage as possible. Also, if I can hit 250 @ 3.3 then do I still need active cooling? Thanks.
deception``
Quote:
Originally Posted by deception``
most likely yes, they will do very tight timing on 250 3.3v :)
I have a dilema. I got a DC kit from another user and I can't seem to run mine at all. I've tried all kinds of vdimm voltage and even at stock 200 and everything at default. I tried tweaking up to 250 at looser timing 2.5-4-3-7 and still not able to get anything going. I've tried the 4V option and raised the vdimm all the way to 3.6V. Here's what I've tried so far. BIOS: 310, 414-3, 510-2 and Hellfire's mod 510-2. Voltage: 2.6V all the way thru 3.6V. Timing: 2-2-2-5 to 2.5-4-3-7. Got BSODs, PC keeps rebooting as soon as it start Windows. Memtest show a lot of errors.
What BIOS are you guys using? What board rev. are you using? Mine is: R.AB0. Could it be my board? Not having any luck whatsoever. Help!
Check your Dram Drive strength, Dram Data Drive Strength and Tref. For me, those are the big three. I can't pass test 2,3 & 5 when I use a "bad" tref, regardless of how much voltage. I've also noticed that when using the wrong tref, increasing the voltage on these sticks gives me more errors.Quote:
Originally Posted by jcniest5
With Dram Drive strength set to 5,6 & 7 I'm stable at 250 with 3.2v and i can set Data Drive Strength to 1,2 or 3. At 260 Mhz 3.5v only Drive Strength 5 with Data Drive Strength set to 2 or 3 will work. Dram Drive Strength set to 6 & 7 would also work but I need more voltage (3.6v) at that the same FSB to be stable.
Tref. I've played with all sorts of settings here and i've found one of the best ways to find your ideal settings for Tref and Drive Strength is find timings that give you just a few errors (around 10-20) at whatever frequency in test 5. Yes thats right, for once in you should be happy to see errors in memtest :D .
Now start playing with Dram Drive strength, Data Drive Strength and Tref - one at a time. I'd start with Dram Drive strength then Data Drive Strength and finally Tref. If you finally find a good combination of Data Drive Strength and Dram Drive Strength and you're able to get rid of the errors in memtest 5 with those settings, note them down (you might end up with several good combinations) and then change back to settings that would give you 10-20 errors again.
Now try and find the most stable tref, you might find several once again, note all of them down.
Once you can pass without errors increase the frequency again and work with only the trefs and Drive Strength combinations you found. You'll be able to narrow everything down to just a few settings.
My working settings:
Tref = 2560, 3120 and 3684
Dram Drive strength = 5 & 6 Depending on FSB, 5 is the most stable at higher FSB
Data Drive Strength = 2 & 3 at 255+ FSB with Dram Drive strength @ 5
With the GH i'm able to throw very tight timings at them and they'll be pretty happy, if i get Tref or Drive Strengths wrong I ran into all sorts of problems and no amount of voltage seems to help then.
Hope this helps.
Here's a screenie of 1.5-2-2-0 @ 260Mhz with AGGRESSIVE timings, I shed off 2 secs in SuperPi and everest read jumped from 7100 to 7400 from my previous 260Mhz settings. Now, if only i could get my winchester stable at 260 x 11 i'd b well happy :D i've topped out at @ 2750mhz (250 x 11) prime stable
http://homepage.ntlworld.com/najmudd...-3120-tref.jpg
^ an excellent post!
What do you think is the max voltage you can run the G.Skill 3200 GBGH at without using active cooling on the RAM and mosfets?
Agent, you somehow describe what I'm experiencing. I also noticed that increase voltage to the memory have more errors. So, I think my culprit may be what you are describing.
You didn't mention the BIOS you are using. Could you please tell me which one you are using? I'm back to 217, which is the only one that I can get a stable system at up to 220. One I up it 230 and up, Memtest for Windows starts to toss errors at me. I'm going to play with the settings you said and see if I can OC my system higher.
Also, no matter which BIOS I use, Memtest (built-in the BIOS) seems to give me the same address 0002a425ba0. Could this be a sign of a bad/defected memory? If I use only one stick, that particular error doesn't show up. But as soon as I put two in Dual channel, the error starts showing up again, even when doing it at stock (200 - no OCing at all).
Thanks for your help. You at least gave me a lead to start I've never had this hard time doing OCing. I'm basically pulling my hair now. Hope I'm not going bald soon.
Hello jcniest5,
If you are getting errors at the same address i'd try OCing one stick at a time and compare how high they go. I've got a "bad" stick, its the only one that gives me errors at 265+ in memtest test 5. However the most critical FSB to test is 200Mhz at 2-2-2-5, if that can't pass without errors speak to OPB, he's started a G-Skill Support forum here
But i'd try and identify if its one of the sticks thats holding you back.
I've updated my sig, i'm using 510-2, and using the yellow slots. I haven't had any bad things to say about the 510 bios, it seems to work best for me.