Mobile Celeron 1.8ghz @ 2.882ghz

[PCNewb]

I did read the overclocking guide, and have been doing slight overclocks on P3's and P4's for a couple years. But more just bs'ing with it, but I'm wanting to experiement more into it now - which is why i bought the setup i did, read the guide, and now posting.

Motherboard: Asus P4P800
CPU: Mobile Celeron 1.8 - Northwood
CPU Voltage: Tried 1.625-1.675, no difference
(Just noticed CPU-Z shows it fluctuating from 1.61-1.69, while set at 1.625 default ack)
Ram: 1x 512mb Corsair XMS PC3500 BH-5
Ram Voltage: Tried from 2.65-2.85, no difference.
FSB: 160mhz 1:1 Ratio
CPU-Z says timings at 2.5 4 4 8

Anything from 161-165 posts, but results in a BSOD while loading.
Anything from 166+ results in needing to clear the CMOS
Anything below 161 runs beautifully.

Temps are 26*C no load, 34*C under load (at the stable 2.882)


Trying to figure out what my limitation may be. The BSOD makes me think Ram, but the BH5's should do a lot better than 160 FSB. The CPU/Mobo was from a very respectable trader, which the CPU does 3.0+ or better, so I'm thinking it's:

A) An unfortunate bad stick of BH5
B) Bad PSU (with fluctuations?)
C) Maybe Bios/Ram settings i'm not catching.

Any suggestions would be appreciated, and i understand the consequences involved.

 

[MercenaryForHire]

Ah, a Celeron-K.

Unsure about that board, but make sure that the PCI/AGP dividers are properly catching.

- M4H

 

[PCNewb]

Made sure the PCI/AGP were locked 33.3/66.6 Thanks though.

 

[stevty2889]

Your core voltage is actualy a bit too high for a mobile chip. It should be running at closer to 1.2v. There was a post on here I saw the other day, that showed a pin you bend on the mobile chip, so that a desktop board will feed it the correct voltage.

 

[PCNewb]

Yeah, 1.2v is for the default 1.8ghz speeds. The 1.625v is needed to achieve the 3.0ghz or so speeds. With this motherboard, the CPU is recognized at the 1.625 which is fine as i'm attempting to achieve the 3.0ghz speeds. I'd only do the bent pin mod if i decided to do lower speeds. Was mentioned in Karaktu's guide/post, which i think is the one you were referring to. Thanks for the tip though.

 

[rogue1979]

Besides maybe trying a different/better power supply, this just might be the limit on the cpu.

Most will hit 3GHz, but there has to be a few that don't make it. 1000MHz is a hell of an overclock for any cpu!

I have two 1.8 mobile Celerons, both are doing just a couple of MHz under 3GHz, without any extra voltage besides what the motherboard gives them (about 1.62v or so).

 

[PCNewb]

Yeah you're probably right, just wanted to hit 3ghz

Still wish i had a way to test the ram though, i've never seen/been able to have it past 160, which is what it is now. My last mobo only pushed it to 148. I'll just try a diff psu and let it be maybe.

 

[DaNorthface]

raise your ram timings to 3-4-4-11

 

[Karaktu]

BH-5 really doesn't like anything other than a CL of 2. I'd change the timings manually to 2-2-2-5 or 2-3-2-6 at the lowest and go from there. Also be sure you are feeding it 2.65v and 2.85v once you cross the 200MHz mark.

CPU-Z is reporting the memory at 160MHz, right?

 

[Karaktu]

Also, do you have Memory Acceleration Mode enabled (any setting other than AUTO) and/or Performance Mode enabled (any setting other than AUTO)? If so, set them to AUTO while you test.

 

[DaNorthface]

you're telling me that the ram will run at faster fsb with lower timings??

 

[PCNewb]

Not faster, stable. The BH-5 didn't like the higher timings. It's more stable now with the timings, [Ran the Blend in Prime95 for an hour, i stopped it, before it would lock within 10-15mins.] but i think i just hit the limit on the setup.

 

[Zap]

Originally posted by: PCNewb
Motherboard: Asus P4P800
Anything from 166+ results in needing to clear the CMOS

Sounds just like the Asus P4P800 Deluxe I used to have. It did not like to POST at around that speed, up to 199. At 200, magically started working again. Your 1.8 would have to be able to POST at 3.4GHz for you to test that theory... try it and let us know.