What was this... o'clocked and then my config.sys is bad?

[jpetermann]

I have just got set up my new rig! Here it is:
Gigabyte 8IRXP
P4 1.8a
ocz 512mb 2700 ddr
sb audigy platinum
tdk 24x cdrw, Pine 16x DvD
Raid 0 w/2xMaxtor 40gb ata133

I bumped everything up to: fsb 133 (1.8 @ 2.4) posted, and went through the raid bios. I thought I was home free, but then I go tthe message that the config.sys was bad, don;t remember the exact words. I just remember thinking I was gonna have to format and re-install. Anyways, I set everything back to default and all is fine. What happened and how can I get around it. Do you think it had to do with my raid controller? I had changed the multipliers and divders so that all was at default speeds except for the P4.

Thanks for your help...
PJ

 

[VirginiaDonkey]

your overclock was too high. If you can bump the voltage any that might help.

 

[Duvie]

what settings are the memory??? default there as well??? may want to check to make sure you don't have a bad stick....

IN those cases I have found either bad ram or bad harddrive...

 

[jiffylube1024]

Win XP gives those errors often when the overclock is unstable so it seems to crash and gives an error that one of the main system files is corrupt and requires a Windows re-install. Finding a more stable overclock is the solution; try 2.1 GHz first (which should work) then play around with voltage, etc, etc. More cooling might be necessary.

 

[DAPUNISHER]

Was the DDR at 166mhz when you upped the FSB and if so does it stay at 166mhz when the FSB is changed on that board?

 

[Duvie]

also a big mistake I see with a lot of ppl is they will install os with system oc'd and memory tweak to ultimate settings...often times with the system never fully being tested as stable...

 

[jpetermann]

Everything was running fine before the o'clock. Except I have a cold boot problem. I had set the timeings so that the mem and pci/agp bus were running at default speed. I will try to back it down a lttle bit.

PJ