• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

P4 2.4C m0 from ZZF

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.
I have whatever came with the AI7 board. I pulled the heatsink off yesterday when I got the board, removed the icky thermal pad and applied to arctic silver to it. Should be making good contact.
 
Tried both 1+3 and 2+4, no change. Batboy, I'm glad to know someone else is having the same problem as me. Make me feel just a touch better :)
 
Well, I managed to figure out the alarm problem I was having. I'm now using windows at 285mhz using 2-3-3-7 with the last two GAT settings disabled.

I have my RAM up at 3.0vdimm. Is 3.0vdimm safe over the long haul?
 
In every case I've seen, they're caused by the CPU having been pushed a little too far.
 
That appears to have been the case. I dropped back to the 3:2 divider and I was seeing the same problem. Seems I need better cooling if I'm to go over 3.3gig. That's a bit disappointing considering this is an m0 stepping with a relatively recently pack date (11/21/03).
 
Yah, running bios 14. That was the first thing I did when I loaded up WindowsXP.
 
ive gotten rounding errors in prime from memory failures before

@285 i can run my 2.4c d1 through a 24 hour dual prime cycle with divider set to 3:2 (infact i can run it all the way up to 303 fsb just needs 1.7 to go 24hours that way though :mad: )

@285 with a 5:4 divider i get the over 5 expected under 4 rounding error after about a minute then 2nd instance crashes in next 5 minutes usualy

im running mushkin pc3500 lvl 2 @ 2.85v im performing vmod to my p4c800-e monday and hopefully will hammer out this problem when i can run 3.1v to my ram



course maybe its the northbridge but why would i be able to run 303 fsb in 5:4 and not even get 285 in 3:2? weirder things have happend i guess
 
I just got my 2.4 mo and hit a wall, cant go over 260 fsb 3/2 disabled everything nothing workers it just beeps. could it be my corsair ram holding me back it is 3200LL oem timings 2326 is that ch5 ram. I have bios 19
 
Arch @ that FSB do you have active cooling on the North Bridge? with my P4C800 it liked to be active cooled past 275FSB. If not give it a try and see if it helps any. Keep us posted.
 
IC7 yes it wont post at 265 at 3/2 it just beeps i have not got to any cooling problems yet. i just removed 2.6c that was running at 254 fsb 3.3g so far the 2.4 is a let down, big time i hope this is a BH5 problem.
 
Last edited:
I'm running an AI7 which comes with an actively cooled heatsink from Abit. I removed the sink and reapplied it with some AS.

I'm having all sorts of trouble finding something that is stable. I'm not sure if its RAM or the CPU. The CPU gets quite hot under full load, high 50s C. What is everyone else seeing for full load temps on their cpus? Please be sure to include case temp and heatsink.

I've started back at the basics and I'm running at 12x250 using default vcore and stock cooling along with the 5:4 divider. I'm going to run two instances of Prime95 overnight to make sure its stable. I should have started here from the beginning instead of going balls to wall right away.

So as of right now, this 2.4c from ZZF is still up in the air as fast as overclocking. I'll be totally bummed if I get another dud CPU.
 
Better cooling compared to SHF is about 100-200 HZ more from what i see in the forms with air. I have had the same experience with 6 p4's The las two years. I hope because we have the same pack date 11/21/03 Im waiting for new mem Mushkin 3500 I think i have 3200LL ch5 use to have geil 4000. i will be happy if i get to 3.5Ghz was your rig stable at 3.3 if not there is no hope for me either. what was your v-core at 3.3GhZ.
 
Last edited:
arch have you tried running memtest to see if its your memory or not?

ive got 3 2.4c all d1 stepping and i can get them all to go from 3.4 to 3.6 with vcores of 1.55 to 1.65 im sure the majority of mo's could do those speeds as well. you may just have a ram issue if your corsairs the ch-5 based module that might explain alot.

also abit boards usualy read the temps 5-8 degrees higher then they should because of the way they calculate the temps across the cpu die.

what do your gat settings look like? this can have a big factor on how well your ram performs as well as what voltage your supplying to the ram and cpu
 
I haven't run memtest as I don't have a floppy drive in my machine. I'm not sure what kind of chips are on my HyperX PC3500, but its from late Feb. early March so I don't think it has CH-5 chips on it. In fact, I can run 2-2-2-5 timings on it, which I here isn't possible on CH-5 chips.

My GAT settings are auto/auto/auto/disable/disable. These don't appear to do anything at all. If I set it to street racer/strengthened/auto/disable/disable I don't see any performance increase at all. Go figure.

She just ran two instances of prime95 over night at 12x250 using stock voltage. Memory is at 5:4 for 200mhz using 2-2-2-6.

Wingman, I can't give you a vcore for 3.3 because it WASNT stable. I was in Windows using the default vcore. Now, it may not have been stable because of this issue with my RAM. I'm going to slowly work my way back up.

I'll keep you posted...
 
I will let you know when i get my new mem. We also have the same FPO/BATCH 335A449
Im running 255 all the time that is all my mem will allow 5/4 OEM v-core. FSB 255 with my 2.6 that was 3.3Ghz all the time but i was at 1.7 v-core The highest i wanted to go. It would do 261 3.4 at 1.82 with geil 4000 that was to high for running all the time.
 
Last edited:
I did a bit more testing. I'm taking it a little slower this time to see how high I can get without making huge jumps. It just completed an overnight run of two instances of prime95 (with affinity set 0 on one instance and 1 on the other) at 3.1gig (12x259). Using the default vcore and stock cooling still.

Memory is at 2-3-3-7 vdimm 2.8v. GAT settings are auto/auto/auto/disable/disable. Divider is 5:4.

I'm going to run it for a few days at 3.1 and then I'm going to shoot it up to 3.2 and see how that goes.
 
Back