First attempt at OCing Celly 1.0 failed..help please

[CaliVW78]

Ok, went for my first attempt at overclocking my Celly 1.0. Upped the FSB from default to the first available setting. Computer will turn on but nothing on the screen. Monitor won't even come out of stand-by. Help anyone? Anyway to reset bios on the mainboard? Thanks...

[pappypete]

Can you provide more info? What mobo etc? You
might be able to remove battery to reset CMOS.

[batboy]

Almost sounds like you need to disable "speed error check" in the BIOS.

[Yodums]

Did you reset the cmos and now posting?

Yea the mobo and User Define options would be a start. Because I think your configing something wrong in the user define.

Make sure you don't touch the multiplier and disable speed error hold like batboy said.

When I was first overclocking I had changed both these and left speed hold on so it took me awhile to figure that out.

[CaliVW78]

Ok, got an FIC FA15T mainboard. 256 PC133 PNY SDRAM.

[CaliVW78]

Sorry for the beginner questions, but I am taking notes :) First, how do I disable 'speed error check?' Where is the multiplier, what does it do, and where are the User Define options? I read all the beginner places but didnt get much detail. Thanks for the help

[Yodums]

They should be in your bios. Assuming you know where it is because you claimed you have tried to change the settings.

Its all in there fsb, multiplier etc take a look for yourself your board is not too farmliar around here.

[CaliVW78]

K, removed battery on mainboard and it reset everything, able to boot now. Now going to change fsb to 100. Thanks for the help. The board is on the new side, from FIC (First Mainboards) Do fine with it so far. Also, what are some good programs to benchmark with? How will I know how much the performance has altered?

[Yodums]

Sisoft Sandra 2002 is a very good benchmarking tool. Your FSB is already 100fsb.

Yodums

[CaliVW78]

K, got to 112 on the FSB, would not go any farther though. What should I be looking at now? System is stable. Have not messed with anything accept FSB...so?

Thanks everyone

[Flu!d]

Up the voltage step by step until it is stable at a higher still FSB....Keep repeating the process until your temps get too high....Then back off a notch or get a better HSF....

[Yodums]

Originally posted by CaliVW78
K, got to 112 on the FSB, would not go any farther though. What should I be looking at now? System is stable. Have not messed with anything accept FSB...so?

Thanks everyone

What FSB options is your motherboard giving you. To go higher you need to pump the vcore to maybe 1.5 or 1.6 later on when say your near 124fsb or 133fsb.

Yodums

[CaliVW78]

Would the voltage most likely be under advanced bios or chipset options? I show the voltage there, but no way to adjust it. Also, whats HSF?

Next option for fsb is about 124 (not at computer right now)
Guess I need to figure out how to adjust the vcore.

[CaliVW78]

also, sorry.....another option in fsb is enable/disable speed spectrum. Currently enabled.

[muddocktor]

Go ahead and disable the spread spectrum. That is a setting to use if your computer is giving EMI interference to nearby electronic devices. It can also interfere with your overclocking attempts because it makes your system a little less stable, from what I've read.

I just downloaded the manual for your board and it doesn't look like it supports too many overclocking features in the bios. I didn't see any entries for adjusting your vcore voltage in there at all. It looks like you will have to manually set them with the dip switches on the board. Also, I didn't see any settings in bios to adjust the front side bus speed, only the cpu host clock/pci clock speed. How are you adjusting the fsb speed? If it's by the dip switches on the board, you are limited on the bus speeds you can choose. You need to go into the cpu host clock/pci clock setting in bios and set it to 1/4 or 4:4:1(whichever way they show it) before trying to go up on the fsb speed any more, so your pci bus devices aren't running too out of spec when you are trying fsb speeds higher than 120 fsb.

If I were you, I'd set the vcore voltage to 1.8(the max shown in the manual) as long as you have a decent hsf on the proc, set the cpu host clock/pci clock to 4:4:1, and go for the 124 fsb and see what happens. I'm betting that your celeron 1.0 will boot like that. If it doesn't, then you will have to do a vid pin wrap to fool the board into giving you more vcore voltage for the chip.

One other note: HSF stands for heat sink fan, FSB stands for front side bus speed.

Hope this helps you out.

[CaliVW78]

K, disabled speed spectrum. Set voltage to 1.4 (Recommended by mainboard manfct) Boots fine at fsb set to 112. K, lets go to up one jump to 124/41......nope.........gets past the bios, but dies loading the os. Says system.ini file may be corrupt. Upped voltage to 1.45........... now gets stuck at bios intro screen and cant get into bios. So....reset bios and set fsb back to 112, where its happy so far. Whats my next step? I cant figure out where to change clock/pci setting in bios.

[CaliVW78]

Damn, knew i missed somthing.....did not try setting vcore to max. Will try when I get home. Anything in the mean time?

[The Doors]

Hi CaliVW78, welcome to the Forum,
you have to check the Cpu temp, never it must go above 40-45 degree C @full load, if you're not using MotherBoardMonitor (http://mbm.livewiredev.com/), take a look into the Bios, where the temps are referred @full load ;)

I hope it helps you :)

[CaliVW78]

K, bumped the voltage to 1.8.......booted fine. Then upped the FSB one to 124...no good. Error "Windows could not start because the following file is missing or corrupt: \windows\system32\config\system" What now?

[TUK101]

Just for the heck of it, try going to 133 fsb and leave everything else alone. That would give you a very good OC and would leave the system buss to standard 33.

[Flu!d]

Sounds like your PCI dividers are set too high....Can you select a pci divider that will get your pci speed closer to spec as 41 mhz is fairly high....(that's what the 41 is beside 124, ie: 124/41).

[The Doors]

Originally posted by CaliVW78
K, bumped the voltage to 1.8.......booted fine. Then upped the FSB one to 124...no good. Error "Windows could not start because the following file is missing or corrupt: \windows\system32\config\system" What now?
Well, like just said, it's for sure your HD that doesn't like at all a Pci bus of 41.3Mhz (very far from the specs of 33.3Mhz) so at this point try to go with a Fsb of 133Mhz with a Vcore of 1.8-1.85v, and the Pci bus will return in the specs for the 1/4 divider ;)

[CaliVW78]

K, tried pushing 133 in the bios, reboot....screen turns on with nothing showing, then turns off to standby. But, theres also jumpers on the board to set it to 133, tried that and it did the same thing. Nothing on the screen. *sigh* Voltage right now about 1.80 - 1.85 Am I running out of options.

Recap-currently at 112 fsb and vcore 1.85 and stable

[The Doors]

CaliVW78 please, what kind of HeatSink & Thermal paste are you using, and what abuot the Cpu temp @full load?
if not an heat related prob, well, you can try to go with the pin wiring mod, so the Bios at boot up will consider this voltage instead of the standard 1.75v that seems to be not enough to go @133Mhz of Fsb.

[CaliVW78]

Using Thermalright SK-5
Temp never above 36c

Got to 36c after playing Unreal for nearly 2 hours straight.

[The Doors]

Here follow the suggestion of Flu!d that helped me a lot, even if on a different Mobo, probably it can help you ;)

You need to vid pin the chip to trick the mobo into thinking the default VCore is higher than it actually is.
What happens, and it is a fault with all 815xx chipsets and not individual mobos, is that the chipset reverts back to the chips default vcore at inital bootup and dosen't up the vcore to the user defined settings until the bios post screen....So for a few seconds there you're poor CPU is trying to boot at it's overclocked speed at standard vcore!!

Try vidpinning the chip....I know it will fix your problem....


P.S. In the afternoon I'll try this mod on the same chip of yours, that doesn't wanna go at 133Mhz, even if on a different system, so I'll post more info ASAP about the OC chance of this chip ;)

[CaliVW78]

*sigh* was hoping wouldnt have to vid pin, never done it before. Guess ill give it a shot. Thanks for your help. will keep eye out for your post with your cpu.


Thanks everyone

[The Doors]

Well, no luck at all @133Mhz, even if with the Cpu VidPinned for 1.95v and an Alpha Pep66/Delta38@12v!!! probably depends by the chip, but anyway is rock stable @124Mhz, I'll try in the next weeks after a good Burn in process ;)

P.S. the VidPinning mod seems to be more difficult of what is in reality, was the same for me ;) take a look here (http://www.hardocp.com/articles/intel_stuff/bumpvoltage.html), and let me know if you need of more support :)

[MadMan007]

If your 1.0 celly is a CuMine core (128k cache) then you should follow the [H] guide for vid-pinning. HOWEVER, if it is a Tualatin (256k) then you need a different vid-pinning setup with one additional pin. The CuMine tops @~1300MHz, the Tualatin much higher. It was not clear to me whether you had a CuMine or a Tualatin Celery, which one do you have?