AGP/PCI clock tool

quakerjtf · Mar 2, 2005, 03:15 AM

I need something that can tell me the current frequency of the agp and pci. Clockgen says it's screwed up (200 and 100) and I just want to confirm it. These KT chipsets suck ass at bus locking.

**MIG-31** · Mar 2, 2005, 03:21 AM

Everest Home 2.00.281 tells you quite alot about you're system,drivers/bios that kind of stuff....it may help you out.

quakerjtf · Mar 2, 2005, 01:24 PM

wow, pretty nice program for system information. has a lot of stuff, but i couldn't find pci and agp bus.

INSTG8R · Mar 2, 2005, 01:40 PM

PCI Latency Cfg may give you the info ya want you can get it here
Hope that helps ya

mkk · Mar 2, 2005, 02:52 PM

Quote:

Originally Posted by quakerjtf

I need something that can tell me the current frequency of the agp and pci. Clockgen says it's screwed up (200 and 100) and I just want to confirm it. These KT chipsets suck ass at bus locking.

Clockgen can't be correct about that since the system would not be able to boot with the AGP/PCI at 200/100MHz. Check the motherboard BIOS settings for FSB clock and AGP/PCI divider. For instance when running the FSB at 200 or more the AGP/PCI divider should be at 3/6 in order to give the standard 66 and 33MHz operating frequencies. It might look differently depending on the motherboard brand. And since there are no higher dividers the AGP and PCI will be overclocked when raising the FSB above 200 on this type of motherboard. Just make sure the divider is correctly set and you've done all that can be done about it.

quakerjtf · Mar 2, 2005, 11:12 PM

In the PCI latency config tool, it gives the latencies in 32 and 64 mhz. Shouldn't they be 66 or 67 and 33? With this motherboard, I thought the agp

ci ratio was locked at 2:1 and by setting hte agp to 66 mhz, you were able to keep both there. Neither seem to stay in place when the htt is changed. I read some crap and the locking issues were supposed to be fixed this time. I've seen other people that have successfully oced to 2.4-2.6 ghz on this motherboard. I just don't see why the agp isn't locking to 66 mhz when I have it set that way it bios. I've found a couple locking problems on google, but most were in german.

mkk · Mar 3, 2005, 12:59 AM

I probably misunderstood what type of motherboard you meant by "KT chipsets", as there are so many. If it was an Athlon64 motherboard then yes it should most likely be locked but to be really sure you will want to check in the manual for easy reference. In either case it's impossible to initiate the AGP and PCI buses with 200 and 100MHz and get the system to boot. They're just too far off values.

The PCI latencies are something completely different and not related to the clock frequencies.

quakerjtf · Mar 3, 2005, 01:31 AM

Yeah I was looking around and finally noticed that. I'm not sure how, but I was able to slowly oc to 250 getting to 2.5 ghz 1.43V and run pcmark04 and 3dmark05 successfully. I thought that maybe the agp lock was working, so I changed the htt to 250 mhz in bios but it wouldn't boot. I tried ocing again, but windows froze or the agp was disabled over 233 htt. I read about some problems getting over 233 mhz. I'm heard both that this board uses an agp lock and a divider. I just hope I don't have to trash this and waste $150 on a dfi board.