Sign in or Register (it’s quick!)

Forgot?
Page 1 of 2 1 2
 
Reply to Discussion Options
ngfrazier
Icrontic Convert
ngfrazier
10 Posts
7 Jan 2004, 7:07am

Unhappy HELP! NF7-S cannot overclock Athlon 2500+ to 3200+

First, thanks for clicking on this post. Your time and effort is greatly appreciated!

Components: (Mobo+RAM+Proc from newegg received 1/5/2004):
Abit NF7-S
2 x 256MB, PC3200 (Buffalo Tech using Winbond CH-5 chips)
AMD Athlon 2500+ (retail box) with the following codes:
AXDA2500KV4D KO22244l31038
PQZEA0332MPMW
Alpha PAL 8045 Cooled by a 80mm fan
Visiontek Geforce3 Ti 200 (using 41.09 WHQL drivers)
WD 160 GB Special Edition JBRTL
16x DVD Lite-ON IDE
24x CD-RW Yamaha IDE
---powered by an Antec TruePower 430 and enclosed in a CoolerMaster ATC-201

Proceedure:
Upon installing the NF7, I updated to the latest BIOS, overclocked the 2500+ by selecting the 3200+ (three selections are available: 2500+; 3200+, and User Defined)
WinXP Pro + SP1 installed without a hitch under the selected 3200+ (using default voltage). Then, I installed the 3.13 nForce drivers. I noticed that computer would freeze 3-10secs within playing an MP3. Hmm, not good!

Started playing around with BIOS settings, specifically memory timings and voltage settings. After reading in these forums, I upped the Vcore voltage (tried different settings from 1.675->1.8) in order to gain stability. I also increased the VDimm voltage and the chipset voltage in various combinations to no avail. As for the memory timings, I tried all the various settings, from “by SPD” to “Optimal” and “Aggressive.”

At this point, I was not sure where the problem lay: memory or motherboard? So, I downloaded memtest and another memory tester from Microsoft. Memory passed both series of tests (from each program) without error. At this point, I think that the problem is related to the onboard sound (because it would freeze when playing MP3s). So, I disabled the onboard sound and installed Wolfenstein Enemy Territory. Proc is still overclocked and it freezes a couple seconds after joining a server. Went to BIOS, enabled sound and set CPU back to 2500. Game does not freeze, MP3s + DVDs all play fine. I set the memory to asynchronous mode (mem 400 + Proc 333) and all still ran stable.

I have spent many hours changing settings in an attempt to reach around 2.2 ghz (3200+) stable (without games crashing and without getting errors from Prime95). I am disappointed because a friend of mine has a $60 Shuttle nforce2 that ran his 3200+ without a problem. Any advice is welcome.

Bios settings which remained consistent:
SoftMenu III (CPU Interface Enabled)
Advanced BIOS Features Setup (Virus Warning Disabled; APIC enabled)
Advanced Chipset Features (System BIOS Cache Disabled, Video RAM Cache Disabled, CPU Throttling Disabled, ALL Spread-Spectrum Disabled)
Integrated Peripherals (SATA Disabled , FireWire Disabled, Parallel Port Disabled, Serial#2 Disabled)..REST all DEFAULT (but PCI transfer enhanced Disabled)
Reply with Quote
Necropolis
Back from the wilderness
Necropolis
1,762 Posts
7 Jan 2004, 7:23am
It sounds like you system may be overheating. What where your temps when running at 3200+? The Alpha Pal was a great heatsink for the older athlon chips but when I put mine on my old 2200+ the temps were stupidly high. You would have been better off getting an SLK-800 or 9** and a good 80mm or 92mm fan.
__________________ Im one of the new breed of geek. The beer swilling, guinness drinking, women oggling, tech loving, football watching, tattoo'd Uber Geek.
Reply with Quote
TheBaron
Veteran Icrontian
TheBaron
2,784 Posts
7 Jan 2004, 7:31am
like nec says, temps would be a good thing to check. try to take a reading while putting load on the CPU (i.e. prime95 or folding@home)
Reply with Quote
tefleming
polytetrafluoroethylene
tefleming
471 Posts
7 Jan 2004, 7:32am
Welcome to S-M!

Necro might be on to something, try installing MBM.

BUT, my guess is that you'll find that your CH5 chips are holding you back. While the BH5's were amazing, some of the CH5's are having trouble running at stock speeds.

Also, you should probably use the "User Defined" option under BIOS and increase your FSB settings incrementally. (rather than jumping straight from 166->200)

Best of Luck,

PS: One piece of advice, I'd make sure the system is running smoothly at stock speeds (everything: CPU, Mem, Vid, etc) before you begin overclocking.
__________________ [center]the non-stickiest of the icky[/center]
Reply with Quote
Jimborae
He ain't mad, just English
Jimborae
1,498 Posts
7 Jan 2004, 3:22pm
The Alpha Pal is easily as good as an SLK 800 when using the same fan. It is by no means past its prime & manages to keep my overclocked XP1800 at 2.2ghz all day at around 40-44c. So doubt heat is the issue unless it was installed incorrectly.
__________________ System 1
DFI DK X58-T3eH6, Intel i7 920 @4.2ghz, 6Gb Patriot DDR3, 1x250g Samsung Spinpoint, Intel 80 SSD, XFX 4890 1Gb, Seasonic S12 600w psu, NEC 4550 DVD-RW burner
Reply with Quote
TheLostSwede
Where's the ****ing beers?
TheLostSwede
3,227 Posts
7 Jan 2004, 5:38pm
I agree with Jim here. That's a great heatsink.

I played around with a few bioses yesterday. I usually have the first bios, but modded by EQuito, D10. DEAD stable at pretty high overclocks. (11.5X230 SYNC, DC) Never had a reboot or freeze at that setting. Tried bios 20 and Call Of Duty kicked back to desktop within 5 minutes. I'm not saying it has to be the bios that is faulty but it might be worth a check. The CH5 chips isn't that bad actually. The newer ones actually goes as high as BH5 with lots of voltage.

Set the timings to 11,3,2, cas 2,5 (we'll change it later) at 166 fsb in 6/6 (sync), disable the 2 cache options in the bios (video and one more, can't remember the name), set the VDDR (memory voltage) voltage to 2.8, vcvore to 1.85 (we'll lower it later on if possible), 1.6 on the chipset voltage, default on the other voltage.

A couple of questions: Is that cpu unlocked? Can you take a reading of the voltages in the bios? 12V, 5V and 3.3V is all you need to check.

We'll sort this out.
__________________ ...
Reply with Quote
seversphere
Slam Poet
seversphere
592 Posts
7 Jan 2004, 6:55pm
are you able to take a picture of the xp2500?


CPU DISCONNECT is enabled by default. DISABLE it if you haven't already.
__________________ "Here I am, so typically, late to a hot thread."

Heatware
Reply with Quote
TheBaron
Veteran Icrontian
TheBaron
2,784 Posts
7 Jan 2004, 9:53pm
and just remember, looking at the timings mac posted, your ram should also be set at x-x-x-11 on nforce boards, as this yields the best performance out of the memory controller
Reply with Quote
Preacher
Contentious Cajun of the Cloth
Preacher
1,286 Posts

» Subscriber

8 Jan 2004, 4:59am
Quoting seversphere
are you able to take a picture of the xp2500?


CPU DISCONNECT is enabled by default. DISABLE it if you haven't already.
serversphere,
this may be a dumb question, but why is disabling this better?
Reply with Quote
ngfrazier
Icrontic Convert
ngfrazier
10 Posts
8 Jan 2004, 5:17am
I appreciate everyone's advice and comments.

First, an update: I suspected that some problems may have been caused from installing windows on an overclocked system. So, in order to eliminate this possibility, I set everything to default speeds and reloaded WinXP + SP1 + drivers (40.72 WHQL'd for Video and the 2.xx nforce downloaded from Abit website). (BTW, my CPU temps at stock are 35-37C)

Now, i attempted to overclock! I followed Mackanz's advice (upped Vcore and Mem. Voltage, set RAM timings, etc...). I knew that my CPU and Mem were stable at default voltage (having run Prime95 on them), so I attempted to gradually OC.

I went from 166 to 173 to 177... it seemed fine until I started to reach the high 180s and 190s. At that point, I OC slowly (2-3 MHz increments). Although I have not been able to fully test each setting (aka >12hrs Prime95) I worked along the principle of finding *unstable* settings rather than proving stable ones. My method was to run Prime95 for about 10-15 mins. Often, this was more than adequate to detect errors. Sadly, at 199 MHz FSB, Prime95 would spit out an error in the first min of testing. The threshold of stability seems to be 195-198 MHz (with vcore increased to >1.8, temps hovered around 47C-51C loaded).

What piece of hardware is to blame? Is it the Mobo or the Proc? RAM maybe? I am fairly sure it is not RAM, as I have tested the module for errors numerous time. As for the Processor, I am left with more questions than answers. According to the CPU code and stepping (AQZEA0332MPMW) the "AQZEA" stepping is not the best nor the worst and should almost guarantee a 3200+ with added voltage. Moreover, having been manufactured the 32nd week of 2003 the multiplier *should* be unlocked--yet it is not!

Lastly, on a side note, how much voltage is too much voltage? Is a Vcore of 1.8v getting dangerous? How about the RAM? Does such an increase only raise the temps, or are their long-term consequences to consider. In other words, at what point should a trade-off be made in voltage to long-term stability (at least 2-3 years)?

Cordially,

Nathan
Reply with Quote
TheSmJ
Whatever!
TheSmJ
3,985 Posts
8 Jan 2004, 5:58am
Did you update the BIOS to the most recent available?
__________________
CPU: Opteron 165 OCed to 2.7GHz (300x9)
Motherboard: ASRock 939Dual-SATA2
Video Card: eVGA 7600 GT OCed		RAM: 2GB OCZ Performance Gold PC3200
Hard Drive: Maxtor MaxLine III 300GB
Cooling: DangerDen TDX + DD Maze4 + PA160 (radiator)		Case: Antec SX1040BII
PSU: SeaSonic S12-500 500W
Audio: Audigy 2 ZS		Mouse: Logitech G7 SE
Optical drives:
Monitors: Sceptre X20G-Naga III + Dell P992
Reply with Quote
keto
SM22 Host
keto
1,829 Posts
8 Jan 2004, 6:12am
I'm trying to remember and going to do some research....but it seems to me that when you hit 200 fsb you turn on the 1:6 PCI divider. If that is correct (I may have dreamt this, it's late heh.), you would be overclocking your PCI bus anywhere in the range 167-199 fsb, using a 1/5 divider. Thus, at 198 fsb, your peripherals are running at 39.6 PCI bus instead of the intended 33.3, possibly causing problems with things like HD's, CD's, LAN, audio, and so forth. If I'm right, when you hit 200 the divider becomes 6 instead of 5 and thus 200/6=33.3, back in spec. So, going straight to 200 may be fine wheras 199 is a problem.

One more thing, if I am right, and if your HD's don't like 39.6 PCI bus, you may have already corrupted your nice fresh OS install. Aren't I just full of....good news?

I'll try and google this but I'm not sure how to word the search....
__________________ i'D rAthEr HAvE a fULL bOttLe iN fRonT oF ME tHan a fULL FrONtaL lobOtomy
Reply with Quote
keto
SM22 Host
keto
1,829 Posts
8 Jan 2004, 6:30am
Couple of quick searches have not yielded the info I was looking for ...take a shot at 200 and see if it's the same or not.

1.8 vcore should be fine for the processor, if your max loaded temp is 51C. There are many running 1.85 and higher, though over that you would want more advanced cooling.

Memory voltage (Vdimm) is a topic of some debate. I am of the school of thought that it must be almost impossible to kill memory with stock motherboard voltages. I always run my memory at max available on the systems I overclock, meaning 2.85-2.9v 24/7 for months and months on my 2 current rigs. This is not, however, long term testing and I do not know the answer over a 2-3 yr period. I do know of many overclockers who feed 3.1-3.3v to their memory via voltage modding their motherboards and have not seen a story of someone killing their RAM with voltage - tho I give the standard "YMMV" disclaimer.

In your shoes, I would not hesitate to go to 2.8v or even 2.9v with your memory, see if that helps, then work backwards down to stability. But at 200 fsb/PC3200 it's stock RAM setting and absolutely should run stable at stock volts/SPD timings. Voltage increase should be reserved for seeking tighter timings or overclocked speeds.
Reply with Quote
ngfrazier
Icrontic Convert
ngfrazier
10 Posts
8 Jan 2004, 7:22am
A couple of comments:

To TheSmJ: Yes, I update the BIOS to the latest one, though I kinda wonder if it may handicap OC in some way.

To Keto: Thanks for your suggestions. Concerning the PCI bus speeds, I have read that the PCI bus is locked on the nForce2 boards. (See: http://www.overclockers.com/tips00213/ )

This makes me rest a little easier, though I am still determined to figure out which component is hampering my OC. If I pump enough juice to the CPU (say 1.8-1.9) , should that not force it to hit 2.2 ghz unless it is POS?

BTW, could increasing the northbridge voltage help out (and if so, why)?

Thanks
Reply with Quote
Jimborae
He ain't mad, just English
Jimborae
1,498 Posts
8 Jan 2004, 9:02am
Ok wack the the Northbridge Voltage up to the max (as this will help you attain High fsb speeds) I think the max is 1.9v but I could be wrong.

The AGP frequency is locked on a NF7-S but the pci bus isn't, that is controlled by the divider which for 200+ fsb should be set to 6:6 or anything that gives a 1:1 ratio eg 4:4 or 1:1.


Regards

Jim
Reply with Quote
Mt_Goat
Relentless Pursuit
Mt_Goat
4,973 Posts
8 Jan 2004, 10:14am
Default NB voltage is fine to around 225fsb. Raising it will only increase the NB temp and make things less stable and is one of the common mistakes people make. I would try going up to 1.875 as the limit for trying to run a 2500 Barton @ 200fsb with the default mulitplier. As long as the idle temp can stay below 45C and full load less than around 53C I would say it will be good to go.
__________________ I met 2 woman in a bar and they said that every good politician needs to start their career with a scandal. Then one of them told me that they were the best of friends and did everything together! So mount up cowboy!
This is a true story that happened in Bowie, Maryland last winter.
Reply with Quote
Jimborae
He ain't mad, just English
Jimborae
1,498 Posts
8 Jan 2004, 10:21am
Quoting mtgoat
Default NB voltage is fine to around 225fsb. Raising it will only increase the NB temp and make things less stable and is one of the common mistakes people make.

mtgoat, I think here its a case of suck it & see cos on mine it wont go above 200 on default voltage and will only get to 210 on max, 215-220 with a volt mod. My previous NF7-s would again had to be raised to get above 200 and on max voltage would hit 234fsb.
Reply with Quote
Mt_Goat
Relentless Pursuit
Mt_Goat
4,973 Posts
9 Jan 2004, 1:04am
Jim, just because you are having a problem doesn't mean everyone is. My board as wel as 3 others I have set-up have all done 220+ with default NB voltage. Next, I will ask why you must be vulgar with me over this??? I see it as totally uncalled for!!!
Reply with Quote
Thrax
Cat Whisperer
Thrax
25,154 Posts
9 Jan 2004, 1:07am
PCI bus is most certainly locked on the nForce2.
__________________ Robert Hallock
Twitter | LinkedIn

CPU: Intel Core i7 920
MoBo: Asus P6T
RAM: 6GB OCZ DDR3-1600
VID: NVIDIA GeForce GTX 275
HSF: Thermalright Ultra-120
Reply with Quote
Jimborae
He ain't mad, just English
Jimborae
1,498 Posts
9 Jan 2004, 8:34am


Mtgoat, err I think something has been lost in translation over the pond, if you're refering to my "suck it and see" comment its not meant to be rude or vulgar. All it means in the UK is that you need to try it to see what result you get, it has no rude connotations over here.... unless one's mind is in the gutter.

Therefore I apologise for any offense caused but I promise you none was intended, I dont do that sort of thing unless under extreme provocation.

Regards

Jim
Reply with Quote
Mt_Goat
Relentless Pursuit
Mt_Goat
4,973 Posts
9 Jan 2004, 9:55am
Quoting Jimborae


Mtgoat, err I think something has been lost in translation over the pond, if you're refering to my "suck it and see" comment its not meant to be rude or vulgar. All it means in the UK is that you need to try it to see what result you get, it has no rude connotations over here.... unless one's mind is in the gutter.

Therefore I apologise for any offense caused but I promise you none was intended, I dont do that sort of thing unless under extreme provocation.

Regards

Jim
Apology accepted as well as offering my own as I was the one who forgot the amount of water between us, thus my lack of latitude in the interpretation. I think 14 hr days are wearing on me!
Reply with Quote
Jimborae
He ain't mad, just English
Jimborae
1,498 Posts
9 Jan 2004, 10:30am


Larry, no problem mate, glad we we got it cleared up, wots that phrase about being seperated by a common language, well I think we just valiadated it.
Reply with Quote
Jimborae
He ain't mad, just English
Jimborae
1,498 Posts
9 Jan 2004, 5:11pm
Quoting Thrax
PCI bus is most certainly locked on the nForce2.

Oopps sorry again, Thrax is right.

The divider just sets the ratio to lock the pci bus at 33MHz, correct??
Reply with Quote
Jimborae edited : 9 Jan 2004 at 5:18pm .
TheLostSwede
Where's the ****ing beers?
TheLostSwede
3,227 Posts
9 Jan 2004, 5:26pm
ngfrazier,

That's still a pretty good overclock that you have. DO NOT use Bios 20. Unstable as grandma on rollerblades. Use Bios 17 if you want a newer bios, or the modded D10 if you want performance (and for me stability). What's the total cpu speed right now?

Weird that your cpu is locked. What happens if you lower the multiplier?
Reply with Quote
keto
SM22 Host
keto
1,829 Posts
11 Jan 2004, 7:50pm
Mack, I've searched around the site but can't find the D10 modded bios file, can you please post or link it? Thx in advance.
Reply with Quote
TheLostSwede
Where's the ****ing beers?
TheLostSwede
3,227 Posts
11 Jan 2004, 8:12pm
Quoting keto
Mack, I've searched around the site but can't find the D10 modded bios file, can you please post or link it? Thx in advance.

Rename the B1 and B4 to .ace.

The EQ bios is the one from EQuito, works very well. I'm currently testing the others. B1 and B4 have totally different menu structure and hidden timings setting which you CANNOT change. The "under 10 multi" bandwidth issue is solved with the B1 and B4 bios it seems. Try them at your own risk. They work for me though.
Attached Files
File Type: zip nf7d_10eq.zip (226.6 KB, 124 views)
File Type: zip NF7D_10b1.zip (222.7 KB, 86 views)
File Type: zip NF7D_10b4.zip (222.7 KB, 85 views)
Reply with Quote
MrBill
Support Our Troops
MrBill
2,138 Posts
11 Jan 2004, 10:07pm
I'm running my NF7-S v2 w/xp2500, SK7 @ 2250mhz. 166x13.5 (cheap ram)


In BIOS:
vCore - 1.85
vDDR - 2.7
chipset - 1.7v

ABIT EQ:
vCore - 1.8
vDDR - 2.7

Haven't really tried to go any higher since it's stable at this speed.
Attached Thumbnails
Click image for larger version Name: abit_eq.jpg Views: 795 Size: 86.7 KB ID: 5338   Click image for larger version Name: wcpuid_2250.jpg Views: 796 Size: 66.8 KB ID: 5339  
__________________ "Hello World"....and so it began.
[RIP Icrontic10]
Reply with Quote
Straight_Man
Playing with Virtual Painter
Straight_Man
3,717 Posts

» Subscriber

11 Jan 2004, 10:22pm
Where we in America would say sip they can and do say suck (seems to go with British or Samual Adams Ale better (with a good head on it, of malt and alcohol suds, draft, FRESH), while sip they use for VERY VERY hot tea, right, Jimborae??).... "Try a bit at a time and see what happens for you" would be cool for both sides, maybe.....

John.
Reply with Quote
Thrax
Cat Whisperer
Thrax
25,154 Posts
11 Jan 2004, 10:26pm
WTF are you talking about? My god...
Reply with Quote
Jimborae
He ain't mad, just English
Jimborae
1,498 Posts
11 Jan 2004, 11:11pm



Quoting Ageek
Where we in America would say sip they can and do say suck (seems to go with British or Samual Adams Ale better (with a good head on it, of malt and alcohol suds, draft, FRESH), while sip they use for VERY VERY hot tea, right, Jimborae??).... "Try a bit at a time and see what happens for you" would be cool for both sides, maybe.....

John.
Well that certainly brought a smile to my face . Urm not quite but nearly John.

I certainly would'nt recommend replacing the word sip with suck in most situations when talking to us British as generally we do use "sip" in most of the same situations as you guys do.

However ,the phrase "suck it & see" has been around for "donkey's years" and has been used in everything, from advertising indegestion tablets to try before you buy offers. But essentianly Ageek's sentiment is correct.

I just, naively, assumed that as its in common language over here it would be the same, and mean the same for you guys.

Apologies for going off topic yet again.

Jim
Reply with Quote
Preacher
Contentious Cajun of the Cloth
Preacher
1,286 Posts

» Subscriber

12 Jan 2004, 4:12am
For what it's worth, Jim, we use the same phrase in the US Navy quite often. I would imagine at some point we picked it up from our Royal Navy allies.

Back on topic, I may be switching to Equito's D10 BIOS. I'm currently using his modified 20 with the SATA drivers and as far as I know it I don't have any stability issues. I'm currently running a 2500+ at 215 FSB on a 11x multiplier for 2365 Mhz in a Koolance system.
Reply with Quote
ngfrazier
Icrontic Convert
ngfrazier
10 Posts
12 Jan 2004, 6:09am
I just wanted to thank all of you for your suggestions and responses. The solution seems to be to raise the Vcore to 1.9v! Unfortunately, this heats the CPU up to 49C idle and 57-59C under load.

As for the other components...
Memory was not holding it back: I tested the memory for errors--it was clean. Next, I set the Proc at default settings (166 FSB) but set the mem async. to 200FSB--it was stable. I then set it higher to about 414 MHz and it was still stable during Prime.

I also tested the Northbridge under default and boosted voltage. Though this is more difficult to test, I have come to the conclusion that you should not increase voltage to the Northbridge (beyond about 1.6v) unless you plan on running beyond stock (like 200+ FSB for Bartons and 133+ for Palominos). The reasoning is to reduce the heat, since once the Northbridge heats up, it will sometimes become flaky.

In conclusion, it seems that I got a POS Barton 2500+, whilst everyone and their grandma got 2500+ Bartons that do 3200+ with little to no Vcore boost. Ah well...

My last concern is twofold:
1) Is a Vcore of 1.9 too high for my Barton 2500+?
2) What temps are too high (59C too high a temp under load)?

Thanks
Reply with Quote
Preacher
Contentious Cajun of the Cloth
Preacher
1,286 Posts

» Subscriber

12 Jan 2004, 7:25am
For comparison, my 2500+ temps (215x11.0 with 1.712 volts) are 40c idle and 44C under load. 59 sounds WAY high for any type of stability.
Reply with Quote
Jimborae
He ain't mad, just English
Jimborae
1,498 Posts
12 Jan 2004, 8:16am
NG, wot type of fan are using with your alpha pal heat sink. Is it a low speed, low noise one? If so then that would explain your high temps. Something like a Delta fan that pushes a lot of air would do but the trade off is noise.

Also for comparison, my temps on my second rig are very similar to yours when running that kind of volage but then i'm using a low speed, low cfm fan.

regards

Jim
Reply with Quote
TheLostSwede
Where's the ****ing beers?
TheLostSwede
3,227 Posts
12 Jan 2004, 6:46pm
Quoting ngfrazier
I just wanted to thank all of you for your suggestions and responses. The solution seems to be to raise the Vcore to 1.9v! Unfortunately, this heats the CPU up to 49C idle and 57-59C under load.

As for the other components...
Memory was not holding it back: I tested the memory for errors--it was clean. Next, I set the Proc at default settings (166 FSB) but set the mem async. to 200FSB--it was stable. I then set it higher to about 414 MHz and it was still stable during Prime.

I also tested the Northbridge under default and boosted voltage. Though this is more difficult to test, I have come to the conclusion that you should not increase voltage to the Northbridge (beyond about 1.6v) unless you plan on running beyond stock (like 200+ FSB for Bartons and 133+ for Palominos). The reasoning is to reduce the heat, since once the Northbridge heats up, it will sometimes become flaky.

In conclusion, it seems that I got a POS Barton 2500+, whilst everyone and their grandma got 2500+ Bartons that do 3200+ with little to no Vcore boost. Ah well...

My last concern is twofold:
1) Is a Vcore of 1.9 too high for my Barton 2500+?
2) What temps are too high (59C too high a temp under load)?

Thanks
Nah...2 volt works well with stock cooling, just exchange the goop to AS3 or AS5. However, you dont need more than 1.6 up to 220 fsb anyway. Also, the NB doesn't put out much heat at all. 207 is still not a bad overclock at all. Default multi is 11 right? Run it at 200X11 (SYNC) and lower the vcore to 1.85. I bet it's stable.
Reply with Quote
Degarmo
New to the neighborhood
Degarmo
3 Posts
20 Jan 2004, 6:11am
I have had the same problems with a recently boaght 2500+ Ngfazier. I have decided it is the cpu it's self. I have had 2 other chips a 3000+ and a 2500+ in this mobo (NF7-s) and no problems at all OC'ing. Same memory same settings. Some chips just aren't good overclockers and some are... Thats my viewpoint. But, with that said... If you solve this problem please let me know because I would be very intersted!
Reply with Quote
Degarmo
New to the neighborhood
Degarmo
3 Posts
20 Jan 2004, 6:19am
Hmmm? 1.9Volts just to go 200fsb? Man thats nuts. I never upped mine past 1.7 during testing .. I thought geeze it's only 33Mhz?? The board containing the cpu that has problems like yours is in my V1.0 board... I can only go as high as 1.85vcore on it... I guess I will try it and see if I come up with the same findings as you. Geeze it sounds like I might need that extra .05 volts lol
Reply with Quote
GHoosdum
tequilavangelist
GHoosdum
10,638 Posts
20 Jan 2004, 11:08pm
I had a similar issue with a 2500+ I had - I got rid of it quickly, and I'm now running a Mobile Athlon XP 2400+ (Barton Core) at 2300MHz, 11.5x200, 1.75VCore, with no problem. It might actually be capable of running 2.3GHz at a lower VCore, but I haven't, eh, 'sucked it to see' yet...
__________________ Is it true it's always happy hour here?
If it is I'd like to stay a while...
Reply with Quote
Jimborae
He ain't mad, just English
Jimborae
1,498 Posts
20 Jan 2004, 11:23pm
Quoting GHoosdum
I had a similar issue with a 2500+ I had - I got rid of it quickly, and I'm now running a Mobile Athlon XP 2400+ (Barton Core) at 2300MHz, 11.5x200, 1.75VCore, with no problem. It might actually be capable of running 2.3GHz at a lower VCore, but I haven't, eh, 'sucked it to see' yet...

Yeah, yeah, go on take the mickey for my "faux pas"
Reply with Quote
speed_x
Icrontic Technician
speed_x
52 Posts
8 Feb 2004, 7:03am
Hi..speed_x here!
Hi all, I'm new at the forum...here is my 2 cents

Check out this article:
http://www.sudhian.com/showdocs.cfm?aid=307

Hope it helps
Reply with Quote
speed_x
Icrontic Technician
speed_x
52 Posts
8 Feb 2004, 7:07am
Hi..speed_x again!

The chip you've got is a good overclocker (AQZEA) you shouldn't need more than 1.7 volts, your voltage is very high just for 200 FSB.
Reply with Quote
speed_x
Icrontic Technician
speed_x
52 Posts
8 Feb 2004, 7:18am
Quoting ngfrazier
I just wanted to thank all of you for your suggestions and responses. The solution seems to be to raise the Vcore to 1.9v! Unfortunately, this heats the CPU up to 49C idle and 57-59C under load.

As for the other components...
Memory was not holding it back: I tested the memory for errors--it was clean. Next, I set the Proc at default settings (166 FSB) but set the mem async. to 200FSB--it was stable. I then set it higher to about 414 MHz and it was still stable during Prime.

I also tested the Northbridge under default and boosted voltage. Though this is more difficult to test, I have come to the conclusion that you should not increase voltage to the Northbridge (beyond about 1.6v) unless you plan on running beyond stock (like 200+ FSB for Bartons and 133+ for Palominos). The reasoning is to reduce the heat, since once the Northbridge heats up, it will sometimes become flaky.

In conclusion, it seems that I got a POS Barton 2500+, whilst everyone and their grandma got 2500+ Bartons that do 3200+ with little to no Vcore boost. Ah well...

My last concern is twofold:
1) Is a Vcore of 1.9 too high for my Barton 2500+?
2) What temps are too high (59C too high a temp under load)?

Thanks
The stepping you've got is one of the best for overclocking!
Go slow and re-check all your settings.
I hope you're not using the nvidia SW drivers? Use the default IDE drivers, SW are not good in all cases. Again, read the article from Sudhian Media, here's the link:http://www.sudhian.com/showdocs.cfm?aid=307

Bartons run best with memory in sync. Your voltage is way too high, you shouldn't need more than at most 1.725 for 200 x 11

speed_x
Reply with Quote
Spinner
Getting it done!
Spinner
5,003 Posts
8 Feb 2004, 10:18am
speed_x, welcome to Short-Media. You have the honour of being our 1000'th member. Congrats and thanks for joining.

Spinner

(please carry on the tech talk now)
__________________

Wedding Band - Junction 2
Reply with Quote
Degarmo
New to the neighborhood
Degarmo
3 Posts
8 Feb 2004, 3:25pm
Sounds like the first thing one should do nowdays is cut the L12 bridge to a 166 barton. I did this to my first cpu and lost 384k L2 Cache. I must have cut to deep. While trying to rejoin the bridge I killed the cpu. I now have another 166 barton with same 11 X 200 no boot problem. I'm not cutting the bridge again, because this one will at least run over 200Mhz at a lower multiplier. 228 X 9.5, since NF7-S have lost 10 and 10.5 multis with cpu interface enabled.
Reply with Quote
speed_x
Icrontic Technician
speed_x
52 Posts
8 Feb 2004, 4:35pm
Hi, thanks Spinner!
It's great to be here and even better to be the 1000th member!
ngfrazier, how is it going with the Barton 2500?

I've found that if you let your hardware "wear in" and get used to each other that it will give you better overclocking. I've overclocked a Barton 3 Ghz with default 166 fsb, a 2500 AQXEA Barton and a TB "B" core DLT3C JIUHB. When I review my settings I've been able to get more performance. This holds for all 3 motherboards I have: 8RDA+, NF7 and A7N8X Del (As an aside, the 8RDA+ and the NF7 do much better than the A7N8X). Sometimes, I'm hostage to my creative urges and I overlook things that should be obvious.

My need for overclocking is for video encoding; I didn't want to wait any longer..I wanted 2 pass DivX encoding in real time or better. I took the Barton 3 Ghz (13 X 166) with an SLK-900U h/s and the NF7 and replaced the NB h/s, lapped the CPU h/s, put a passive h/s on the SB, cut a 120mm blowhole on the top of the case, (2 )90mm holes on front and rear and a passive air intake hole on the case in front of the CPU, leading to the Vantec 92mm (more on this beast!) through a double Mylar insulated channel always feeding the CPU cool exterior air, not re-cirulated hot air. I also cut the 3rd L12 bridge on the CPU to drop the default fsb to 133 Mhz !!!

It took me most of last summer to play around with many fans, heatsinks, etc. and it was ready to fly! All my work was rewarded with 2 pass real time DivX encoding! Final settings 194.19 X 13 =2524 Mhz @1.875 Vcore using the NF7!

About the Vantec Tornado 105cfm fan: it's very, very loud! The minute I started the computer (and heard it!) I ran out the door to get a voltage regulator for it. I mean the thing sounds like 10,000 screaming Banshees! Funny, some of the OCing sites never mentioned this painful fact!

So there, that's the complete story of how I got into OC'ing! The good results come from knowing that it's an ongoing process more so than a final destination.

Yours,

speed_x
Reply with Quote
speed_x
Icrontic Technician
speed_x
52 Posts
8 Feb 2004, 5:08pm
Quoting Degarmo
Sounds like the first thing one should do nowdays is cut the L12 bridge to a 166 barton. I did this to my first cpu and lost 384k L2 Cache. I must have cut to deep. While trying to rejoin the bridge I killed the cpu. I now have another 166 barton with same 11 X 200 no boot problem. I'm not cutting the bridge again, because this one will at least run over 200Mhz at a lower multiplier. 228 X 9.5, since NF7-S have lost 10 and 10.5 multis with cpu interface enabled.
Many CPU's will hit 200+ fsb with no problems however, mine didn't 'till I cut the 3rd L12 bridge. It took me 2 days of thinking and fretting...did I want to roll the dice? So far, I've done it to 3 Bartons and had good results. All it takes is 1 or 2 very gentle passes with a sharp blade.

Another method I've read about is to touch both ends of the bridge with the leads from a 12 volt battery. According to the person that posted this method (I contacted him) the overvoltage just burns the bridge and doesn't do harm to the rest of the CPU.

The best thing to do is to research, have all the proper tools and take your time. Wait 'till you feel more confident about what you're doing!
Reply with Quote
ivorycruncher
New to the neighborhood
ivorycruncher
4 Posts
11 Feb 2004, 3:17am
Hi. I've been browsing through this thread, trying to figure out how to tweak my own system. I've got an Athlon 2500+ (locked multiplier) in a Biostar M7NCD Pro mobo with an nForce2 (SPP/MCP) chipset and 2x256MB sticks of Kingston CAS2.5 DDR400 in a dual-channel DDR config. I'm using the retail heatsink that comes with the 2500 (crappy one, I know) but it's been hanging around 46-47 C under normal load. I've been running at default BIOS settings for about 2-3 weeks now, and I decided to try overclocking after hearing about everybody under the sun pumping the 2500 up to 2300 speed.

I pumped up the FSB speed incrementally, starting with bumping 166 to 170, and then 5MHz increments from there. I managed to get up to 190FSB without stability problems (I increased the Vcore to 1.7-1.725 along the way for good measure). When I tried to go to 195, Windows failed to even show me the XP boot logo. I tried both 193 and then 192 at various Vcore voltages. The closest I came to being stable is 192 at 1.75-1.775 Vcore (haven't tried 1.8 yet). Windows loaded and ran a SiSoft Sandra CPU burn-in test successfully, and then it blue-screened when I attempted to load another program.

I'm trying to figure out what's holding it back. Is it the heatsink (still holding around 46-47C idle)? Is it the Vcore? Is it the memory timings (currently 2.5 2 2 7)? Or is it something a little more obscure like the PCI bus speed mentioned earlier? I'm afraid to try too much more because if I kill this CPU, I'll be back to my old 1700 because I can't afford another 2500 right now. Any suggestions would be greatly appreciated.
Reply with Quote
Jimborae
He ain't mad, just English
Jimborae
1,498 Posts
11 Feb 2004, 4:02am
What is the divider set too? I'm not familiar with that board so I don't know whether it has an auto setting or whether you have to change it manually but it sounds like you may need to change it. But because your multiplier is locked you may have just reached the limit of your cpu speed. If you could unlock it then you could lower the multiplier a notch or two and carry on raising the fsb but that doesn't appear to be an option.

Also its highly unlikely you'll kill your cpu through playing with bios settings,the worst that will happen is that it wont boot & you have to reset the cmos.
Reply with Quote
speed_x
Icrontic Technician
speed_x
52 Posts
11 Feb 2004, 10:55am
Quoting ivorycruncher
Hi. I've been browsing through this thread, trying to figure out how to tweak my own system. I've got an Athlon 2500+ (locked multiplier) in a Biostar M7NCD Pro mobo with an nForce2 (SPP/MCP) chipset and 2x256MB sticks of Kingston CAS2.5 DDR400 in a dual-channel DDR config. I'm using the retail heatsink that comes with the 2500 (crappy one, I know) but it's been hanging around 46-47 C under normal load. I've been running at default BIOS settings for about 2-3 weeks now, and I decided to try overclocking after hearing about everybody under the sun pumping the 2500 up to 2300 speed.

I pumped up the FSB speed incrementally, starting with bumping 166 to 170, and then 5MHz increments from there. I managed to get up to 190FSB without stability problems (I increased the Vcore to 1.7-1.725 along the way for good measure). When I tried to go to 195, Windows failed to even show me the XP boot logo. I tried both 193 and then 192 at various Vcore voltages. The closest I came to being stable is 192 at 1.75-1.775 Vcore (haven't tried 1.8 yet). Windows loaded and ran a SiSoft Sandra CPU burn-in test successfully, and then it blue-screened when I attempted to load another program.

I'm trying to figure out what's holding it back. Is it the heatsink (still holding around 46-47C idle)? Is it the Vcore? Is it the memory timings (currently 2.5 2 2 7)? Or is it something a little more obscure like the PCI bus speed mentioned earlier? I'm afraid to try too much more because if I kill this CPU, I'll be back to my old 1700 because I can't afford another 2500 right now. Any suggestions would be greatly appreciated.
I had the same problem with a couple of my Barton 2.5's and I cut the 3rd L12 bridge and was able to go above 200 FSB. Many folks report not being able to go above 190-195 FSB on Bartons. Look for the Sudhian Media link on some of my previous postings, it's got a good article on cutting the L12 bridge. Some Bartons refuse to run above 190-195 Mhz, period! I have a 3000 that has never ran dependably over 195 WITH the L12 cut! The luck of the draw has a lot to do with it. Not all Bartons are the same.

BTW, the best utility I've found for testing is Prime95. If your computer will run it overnight, it will just about run any other benchmark. I don't think too much of the Sandra burn in utility. Your memory setting seems OK; I think if you stay under 1.9 Vcore you'll be OK. I've read 1.9+ Vcore is considered burned CPU danger zone.

If after doing all that you can the CPU fails to run beyond 192 or so, then use the best memory timing for that FSB, knowing that's all you can get!

If later on you'd like to get a good OCing CPU, look to buy a good stepping like AQXEA or AQZEA.

speed_x
Reply with Quote
ivorycruncher
New to the neighborhood
ivorycruncher
4 Posts
12 Feb 2004, 5:06am
Well, this is the first time I've ever attempted overclocking. Some of these things like memory timings and AQXEA and whatever mean nothing to me. If you could fill me in a little, or point me to some good "overclocking basics" FAQs, that's be great.

In response to Jimborae, do you have any idea where that setting might be in an Award BIOS? I don't recall seeing anything like that in the Advanced Chipset Features where I was playing with the FSB and memory timings. If I can find such a setting to change, what do I change it to?
Reply with Quote
Page 1 of 2 1 2
Similar Threads
Thread Thread Starter Forum Replies Last Post
September 23: AMD Athlon 64 Launch Day SimGuy Tech Articles 9 23 Sep 2003 9:39pm
AMD, HP & a Athlon XP 2.33ghz (3200+)?!? Omega65 Tech Articles 1 3 Sep 2003 11:46am
CPU News & Reviews (Around the Web) Omega65 General Hardware 7 26 Aug 2003 5:02pm
AMD to ship Athlon 64s as Athlon XPs Spinner Tech Articles 11 23 Aug 2003 8:01am
Apple G5 Benchmark Controversy Continues.... Omega65 Tech Articles 8 30 Jun 2003 7:14pm

Go Back   Icrontic Forums > Tech: Hardware > Overclocking
Reload this Page HELP! NF7-S cannot overclock Athlon 2500+ to 3200+
Jump to
This Thread Search this Thread
Search this Thread:

Advanced Search

Today's Posts - Mark All Read - Contact Us - Icrontic.com - Archive - Top

Current time: 3:51am (GMT)
Powered by vBulletin®
Copyright ©2000 - 2010, Jelsoft Enterprises Ltd.
Get Vanilla Forums instead. Trust me.