AGP Frequency

So I set my FSB on my BX133 RAID to 133MHz
I set my AGP to 2/3 giving me almost 89MHz.
If I set my frequency to 1/1 what will happen?

Will it simply not work?
Will it cause instability?
Will it damage components?

Maybe I should start a poll.

<b>
"Now drop your weapons or I'll kill him with this deadly jelly baby." :wink:
</b>
28 answers Last reply
More about frequency
  1. Most likely it will not work at all with the AGP at 133 (1/1 with the 133 bus). If it does work, it will probably overheat. If your gutsy try it, if your not, don't. There is the possibility that you could permanently fry a component, possibly the Clock Generator of the card itself.

    Since it's not my money I say go ahead and try it and tell us what happens. I'm curious, not rich!

    Cast not thine pearls before the swine
  2. You'll most likely fry your video card, and possibly your AGP bus in the process.

    ------------------------------
    Apple? Macintosh? What are these strange words you speak?
  3. Shhhh! Don't discourage him! I want to find out what happens for sure!

    Cast not thine pearls before the swine
  4. lol
    Sorry
    [sarcasm]Just make sure that you set your FSB to ABOVE 133 if you're using a 1:1 ratio. Most motherboards are too comforatble at a setting of 133. Also, try using your PCI cards in the AGP slot and vice-versa. They usually can fool the computer into not knowing what's going on, and giving you more freedom. Don't worry if the cards don't seem to fit right. They will eventually, push harder![/sarcasm]

    ------------------------------
    Apple? Macintosh? What are these strange words you speak?
  5. Get Lost!

    My graphics card & mobo make up over 17% of my system costs.

    I'll let the experts "try it out".

    It was just that a guy I know with over twenty years experience said "Yeah, it'll work."

    I'm just starting to wonder if he is Crashman. You don't teach hardware classes in Aberdeen, Scotland do you Crash?

    <b>
    "Now drop your weapons or I'll kill him with this deadly jelly baby." :wink:
    </b>
  6. ...and you can get lost too!

    Sarcastic sod!

    Here is a true story.

    On my first ever college class (hardware Yeehah), the class was two people to each computer. My partner was the most interesting techie I have ever seen.

    Face all covered in scratches.
    Clothes reeking from lack of washing.
    Breath reeking of alcohol.
    Accent and demeanor hinting at "I come from the rough end of town"

    He was asked to put the memory board into the slot. The lecturer told us "you can only put DIMMs in one way, due to the slot cuts". My partner then..wait for it...laid the board flat down on top of the slots!!!!

    To this day I reckon the unemployment powers that be forced him to that class, and he did hid best to get out fast.

    <b>
    "Now drop your weapons or I'll kill him with this deadly jelly baby." :wink:
    </b>
  7. Check it out:
    I have seen that most cards will operate at 89MHz, but a few won't. Of those that do, most eventually get too hot and give errors or locks. The only ones I feel safe with at 89MHz are GeForce 2's and Radeons. And even at 89MHz, the Radeons get pretty warm-but still tolerable.
    A lot of companies call AGP2x "AGP 133MHz". But it's not really clocked at 133, it's just 66MHz +DDR. Which is probably why your professor was so misinformed.
    I know as a fact that many GeForce 2 cards can tolerate 100MHz. Tom even did that in his 150MHz project. But that's really pushing it. I frequently run 3D apps with the AGP bus at 100MHz with a generic GTS card, for testing purposes.
    But 133? That is much beyond 100 even. I don't think TOM would even try it. But you could always chance it. If I were to try it (I have a little more guts than Tom), I would probably think about using better cooling on the graphics chip (I do), and putting a small heatsink on the clock generator. I give it about a 40% chance of success, and about a 20% chance of frying something. The remaining 40% chance is that it won't work but won't hurt anything permanently. At any rate, I serioulsy doubt it would kill the motherboard.

    Cast not thine pearls before the swine
  8. Crashman:
    So if AGP 2X is 66MHz+DDR, what is AGP 3x and AGP 4x ?

    Camieabz:
    I knwo what you mean about those Jobcenter people! :-)

    Christopher

    Don't wait for tomorrow! Live for Today! :-)
  9. Athough I have never seen 3x, it would be tripple data rate, and 4x is quadruple data rate. They simply transfer 3 and 4 bits of data per clock.

    Cast not thine pearls before the swine
  10. So 66MHz bus @ AGP 4x = 266MHz
    And 89MHz bus @ AGP 2x = 178MHz

    But 133MHz @ AGP 2x = BOOM! CRACKLE FIZZ

    <b>
    "Now drop your weapons or I'll kill him with this deadly jelly baby." :wink:
    </b>
  11. Actually it's less confusing to refer to the transfer rate in bits, but you got the idea.

    Cast not thine pearls before the swine
  12. Why are you calling me a sadistic sod?

    ------------------------------
    Apple? Macintosh? What are these strange words you speak?
  13. okay (scuse me if I'm being dumb...I'm just trying to get my head around all these clock frequencies and bits er cycle...its what I do, try and understand techy stuff. Being a real time software engineer, I know a little about clock cycles for software apps)

    Reading elsewhere on these forumns, I got the impression that DDR meant that data was sent both on the Up part of the cycle AND the down part, thus doubling the data rate.

    So if AGP 4x is quadruple data rate, does this mean it sends 2 bits of data on each UP and DOWN cycle?

    Or is the way AGP works different from Memory?

    Great Learning forumn this!

    Thanks y'all!


    Topher Bear

    Don't wait for tomorrow! Live for Today! :-)
  14. I kind of woundered myself how they divided the cycle for QDR, but it obviosly works well if Intel uses it for their entire P4 line (400QDR bus).

    Cast not thine pearls before the swine
  15. Topher - I think you are missing the boat on AGP - it is a clock frequency multipier.
    However, it does raise a very intersting point, albeit picked up by crash, does QDR RAM send 2 up and down? hmmm.... wonder if leo leporte knows.

    :cool: <i><font color=blue>on company time....</i>
  16. Not sadistic...SARCASTIC.

    RE: your post on sarcasm.

    <b>
    "Now drop your weapons or I'll kill him with this deadly jelly baby." :wink:
    </b>
  17. How the hell did I get sadistic from sarcastic?
    I need to get more sleep.

    ------------------------------
    Apple? Macintosh? What are these strange words you speak?
  18. So let me try this one Crash.

    If I'm running my PIII 1GHz (133 x 7.5), and the multiplyers are locked, then when I up the FSB to say 140 I'd be running my AGP bus at 93.3 (2/3)

    Subsequent raising of the of the fsb will cause the AGP and the PCI to be upped?

    So if the PCI should be kept below say 40, I could run the fsb at 160 (in theory) and the AGP would be 106.6 (2/3)

    This is interesting, but I think I've either got it wrong, or I'm touching nothing!

    <b>
    "Now drop your weapons or I'll kill him with this deadly jelly baby." :wink:
    </b>
  19. At 140 your AGP runs 93, but your PCI only runs 35MHz. The BX does have a 1/4 PCI divider, but not a 1/2 AGP divider. Some motherboards let you choose your divider, but most do it automatically (1/2, 1/3, and 1/4 for PCI, 1/1 or 2/3 for AGP). The Geforce 2 can support up to 100MHz AGP port clock, acording to Tom in his 150MHz FSB project.

    Cast not thine pearls before the swine
  20. In the list on my manual it has a "user define" option, but doesn't state what options are available. What can I do there?

    Also, if I upped the FSB and the Core Voltage and reduced the I/O voltage, could this be a good way to get more CPU MHz safely, or does the reduction in I/O voltage nullify the MHz/performance gains?

    <b>
    "Now drop your weapons or I'll kill him with this deadly jelly baby." :wink:
    </b>
  21. I would go into BIOS and chesk to see what options are available.
    You should be able to get your system up to about 150FSB as long as your memroy can handle it. I would raise VIO to ~3.5v and core voltage to 1.80v to try it.

    Cast not thine pearls before the swine
  22. Just let me double check:

    Crucial CAS 2 RAM
    Radeon 64MB DDR retail

    At 150FSB these should be fine?

    <b>
    "Now drop your weapons or I'll kill him with this deadly jelly baby." :wink:
    </b>
  23. Maybe. You should try it at 2/2/2 5/7t. If it gets errors, try 3/2/2 or 7/9t or both. The memory will go 150MHz but not always at it's fastest settings. Raising VIO to ~3.5v may help you keep the fastest settings.

    Cast not thine pearls before the swine
  24. Now you've really confused me.

    Sorry but I don't know much about the 2/2/2 thing.

    Willing to learn though...

    <b>
    "Now drop your weapons or I'll kill him with this deadly jelly baby." :wink:
    </b>
  25. 2/2/2 are individual wait states used to specify Cas Latency. 2/2/2 is cas 2, 3/3/3 is Cas3. I believe 3/2/2 is Cas 2.5.

    Cast not thine pearls before the swine
  26. You wouldn't have a link for me to read up on this would you.

    2/2/2, 3/3/3, 3/2/2, 7/9t???, vio etc.

    It would be great to blether a while but it is 0105hrs here and my eyes are going together...LOL

    Got to be up in 5 hours, so I'd better not hang aroung too long.

    <b>
    "Now drop your weapons or I'll kill him with this deadly jelly baby." :wink:
    </b>
  27. You can look it up as easily as I. These are just general overclocking tips.

    Cast not thine pearls before the swine
  28. Allrighty then.
    Goodnight man.

    <b>
    "Now drop your weapons or I'll kill him with this deadly jelly baby." :wink:
    </b>
Ask a new question

Read More

Motherboards NAS / RAID Components Overclocking