XP2500 Overclocking results?

[ukiro]

There's a high probability that that's a driver issue, but with prime95 erroring out, there is a pattern starting to emerge... make sure you've got directX of the required version, up-to-date video drivers and all that. If it still won't run, then RMA the thing...

I feel sorry for you man...

 

[chizow]

Hmm problem sounds like its between your CPU and your RAM. RAM passed memtest so its probably RAM settings or the NB memory controllers not taking to the Barton. From what I've seen and read the Barton stresses the NB subsystem harder than the T-bred B's.

Update to the latest BIOS if you haven't already, or check out the MSI forums over at AMDMB.com or nForcersHQ to get an idea of what 2500+ Barton users are using. I'd try relaxing your timings in your BIOS. Make sure you're running the FSB/memory synchronously or 100%. I'd also change the CPU and/or Memory interfaces (not sure what's in there for KT400) to optimal if you have any set to aggressive. Try increasing Vdimm to 2.7V as well. You shouldn't have to notch up your Vcore, but try raising that .05V, as I've found this chip to be hot and hungry. Disconnect, remove any non-essential components that could be stressing your PSU. This chip seems to have a lower fault tolerance than the T-bred Bs when it comes to voltage fluctuations.

Chiz

 

[ukiro]

yours is from the week before mine. chizow has one just like yours, and I saw you had been in his thread too. make suer you have the proper drivers and directX for BF1942. if it still won't run, try other apps/games too. if you're getting any more crashes and odd behaviour, I'd RMA.

 

[Jeff7181]

Well, I played SoF2 for about 15 minutes, no problems... ran 3DMark2001 about 3 times... ran PCMark2001 twice... no errors in those.

I've had some bad experiences with EA in the past (Motor City Online in particular) but I haven't heard about any major problems with BF1942... I'm looking over some message boards now... also running Prime 95... gonna see how long it takes for it to error out again.

BTW... all my drivers, Direct X, and BIOS are the most up to date versions. Never had problems like this before. I'm getting a 2nd stick of PC2700 RAM tomorrow, so I'll stick that in and see if I get the same problems.

 

[Jeff7181]

By the looks of BF1942 message boards... this isn't because of my CPU. BTW... I reset CMOS to get everything back to defaults (in case I forgot what default REALLY is) and set everything to auto except the FSB, because that defaults to 100... on Test 20 in Prime 95 with no errors so far.

 

[Jeff7181]

Been running Prime 95 continuously since my last post, no errors.

 

[chizow]

Originally posted by: Jeff7181
Been running Prime 95 continuously since my last post, no errors.

Cool :beer:

Once you're satisfied with stability at default, you can your luck at OC'ing again. I would leave everything at defaults other than Vcore and Vdimm adjustments when necessary as you increase your FSB or lower your multiplier. Once you've reached a clockspeed you think is stable, then try tweaking your timings and settings.

Chiz

 

[Jeff7181]

I've about had it with EA products... looks like there's LOTS of issues with BF1942... I look at the tech help section of the SoF2 boards, and I see people asking how to get better frame rates... I look at BF1942 and see people asking how to get the game to work AT ALL. EA's all run out of Canada now... maybe that's the problem (no offense to Canadians )

 

[Jeff7181]

Must have been a RAM timing settings that I hadn't set back to default... cause I'm at 2.083 Ghz again and running Prime 95 for 15 minutes with no errors.
Thanks for the help guys. Oh yeah, someone helped me with BF1942 also. So I'm happy again

 

[salamanzer]

Lo, Jeff

Sounds like you have been having a good time with your barton system

But im glad you have it sorted now

Im starting to get well annoyed with my Barton Will not go over 2650, damm - i needed the extra cache for games benchmarks like Madonion 2001 SE - gutted I have a nice oc'd graphics card now but i cannot get over 20K errr bloody Barton.

Oh well - when the 3100+ comes out maybe they will get better - untill then - i think i may just put my old 2700+ back in (because it runs happy at 2.8Ghz+)

With the Nforce mobos - the barton will revert back to some strange multis when using 12 and 12.5 - all you need to do is go back into bios and save again - this should sort out the problem

Gonna get a multimeter today - gonna do the VDD mod - the FSB will help the barton a lot i think

Jason

 

[Jeff7181]

Actually... it's not stable at anything above 11.5x166. I have my nForce2 board now, A7N8X, and it does better than with the KT4VL, but I can't get a decent overclock AT ALL. I've tried using conservative RAM timings and all that... tried backing down the overclocking on my video card. I'm at a loss... I don't know what else to do. Increasing Vcore doesn't do anything... I can't even get it to run 12x166 with 1.750 volts... it always locks up in games... white screen, then it reboots. Maybe it's my bargain RAM... but I don't know... I don't get any errors in Prime 95... I've run Memtest and the RAM checks out fine... you wouldn't think just raising the multiplier would cause the RAM to screw up, so I don't know what the deal is.
It's running 33 C idle, and I believe 38 under load... so it's not a heat issue. I'm starting to wonder if it's an issue with my power supply... it's an Antec 350 watt that came with my Performance II Workstation Tower. If I raise the speed of the CPU, or the video card, I get those crashes. Oh well... I'm happy with the performance of it... just a little disappointed I can't get it to overclock any better than this.

 

[salamanzer]

Geeze - 166 x 11.5 = 1909

Thats bad - on a nforce2 mobo as well Im running my RAM at 7 3 3 2 - it will run at 2 2 2 2 at 215FSB ummm 1.750 volts - its a little low for a barton - becuase of the extra cache - they make very bad overclockers - increasing the multi should not affect the memory at all so thats not the problem !

Do any of your friends have a better PSU you can borrow ?? I run a 550W so Amps aren't a problem for me have to tried just increasing the FSB ? Does it still crash ? Just try a little more Vcore - im having to run mine at 2.06V !!

Jason

 

[Jeff7181]

Strangely enough I'm the only one in my little group of friends who tinkers with computers. The rest of them use them, but always have me build them one... and all they do is use it for music and porn and games... they don't care about the hardware aspect of it.

I was thinkin my next upgrade would be a video card to replace my Ti4200, but now I'm thinking, maybe I should invest in some quality RAM for once =)

 

[Jeff7181]

Well, after reducing the overclock on my video card to 250/500 I'm able to get 2.2 Ghz (200x11) out of this XP2500 @ 1.7 volts. Looks like my video card didn't like being overclocked that much with this CPU. I got it to 2.3 Ghz at 1.825 volts... but I don't like the idea of running it that high... so I'll settle for 2.2 =) Temps were well within safe zones, but I'd rather not push the voltage that high for long periods of time.
Still can't increase the RAM timing at all, but as you can see from my benchmarks, it's not hurting anything =)

 

[Shimmishim]

in order to reach over 200 mhz on the fsb, do you have to cut the L12 bridge?

 

[Jeff7181]

My A7N8X lets me set it up to 211 Mhz without any modifications.
However, I decided to set the FSB back to 166, and the multiplier at 12.5 because my RAM won't run at 200 Mhz so I had to run it a-sync to get the FSB to 200... and it felt sluggish when I had it like that, probably cause it was wasting clock cycles waiting for the RAM. So... I'm back at 2.083 Ghz (Barton XP2800) Maybe I can give my video card a little more now that I've backed off the CPU OC.

 

[boyRacer]

Cooool... looks like 3000+ is a guaranteed clock on a 2500+... I'll be happy...

 

[Jeff7181]

Originally posted by: boyRacer
Cooool... looks like 3000+ is a guaranteed clock on a 2500+... I'll be happy...

Yeah, if you can't hit 2.08 Ghz with an XP2500, send it back and get a new one =)