problem with celly 366

[alien76]

I have got an old celly 366, which was overclocked to 458 on mobo with 440 lx / bx chipset, when i had win 98. Now i have win 98 SE and if i try to reach 458 Mhz the sistem crashes. i have to reinstall windows then.

Other parts of my computer:
Winfast leadtek geforce 2 pro AGP 2X
2*64 megs of pc100 sdram
1*128 megs of pc133 sdram
sound blaster 16 on ISA port

When the CPU was overclocked i had:
Creative Blaster Riva TNT 16 MB on PCI port
2*64 MB pc 100 SDRAM
Other parts was the same as they are now

Because of my mobo i cannot change CPU voltage and i can set FSB to 75 and 83 MHz. I just now the my mobo is built on intel 440LX\EX chipset, i do not know exactly which mobo is!

Thanks for answers!

[Ebola]

welcome to the forum.

its the 83 fsb. your pci divider at this speed is probably 1/2 so your pci devices are way out of spec. they are running at 41.5 mhz when they are suppose to be at 33mhz. this causes a ton of errors. I had a celly 466 and same thing happened. worked fine at 75 but at 83 i would get random crashes and bsods.

win98se may be slightly more hardware intensive than 98 which may add to the problem.

all i know about the 440LX\EX chipset is that it came before the 440bx chipset and i think it was ment for 66 mhz fsb chips.

[alien76]

if i try to overclock this celly the windows do that:
The windows starts to run
Then i get a message that the data is not write corectly in register and windows have to restart and try to corect register
but the windows don t corect the register they do suicide.
i only try to set FSB to 83 Mhz, i never try to set it to 75Mhz.
I am affraid of changing the FSB again cause i cannot format disk.
What shall i do for save overclock??

I have to salute you all!!!!! cause i m new one

BTW: Is there any folk from Slovenia on this forum???

[alien76]

doesn t anybody know what shall i do?

[Pinky]

Originally posted by alien76
doesn t anybody know what shall i do?

Try Jon's suggestion and lower the bus speed to 75mhz.

[Trap]

I'm affraid that your CPU is too slow for GeForce2 chip...maybe I'm wrong but...

[alien76]

i had selected 75 Mhz but windows died anyway. now i reinstall windows and use 66 mhz fsb

[alien76]

when i try to overclock all things are ok. But when the windows start i get a message about problems with register. After that i can only run computer in DOS mode and i get a message use command SCANREG - how can i use this command. if i try to run windows i get message the win.com file does not exist. any suggestions?

[TUK101]

That is a common problem for OC'ers. When you start getting everything out of sink, things do not load properly and you start recieving those kinds of errors. I think that almost everyone who has ever overclocked has seen that same screen. Its what happens when the system bus starts getting too far out of spec.
That is not a good motherboard for OC'ing anyhow, if you want to OC then I would spend a few bucks and get a newer board. You can pick up a SOYO mobo for around 30 bucks that will OC that older 366 Celeron just fine. I have one running at 100fsb@550 mhz right now on my backup rig.

[TUK101]

By the way? Is that an Emachines? I had the same board that would not OC at all lol.

[Johan]

Tuk, which Soyo board is that? $30 new or used?

[TUK101]

That was for the Soyo SY-6IZA. I bought it through www.justDeals.com. I dont think that they have that particular board anymore, but they have a newer one there now for around the same price. And you didnt answer my question lol, but is that an Emachines computer?:confused:

[Snarkey]

I go with Tuk101. I rolled a cel366@550 for quite awhile. Same board I'm using now. 100fsb. Old asus p2b-f

[alien76]

I was thinking about just one thing, which might causes problems to system while is overclocked ( for one minute ). Ram CAS latency is set to 2. could this be a reason for crashes???!!!!

I even don t know if my ram supports CAS latency 2

[Caffinehog]

I've had problems like that all the time. Two problems cause it for me. The first is bad/improperly seated memory. The second, I don't know what it is, but it can usually be corrected by booting at default (or lower) fsb, shutting down properly, and then putting the fsb up where you want it again. How does that work? I have NO CLUE. But it does. At least for me.