Please report all spam threads, posts and suspicious members. We receive spam notifications and will take immediate action!
Page 1 of 2 12 LastLast
Results 1 to 10 of 18

Thread: FSB won't run at 133 mhz




  1. #1
    Join Date
    Jun 2002
    Posts
    28

    Default

    Last Christmas I got my comp... and I never really fixed this problem (worked on it for a while and just gave up) The problem is that my Athlon XP 1800+ will only be recognized as an Athlon XP and only run at 1.14 Ghz as opposed to 1.33. It doesn't sound like much but the extra .2 ghz probably costed me 75-100$.

    The reason why it does this is that the mobo is only running at 100 mhz FSB. When I set the FSB to 133 mhz the computer properly recognizes the processor but it won't boot so that doesnt do much good. When I start up with the 133 mhz I get a stop error saying that a system file is corrupt (the first time it was ntfs.sys but it changes). I've reformatted the system recently and the problem still occurs. If you need the specs for my mobo I can't get it to you until tomarrow, sry (I know its supposed to run 133 mhz system bus and is compatible with Athlon XP, and I've also updated the bios) Any help on this would be greatly appreciated

    And my other question is if I settle with the slower FSB (and hence a slower processor) will the slower FSB really slow down the overall performance. I don't know how much the FSB speed contributes to performance so I really don't know. Thanks alot


    The mobo is FIC AD11 (the Athlon XP one).

    Although it says 266 FSB I can assure you that it only runs at 100 or 133 mhz. Also, I looked for the clock multiplier again in Bios and couldn't find it. The closest one to that is "CPU Host/PCI Clock" (this setting was under the Frequency/Voltage Control category) the options for this setting are:

    Default (currently checked)
    100/33 MHz
    120/30 MHz
    133/33 MHz

    Two days ago I checked the 133 MHz assuming that was the FSB speed. Then the monitor wouldn't respond and my comp wouldnt post so I changed the jumper on the mobo to 133 MHz. The monitor then responded and it posted but it wouldn't boot (that is where I got the error messages) but I could go into Bios and change the setting back to default and then I changed the mobo jumper to 100 mhz and my comp was back to normal (but still at the slower speed).

    If I do end up buying another mobo and Athlon XP mobo's to recommend??
    Thanks

  2. #2
    Join Date
    Jul 2002
    Location
    Home
    Posts
    315

    Default

    I have a new Epox 8KHA+ and AMD XP 1800+ and have the exact same issue. I've been thinking it is a motherboard issue but now hearing this issue on another mb I'm thinking maybe its a processor issue.

  3. #3
    Join Date
    Jun 2002
    Posts
    28

    Default

    really :eek: i was sure it was the mobo... so u have the exact same problem? what is the comp recognizing ur processor at?

  4. #4
    Join Date
    Jul 2002
    Location
    Home
    Posts
    315

    Default

    Here is the thread I started.

    http://forums.tweaktown.com/showthre...&threadid=3946

    I'm calling Epox right now to see if they have any ideas on this issue. Will keep you posted.

  5. #5
    Join Date
    Jun 2002
    Posts
    28

    Default

    thats exactly the problem that I have... I was thinking about buying a new mobo but now i don't know.

  6. #6
    Join Date
    Feb 2002
    Posts
    777

    Default

    I have the same problem with my K7S5A, so i got a Soltek and still having probs, think it might be the cpu, coz i alsdo replaced the RAM and that didn't fix it either:cry:
    Athlon XP 1600+ @ 1662Mhz | Volcano 7+ HSF | Soltek SL-75DRV5 | 256MB Corsair XMS-3000 DDR RAM | 44x44x24 Yamaha CDR-W F1 | 16x Liteon DVD | 40Gig 7200rpm Seagate Barracuda | 20Gig 5400rpm Seagate | GeForce2 MX-400 | SB Live! | RTL8139A NIC | RTL8139B NIC | 12 Fans | 1 x ss Blue cc | 2 x Red Neons | 450W Codgen PSU | Logitech Z-340 2.1 Sub and sats | 17" Osborune Monitor | Win XP Pro | M$ explorer rat and keyboard | Everglide Attack Optical

  7. #7
    Join Date
    Jul 2002
    Location
    Home
    Posts
    315

    Default

    Epox tech told me to run the motherboard outside of the case on a non-conductive surface, like the box it come in, with only the RAM, video card, and processor attached. No PCI cards plugged in. He said it sounded like there could be a short somewhere.

    So, I took the motherboard out, did as he said. It booted into Windows! And then about 30 seconds later it rebooted itself and booted to the same file error as before. :eek:

  8. #8
    Join Date
    Jun 2002
    Posts
    28

    Default

    hmmm has anyone contacted Intel about this

  9. #9
    Join Date
    Jul 2002
    Location
    Home
    Posts
    315

    Default

    Fortunately, I have another computer to use for the next week or two. I called AMD and will be sending in the processor for testing. If nothing is wrong with the processor then I know its the MB and have already received a RMA number for a replacement. If its the processor AMD will send a replacement.

  10. #10
    Join Date
    Jun 2002
    Posts
    28

    Default

    well i don't have a good enough computer to run in the meantime so please tell me when u hear back from AMD, email me or somethin.

Page 1 of 2 12 LastLast

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •