What am I missing when I try to overclock my CFX3200?

[wildside50]

CPU Opty 170 2.0ghz
Mobo DFI Lanparty CFX3200
RAM G.skill 2-gig

Okay, so I must be missing something when I try to overclock. I can get the system to boot and run at 2.3ghz, using x10 multiplier and 230 FSB, and the RAM divider to run the ram at 209. However, if I went higher than 230 FSB, no boot.

But what I don't understand is, if I set the FSB to 240, multiplier to 8.0, the DRAM divider to 166, and the LDT/FSB to 4.0, the CPU would be running at 1920mhz, the Ram at under 400, and the LDT is at 1920. So everything is running slower than stock. So why won't the system boot? What else do I need to turn down to get the FSB up? Is it making my PCI run too fast, or my SATA, or something? I'll worry about stable later, but it seems like I should be able to at least BOOT at those settings. What am I missing?

 

[lyssword]

Originally posted by: wildside50
CPU Opty 170 2.0ghz
Mobo DFI Lanparty CFX3200
RAM G.skill 2-gig

Okay, so I must be missing something when I try to overclock. I can get the system to boot and run at 2.3ghz, using x10 multiplier and 230 FSB, and the RAM divider to run the ram at 209. However, if I went higher than 230 FSB, no boot.

But what I don't understand is, if I set the FSB to 240, multiplier to 8.0, the DRAM divider to 166, and the LDT/FSB to 4.0, the CPU would be running at 1920mhz, the Ram at under 400, and the LDT is at 1920. So everything is running slower than stock. So why won't the system boot? What else do I need to turn down to get the FSB up? Is it making my PCI run too fast, or my SATA, or something? I'll worry about stable later, but it seems like I should be able to at least BOOT at those settings. What am I missing?

try lowering mem timings even more?

 

[wildside50]

But the memory is running at less than stock speeds. That shouldn't be necessary. Furthermore -- yeah I tried that. No dice. There has to be something else affected I'm not accounting for.

 

[wildside50]

Would running 1 stick of RAM vs 2 in dual channel make the system more or less stable while overclocking?

 

[Pyrokinetic]

Are your PCI and PCI-E clocks locked to stock levels or are they still tied to the FSB? If they are not locked, it will cause system instability. Your wall of 230 FSB is about where the PCI buses will start causing you problems if they are being overclocked, so that is my hunch of what is wrong.

 

[wildside50]

Originally posted by: Pyrokinetic
Are your PCI and PCI-E clocks locked to stock levels or are they still tied to the FSB? If they are not locked, it will cause system instability. Your wall of 230 FSB is about where the PCI buses will start causing you problems if they are being overclocked, so that is my hunch of what is wrong.

See, that's what I figured too -- the PCI bus. I found no way to adjust the PCI bus, however. At least not yet. I guess I'll have to do some more research.

 

[Blain]

Originally posted by: wildside50
What am I missing when I try to overclock my CFX3200?

A Core 2 Duo CPU/MB combo... that's what you're missing! :laugh:

 

[PliotronX]

Try the other RAM slots (remember to switch of the PSU if the light next to the slots is shining), setting all timings manually (particularly max async latency and read preamble, try 8 and 5.5 to start with). Drive strength to say 4 or 5, data drive strength to 3, idle cycle limit to 64, disable dynamic counter, etc.. You could try one stick at a time and/or CPC disabled, in mismatched slots to force dual channel coupling off just to see if it helps. You could leave northbridge voltage at default, mine doesn't need a bump until around 309 HTT. I wouldn't worry about VCore either, until around mid 2500's or above. NMOS/PMOS drive strength and HT impedance can remain at 5, try CPU HT drive strength at strong. Try tRC 9, tRFC 15, tRRD 2, tRWT 2 or 3, tWTR 2, tREF 1560.

 

[Pyrokinetic]

wildside50: I downloaded at looked at your motherboard manual from DFI, and I think you will find what you are looking for under the Genie BIOS settings (page 107).

Specifically, look at the "LDT/FSB Frequency Ratio" and/or the "CPU/FSB Frequency Ratio."

The manual only generally refers to the headings and doesn't get into specifics like it does with the "PCI Device Control" and the "LDT & PCI Bus Control"; both of which do not contain what you are looking for.

On my Nvidia board, I have BIOS options to lock both my PCIe (slots 1 & 2 -- for SLI) buses to 100Mhz; and my "SPP <-> MCP Ref Clock" to 200Mhz. (SPP & MCP refering to the North & South Bridge chips). Leaving the settings on "Auto" scales them with the FSB (properly known as the HTT -- AMD chips do not have a Front Side Bus due to the integrated memory controller -- but the term "FSB" hangs around.)

Thus I have to switch the settings from "Auto" to the respective 100Mhz and 200Mhz frequencies to allow the board to overclock properly.

Hope that helps.

 

[myocardia]

Originally posted by: wildside50
What else do I need to turn down to get the FSB up?

Your RAM speed. Are you trying to overclock your RAM, or your CPU? You can't do both at the same time. Use the 100 Mhz divider for the RAM, and worry about it later. If you'll keep the settings you have now, and change your CPU VID to 1.250v, and your CPU Special VID to 110%, you'll have no problems running @ 10x250, including being able to leave Cool n Quiet turned on.

 

[wildside50]

Originally posted by: Blain

Originally posted by: wildside50
What am I missing when I try to overclock my CFX3200?

A Core 2 Duo CPU/MB combo... that's what you're missing! :laugh:

No way!! AMD FOR LIFE!!!!

And yeah, I just ordered a Q6600.... leave me alone.

 

[wildside50]

Well, all of the above suggestions have helped. I right now am running a 250 FSB, the HT Link is at 1000, the CPU is at 2250 (9.0 multiplier for now, just seeing if I can get the FSB up or not), and memory at 225mhz, with really relaxed timings. I think it might have just been the auto timings the whole time. Just seemed to me, if I kept the RAM at 215ish or less using the divider, I should be able to run it at the rated timings. I guess we'll find out manually later.

Thanks to everyone for the help.