Athlon XP keeps downclocking itself!

[masshass81]

AXP 1700+ T-Bred A
1x128 Crucial PC-3200
Abit NF7-M

I've OCed this system a few times before and have gotten stuck at 1.7Ghz. THen today I thought I would try to mess with the memory ratios. So first thing I do is set vcore to 1.625v and FSB to 150 w/ 11x multiplier (I've been stable on this setting before) and when the BIOS saves and restarts, its clocked at Athlon XP 1100Mhz and it resets all my BIOS settings!! Dunno why it does this, I have not changed my BIOS version since the last OC..

Now everytime I change the vcore setting (.1v above default) or FSB up (by 15mhz for example), the BIOS resets and the cpu downclocks itself to 1100Mhz.. The weird thing is, if I change things in a certain order - raise vcore, reset, then raise FSB, it would POST.. but then a few Mhz later it would set back to 1100Mhz.. Then I would try the same steps that worked before and it would downclock to 1100Mhz if I only change the vcore about .1v... Please help!

 

[Carskick]

Is all your cooling working? Fans runing at optimum speeds, etc? All wires in place and everything? I'd look in the tower and see if there is anything that looks faulty or out of place.

 

[masshass81]

All fans are working fine. Power connectors and IDE cables all seem fine too.

 

[Zebo]

So first thing I do is set vcore to 6.25v

Probaly a little high, try 5.25V.

 

[Corsairpro]

Originally posted by: Zebo

So first thing I do is set vcore to 6.25v

Probaly a little high, try 5.25V.

lmao

 

[masshass81]

omg LOL, I meant 1.625v

 

[Zebo]

Sounds like battry on mobo is shot. Leave stock Vcore and set cpu to 1200 mhz and see if it resets.

 

[masshass81]

Its on stock vcore (1.5v) running at rated speed 1700+ 1.477Ghz. Runs fine. I POST fine with something like 155FSB vcore 1.6 with 11x mult (1.705), then I change the shared RAM (for onboard GFx) from 32 to 16mb (GF would benefit from more RAM than more gpu RAM) and then its resets BIOS and clock down to 1100Mhz..

Ok, so then I set it back to 1700+, boots up fine at 1700+ then all I do is set it back to something like 140FSB vcore 1.6 11x mult (1.540Ghz) and then clocks back to 1100Mhz and resets BIOS again (I didnt mess with onboard gfx RAM)... THEN, I get it running at 1700+ again, get it to OC around to 1.75Ghz, then it craps out again.. Its so variable =(

 

[FelixDeCat]

Must be that wonderful AMD quality again...

 

[MDE]

Originally posted by: masshass81
Its on stock vcore (1.5v) running at rated speed 1700+ 1.477Ghz. Runs fine. I POST fine with something like 155FSB vcore 1.6 with 11x mult (1.705), then I change the shared RAM (for onboard GFx) from 32 to 16mb (GF would benefit from more RAM than more gpu RAM) and then its resets BIOS and clock down to 1100Mhz..

Ok, so then I set it back to 1700+, boots up fine at 1700+ then all I do is set it back to something like 140FSB vcore 1.6 11x mult (1.540Ghz) and then clocks back to 1100Mhz and resets BIOS again (I didnt mess with onboard gfx RAM)... THEN, I get it running at 1700+ again, get it to OC around to 1.75Ghz, then it craps out again.. Its so variable =(

Overclocking with onboard graphics is asking for trouble.

Originally posted by: FelixDeKat
Must be that wonderful AMD quality again...

Troll troll troll your boat...

 

[Jeff7181]

Originally posted by: FelixDeKat
Must be that wonderful AMD quality again...

That must be ignorant asshat again...


Anyway... OP, your problem is more likely due to an unstable overclock that causes the BIOS to reset when you reboot. It's not uncommon for that to happen. Manufacturers are building those kind of features in now that automatically reset everything to default rather than just letting it lock up and let you sit there and stare at a blank screen. 150/155 is an odd speed for a FSB. Try going right to 166 and see if that works.

 

[FelixDeCat]

Originally posted by: Jeff7181

Originally posted by: FelixDeKat
Must be that wonderful AMD quality again...

That must be ignorant asshat again...


Anyway... OP, your problem is more likely due to an unstable overclock that causes the BIOS to reset when you reboot. It's not uncommon for that to happen. Manufacturers are building those kind of features in now that automatically reset everything to default rather than just letting it lock up and let you sit there and stare at a blank screen. 150/155 is an odd speed for a FSB. Try going right to 166 and see if that works.

When people speak of problems and I say Ive heard that before why does it get you mad?! Dont be so touchy - its just a stinkin chip already.

 

[Jeff7181]

Originally posted by: FelixDeKat

Originally posted by: Jeff7181

Originally posted by: FelixDeKat
Must be that wonderful AMD quality again...

That must be ignorant asshat again...


Anyway... OP, your problem is more likely due to an unstable overclock that causes the BIOS to reset when you reboot. It's not uncommon for that to happen. Manufacturers are building those kind of features in now that automatically reset everything to default rather than just letting it lock up and let you sit there and stare at a blank screen. 150/155 is an odd speed for a FSB. Try going right to 166 and see if that works.

When people speak of problems and I say Ive heard that before why does it get you mad?! Dont be so touchy - its just a stinkin chip already.

Because it's not a problem with the "chip"... if you think it is, you're more ignorant than I first thought.

 

[masshass81]

Slapped in a PCI Gfx card and disabled the onboard Gfx to eliminate any potential memory problems.. Tried going from 133 to 166Mhz like you suggested with vcore at 1.65v, when it saved to BIOS, it just downclocked again to 1100Mhz and reset the BIOS. I set it back to 1700+, then tried going to 143FSB, booted fine.. Reset, brought it up to 153FSB (I've POSTED and ran stable at this setting before) and it clocks back down to 1100Mhz and resets BIOS again. Do I need a BIOS update? I bought the NF7-M about 5 months ago so the BIOS can't be that old.. Also, why would it always clock to 1100Mhz (100x11)? Stock 1700+ is 133x11..

 

[MDE]

I just noticed that this is a Tbred A in your OP, and you're tryong to go from 1.4 to 1.8 on stock voltage. I highly doubt that's going to work without upping the voltage to 1.75 or more.

 

[masshass81]

The first thing I do before I bump up the FSB is set vcore to 1.65v. I've OCed to 1.7 with 1.65vcore before (about 2 months ago) with no problem, but just set it back to stock since there wasnt a noticeable difference. Now, when I try to OC, it does all that crazy downclock and BIOS reset... It never reseted BIOS before, I dunno what happened.

 

[Jeff7181]

Originally posted by: masshass81
Slapped in a PCI Gfx card and disabled the onboard Gfx to eliminate any potential memory problems.. Tried going from 133 to 166Mhz like you suggested with vcore at 1.65v, when it saved to BIOS, it just downclocked again to 1100Mhz and reset the BIOS. I set it back to 1700+, then tried going to 143FSB, booted fine.. Reset, brought it up to 153FSB (I've POSTED and ran stable at this setting before) and it clocks back down to 1100Mhz and resets BIOS again. Do I need a BIOS update? I bought the NF7-M about 5 months ago so the BIOS can't be that old.. Also, why would it always clock to 1100Mhz (100x11)? Stock 1700+ is 133x11..

It's resetting to 100x11 because 100 MHz is the default FSB speed for 90% of Socket A motherboards. It has nothing to do with the processor as I said. It's possible that your motherboard just isn't capable of a FSB that high.

Couple more things to consider/try... are you running your RAM in dual channel? Maybe try single channel and see if that has any effect on it. Test your CMOS battery... take it out, check the voltage, shouldn't be more than a tenth of a volt under it's rated voltage. Reset the CMOS yourself using the jumper.

You said stock vcore is 1.5V... if that's true, then you have a T-bred B and should easily pass 1.8 GHz so it's more likely not the CPU that's the problem. I don't suppose to have another CPU you can put in and see if it acts the same way, do you?

 

[masshass81]

Sorry about the noobness, but how do I check the voltage on the CMOS battery. Yes, I'm running DC, but its only 2x128.. I'll try a few runs with a single 128 stick.. I've already reset the CMOS jumper. Also, in CPU-Z, it identifies the cpu as A under revision, but yeah, the 1.5v would make it B so I'm really not sure what it is now.. And I don't have another socketA cpu to test out. But yeah, screw this one, I am going to get a Mobile XP soon anyway.. Thanks for explaining why it clocks to 1100Mhz though, could'nt figure that one out :thumbsup:

btw, if I find that the CMOS battery is messed up (someone else said it might be that also), how do I go about getting a new one?

 

[FelixDeCat]

duh! what are you, a betazoid? based on the OP the problem seemed obvious - the chip. stop being such a baby and grow upalready. :roll:

 

[FelixDeCat]

dp

 

[masshass81]

oh, thats why everyone hates you and that explains your low rating.. gotcha :thumbsup:

 

[FelixDeCat]

Originally posted by: masshass81
oh, thats why everyone hates you and that explains your low rating.. gotcha :thumbsup:

Go easy on Jeff.

 

[Budman]

Originally posted by: FelixDeKat
Must be that wonderful AMD quality again...

Link just for you.

 

[DrMrLordX]

Originally posted by: Budman

Link just for you.

V I C T O L Y

I'll have to remember that link. Awesome.

 

[Jeff7181]

Originally posted by: masshass81
Sorry about the noobness, but how do I check the voltage on the CMOS battery. Yes, I'm running DC, but its only 2x128.. I'll try a few runs with a single 128 stick.. I've already reset the CMOS jumper. Also, in CPU-Z, it identifies the cpu as A under revision, but yeah, the 1.5v would make it B so I'm really not sure what it is now.. And I don't have another socketA cpu to test out. But yeah, screw this one, I am going to get a Mobile XP soon anyway.. Thanks for explaining why it clocks to 1100Mhz though, could'nt figure that one out :thumbsup:

btw, if I find that the CMOS battery is messed up (someone else said it might be that also), how do I go about getting a new one?

Take the battery out and use a volt meter to check it... one side is positive, one is negative.

If you need a new one just take the old one to Radio Shack or any place that sells watch batteries, hand it to them and say, "I need one of these."



FelixDeKat... I suggest you shove it up your ass. You've been no help AT ALL in this thread, and your maturity level is that of a 12 year old. YOU are the one who needs to grow up.