Overclocked computer but lost registry..had to reinstall WIN98 and everything else.

[CraigCampos]

Title speaks for itself. I couldn't have damaged anything could I? I overclocked a PII 400 to 497 by dropping the multiplier to 3.5 and raising the FSB to 133. It runs smooth as glass at 448 4@112. It booted fine and everything was fine until windows started to load. It stated that my registry had changed and it loaded an older version. It continued doing this until I turned it off and put back it back to 448mhz. Windows loaded fine but registry was completely out of whack. Files were not in the same order, USB, printers and scanner were not loaded. It was a huge headache. To get stable again took 5 hours of reloading and configuring! Will the hard drive be fine? I reformatted it! Is the board and chip fine? Have another question...I am using a promise ultra66 card (pci) to run my hardrives....could this have caused the problem? Meaning if I used the motherboards IDE port(at 33dma) which can handle 133 mhz...would the computer boot through windows?

[[OC]_SR20DE]

hey, Check your RAM module. This kind of problem is very common and it's usually due to RAM instability. Get better RAM something like Mushkin PC133 Rev2 or newer. If you already have a good RAM then it might cooling problem.

[LutaWicasa]

Yep, could be ram. Bbuuutttttt it could also be hd unable to handle out of spec oc. Might help with some info on your sys. Also, you didn't drop your mult. PII400 is locked. Actually the math says you were running 4x124 which leads me to suspect pci bus spec. probs.

[jr]

It was the ram for me when I got errors like that. I used to think it was my poor maxtor but now I know it isnt. Check your ram. If you tried it at cas2 try at cas 3 it might work.

[DocClock aka MadClocker]

When you clocked it, did you keep your pci and agp dividers the same? for 133fsb, you need to set the pci to 1/4, and the agp to 2/3.
Remember that agp at a 1:1 ratio @ 133 is a nogo,
you might be able to get by with a pci divider of 2/3.
Something to think about

[CraigCampos]

LutaWicasa (Jan 09, 2001 10:51 p.m.):
Yep, could be ram. Bbuuutttttt it could also be hd unable to handle out of spec oc. Might help with some info on your sys. Also, you didn't drop your mult. PII400 is locked. Actually the math says you were running 4x124 which leads me to suspect pci bus spec. probs.

I can change my multiplier on my PII 400. You cannot go over the original setting of 4 but you can set it lower. It has show the correct amounts when lowered. ie 3.5@100 will show 350. 3.5@112 will show 392.

[quegyboe]

CraigCampos (Jan 09, 2001 10:17 a.m.):
Title speaks for itself. I couldn't have damaged anything could I? I overclocked a PII 400 to 497 by dropping the multiplier to 3.5 and raising the FSB to 133. It runs smooth as glass at 448 4@112. It booted fine and everything was fine until windows started to load. It stated that my registry had changed and it loaded an older version. It continued doing this until I turned it off and put back it back to 448mhz. Windows loaded fine but registry was completely out of whack. Files were not in the same order, USB, printers and scanner were not loaded. It was a huge headache. To get stable again took 5 hours of reloading and configuring! Will the hard drive be fine? I reformatted it! Is the board and chip fine? Have another question...I am using a promise ultra66 card (pci) to run my hardrives....could this have caused the problem? Meaning if I used the motherboards IDE port(at 33dma) which can handle 133 mhz...would the computer boot through windows?

I know what it might be....it might be your Promise UDMA card. I have a Promise Ultra66 card and I know from experience that they do NOT like running past about 37mhz PCI bus. Any higher than that and they go flakey...just an idea...If you want to OC, change your PCI multiplyer so you can get 133mhz / 33mhz for your buses.

[LutaWicasa]

I've heard of upwardly locked procs but never seen one (yet). One day I'll run across one, I love dinking with old stuff (as the sig shows)