Overclocking a 2.4B

[BuddMan]

Err, you got me a bit confused. What do you mean by the Winbond temp? And I did a search for AIDA2 and found nothing. What should my mobo temp be at in normal circumstances? I will try putting my voltages to normal and see what happens.

[mutz]

Oops! That's AIDA32 here.

The trick is to make sure the monitoring program is checking the right Windbond sensor at the right address. Dunno how, but some programs manage to screw this up.

In my rig at the moment:

CPU 31.4C
MB/NB 35.9C
Parhelia 42.6C
Case internal air 27.2C

I'd say normal MB/NB is between 36C and 42C, but this is very dependent on ambient temps. If it works and nothing is screamin at you, it's normal.

[BuddMan]

Well I did some all night testing. Thanks for showing me that program mutz, my chipset temp is 25 Celcius, probably because of the waterblock and the 92mm fan blowing on it. I'm starting to think it's the ram. At 165 at default ram timings, everything runs great, no high temps, etc, all is good. I tried increasing my ram timings from 2-6-3-3 to 2-5-3-3 and upon saving CMOS the computer would not reboot. Had to take out the battery and reset everything. With the CPU at default, I can put the RAM timings at 2-5-2-2 with no problems. So based on this, do you guys think it's the RAM? If so, maybe an upgrade is in order on the ram...hehehe.

[mutz]

Dunno. I've never had problems with RAM (that I know of), and Corsair is suppose to be good.

Heat isn't everything. Any component can mess things up. Sometimes the whole rig or just the board refuse to go further.

Don't know why, but I keep thinking CPU or board.

Take a look here.

[rylan]

Hrm, it could possibly be the ram. Kinda wierd though, since thats 400MHz ddr so it shouldn't have any problem running up past 166MHz (333 ddr).

[mutz]

Well that's what keeps you up all night. Torturing yourself over all the things you think it could be and ignoring all the things you don't think it is, but in the end it turns out to be just what you didn't think it could be.

Nice sentence. Wonder if I could do that again...

[BuddMan]

But the problem is that it doesn't make sense for it to be the CPU. If it can hit 3Ghz at default voltage but can barely handle 3.05Ghz at a Vcore of 1.75, then I think it has to be something else. I've never seen that steep of a ceiling, though I know it isn't unheard of. Well, I have a friend that has some Corsair 3500, will try it with that first and then pretty much work from there. I might just go back to my 2.8, but I was really hoping I could sell it and make a little dough, heh. We will see...thanks for the help all. I'll post results when I have them.

[mutz]

I had that with a P 2.4. At 1.5v it was fine, at 1.75 it didn't like anything. I said F it and bought a 3.06. Haven't messed with the 3.06 yet though.

Just thought about your clock and RAM timings again. You've maxed the RAM timings and then pushed the clock which in turn pushs the RAM, PCI, AGP and all. Maybe with the 3500 it will hold, but I think you've gotta find a compromise in there.

Just realized I haven't dumped XP, format C: and reinstalled everything fresh and direct to the latest drivers, updates for a whole year now. That's where my next speed is coming from.