Originally Posted by Dputiger
Just my .02 on this, take it for what you will:
I received a gig of Redline from Mushkin (for review) in late May. I didn't have the DFI board at that time, but I used the modules (at 2.7v) for well over a month. During that period, I tested them / ran them extensively on both the Gigabyte K8NXP-SLI and the ASUS A8N-SLI. They kept both systems absolutely stable under load and under heavy testing.
Last week my DFI NF4 board arrived. I fired up the FX-57 and ran another round of tests, again using Redline. After a week the modules were still completely stable, and still running perfectly at 2.7v.
I then flipped the 4v jumper, increased voltage to 3.3v (the maximum Mushkin recommends for the Redline 3500) and began testing the modules for latency and clockspeed. I hit 2-2-2-5 at 218, and 2.5 -3-3-6 at 250 MHz, still at 3.3v. Considering this was only PC3500 memory, I was quite happy with that.
I tested overclocking stability and headroom for about 3 days total. I then shut the system down for about two days.
Last night I turned the system back on to check a few things while working on the review, and discovered the RAM was no longer stable in Prime95. MemTest86+ confirms a damaged block on one DIMM at the 256.6 MB mark. The DIMM in question was in DIMM slot 3 (I was using DIMMs 1 & 3). I've run MemTest86+ on two separate systems--the memory in question is definitely damaged, and no BIOS flash on earth is going to cure it. The only way to stop the errors from appearing is to drop to around 133 MHz, at absurdedly high latencies.
Here's what I know:
Could it have been the memory? Yes. But the RAM was perfectly stable for over a month, even when stress-tested. Within four days of running on the DFI board, even though voltage never officially exceeded 3.3v, and the RAM was never swapped, it blew.
Given the multiplicity of issues reported with DFI's 4v setting, I can't say I see this as Mushkin's fault--at least not yet.