Okay, so I am building a *budget* system for my friend, he wants to go Intel, and likes the price of the 2.4 Gig Celeron. We were getting a little happy tokin' and sippin' a few beers when we ordered his parts. Inadvertantly, we ordered some Kingston DDR400 RAM, and his Celeron only takes DDR 200. I tried explaining that the 2.0 Celerons OC quite nicely, as I have gotten them up to 2.66 Ghz. just by running faster RAM in them, with nothing but the stock HSFU in the case.
He opts for the 2.4 Ghz. CPU.
Upon first boot, the system posts into BIOS. The default for the first boot, or new CPU is for it to start at 66 Mhz FSB. So, I look, and sure enough, the processor is set to go to 3.2 Ghz. as soon as we reboot. I manually set it to this speed, as it was going to do it automatically as soon as I re-booted.
WELL....when it booted, It locked up, gave us a bunch of garbled looking stuff on the screen. Tried clearing the RTC reset the processor, tried to boot using the Crash Free Bios feature on the driver disc, nothign worked.
So.. I pulled my P4 2.26 Ghz. CPU from my machine. We bought some slower RAM, PC 2100 and installed that. System booted fine, saw my processor perfectly.
So, I figure he has a low yield chip, that can't handly any OC'ing, or a bad proceesor that won't run at the rated speed.
He was worried that we ruined the CPU by OC'ing it. I don't think you could hurt it that bad by trying to boot it. If I had it OC'd and was running it hard for a long time, and it got really hot, I could see problems.
SO, what do you guys think? Needs to run the rated speed RAM, and forget OC'ing it? Did the processor get damaged already? Or, is this just a bum chip, and it won't run period???
Facebook
Twitter