Hokay. WHen my previous motherboard exploded; I got a horde of new bits, among them was COrsair XMS3 Classic 1.5V ram (1600mhz,) (Scan page here.) Now it runs flawlessly at 1333mhz, as you'd expect, but it's unstable at the rated 1600mhz, even if I up the Voltage through it to 1.65. Every trick I try fails, I've raised timings to give it more room to breathe, I've increased voltages; nothing works. So the question is this: Is it worth trying to RMA it? Even though I've technically voided the warranty, or should I just suck it up and buy some new ram at some point? Or is there something I've missed that would let these modules run at the rated speed?
Does upping the RAM speed to 1600 cause the BIOS to automatically overclock the CPU? Are they linked? I had this issue with an MSI P55-GD65 board that overclocked the CPU as soon as I turned on the XMP profile. I had to manually mess around with the BIOS settings to sort it out.
I have to manually take the Ram multiplier up to 8X, because the motherboard will default to 6.66 (1333mhz) but other than that; No. As far as the CPU goes: I've tried everything from 4.3Ghz all the way down to the 3.2 stock and the results still come back to Ram Stability in the cases where it's actually been stable long enough for me to test the Ram. Most of the time it's okay, but it seems that any games, or Prime95 tests (Haven't run Memtest yet, but I've already narrowed it down to the memory) fail at the Memory stage. Sometimes with the wonderfully dramatic Blue Screen.
Memtest is where I would go next. Try it with the RAM set to 1333 and 1600. Leave it for a few hours on each test. It could be a faulty stick.
I'll probably leave it to run overnight then, I'll try it at 1600 first, just to see if my suspicions are correct. Very little's likely to occur till then. It's stable at 1333 atm, so I shalln't fiddle with it till tonight.
Good call, try setting all timings manually as well, including setting it to 2T rather than 1T. Sent from my HTC Desire S using Tapatalk
So far as I can remember; It's actually running at 2T already. I do remember going through and setting all the timing to the fastest the memory supported this time around, just to see if that would get me anywhere.
I'm curious to see the out come on this one as I've had the same probs with mine. It was fine before in my intel rig, so some thing makes me think it's a strictly AMD thing. I can get it to urn at 1499Mhz any further and it doesn't like it. Or it might be a gigabyte thing I had probs getting my Gskill to run on my UD3, thats why I sold it and bought the XMS3. If I manage to work out what it is causing it I'll let you know.
Cheers, Jeff. Similarly: If I manage to figure out the problem: I'll be happy to tell you, and anyone else who needs an answer.
