Amd64 3400+ and Ratio problems / confusion

[Samurai]

basicly , my cpu is clicking rather loudly .... when im in game , the click = lag ... my graphics card is capable of the high frame rates i see , but the lag is still presant , sudgesting cpu or memory problems . btw the processor is probably OEM that i recived in a stoor bough desktop pc, i built this ... my first machine using only the cpu from my old pc , everything else is new .

the old xp2700 i overclocked for my brother with some alright pc2700 ram and an excellent 9800 256bit/256meg card , its capable of running bf2 extreemly smooth with low-mid graphics and 4x AA .. it will quit outa harsh games like bf2 in seconds ... doesnt hang at all , like this system .

OH, and BTW thanks for all the help . idkfa

 

[Dippyskoodlez]

basicly , my cpu is clicking rather loudly .... when im in game , the click = lag ... my graphics card is capable of the high frame rates i see , but the lag is still presant , sudgesting cpu or memory problems . btw the processor is probably OEM that i recived in a stoor bough desktop pc, i built this ... my first machine using only the cpu from my old pc , everything else is new .

the old xp2700 i overclocked for my brother with some alright pc2700 ram and an excellent 9800 256bit/256meg card , its capable of running bf2 extreemly smooth with low-mid graphics and 4x AA .. it will quit outa harsh games like bf2 in seconds ... doesnt hang at all , like this system .

OH, and BTW thanks for all the help . idkfa

your memory is at 1:1... CPU's cant click. it has no moving parts.. if your hearing a click, its probably hard drive or a fan.. listen to your computer and find out what that is first.

your ram and CPU are running full speed and should not cause any slowdowns. look elsewhere for the problem.

 

[zAAm]

I can definitely say the socket 754 DOES NOT have an integrated memory controller. It is located in the chipset. That's also why chipsets are designed differently for socket 754 and socket 939. So for your and my systems, the memory controller is integrated into the northbridge chipset and NOT the CPU.

And your CPU is running the exact same way it should and your RAM runs correctly as well... It's just that I haven't seen many BIOS's that you actually adjust the CPU:RAM ratio. Because your CPU runs at 2400MHz, your RAM runs at 200MHz. And because the CPU uses a 12x multiplier (Athlon 3400+ uses 12, my Athlon 3000+ uses 10), your FSB runs at 200MHz as well. This is where you get the 1:1 ratio from... And the ratio wouldn't directly cause a problem like this, but the consequence of it might. If it is causing the RAM to run faster than it should (which according to your specs it doesn't), it may stall or freeze frequently.

Have you tried other RAM in your system? I don't think it is the timings since they are quite stable timings for PC3200.

Are you sure you have PC3200 (DDR400) memory?? PC2700 might give problems like you describe if overclocked to PC3200. (It may be that you received the wrong RAM??? Just check to rule that possibility out)

Try to swop the RAM with other PC3200 to check if the problem persists.

Check if you can get a hold of any other socket 754 to see if it causes the same problems. I don't know if you have a friend maybe that has a socket 754 Athlon64 to check with??

Also, the Athlon64 FSB is multiplied in much the same way as DDR RAM. The basic frequency is 200MHz as you know, but it is multiplied by 8 to give you 800MHz if you have a socket 754 or 10 to give 1000MHz if you have a socket 939 CPU. I don't know if that would clear something up, but thought it would be useful...

Hope this helps a bit at least.

 

[Dippyskoodlez]

I can definitely say the socket 754 DOES NOT have an integrated memory controller. It is located in the chipset. That's also why chipsets are designed differently for socket 754 and socket 939. So for your and my systems, the memory controller is integrated into the northbridge chipset and NOT the CPU.

And your CPU is running the exact same way it should and your RAM runs correctly as well... It's just that I haven't seen many BIOS's that you actually adjust the CPU:RAM ratio. Because your CPU runs at 2400MHz, your RAM runs at 200MHz. And because the CPU uses a 12x multiplier (Athlon 3400+ uses 12, my Athlon 3000+ uses 10), your FSB runs at 200MHz as well. This is where you get the 1:1 ratio from... And the ratio wouldn't directly cause a problem like this, but the consequence of it might. If it is causing the RAM to run faster than it should (which according to your specs it doesn't), it may stall or freeze frequently.

Have you tried other RAM in your system? I don't think it is the timings since they are quite stable timings for PC3200.

Are you sure you have PC3200 (DDR400) memory?? PC2700 might give problems like you describe if overclocked to PC3200. (It may be that you received the wrong RAM??? Just check to rule that possibility out)

Try to swop the RAM with other PC3200 to check if the problem persists.

Check if you can get a hold of any other socket 754 to see if it causes the same problems. I don't know if you have a friend maybe that has a socket 754 Athlon64 to check with??

Also, the Athlon64 FSB is multiplied in much the same way as DDR RAM. The basic frequency is 200MHz as you know, but it is multiplied by 8 to give you 800MHz if you have a socket 754 or 10 to give 1000MHz if you have a socket 939 CPU. I don't know if that would clear something up, but thought it would be useful...

Hope this helps a bit at least.

yes it is in the CPU.... trust me... it is.. thats why nf3 supports socket 754 and socket 939?

200mhz*8 = 1600mhz. HTT should be around a ghz. the HTT is 200*LDT of 5x for 1ghz. at 25-mhz you would use a mu8ltiple of 3x LDT.

 

[Samurai]

yeh i kinda figured these things out last night when i did the maths myself, the problem was i was just not accounting for the two diffent types of ratio that are talked about . cpu;dram , fsb;dram are abviously different ., i just didnt make that connection in meh brain .

as for the performance issues , i guess ill never know ...

as i have tried replacing every part in the machine , with the exeption of this processor thats been desgused, the clicking noise , "was" only when the machine loaded, did not come from a fan or hard drive and did not corrispond with the hdd access led ... and tbh sounded like it was commin from cpu , and would only occur when it came under heavy load .
as i only built the system yesterday , i assume it has just gotten used to things . isnt sounding to loud today ...

 

[zAAm]

yes it is in the CPU.... trust me... it is.. thats why nf3 supports socket 754 and socket 939?

200mhz*8 = 1600mhz. HTT should be around a ghz. the HTT is 200*LDT of 5x for 1ghz. at 25-mhz you would use a mu8ltiple of 3x LDT.

Oops sorry... I remembered it wrong. And I was too stubborn to realize it FCOL. The 185 pin difference is for the DUAL CHANNEL memory controller vs. the single channel in socket 754. My mistake. Also, I'm not too good at doing maths while I'm typing. And I've proven that in about 5 posts now...

btw, you can hear a PSU without fans so that kinda rules out the "CPU's can't click cause no rotating parts" theory. Hehe. But I don't think it's very healthy for a CPU to "click" though... And other than heat or a faulty CPU I can't think of anything else now. Sorry.

 

[Dippyskoodlez]

btw, you can hear a PSU without fans so that kinda rules out the "CPU's can't click cause no rotating parts" theory. Hehe. But I don't think it's very healthy for a CPU to "click" though... And other than heat or a faulty CPU I can't think of anything else now. Sorry.

CPU's cannot click.

no physical way. unless its dead.. but thats not the point

The reason you can hear a PSU is because the coils inside are capable of making noise my Abit AN7's vdimm coils were very loud.- if a CPU did the same it would probably explode.

generally not best to argue with someone thats going into EE

 

[zAAm]

CPU's cannot click ... generally not best to argue with someone thats going into EE

Okay, I give up. You know. I don't. You win. I lose. No click. I go.