Cant get correct Speeds on XP-m 2500+

[Fenris]

Just built a new system on the cheap based around an XP-m 2500+ and the NF7-S v2 (BIOS 26). I know that the system will not recognize the chip and thats fine but it starts me off at 100mhz at x6.0. Which is also fine, I can get the installs done and all.

As I understand it the correct base for the 2500+ should be something like 166 at x11.0. Here is where I run into problems. it seems very unstable at that speed. Actually it just keeps restarting...so its completely unstable.

I plan on OCing to 200 at x11 (why else get the thing) and would like to do it slowly as to prolong the longevity of the system. Just not happy about starting at 133. Should I just get Prime and start moving it up slowly...or is something wrong here?

Other new parts
Vantec Stealth 520
Geil 3200DDR (plain ole)
new Vantec Aeroflow (on Arctic Silvered chip)


I am sure this has been covered the typical 1000 times...so flaming is ok...just gimme a link also

------------------------------------------
"It's a common conceit in games: play, die, reload, and ride the karmic wheel of kick-ass, until you get it right"

 

[skinnyjoint]

how many stix of ram are you running? cuz my buddy had a 2600m and if he had more than 2 stix of ram it kept doing exactly what your saying when he tried to up the multiplier. worth a though..

 

[khha4113]

As I understand it the correct base for the 2500+ should be something like 166 at x11.0.

No, it's not. Actually it is 133FSB@13.5.
You need to enter its settings manually in NF7-S mobo's 'Soft Menu Setup'. Change the <b>CPU Operating Speed</b> to 'User Define', and set FSB and its multiplier (for instance, 166 and 11 respectively).

Good or Bad have no meaning at all, depends on what your point of view is.

 

[Fenris]

Ok..thx for correcting that....
But either way the fact that I cannot do 166 at x11 is an issue, is it not? Possibly I was accidentally pushing it to hard to fast.

To the other poster its only one stick of 3200 in 512.



------------------------------------------
"It's a common conceit in games: play, die, reload, and ride the karmic wheel of kick-ass, until you get it right"

 

[DonnieDarko]

you probably need to increase your vcore voltage. What do you have it at now? Because if it's running at a low voltage, it may not be getting the juice to run the higher fsb.

Watch out for the <b><font color=red>bloody</font color=red></b> Fanboys!

AMD64 2800+ :: MSI Neo-Fis2r :: 1024mb Kingmax ddr400 :: Sapphire 9800pro 128mb :: 10K WD Raptor

Addicted, finally.

 

[Cybercraig]

A higher buss will be faster all the way around. Drop your multiplier to 10.5 and raise your buss speed to 200mhz. You will need some extra voltage too. Start your Vcore at 1.55. Try it from there. Get it to post at your stock memory speed first.

Abit IS7 - 3.0C @ 3.6ghz - Mushkin PC4000 (2 X 512) - Sapphire 9800Pro - TT 420 watt Pure Power
Samsung 120gb ATA-100 - Maxtor 40gb ATA - 100
Sony DRU-510A - Yellowtail Merlot

 

[Fenris]

OK just been testing some settings.

My CPU VC is/was at 1.575 (This was default so I left it)

I cant get a stable system at anything higher than 100mhz at varying multipliers... x 10-11 worked. 105, 110 and 115mhz's locked the system up even at x10.

I upgraded from an AMD 1ghz.....seems I am still stuck there.

------------------------------------------
"It's a common conceit in games: play, die, reload, and ride the karmic wheel of kick-ass, until you get it right"

 

[pauldh]

With an NF7-S rev. 2 and an XP-M, you should have so much flexibility to get that thing running well and fast.

EDIT: I forgot to say, make sure that one stick of ram is in Dimm Slot 3. On NF7's dimm 3 should be used first.

For starters, I assume you used some kind of thermal paste on a clean heatsink and have the heatsink fan plugged in. Make sure you installed the NVidia Chipset Drivers also. If so, You may want to clear the cmos jumper before proceeding further. After this, lets head to the bios.

In SoftMenu III, set cpu operating speed to USER Define. We will shoot for stock desktop Xp2500+ speeds for now and get those stable. Set the CPU External Clock to 166 and the multiplier to 11. AGp Frequency should be set to 66 and the cpu/fsb Dram ratio to By SPD. Next, in the case of the mobile, set CPU Interface to Enabled.

Set Power supply controller to User define and bump up the CPU Core Voltage for now to 1.65v (stock for a desktop XP2500+) Make sure the DDR voltage is 2.6 or even 2.7 if need be. (occasional some ram needs just a tad more juice, and 2.7 or under is safe).

Go back to main menu and go into the advanced chipset features menu. Make sure memory timings is on optimal for now. If it isn't stable still, you can manually relax these timings. You are at this FSB running your memory at PC2700. You may want to put the rated timing for your ram at PC3200 speeds into these fields if things aren't stable. (ie. 8-4-4-3)

Save and reboot. Your cpu should now show up as unknown cpu at about 1833 MHz.

Run some tests like 3dmark2001se and see if it's stable. Also keep an eye on your system temps either back in the PC Health Status in the bios, or better yet in windows by having Abit's Hardware monitor system isntalled. If cpu temp is under 50, you don't have a heat problem.

Let us know how it goes. If things are stable, you should be all set to change some settings and run this puppy at XP3200+ speeds (11*200) or beyond. I have 1 that does 2.4GHz and one that Does 2.6GHz, both air cooled on NF7/NF7-S Rev 2.0 mobos.


ABIT IS7, P4 2.6C, 1GB Corsair XMS 4000 Pro Series, Radeon 9800 Pro, Santa Cruz, TruePower 430watt<P ID="edit"><FONT SIZE=-1><EM>Edited by Pauldh on 10/02/04 03:19 PM.</EM></FONT></P>

 

[Fenris]

Pauldh...ok did all that.
Cleared CMOS.
Set at 166 x11 with CV of 1.65. My RAM was set at "Optimal" of 5-3-3-2 I set it to 8-4-4-3 anyway.

Posts, Boots, and as soon as the Desktop pops up it resets. I actually let it do that a few times then checked the CPU Temp, 35C, so its not that. Went back tried 133 same thing. Tried bosting the CPU CV to 1.7 same thing. Tried RAM at 2.6 and 2.7.

The RAM is in DIMM 3.

------------------------------------------
"It's a common conceit in games: play, die, reload, and ride the karmic wheel of kick-ass, until you get it right"

 

[pauldh]

Did you set CPU Interface to <b>Enabled</b> in the Softmenu III menu?

ABIT IS7, P4 2.6C, 1GB Corsair XMS 4000 Pro Series, Radeon 9800 Pro, Santa Cruz, TruePower 430watt

 

[Fenris]

Yes.

Actually tried Both.

BTW...got it to 105 x11...which honestly/sadly is progress....

------------------------------------------
"It's a common conceit in games: play, die, reload, and ride the karmic wheel of kick-ass, until you get it right"<P ID="edit"><FONT SIZE=-1><EM>Edited by Fenris on 10/02/04 06:16 PM.</EM></FONT></P>

 

[pauldh]

Weird. Could be many things, I suspect ram. Are you sure it is PC3200? Any chance a buddy can load you a stick of PC2700 or 3200 to try out? While running 166*11, I'd try 7-3-3-2.5 timings on the ram also if you have not done so.

I had a mobo who's northbridge heated up and it can't run a 200 bus. But it was a refurb, so what can I expect. But 105 max is rediculous. There's no jumper on the mobo for 100fsb/other from what I remember (Gigabyte does this).

Anyway, try this for fun. (Sorry, I suspect this isn't much fun right now as that is an expensive 600MHz Athlon right now. :frown: ) I've never messed with Async memory on an NF2, but it's worth a try to see just what is limited at a 100 bus. Go back to by SPD timings again for the ram. In SoftmenuIII, try to cpu fsb/dram ratio to 5/3. This will let you run the 166 fsb but keep the ram running at 100MHz. Try this and set the cpu for 166*11 and see if it's a go.



ABIT IS7, P4 2.6C, 1GB Corsair XMS 4000 Pro Series, Radeon 9800 Pro, Santa Cruz, TruePower 430watt

 

[Fenris]

DUDE I LOVE YOU....

Well ok...maybe Heartfelt Gratitude ....or maybe its gas

Either way...who cares its fricking running at 166 x11 with the fsb/dram at 5/3. O yea...and the 7-3-3-2.5 timings...not sure how vital this is...may test it at optimal "5-3-3-2"

Now the next problem....what exactly does this mean..?
Is my RAM bad?

------------------------------------------
"It's a common conceit in games: play, die, reload, and ride the karmic wheel of kick-ass, until you get it right"

 

[Crashman]

Yes, generally speaking if you have to underclock RAM to make it stable, it's bad. I sell a LOT of systems with bad RAM! That is, I'll put a stick of PC133 that only test ok at 100MHz max in a Celeron system with 66MHz bus. How can I do that? I don't advertize the RAM as being anything faster than PC66!

<font color=blue>Only a place as big as the internet could be home to a hero as big as Crashman!</font color=blue>
<font color=red>Only a place as big as the internet could be home to an ego as large as Crashman's!</font color=red>

 

[Fenris]

Thanks....

Ok so I guess the RAM goes back....

------------------------------------------
"It's a common conceit in games: play, die, reload, and ride the karmic wheel of kick-ass, until you get it right"

 

[pauldh]

Hey good deal. It was hurting me to see a NF7-s/ mobile XP not running well. Anyway, I hope it's gas, the love thing scares me.

Now on to see if you can run XP3200+ speeds 11*200 and set the cpu fsb/dram ratio to 6/3. Ram will still run 100 (200)MHz. Anyway, congrats and time to look for some new PC3200 ram so you can get some more performance. AXP's aren't memory bandwidth limited to the extent of a P4, but I'd have to think that running your ram at half the fsb has got to hurt performance. So like Crash said, you can sell the ram wih your old TBird as PC1600. Or just sell the 200 bus TBird CPU with matching DDR? :tongue:


ABIT IS7, P4 2.6C, 1GB Corsair XMS 4000 Pro Series, Radeon 9800 Pro, Santa Cruz, TruePower 430watt

 

[Nights_L]

At least those RAMs works fine..so they are not too bad