I think I understand. by dropping the cpu multi down to 6x or 7x i'm underclocking the processor and then I raise the FSB to see what my max memory is. Should I leave my timings at stock? Also should i drop my LDT/HTT down to 3x?

I set the timings to 2.5-3-2-5 1T and dropped the vdimm back to 2.6 stock, got it up to 205 FSB . Tried 206 - booted, ran Super Pi and then when I went to open notepad BSOD and it rebooted.. I then tried upping the vdimm to 2.7v it failed to boot into Windows. Changed the memory timings to 2.5-3-3-5, failed to boot into Windows. Dropped the vdimm back down to 2.6v at memory timings of 2.5-3--3-5
failed to load Windows.

It appears upping the vdimm on any FSB past 2.7v causing the system to crash. I'm gone as high 2.9. I've even tried these vdimm settings on 210 FSB.

The gain from overclocking your memory for more bandwidth is a debatable affair. If you're trying to increase the memory bandwidth, then you are basically nearing the limit of your modules. The K8 architecture's integrated memory controller is much more sensitive to memory timings than transfer rates, so by your timings being as incredibly low as they already are, you've basically squeezed as much as you can as far as memory is concerned.

If you want maximum computing power from your processor, your memory must sacrifice the timings you are used to having them run. You need to ramp them up to 3-3-3-6 2T if you want a chance at breaking your overclocking barrier. Up-volt the DIMMs to 2.8v and leave them there; you are using Platinum EL DIMMs, which can take the overvoltage easily.

FYI: forcing a T1 command rate is somewhat useless when you are aiming at maximum processing power.

I tried that. I put the vdimm 2.8v, settings the memory timings to 3-3--6 2T set my cpu multi to 7x and my HTT to 3x and set my FSB to 206. It wouldn't even get to the XP splash screen. So I then dropped the vdimm to 2.7v got to the login screen and crashed. Then I set it to 2.6v and I was able to log into Windows but when I got half way through running Super PI it BSOD and rebooted. So then I set to the vdimm to 2.9 and it gave me a corrupted disk error. I'm starting to think, maybe the max of my RAM is only 205.

You need to ramp them up to 3-3-3-6 2T if you want a chance at breaking your overclocking barrier.

FYI: forcing a T1 command rate is somewhat useless when you are aiming at maximum processing power.

Okay are you telling him to run 2T on a 939? 2T sucks dog balls on ddr, pure and simple, correct me if I am wrong but isnt it like a 20mhz hit running 2T.
BALISTX: doesnt sound like your going to get much out of those sticks, figured they would have done @ least 210mhz.
NP so they top out @ 205mhz. Thank god a64 doesnt take big divider hits.

Have you found the limit of your cpu yet? Now that you know your not going to get much out of the ram it's time to raise the multi on your cpu and run the lowest memory divider. Start with stock volts on the cpu and start uping the fsb.

Keep your htt @ x3 for now

__________________

R.I.P.

Quote:

Originally Posted by 3.0charlie

My knuckles are bleeding from fishing through walls a new CAT6 network cable... I found fresh, untapped electrical outlets...