Quote Originally Posted by Mr Roboto View Post
I can boot into Windows without issue at up to 500Mhz FSB. Anything beyond that takes a bit of work. I almost never use 8x multiplier for that reason. I checked ClockGen out a while back but it didn't show support support for 680i so I deleted it. I saw someone mention a beta version in a previous post in this thread but Google turned up nothing. Do you have the beta version of ClockGen you could upload somewhere?

I noticed with all these memory timings that most are better left alone unless you have a great understanding of them. There are a lot of variables. The advice I've seen posted on the web ranges from the ridiculous to hearsay and guesstimates. I think what it comes down to is researching, benching, trial and error.

I do have a few questions though. When using MemSet are there some values that if you run too low you actually risk physically damaging the RAM or is it just like CPU\GPU overclocking where you'll just BSOD and have to reboot? Mostly I'm talking about tRFC, I noticed that lowering it gets some of the best bandwidth increases. What about running at 1T command rate? I know you have to downclock considerably. Is there any value in adjusting RMS? I was always interested in it because the values are so different from the rest being measured in µs instead of cycles. Thanks.
Sorry, I don't have such a version, I always used Asus' own software, AI Suite. Maybe you can try SetFSB, but I don't know if your motherboard is supported. However, it's not about booting very high FSBs, but rather booting with a low FSB speed and then raising it in Windows. The chipset will set the strap according to the FSB set in BIOS, and once above 400MHz internal chipset latencies are very loose, and thus your performance will go down. If you can, test 395MHz and 405 MHz FSB speed and leave the rest of the configuration unchanged to see it for yourself.

When I tested 680i, the sub timings that showed bandwidth gains were tRFC and tRC, you just have to test how low you can run them on your memory. Of course it isn't guaranteed, but I never killed memory because of tight latencies, and I've never read about such a case. Most likely you will get a bluescreen instantly if the timings are too tight. If you want to run CR 1T you will need to run excessive volts on the chipset, I reached about 425MHz CL3 1T relatively stable but in my opinion performance is not optimal. For 680i it's better to go for highest possible CL4 frequency.

I can recommend the lecture of this thread by eva2000 if you haven't done so already. He is really the God of 680i tweaking.