OC'ing Athlon, where do I need help?

[jedcred]

System Specs are:

MSI K7N2 Delta-L
Athlon XP 2600+ w/ 512 L2 cache (original speed 1.9Ghz, current speed 2.19Ghz)
2 x 512 Corsair Value Select Memory Dual Channel VS512MB400
450W PSU

FSB speed - 190 Mhz (doubled to 380 effective)
T (RAS) 7
T (RCD) 3
T (RP) 3

CPU Voltage: 1.675
DDR Voltage: 2.7

CPU Average Temp: 49C

Unfortunately I'm not able to get the FSB up any higher to get to 200 Mhz (400 effective). Any advice, or want any other information?

Thanks in advance.

 

[TheStu]

You may want to put a little more voltage thru the RAM, I assume the RAM is PC3200? If it is then a little more voltage may be required to bring it up to stock speeds, I would neccesarily recommend going much further than 200 on the Value RAM though.

Does your board support dual channel? If yes, is your RAM set for Dual Channel?
What is your CAS Latency?
By average do you mean idle? (i.e playing solitaire, or music....)

Your VCore looks good on your chip, maybe a little bump higher, but if you are stable you shouldn't worry about it.

 

[jedcred]

The board does indeed support dual channel, and the memory is on DC.

The memory timings are 2.5-3-3-7, so the CAS should be 2.5 (from what I understand).

By average I mean that it idles at 47-48 and loads at 52-53.

Unfortunately it looks like I can't increase the voltage above 2.7. Does anyone know about a modified BIOS that would allow this?

I don't think the problem is with any of the PCI cards because the FSB is locked on the PCI, so there shouldn't be a problem there.

I thought I should be able to go higher than 200 with Value RAM too; that's why I posed this question, unless others have been getting dismal performace from Corsair Value RAM.

Maybe I should relax the timings to 2.5-3-3-11? That's what I saw from one other Corsair Value user.

 

[TheStu]

realxing the timings might not be a bad idea... what is the FSB CPU Ratio? Those temps are okay if you are running stock cooling... in all honesty you should be able to hit 200 MHz, however I am not p to spec on MSI boards so....

 

[Elcs]

Originally posted by: jedcred
I thought I should be able to go higher than 200 with Value RAM too; that's why I posed this question, unless others have been getting dismal performace from Corsair Value RAM.

Maybe I should relax the timings to 2.5-3-3-11? That's what I saw from one other Corsair Value user.

If it says it does 200 and it doesnt, then its RMA time... but keep at this a little while so we can see if somethings wrong. People here know what they are doing most of the time and will be happy to help.

I googled up your motherboard and it supports 200mhz FSB's so that isnt the problem.

It is also based upon the Nforce2 chipset. Results show that Nforce 2 boards prefer the end number to be 11 (whichever that one is)... so 2.5-3-3-11 would provide very slightly better performance than 2.5-3-3-7.

PCI/AGP locks.... Id make sure you are using them. It sometimes causes problems, a longshot but possible.

 

[Fern]

I wouldn't be so sure that your ram is holding back the OC. It s/b able to handle a FSB of 200, that's what its spec'd for. I've used Corsair Value Select pc3200 and it didn't have a prob running at FSB 200.

If you DO suspect the ram, instead of jacking up the vdimm willy-nilly, first run memtest86 to make sure the ram is the problem. No need to jack up voltage and increase temps unneccessarily.

I'd be more inclined to suspect the cpu, it prolly needs more vcore. Test it with Prime 95.


There are BIOS changes to made which can help OC, but at only FSB 190 I can't imagine that holding you back either.

Basically, There's cpu, chipset and ram. The only one you have not spec'd for FSB 200 is the cpu. I'd look there.

Fern

 

[jedcred]

I have been checking stabilty first with Memtest86, and when I used to go over 190 with 2.5-3-3-7 and 1.675 vcore, it would give memory errors. Now I'm running at vcore 1.7 with 2.5-3-3-11 and it seems to be passing the memtest. I'm going to stress test all day today and get back to you guys tonight. I'll also try higher vcore settings.

Thanks so much for your help so far.

**UPDATE**
The computer passes memtest at 195 with vcore 1.75 and 2.5-3-3-11. However, the memtest crashes (note, freezes, not gives errors) at 57% at 200. Just thought you'd like to know.

 

[jedcred]

I was burning-in with Sandrasoft at 195 with vcore 1.75 and 2.5-3-3-11, and I got a memory error inside Windows (Application Error: Memory at xxxx could not be read) although Memtest86 passed. My guess would be memory. However, the memory does function OK most of the time. Any advice as to figure out which module is worse/bad?

 

[Fern]

Originally posted by: jedcred
I was burning-in with Sandrasoft at 195 with vcore 1.75 and 2.5-3-3-11, and I got a memory error inside Windows (Application Error: Memory at xxxx could not be read) although Memtest86 passed. My guess would be memory. However, the memory does function OK most of the time. Any advice as to figure out which module is worse/bad?

Yeah, just pull one stick and test individually at a time.

If bioth sticks individually pass, I'd still think cpu (up vcore another notch maybe, or be happy @ 190 or whatever)

How are the temps at 1.75 vcore?

Fern

 

[jedcred]

The load temp of the processor at 1.75 is about 55C. I was thinking about testing each individual stick, but I'm wondering if this problem may be coming from the dual channel nature of the setup. Any experiences where dual channel doesn't help?

 

[Fern]

Another thought. Assuming your mobo provides for ram dividers, you could run your ram at FSB 200, while keeping the cpu @ 166. Then test it with memtest86. You wouldn't wanna run a AMD in asynch mode, but for testing spurposes it w/b OK.

That way I think you eliminate the cpu as a prob and if your ram won't handle DC @ FSB 200, RMA it.

As far as where DC doesn't help, If you're gnna go over 200 FSB, single channel will get you farther than DC AFAIK.

 

[Delorian]

Originally posted by: Fern
Another thought. Assuming your mobo provides for ram dividers, you could run your ram at FSB 200, while keeping the cpu @ 166. Then test it with memtest86. You wouldn't wanna run a AMD in asynch mode, but for testing spurposes it w/b OK.

That way I think you eliminate the cpu as a prob and if your ram won't handle DC @ FSB 200, RMA it.

As far as where DC doesn't help, If you're gnna go over 200 FSB, single channel will get you farther than DC AFAIK.

I have the same mobo he does and I was just about to suggest that. BTW if you are using stock cooling on your CPU, that's probably why you are hitting your limit. I can only get about 200 stable on my 2500+ but that's with a TT Volcano 12+.

 

[xbassman]

Another thing that might be holding you back is your power supply.
I have seen generic supplies that would vary the vcore more than .2v (>10%)

But yeah, you might consider better cooling also.
My 2500+ runs 100% stable 11x200 @ 1.775v 37C idle-47C load. (SLK-800U/PanafloU1A)