Don't know.Quote:
Originally Posted by Rabbi_NZ
I was able to run 1 stick of PC4800 Gsill at 290, 2.5-3-3-7, 1T on the DFI.
But it might be, indeed.
Printable View
Don't know.Quote:
Originally Posted by Rabbi_NZ
I was able to run 1 stick of PC4800 Gsill at 290, 2.5-3-3-7, 1T on the DFI.
But it might be, indeed.
Mine are only pressed too, and it seems most of them had the black badge right from the start... even the picture on their site has always had the black badge.Quote:
Originally Posted by aCidbAbY
I'm wondering if the pressed ones were the beta sticks or something....
Quote:
Originally Posted by Rabbi_NZ
no i am saying that the best i could do @ 200 2-2-2-10 is 3.2
yeah thats what i was thinking about these too..
i got mine from the first batch thx to trans_am...
SOrry jus to clearify... your modules WONT do 200 2-2-2 without at least 3.2v right?Quote:
no i am saying that the best i could do @ 200 2-2-2-10 is 3.2
yes sir
Same problem here, 2-2-2-5 3.1V isnt memtest stable. I can 3D bench and pi tho.Quote:
Originally Posted by aCidbAbY
That's real strange... your modules are doing real well with 3.2v but anything below they jus wont play. Looks like the "2-3-3 @ 2.6v 2-2-2 @ 3.2v" rating was very well thought out after all... some of these modules NEED 3.2v to get going.Quote:
Originally Posted by aCidbAbY
Funny thing is mine did 220 2-2-2 @ 3.0v straight out the box... might test again soon to see how they go with 3.0v after the burnin.
Either way though, I dont see you putting less than 3.2v into those badboys so it's really not important :toast:
Mine need at least 3.2 just to get going as well.
I've just received my VX replacements today and so far the results looks very promising, better than the first pair. The new pair just did 2 hours of memtest Test #5 and one hour of 3D Mark Lobby test at 255Mhz 2-2-2-5 3.5v (multimeter). I think I can squeeze out a few more Mhz out of this babies. My first pair can only do about 245Mhz 2-2-2-10 3.5v.....
wow, very good news. Did your first ones die?
I can't wait to get my new setup so I can see what mine can do. This is killing me being stuck on NF2 with crap results.
I experienced about the same.
After I finished benching, went back to normal settings (222*11). Knowing that they need volts, set VDimm at 3.0 and started the system.
I then noticed that it took a long time for the system to boot, until it suddenly froze.
Rebooted and increased vdimm to 3.1. Same thing happened, system felt sluggish and slow.
Took the sticks out, and put my Corsairs BH5 back in and rebooted.
System booted as normal, and felt quick and responsive again. Weird.
As you said, perhaps they need 3.2V to start with.
After running the first pair with 3.5v for nearly two weeks 24/7 (Folding), I began to experience frequent reboots and the frequency of reboots increases over time. When I tested the rams individually, one of the sticks have thousands of memtest errors, even at stock settings. The other stick has no problems at all.Quote:
Originally Posted by cantankerous
Would you mind finding the max MemTest stable MHz @ 3.1v please Jupiler?Quote:
Originally Posted by Jupiler
With 2 sticks, I suppose?Quote:
Originally Posted by Rabbi_NZ
Will do, but can't post results until tomorrow evening.
Guys, as far as burning in your VX, the best way for you to do it, while charting to see if you are getting any gains, would be uwackme's BH-5 burnin.
http://www.dfi-street.com/forum/show...ackme+BH5+burn
Basically, you overvolt your RAM as high as you can, running it with 2-2-2 timings. You run the memory at a speed that is unstable, that causes errors in memtest86 test #5.
You run test #5 looped for ~6-12 hours, recording the number of errors that appear by the time the test period is over.
Then, you repeat the cycle for the exact same amount of time (~6-12 hours), at the same voltage, and unstable speed. You record the number of errors again.
After several cycles, you should see that the number of errors your memory causes starts to decrease (you record the number of errors, so you can chart, and see if your RAM is having any gains from the burnin process). Eventually, the errors may go away entirely.
Once you are getting <100 errors, boost the FSB up 1-2 MHz, and repeat the process.
This worked quite well for my BH-5, and gave me a good visualization of the gains that my memory was seeing, throughout the burn-in process. Worth a shot for you guys :)
Great thread by the way, an interesting read.
Cheers felinusz :toast:
I'll add uwackme's guide to the first post... I've actually read it a long time ago but forgot about it
ok, i think this is the best thread were to implement this Rabbi_NZ. :)
let's list our stick pcb aswell as oc results, to try to understand wich is the best pcb for UTT chips.
mine pcb is KO-6633 and btw i'm using TwinMOS DC kit (non SP) 50D with 0451 chips. (if i'm not mistaken)
PS: as OCZ VX has heatspreaders, it will be more dificult to do this for them. only some will be bold enought to take them off in order to see pcb rev... :p:
a copy-paste from my reply in the xtreme twinmos thread
tested my mem's today :)
# 1 : 261MHz
# 2 : 254MHz
# 3 : 240MHz
# 4 : 257MHz
# 5 : DOA
# 6 : 253MHz
3,65V, according to the multimeter
not too bad for out of the box, without burn in
pity one module is dead,
gonna rma that one with # 3...
next week burn-in :D
can I have module 1?
hehe
Rabbi, I already flashed to a newer bios, 1.51 but that didn't help either...
When I pop in my old trusted BH5 sticks the problems are gone.... looks like RMA time :(
I wanna test them elsewhere though, maybe it's my cpu messing about (memcontroller)
enok,
thanks enok I have added your info... if everyone else could do the same I will add all info we have here.
eventually I'll post requirements on the first post but I have little time now.
Jack,
thanks for that. how many loops of MEMTEST #5 did you do to get those figures?
Garrett,
try this...
clear CMOS, put UTT sticks in, go into BIOS and load optimised defaults, set timings to something like 2-2-2-10-12-15 and all the rest to how you usually have it, run memtest again.
you said sticks work individually but not together... are your BH5 2x256 or 2x512?
5 loopsQuote:
Originally Posted by Rabbi_NZ
i'll report back after i did a burn-in :)
i am trying this method right now and will let you guys know if this is better than what i was trying b4 (just putting them on a load at 240 3.3vdimm for 12-24 hrs)Quote:
Originally Posted by felinusz
check out my VX
3.4V 240~249MHz
3.6V 250~258MHz
3.7V 259~261MHz
3.8V 262~264MHz
3.9V 265~?
same timings 2-2-2-5 1T
I found if I add volt during memtet86 bench will be more stable, e.g 265MHz 4 errors in 20 loops #5, no errors and superPi&3Dmark stable after 0.1V added
I stopped at 265MHz since booster is burning at 3.9V, maybe I can gain few more MHz but I won't hit 4V at all I mean isn't it scary?
I've been running 255MHz for few weeks, just upped my FSB up to 265MHz yesterday and system runs fine expect the massive heat
Pictures are horrible which were taken by my cam phone
Add: For every 2~3Mhz increasement I ran 20 loops #5 and #5~10 loops #7 plus 5 loops std test. If error free then jump on superPi and 3Dmark and Sandra etc