Is this from Overclocking ????

[Nemo]

Windows 2000 could not start because the following file is missing or corrupt:\WINNT\SYSTEM32\CONFIG\SYSTEMced

Does anyone know the cause of this, the microsoft knowledgebase told me "The System hive in the registry is damaged or missing."
I am running:

Windows 2000 Professional SP2
AMD 1.2GHZ
Abit KT7-Raid
ATI 64mb Radeon
128 mb ram

The only thing I do to the machine is change the bus to 101 when I game a little, then move it back when I am done.

[gdlewis]

Win2000 never overclocked well for me. I would get stop errors, file corruption all the time and end up reformatting. But, if you only bump the fsb up by 1, I would say your problem was not from overclocking.

[PassnThru]

If it's an overclocking problem then save that processor for the AMD museum as the least overclockable proc they ever produced. I believe most AMD procs can handle a 12MHz overclock even with standard cooling. Where did you get the processor - you could have gotten a remarked processor - you could be severly overclocking it without knowing it and the extra bump puts it over the edge. Try underclocking it for awhile and see if it helps.

[NDC]

The only thing I do to the machine is change the bus to <u>101</u> when I game a little.

I would most likely say that it's not due to overclocking. Assuming you have a T-Bird 200FSB, you're only overclocking the system bus 1Mhz! Even with the AGP/PCI divider set at 1/3, that's only .33Mhz. Even if you did set it at 110Mhz, that would only be 36.6Mhz which isn't severe enough to corrupt data on the hard disk in most cases...

[otheos]

As funny as it may sound an FSB of 101 (at a mutliplier of 12) can cause loads of problems and this is a first hand experience:

While the PCI bus is perfectly ok at 101Mhz, if you run your RAM at 133 then at 101FSB it goes to 134Mhz. But if your RAM is CL3 and you run it at CL2, even 1Mhz will **** it out! It may boot or it may not boot. If it does, data corruption and/or lockups are common.

While the 1.2 Athlon can certainly take at least another 100Mhz, I think it's your RAM that causes the problem. You should overclock by multiplier then: First you get a higer jump (but now you also need more voltage usually) and you don't mess with your RAM.

Oh and btw, taking the RAM speed to 101 to avoid the 134 problem renders your o'clock worthless as 12MHz extra CPU speed is by no means covering up for the lost bandwidth of 32Mhz in the RAM subsys.

What brand is your RAM? I bet it's PC100 CL2 and you run it at 133 CL2 or it's PC100 CL3 and you run it at 133 CL3.

[Nemo]

My processor is a retail box 1.2 athlon
and my memory is Micron Pc133 - 128mb stick.

Do you think I should get a new stick?

[otheos]

set the memory speed to 100 instead of FSB+PCI to see if it is the memory that stops you and test again.