Printable View
System specs:
C2D E6400
ASUS P5B
2x512MB handpicked 8000ULs (92mm + 120mm + chilled air)
2MB PCI video :D
500W BlueStorm
Vcore = 1.35V
Vmem = 2.65V (Vmem mod)
sry for low results : running CPU under BOXed cooler :( and using old OS w/o tweaks :D
3-2-2:
500MHz - 4M stable
507MHz - validation (sry no link - validator reports "corrupt file") :slobber:
3-3-3:
537MHz - 4M stable
542MHz - validation
and now ... WR for CAS3 : 573.8MHz :woot:
:slobber:
extremely impressive, even if they're handpicked, very very nice :D
[ramble]
though to me, it's just another reason why memory WRs should be sorted by the primary 3 timings. let's say someone pulls off 550mhz at 3-3-3. to me, that is much "better" than 574mhz at 3-6-6, but won't be listed anywhere because the records are listed by cas latency only.
[/ramble]
TaPaKaH,
could you try max oc with 4-4-4-5 ?
620MHz - 4M stable :D eeeeeeasy
640MHz - suicide validation (quick run, not pushing it)
Vmem = 2.63V
Awesome runs ;)
hehe this was nice :D
but 2.63 is hard pushing for 24/7 right?
even with customized sinks on each memory ( not "single" heatsink ) and 92mm on it?
thanks for the test
Chipset volts?
Why do you use the strange 3:5 ratio divider for your CAS3 tests ?
Nice results. 2.63V is indeed a bit too much for 24/7 usage if you ask me.
But then again we dont have that much information about long-term usage.
I will give my sticks 2.4V max for 24/7 usage.
Thats already 0.2V more than the sticks are rated for and 0.6V over jedec specs.
Maybe 2.3V will do it as well.
Gah who knows, no risk, no fun :)
Impressive! :slobber:
especially that 3-2-2!
1.6V I think :)Quote:
Chipset volts?
cuz, my CPU doesn`t go 2.8GHz+ very much under BOXed cooler :( ... so I have had to use 3:5 and 1:2 dividers :)Quote:
Why do you use the strange 3:5 ratio divider for your CAS3 tests ?
24/7 I use 2.45V ... 2.63V was for benching :DQuote:
2.63V is indeed a bit too much for 24/7 usage if you ask me.
Tell me... what's the use of running your ram at eg 800 3-3-3 for 24/7?Quote:
Originally Posted by Fr3ak
Personally I can't feel any difference with 667MHz 3-3-3 or even 667MHz 4-4-4...
It's senseless to overvolt your ram 24/7. You're killing it, your max overclock will degrade over time.
:edit:
I just looked, currently mine is running at 533MHz 3-3-3-9 (1.8v).
If someone told me it's at 800MHz 3-2-2-1 I would have believed him, just can't feel the difference.
Altough, high numbers still look great :D
http://valid.x86-secret.com/show_oc.php?id=125192
http://valid.x86-secret.com/show_oc.php?id=125198
P5B dlx bugged with cas 3 .... look My gskill @ 2.4v :banana:
how do you get the bug to show up?Quote:
Originally Posted by Pt1t
I have this board, and about 5-6 sets of ram, and I tried most of it, on this board, and I have spent tons of time tweaking ram with this board, and I have never had a bug show up yet, in any form.
I know the Gigabyte DS3, is exceptionally prone to crazy latencies (800 mhz at cas 3-1-1-4 come to mind... which I do have screen shots of) however, I have not been able to stump this P5B deluxe at all to get it to show any bug or even a minor glitch...
http://valid.x86-secret.com/show_oc.php?id=125204
and WR cas 3 @ 2.45v ....
in 1:2 that would hit 600.
585 also ... http://valid.x86-secret.com/show_oc.php?id=125205
It's not a *bug* per se, but you can e.g. boot @ 600MHz 8-4-4-4.0 and use Memset to change it to 600MHz 8-3-4-3.0... CPU-Z picks it up and that "8-3-4-3.0" is as stable as what you booted at ;)Quote:
Originally Posted by Kunaak
I'm not gonna comment on above results, though... Athough, they seem a bit high. Besides, as ozzimark said, 3-6-6-8 should NOT be considered CAS3 WR. In my mind, and probably many others, CAS3 record is 3-3-3-5 one... :)
it does only this when p5b dlx boot @ spd , when cas 4 is set manualy , changed cas 4 by cas 3 to high gave freeze.Quote:
Originally Posted by bachus_anonym
and now ... WR for CAS3 : 585MHz :woot:Quote:
Originally Posted by TaPaKaH
Not fake but Not real :D
nah, I can do this all day long and on at least 0507, 0614 and 0706 BIOS :lol:Quote:
Originally Posted by Pt1t
This is just to ilustrate the problem and I'm not saying this is the case here! TaPaKaH's CAS3 results seem very high but they are not neccesairly bugged or faked.
http://www.clockmehigh.com/cooler/sc...6_8343_bug.png
... and a bit higher, and on a different ratio...
http://www.clockmehigh.com/cooler/sc...4_8343_bug.png
:(
my result is not bugged !!!
you can try P5B if you want - changing the timing by MemSet doesn`t affect CAS !!!Why ??? :confused:Quote:
Besides, as ozzimark said, 3-6-6-8 should NOT be considered CAS3 WR. In my mind, and probably many others, CAS3 record is 3-3-3-5 one...
TaPaKaH OWN3D by bug :DQuote:
Originally Posted by Pt1t
If you boot at cas 3 on this board then it should be real :) i.e. don't use memset
Quote:
Originally Posted by kiwi
but , how to proof it :rolleyes:
edit : a video :banana:
you can always run benches to prove it :DQuote:
Originally Posted by TaPaKaH
extraordinary results require extraordinary evidence was it? :p:
for the why? it's because from my own experience with micron chips on AM2, 3-3-3 and 3-6-6 and everything inbetween clock very very similarly. like within 10-15mhz close
tested i can boot with cas 4 @ 500mhz mem and set in windows with mem set on p5b non deluxe , notting in time changes for super pi ;)
2 fakes :D
One with an extraordinary spi result
The other with a memset bug :D
Next will be on gpu or maybe an hdd ?
Keep me in touch :D
Quote:
Originally Posted by blind_ripper
Yep, I noticed that a few days ago as well
Unfortunatly, this is a confirmed way to fake things... :(
so now the question is... can we really call any claim on a WR, a WR, if it's done on a 965 chipset?
cause I've known the DS3 and basically all gigabyte boards are prone to crazy stuff, and I can dismiss them without a second thought, after my experiences with the board.
but now to see even Asus isnt immune to this kinda bug, it makes me question all 965 chipset claims on WR's.
I've always been the most severe skeptic, which is why you will rarely see me in a WR post, being the first saying congrats. cause thats kinda what I do... be the skeptic...
I've seen some crazy claims at WR's with 975 boards too, but thats always when using the bad axe, so it's easy to dismiss them too... cause to me a WR, really doesnt mean anything, if it's just a high number, but slow as dirt.
would a 3DMark WR impress you, if it was done at 6 ghz conroe... but only 47,000 with a X1900?
but now seeing this weirdness with the cas 4 - 3 being easily manipulated... just makes me think, 965 boards just plain old should not be taken serious, if anyone wants to really claim a WR with one.
but thats just me...
heres my confimation that the bug exists, and is easy to do...:(
Corsair 5400 UL, I run straight from bios cas 4-3-2-8 everyday, at 510-520 depending on how much I feel like pushing the voltage that day on the CPU.
but always 2.41 volts regaurdless.
cas 3 from this ram, is not possible past 450, regaurdless of voltage, atleast, not from a cold boot.
so seeing cas 3 at over 500 mhz, in windows, is really just a joke really...
again, below, these are fakes.
just testing the bug, nothing more.
http://img234.imageshack.us/img234/5...tpi1an4.th.jpg
http://img181.imageshack.us/img181/2...tpi2uw6.th.jpg
validated, to show, validation means nothing on this kinda bug.
http://valid.x86-secret.com/show_oc?id=125236
Hehe, lemme show you how its done with CAS 3 on D9 fatties. :p
http://mysite.verizon.net/gautamb/memory-3101.JPG
http://valid.x86-secret.com/show_oc?id=102872
CPU-Z has a lot of holes that seem to be able to be exploited pretty easily with today's mobos. One things for certain, it can't be trusted as the end-all and be-all anymore.
this isn't a CPUZ issue, and CPUZ was never intended to be the one and only absolute form of OC verification.
frank is about the only programmer, besides the guy that made XS Super PI, to actually take any of my advice when it came to trying to make cheating harder.
CPUZ alone, is only 1 tool.
still as good today, as any other day.
this just shows theres more flaws to take advantage of, with the 965 chipsets, thats all.
Yes, I could have worded myself a bit better.
However, one issue I *think* is that CPU-Z seems to calculate the memory frequencies based on other parameters instead of reading it, such as Clockgen does. I'm sure it used to in the past with A64's, hence so much of the divider confusion, etc. Whether that algorithm has been changed or whether its even easily possible to be changed is beyond me. However, in the case of the Bad Axe, and the screenshot I showed above, it appeared to read the memory divider incorrectly, and then report an incorrect memory speed based on this.
Nothing against Franck or CPU-Z, just saying its always worth it to take any results with a grain of salt at first glance.
With 0609 i could boot at 500MHz@3-4-3 with only 2.45V, max at 504Mhz (SP1M), but if i set 505Mhz i coulnd't enter to windows, just i get a reboot. BUT, actually, i think that was a bugged *strange*cas, cuz if i set 500Mhz@3-4-4 the system hangs in bios, i mean, even there was no boot.Quote:
Originally Posted by bachus_anonym
Testing with 0507, 0614, 0701 or 0706 i can't repeat that. So, the "only way" is using Memset but as we know that new CAS is unreal, so, BS if you ask me :) .
so the moral of the story is that cas3 can only be trusted on AM2 setups :lol2:
hehehe :D
Quote:
Originally Posted by ozzimark
Don't call results a fake, if the guy doing this don't know about a "bug"..
But RAS# Precharge works for me with Memset, i bootet with 3 and set it to 2, and i got a boost in 1M.