• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

A-DATA 533mhz OC's to 1066MHz with tight timings

I have had A-Data 2gb 533mhz ram for a year and the other day decided to go phsycho and overclock. What I found was the with the voltage at 1.95v, I got the ram to 1066MHZ stable with 3cas latency timing.
Is that a good OC.
 
I call BS till we get a verifiable CPU-Z screen shot. No offense but, 1066 at cas 3 at 1.95 is nearly impossible with premium ram, let alone cheapy ram. Heck, I'm running cas 3 on my ddr550
 
I call Shens. Even on my premium DDR2-1066 Can I barely get CAS4 without an insane amount of voltage.
 
without proof.... I'd say its BS... no offense, but OCers are like scientists... we need to rationalize things and we need proof....
 
Yeah, that claim is rather hard to believe.

My Corsair VS 667 does 1000MHz @ 5-5-5-15 with 2V, I was quite impressed. It actually does DDR2-1000 4-4-4-12 with 2.35V, but I'm not game to run at those volts 24/7. 😉
 
Someone has their dividers mixed up.... really? I say the system has an auto Failed OC option to reboot at safe timmings... CAS 3 @ 1000+MHZ?
 
Originally posted by: x2 3600 rules sazakky
I have had A-Data 2gb 533mhz ram for a year and the other day decided to go phsycho and overclock. What I found was the with the voltage at 1.95v, I got the ram to 1066MHZ stable with 3cas latency timing.
Is that a good OC.

[The thread should be in the Memory and Storage forum.]

I suspect you got your dividers mixed up there and you are actually testing DDR2-533 at 1.95V and realizing you can tighten to CAS3 when doing so. As other's requested, a CPU-Z screenshot will remove all doubt either way.
 
I say leave it here, the memory section moves to slowly to see what's really happening here (mixed dividers or the memory everyone's going to buy really, really soon 😛)
 
capture1zh3.jpg

 
Back
Top