• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

Changing FSB jumper causes system not to boot?

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

Saleen

Registered
Joined
Apr 5, 2002
Folks,

i just recently setup my duallie running the following -

A7M266-D
2 Athlon 2000+ MP
1GB DDR
VisionTek G4 Ti 6400

everything works fine with the standard config. System boots, Windows XP Pro loads and i can do everything i normally do.

However last night i was trying to start playing with the FSB settings in the BIOS. According to the DOC the first thing i had to do was change the Jumper for the FSB on the board to Pins 2-3 instead of 1-2. When i do that the system no longer boots. Doesn't even looks like it tries to post.
The display never initializes and the system seems like it's in a standby mode.

Anyone have any ideas what's going on here? I put the jumper back to 1-2 and the system boots up fine. I'm going to try to updat the BIOS tonight but have been having a dreadfull time trying to download it from the ASUS sites.

Thanks!
 

WarriorII

Moderator #666
Joined
Nov 13, 2001
Location
Moderating
1st - Welcome to the Fourms ! :)

What does the book say changing the jumper from 1-2 to 2-3 say?
Is it to make it jumperless and workable in the BIOS?
Or is it changing it to 133 from 100 mhz?
Are you positive you have the right set of jumpers?
I know they are small and hard to be sure you've got the correct 1's.

:cool:
 
OP
S

Saleen

Registered
Joined
Apr 5, 2002
WarriorII,

Changing the jumper from 1-2 to 2-3 enables jumperless in the BIOS as you said and according to the book :)

I'm 99.999% sure i have the right set of jumpers. There's really nothing else around that looks even remotely close to what the book is showing. I will be sure to triple check it again tonight

:)
 

WarriorII

Moderator #666
Joined
Nov 13, 2001
Location
Moderating
Hmmmm.

Try clearing the CMOS, then replace the jumper.
See if boots then.
I know on my A7V266-E mobo, when I hit the start button on the case,
It takes FOREVER to boot up.

1st I hit the button, then everything spins up,
screen still black, then maybe 20-35 seconds and I have a vid card boot, then up with the system.
I don't know if it's ASUS or what?

If it doesn't boot by the jumpers/ for jumperless.
Try setting it to jumper mode.
It might work that way.

Either way let me know. - Now you got me goin.:eek:

:cool:
 

WarriorII

Moderator #666
Joined
Nov 13, 2001
Location
Moderating
Here is the latest BIOS for ur mobo.
( I believe it to be ) A7M266-D mobo.

Took me 30 minutes to get it w/ DSL (800up/down)
From ASUS.
:cool:
 
OP
S

Saleen

Registered
Joined
Apr 5, 2002
Thanks for the file. That actually isn't the one for my board but i was finally able to get to the ASUS ftp site tonight and downloaded the latest BIOS.

I just realized something tonight after doing some reading and i'll probably get a good flame for this one :) Keep in mind this system is my first AMD! :)

I was reading up about OC'n AMD's and about unlocking the CPU's when i realized i haven't unlocked mine! I'm guessing that's the problem? I originally thought unlocking the CPU was only needed when trying to change the multiplier for the clock speed. Based on some reading tonight sounds like i have to do that to make the FSB changes too.

Gonna order an unlocking kit tomorrow and give that a try.

Do you know of any problems unlocking Athlon MP 2000+ ? From what i can gather the process is the same, it's only the XP 2100+ series where things were changed quite a bit.
 
OP
S

Saleen

Registered
Joined
Apr 5, 2002
OK, now that i've done even more research it seems like Athlon MP's come unlocked?

Haven't tried your CMOS suggestion yet but i will do that tomorrow.

Man this AMD stuff is confusing, should've stayed with my P4 :) j/k I still do love my P4 :)
 

WarriorII

Moderator #666
Joined
Nov 13, 2001
Location
Moderating
MP's come unlocked. as for FSB clockin, It doesn't need any thing. Just for the mobo to support it.

P-4 Ewwwww (Flame)

Stay at it, it'll come. Your 1st -cough- *Int*l*
wasn't easy either. :D

CMOS jumper is like removing the battery.
I have your Manual (PDF file) I will look @ it tonight.

:cool:

lemme kno.
 
Last edited:
OP
S

Saleen

Registered
Joined
Apr 5, 2002
OK, i finally got it to work.

What you need to do once you switch the jumper to 2-3 is also all 4 DSW Dip Switches to OFF. By default it comes ON ON ON OFF which in jumper mode sets the FSB to 133.

I started at 150 FSB and XP Pro blue screened before the spalsh screen came up. Went down 1 at a time and was able to boot in to XP at 147 FSB. Ran some tests with 3DMark2001 and got some decent results.

Rebooted the system and it blue screened right after logging in to XP. Tried to reboot 4 more times with the same FSB setting and blue screened every time. I dropped it down to 146 FSB and could log back in to windows and tested with 4 reboots and everything worked fine. Everything ran fine including some benchmarking and Half Life :)

However my Everquest locks up about 10 mins in to playing and this happended consistently 3 times in a row, needing a hard reboot each time. Same thing at 145 FSB. Dropped down to 144 right now and everything seems to be running fine.

Now off to do more reading and research on this stuff :)

Thanks for your help and suggestions Warrior, never would have made it through this without ya :)
 

WarriorII

Moderator #666
Joined
Nov 13, 2001
Location
Moderating
1 is glad to be of service. :D

Now try lowering your multiplier a little, and go back up on the FSB.
This should help a bit more.

Good Luck.

:cool:
 
OP
S

Saleen

Registered
Joined
Apr 5, 2002
I don't think you can adjust the Multiplier on my board. I remember reading somewhere that ASUS didn't left that capability out for some reason.

I read through the DOC and looked through the BIOS and there's no where it mentiones adjusting the multiplier.

The only things i think i can do is adjust the voltage to CPU0 and to my RAM.