Overclocking the FX-60 on ECS KN1SLI Extreme mobo?

[Ken FX-60]

I just got an FX-60 to go with my ECS KN1SLI Extreme mobo and I can't get the blasted thing past 2.87 Ghz without no system boot, crashes and I have to reset. Capper, I was told you reviewed and worked with both products and I was hoping you can offer some advice.

Mobo: ECS KN1SLI Extreme
CPU: AMD FX-60 (OC'ed to 2.87Ghz and hoping to hit 3.0!)
RAM: 2GB Corsair DDR400 XMS 3-3-3-8
GPU: (2) XFX 7900 GS in SLI (OC'ed to 500/723)
PSU: Ultra X-Connect 650w

[Jokerswild]

Welcome to the forum. Why don't you post your settings for memory and other bios settings so we know where you are at. Might be your memory holding you back.

[pc_guy]

What are the settings you use right now to overclock the FX60?
Have you lowered the memory multiplier a bit? HTT multiplier also?

Lowering the memory multiplier did wonders for me and eliminated random lock-ups when I tried OC'ing my Athlon3800+

oh, and...
Welcome the the HL forums!

[Capper]

The only issue with that motherboard, if I remember correctly was the complete lack of chipset voltage control, which could be holding you back.

I also know that a lot of people were unhappy with the FX-60s because after such promise with the review samples, many could not hit 2.9GHz regardless of the voltage. I was lucky enough to hit 2.94GHz on mine, but from what I've seen those processors are extremely hit or miss.

[gvblake22]

Yeah, make sure your memory isn't what is causing your instability. Just lower the CPU:RAM divider so your memory runs slower so you know it's not erroring out the system. Also, have you lowered the LDT multiplier to keep the HT Bus below 1000 MHz?

[Capper]

One last thing....make sure you have the latest BIOS for that board. I've really liked the ECS boards of the past two years because they are rock solid, and have a great bundle....but the lack of NB voltage makes them a poor choice for serious overclocking.
Alas, I think its a combo of the chipset voltage issue, and the FX-60 not being a great overclocker that is the problem.
As a last resort, you might try different approaches to the issue....maybe reducing the CPU multiplier, dropping the memory divider, etc.