Announcement

Collapse
No announcement yet.

PC Upgrading Questions

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #76
    1. It is an Athlon 1700+ and the 1500+ recognition screws Windows up.


    IIRC there was a windows patch for this, anyway it SHOULD only be the labeling that is wrong.

    nice double post alva... 22 minutes apart


    Terrible DP, I know. I was gone for a bit then clicked 'sent' again.

    Is God willing to prevent evil, but not able? Then he is not omnipotent. Is he able, but not willing? Then he is malevolent. Is he both able and willing? Then whence cometh evil? Is he neither able nor willing?
    Then why call him God? - Epicurus

    Comment


    • #77
      That said... the inability to run at 133Mhz may be due to the mobo's controller. Is it actively or passively cooled?
      I have no idea... is that the processor fan? I have a huge processor fan which keeps my processor around 50-55 degrees Celsius. I have two case fans. Does this answer the question? I'm not sure what you mean by mobo(I assume motherboard) controller.

      alva... is there a downloadable version of this patch? I have had problems with Microsoft's auto-update site.
      To us, it is the BEAST.

      Comment


      • #78
        well, the FSB settings are unstable, so I have to stick with 100...

        I'm back to square one, and my desktop is dark again.

        Anyone have any idea why I can't have my FSB at 133?

        I'm open to suggestions.

        btw, my motherboard is a K7T266 Pro2A... if that helps...
        To us, it is the BEAST.

        Comment


        • #79
          c'mon, doesn't anyone know? UR?
          To us, it is the BEAST.

          Comment


          • #80
            Originally posted by Sava
            I have no idea... is that the processor fan? I have a huge processor fan which keeps my processor around 50-55 degrees Celsius. I have two case fans. Does this answer the question? I'm not sure what you mean by mobo(I assume motherboard) controller.

            alva... is there a downloadable version of this patch? I have had problems with Microsoft's auto-update site.
            Nope...

            Here is a picture of the mobo... I can't remember if its called the North or South Bridge off the top of my head... but the chip circled in green, IIRC, is the one that controls the memory transfers.

            Sometimes the (lack of) cooling on this chip can give you problems with memory and/or general bus traffic.

            Often passive cooling is enough... but sometimes not.
            Attached Files

            Comment


            • #81
              there's a heatsink (is it sync? or sinc?) on mine... is that good 'nuff?
              To us, it is the BEAST.

              Comment


              • #82
                I really doubt that being it. Would be wierd if they sold a mobo that didn't have enough cooling on stock speeds, he is not overclocking, just trying to get what's his. I would think that cooling the board will come in play when overclocking more than just little, some mobos simply don't need a fan anywhere else than on the cpu. My old one didn't have any.
                "Set certain defaults" settings are bad because they change so many settings at once it's hard to know which one of them caused the system not to work.

                So your comp crashes at 133? Hmm.. Is the fan for 1700xp's or above, if so then it shouldn't be the cooling. Too fast memory timings? Hardware forums could be of more help, just go check if others have had similar questions. Google is your friend too, atleast sometimes :/

                Comment


                • #83
                  heat sink... and maybe it is... I can't tell.

                  I could probably solve this in person, through a process of eliminination, but I'm not sure it can be solved without any alternative parts...

                  I had an AMD mobo that simply wouldn't do 133, even with different procs, different sticks of the best ram, and different components. I worked on it for a while.

                  Now I stick to sure bets. Abit IS-7. P4. Corsair XMS. ATI. everything onboard. I have no problems.

                  Comment


                  • #84
                    I had an AMD mobo that simply wouldn't do 133, even with different procs, different sticks of the best ram, and different components. I worked on it for a while.
                    sounds exactly like my situation...
                    To us, it is the BEAST.

                    Comment


                    • #85
                      Originally posted by Sava
                      sounds exactly like my situation...
                      Well.. you haven't tried alternatives. It wouldn't surprise me terribly if you never got it to work, though. I've seen the issue before.

                      Comment


                      • #86
                        I'm pretty sure that the problem is not from the proc, but from the mainboard.

                        It's entirely possible that the chipset isn't able to endure the 133 MHz settings, despite the name of "KT266".
                        In fact, I had a KT133 that was never able to do better than 110 MHz before freezing/crashing.
                        My actual MB is supposed to be able to reach 166 MHz, and is able to go as far as 200 MHz for the RAM, but crash as soon as I go to 147/150 MHz.
                        Science without conscience is the doom of the soul.

                        Comment


                        • #87
                          Originally posted by Sava
                          well, the FSB settings are unstable, so I have to stick with 100...

                          I'm back to square one, and my desktop is dark again.

                          Anyone have any idea why I can't have my FSB at 133?

                          I'm open to suggestions.

                          btw, my motherboard is a K7T266 Pro2A... if that helps...
                          I have a K7T also (6330) and i can't get the bus to 133 either. If yours is an MSI also, have a look here: http://www.msicomputer.com/support/f...sp?newsearch=1

                          There are a few good tips there, but be careful: i found one post where they tell me how to get the FSB to 133... and another one that says it can't be done. And both are from the tech support of the MoBo manufacturer.
                          What?

                          Comment


                          • #88
                            Have you checked the jumper setting yet?

                            Motherboard details are here (including the manual, if you don't have it already): http://www.msi.com.tw/program/produc...il.php?UID=386

                            Oh, and according to that, it supports up to Athlon XP 2600+, so you should be able to just upgrade the CPU if you decide your current one isn't good enough after all.

                            FSB jumper is here... Once that jumper is set correctly, I think the BIOS should update itself correctly... I think what you're doing now is overclocking the 100MHz FSB to 110 or so, rather than having the FSB set to 133 correctly in the first place (if that makes any sense)...
                            Attached Files
                            Civilization II: maps, guides, links, scenarios, patches and utilities (+ Civ2Tech and CivEngineer)

                            Comment


                            • #89
                              thanks Merc, I'm gonna try that now...

                              ermmm wait, that mobo pic isn't the same as mine... the SW3 on that diagram is where JBAT1 is on mine.

                              thanks for the links guys
                              To us, it is the BEAST.

                              Comment


                              • #90
                                I'm looking in my manual, and I can't find an SW3 jumper. Mine only has 3 jumpers and none of them have anything to do with FSB. DAMMIT &*#TY*()$&&)#$)#*)$@#
                                To us, it is the BEAST.

                                Comment

                                Working...
                                X