XP2500+ hit its ceiling?
I finally got a decent fan to put on my Primary's SLK-900A, a ~60 CFM Enermax 92MM unit. Even with 60 CFM though, this processor is only doing 2.2GHz (200x11) at 1.875 VCore and running at 48C. That's too much for me, and it hard-locks at 200x11.5 - any suggestions?
0
Comments
Do you have the stepping of the chip?
The memory is not a factor, except that in order to run synch I can't go more than 200 FSB because it's PC2700 RAM, But when I first OC'd the Barton I was running the RAM at stock PC2700 speed.
Funny thing is, this same chip was stable at 2.2GHz at 1.825v on the old DFI board I had, with the same PSU. Still, I'm rather disappointed in this chip since my XP2100+ cranks away all day at 2.3 GHz at a cooler temp at lower VCore and 10 less CFM on an SLK800A...
Tried re-seating the SLk900?
Yes, it's a weak 2500.
I'm using whatever version of BIOS shipped with the mobo... will a newer BIOS affect the OCability though?
Yes a new bios will. Also change the timings to 11/3/3/2.5 should help with bandwith.
I'll update the BIOS and see what that does for me.
Optimal is 2/2/2/11.
bwahahaha!
So I shouldn't be trying to set that thing at 6??? Hmmm, I'm with Ghoosdum here. Should I leave mine though if I'm doing 2/3/2/6??
Period.
Fill in the Xs with whatever else your RAM is capable of doing. Be it 2/3/2, 2/2/2, 3/3/3, 2.5/3/3... Just end in 11.
Will it work on any speed DDR? I'm at 2-2-2-5 @ 400, because my Cpu is running at 200x11. I've finally decided to try to get a little more out of 2500+a7n8x, since it's been quite stable these past few weeks.
Lets say I were to reach 217x _ , should I stick with Corsair's recommended 2-3-3-7?
This works on any DDR module in existence.
2 just sealed it.
Going to test it now
axda2500dkv4d
aquca 0323tpmw
And it's #231 in the batch
If not, I'd say that you just have a really rotten chip.
Since my primary has no floppy drive, would you guys recommend using Abit's GUI BIOS tool for the update?
I swear by it.
Now, of course, the next person that uses it is going to fry their BIOS...
Maybe it's time to look elsewhere; but I wouldn't get worked up over finding another culprit, you might have just gotten a worse-off one.