My issue is, I'm on my 3rd RMA of Ballistix 4GB(2x2gb) kit. I got the first around May 2008, and have had to RMA in August 08', Then again in Dec 08', and now again here in April 09'. I'm not overclocking these things at all and I'm running them exactly at the spec voltage the crucial tech people recommend. In fact in several cases I was running them at 667 mhz, even though they are speced at 800 mhz. The system runs pretty cool, and I don't really need to up voltage on anything.
The RAM works fine out of the box, and then it runs for 2-4 months and I'll start noticing program crashes and the occasional BSOD. I'll Run Prime95 then, and it will crap out in less then 2 minutes on all 4 cores. It will typically run fine on Small FFTs for hours, which definitely points to RAM, and of course then I run Memtest86 and it confirms RAM failure.
*Note: when I first put the RAM in I make sure they run for at least 48 hours under Prime98 to ensure its "Prime Stable" before being satisfied, and passes fine initially.
I'm not sure whats going on, but the cost of shipping the junk back and RMAing it is getting upsetting. Also since it originally cost $112, that's what they charge my CC for a cross ship even though that model is currently worth less then $50 (for 2x2gb).
I don't know why its failing, but after a Year it kind of seems like they aren't fixing the problem. If it was a compatibility issue, I'd expect the RAM to not really work in the first place, not fail after 3 months.
So my question is, have other people been having this difficulty for the past year (or recently)? Has anyone found a solution such as changing a Setting, or switching to a different model of Crucial RAM, when working with tech support?
MB= Asus P5E-MG613 (BIOS revision 0607)
RAM = Crucial Ballistix 4GB (2x2GB) in the 2 slots recommended by MB manufacturer.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.