So, does this mean I can overclock my processor with the click of a button (I have an Abit NF7-S v2)?! If it is, i'll be in overclocking heaven... does anyone know how well an Athlon XP 2500+ Barton will overclock?
A bad one should do 2250-2300 at 1.9Vcore. Good one will do 2300 at 1.75-1.8vcore and 2400 at 1.9vcore. What heatsink are you using? You should be fine as long as vcore doesn't exceed 1.9 and temps don't exceed 65*C. What are your full specs Dodger?
Both will do an excellent job and not bottleneck your overclock. Should last you about 1.5 - 2 years. If you had to choose between the two I would go with the enermax.
How did you get the NF7core proggy to start?
I get the "Cannot get the IO handle" message.
Readme says:
This version uses the GiveIO.SYS driver (under NT/2000/XP) and try to automatically install it. You can uninstall the driver with the Device-Manager,
VIEW->Show all devices (or something like that), Non-PnP-driver->giveio. Or use remove-giveio.zip
hmm..., I just unzip it to a folder called nf7vcore and double click the exe, that's all...
You must have a corrupted download or maybe you're missing Windows runtime files.
I also have the xp2500 barton i just started messing around with over clocking. Right now its running at 2.02.What i was wondering is if i raise the vcore do i lower the fbs settings and play with it that way.
vcore;1.725
multi;11.5
fsb; 175mhz
my specs are:
xp2500
msi k7n2g-ilsr mobo
2-512 ddr pc2700 samsung (dual channel)
msi g-force4 ti-4200
thermaltake volcan5
1 intake fan
1 exhaust fan
300 watt agi power supply
1-120 gig ibm 8mb hd
1-80 gig ibm 8mb hd
54x cd-rom
54x cd-burner
win xp pro
Got it...i had to manually install a .sys to make it work.
However, that NF7 proggy didn't take me further than i already am though. The vcore bug at high fsb is still there.
But i guess it's a good tool to see how far a rig can get without having to restart.
I'm glad you got it working.
I like nf7vcore better because of the extra options and the fact that the author is improving it day by day. The newest beta from yesterday adds CPU usage, refresh intervals, etc.
There are a few bugs like adjusting vdd to 1.7v and voltage over 1.85v but there are warnings before you make the changes. Give it a try, I think you'll like it and this program is far superior to nVIDIA utility.
On a totally different note, let me tell you the latest about my Thorton and get some feedback from you.
I modified the chip to be 166MHz and everything is fine but something about this chip is so weird. With newer bios the auto detection is disable, the multi is always locked and the chip is detected as 166x15 but if I use an older bios like v17 for example, the chip is seeing as a 3000+, advance setting is enable and the chip shows up as 166x13 or 3000+
Check it out, any ideas as to what's going on? TIA
I have the same thing actually...on newer bioses, my chip turns up as a 200 fsb chip, but D10 gives me 166. Go figure.
To be frank, i have no clue what is causing it but i think Nvidia have changed a lot in the registry of the bios. I would love to get my hands on some engineering emails from Amd to Nvidia and vice versa. :P
No info on any hardmods on the multi yet? You need that badly my friend.
Comments
Gainward Ti4200 128mb 8X
256mb samsung memory
Thermaltake Smart Fan II
Thermalright SLK-900A all copper heatsink
300w power supply (will upgrade soon, anyone card to reccomend a good one?)
80 gigabyte western-digital harddrive
24x16x24 Samsung cd-rom drive
Well, that's about it.
On the PSU,
Either this enermax or this Antec .
Both will do an excellent job and not bottleneck your overclock. Should last you about 1.5 - 2 years. If you had to choose between the two I would go with the enermax.
How did you get the NF7core proggy to start?
I get the "Cannot get the IO handle" message.
Readme says:
This version uses the GiveIO.SYS driver (under NT/2000/XP) and try to automatically install it. You can uninstall the driver with the Device-Manager,
VIEW->Show all devices (or something like that), Non-PnP-driver->giveio. Or use remove-giveio.zip
Which doesn't make sence to me at all.
You must have a corrupted download or maybe you're missing Windows runtime files.
vcore;1.725
multi;11.5
fsb; 175mhz
my specs are:
xp2500
msi k7n2g-ilsr mobo
2-512 ddr pc2700 samsung (dual channel)
msi g-force4 ti-4200
thermaltake volcan5
1 intake fan
1 exhaust fan
300 watt agi power supply
1-120 gig ibm 8mb hd
1-80 gig ibm 8mb hd
54x cd-rom
54x cd-burner
win xp pro
However, that NF7 proggy didn't take me further than i already am though. The vcore bug at high fsb is still there.
But i guess it's a good tool to see how far a rig can get without having to restart.
Or did the clockgen get better results?
I like nf7vcore better because of the extra options and the fact that the author is improving it day by day. The newest beta from yesterday adds CPU usage, refresh intervals, etc.
There are a few bugs like adjusting vdd to 1.7v and voltage over 1.85v but there are warnings before you make the changes. Give it a try, I think you'll like it and this program is far superior to nVIDIA utility.
On a totally different note, let me tell you the latest about my Thorton and get some feedback from you.
I modified the chip to be 166MHz and everything is fine but something about this chip is so weird. With newer bios the auto detection is disable, the multi is always locked and the chip is detected as 166x15 but if I use an older bios like v17 for example, the chip is seeing as a 3000+, advance setting is enable and the chip shows up as 166x13 or 3000+
Check it out, any ideas as to what's going on? TIA
To be frank, i have no clue what is causing it but i think Nvidia have changed a lot in the registry of the bios. I would love to get my hands on some engineering emails from Amd to Nvidia and vice versa. :P
No info on any hardmods on the multi yet? You need that badly my friend.
Yeah, if I had multis this thing would fly high.
Hard to believe nobody has figured out how to unlocked these chips yet huh?
The thing is, not that many peeps has these cpu's, at least not enthusiasts.
Why not try one of those unlock strips? Might come in handy on more than one cpu actually. Seen any review of it or that it actually works?