OCZ 3200 EL Plat Rev2 + CAS2.5 = No Go?

[MaxxxRacer]

Hey guys, I have some 3200 EL plat rev2 that decided to go wacky on me recently. For the past 7 months it has served me well giving great timmings and good clocks, but in the past few days it decided to loose its mind.

My Setup: the and is for when i switched out components during troubleshooting
DFI nF4 Ultra-D or MSI K8N Neo2
3000+ Venice or 3000+ Winnie
OCZ VX4000 or OCZ 3200 EL Plat
X700 and/or PCI video card
OCZ 520Watt

The Problem:
The memory ONLY wants to work at CAS 2. If i select any other setting than CAS2 it will not work in windows. If i try to boot up in anything but CAS2 it will just BSOD before its done loading into windows. Any other timming will work fine with the memory, just not the CAS latency. Whats even odder is that hte memory runs great at 275mhz with karakato timmings in memtest. Tested in memtest for appx 20minutes of test 5 with no issues and let it go through the full test once.


My Testing
To weed out any other factors I tested the memory in various setups. Here are the differnt setups I used

DFI mobo w/Venice CPU and X700
DFI mobo w/Winnie CPU and X700
MSI Mobo w/Venice CPU and PCI video
MSI mobo w/Winnie CPU and PCI Video

I also ran my VX memory in both of these setups at hte same settings as the TCCD 200mhz 2-3-3-7 and it worked fine at 2.85 volts. To make sure hte cpu and mobos would do 2.5CAS i tested all the above setups at cas 2.5 with the VX and it passed every time.

[brandinb]

wtf so you have some crazy tccd or something but i think its another problem

i would reflash your bios on your dfi maybe and see whats up.

got any friends with a computer you can try them in??

what about trying them one at a time??
________
Vaporizers

[stealth17]

sure its tccd?

[CRUSH-ER]

Burnt out IC's?

[stealth17]

rma time it sounds like...but just to see try running higher voltages like 3.4v and tight timing like 2-2-2-5 or so and see how high they will go for s and giggles! let us know!

[formyfaith]

I've had the same experience and found out how it happened at least for me. Had 2 sets of OCZ EL Platinum Rev.2 and both of them went strange as yours.

My ansawer is that if you play with high voltages(above 3.3~3.4) for some period of time, they start to loose their minds, and CL 2.5 or more(loosened) won't work anymore. Only works with CL2.

Remeber when there were Rev.2 TCCD sticks that liked high voltages? At that time I thought mine would like them, too, so started putting in like 3.3, 3.4, and 3.5v. When I played with 3.5v for like a few hours, it suddenly couldn't start taking CL2.5.

So I tested another pair of the OCZ EL Platinum Rev.2 pairs, and played with high voltages, and the same thing happens again.

I'm not sure what's the exact reason, but the above is what happened to me.

[Major]

Maxxx if you have been running them at 2.9v or higher you have wacked them. TCCD is very sensitive to voltages. I see people running at high Vdimm with them for short periods but long term it will damage them.

[MaxxxRacer]

Major 2.85 is the highest I have ever gone with them. I think i might have booted them up at 2.9 once or twice, but I never went over the warrantied voltage.

Its garunteed the memory. Like i said, tested with two cpus and two different motherboards. reread the first post and ull see that i mentioned that in detail.

LOL. Im sure its TCCD.

Here is something funny though. With my Neo2, i just tested the TCCD again. at 2-3-3-7 at 245mhz the darn stick is rock solid. I should note I was running single chanel with one stick of 512, but you have to admit 1T at 245mhz CAS2 is REALLY wierd and really freaky. I will post a SS when I can get it off that computer.

[Tony]

Major 2.85 is the highest I have ever gone with them. I think i might have booted them up at 2.9 once or twice, but I never went over the warrantied voltage.

Its garunteed the memory. Like i said, tested with two cpus and two different motherboards. reread the first post and ull see that i mentioned that in detail.

LOL. Im sure its TCCD.

Here is something funny though. With my Neo2, i just tested the TCCD again. at 2-3-3-7 at 245mhz the darn stick is rock solid. I should note I was running single chanel with one stick of 512, but you have to admit 1T at 245mhz CAS2 is REALLY wierd and really freaky. I will post a SS when I can get it off that computer.

How old are the modules, did they come from older stock at a store?

We did have an issue a long while ago with some modules not liking anything apart from cas2

[Archon]

I Have this exact issue with my Patriot XblK for a couple weeks, wont boot with cas 2.5 or cas3 in any FSB, even 200mhz. In cas 2 i can reach 250 mhz 2-3-3-5 3.1V prime 5 hrs Ok. Before i reach 280 mhz in cas 2.5.
¿why is this? i am worried that the memory finally dont work even in cas2.
Please help.

[formyfaith]

I Have this exact issue with my Patriot XblK for a couple weeks, wont boot with cas 2.5 or cas3 in any FSB, even 200mhz. In cas 2 i can reach 250 mhz 2-3-3-5 3.1V prime 5 hrs Ok. Before i reach 280 mhz in cas 2.5.
¿why is this? i am worried that the memory finally dont work even in cas2.
Please help.

It usually happens when you play with high voltages. Anyways, I'm pretty sure your sticks are damaged permanantly so should either look for an another one or see if you can RMA them.

[xs64]

My friend have same problem with Tccd week 49 , running fine with cas2 , but cas 2.5 and 3 is no go

[formyfaith]

My friend have same problem with Tccd week 49 , running fine with cas2 , but cas 2.5 and 3 is no go

Which week doesn't really matter.
TCCD are very sensitive stuff, and it happens when they are damaged.

[MaxxxRacer]

Tony, they were bought in december 2004, but they ran in my neo2 for months on end at cas2.5 with no issues. Also tested them in my NF7-S briefly and they ran great there too.

As to the voltage. As I have said, I NEVER pushed these dimms past 2.85~2.9. Most assuredly I know that TCCD does not like higher volts and hence I NEVER pushed them with higher volts. Even when there was that TCCD loves volts craze I never went above 2.85.

[xs64]

Which week doesn't really matter.
TCCD are very sensitive stuff, and it happens when they are damaged.

I dont know his Ram got damaged or not , but they run fine with cas 2.5 in MSI Neo2 , just have problem with in DFI NF4 Ultra

[Archon]

It usually happens when you play with high voltages. Anyways, I'm pretty sure your sticks are damaged permanantly so should either look for an another one or see if you can RMA them.

But, 3.1V isnt a very high voltage, the question is, if the memory is damaged why run fine in cas2?

[MaxxxRacer]

3.1 is way high for TCCD...

[Archon]

3.1 is way high for TCCD...

Maybe, but less voltage got errors in memtest..

[MaxxxRacer]

Ok, I was able to do 310 in memtest on one stick and 300 on the other.

here are two screenshots of the testing I did. its sad really as they are very good sticks.

[THunDA]

I had the same thing happen to a set of tcc5..

200htt 5-2-2-2 worked fine..

200htt 5-2-2-2.5 bsod'd..

They just didnt wana run cas2.5 @ ANY speed..

[twiggy]

My old Gskill LE's would BSOD with CAS 2.5 at anything under ~250 FSB but would run fine at 250+ CAS 2.5. They did 260 2-3-3 and 310 2.5-3-3. Weird I know but what can I say.

[Archon]

Ok, I was able to do 310 in memtest on one stick and 300 on the other.

here are two screenshots of the testing I did. its sad really as they are very good sticks.

How do you fix the cas 2.5 problem?

[Bamboo]

He was running at single channel, may be that was the fix.

[MaxxxRacer]

no that wasnt a fix. it would run dual cahnnel in memtest too.

I just wanted to test out each stick to make sure if it was both that were borked or just one. Its really a pitty too as these are some GREAT sticks as you can see from the memtest.


On a side note i got the system to boot with one stick at 300mhz 2.4-4-4-8 but it wasnt stable at all. rebooted at slower speed (280) and it just crashed instnatly.

[Bamboo]

Dual channel, DDR 600 at 2.5-4-4-8? sorry I thought that you were having problem with this RAM running other than CAS 2.0?

I will need to go back to your problem more closer then, sorry.