Originally Posted by mdzcpa
Here guys....chew on this.
I was running into the same situation with my Ballsitix. They could prime 24 hours, pass SPI32, and loop memtest for 24 hours at 250 mhz but I would get intermittent freezing while gaming. This was with an FX 57 under phase.
Strangely enough, lowing the mhz on the RAM didn't really help. Whether I lowered the RAM at 1:1 (and upped the CPU multi) or used a divider it was a no go. The only way lowering the RAM mhz worked was to tighten the timings to 2-2-2-5 which only ran to about 210mhz. Anything at CAS 3 could not be run from 200 to 250 without random freeze (note the ballistix are rated at 3-4-4-8).
I tried ALL the BIOS settings...nothing worked. More voltage, less voltage, Vmem, Vcore, chipset voltage, HT bus...didn't matter.
Then, just for the hell of it, I raised my mhz. I lowered the mutliplier and upped the RAM to 280mhz 3-3-3-8 and lowered the voltage to 2.62v. BAM! Stable gaming. Been this way for 6 weeks now. Not a single freeze.
Now, I'm not saying this is the fix, but it has now worked on 2 of my rigs with DFI boards and 2 x 1G Ballistix kits (my gaming rig, and my mutlimedia rig that sees some gaming from time to time when friends visit). The situation reminds me a lot of my Gskill LE and FF that would not like to run at lower mhz (unless you changed to super tight timings (2-2-2-5).
What this tells me is that it is definitely a "tuning" issue. Something between the memory controller and RAM at various frequencies is causing the problem. I think with the right BIOS adjustments, this issue can be fixed. 3D gaming is still the most stressful on the CPU memory controller and RAM.....this is why we see it with 3D apps.