Need hardware primer - I guess?! Computer hungry!

[langleyl]

All right, my computer keeps eating the Config file. It runs fine for a while (12 hours the last time, a week the time before that, 2 days the time before that, etc.) and then BAM it suddenly reboots and can't find the Config file. I'm aware of the fix from Microsoft for WINDOWS\SYSTEM32\CONFIG\SYSTEM... Which is the file my computer says is missing. But this seems more like a band-aid then a fix. I mean, this file had to have been there at one time for my computer to work... What happened to it? What keeps eating this file?
I've reformatted my HD at least 4 times and even swapped out the HD once... same problem. I've ran the extensive memory test mem30/mem86... everything looks good. I've reseated my mem, vid card, made sure all connections were nice and tight (at least a dozen times!), and I've contacted the MB manuf (Soltek - SL-DRV4). Soltek told me to perform the same tests I've already performed...!? I made this clear to them when I submitted my problem...
I guess I need a primer on certain aspects of computer operation! When a computer boots up, where does it look for the config file? Is this found solely on the HD? I originally thought this to be a BIOS or CMOS problem... Is it, or could it be? Folks, I've been all over the Internet with this problem and all I've found so far are the band-aid remedies. I need to know what the hell is eating my config file?! I'm getting real tired of reformatting...
System: Soltek MB, WinXP Pro, AthlonXP 1700, 512 RAM, Maxtor 60GB HD, Leadtek Geforce 4 170, Antec case with enough cooling to keep everything about 43*C.

Thanks to all who respond...

 

[franklin97355]

More information is needed. What is the actual message or symptom you get when the error occurs? You may have a MB problem since you have tried other things but the messages will help.

 

[rockerfellerz]

What file are you talking about exactly? Config.sys? try and back up the file to a disk before it dissappears.....
franklin97355 is right, more info is needed. If you're going through Hell...keep going... (Winston Churchill)
RocKeRFelLerZ

 

[langleyl]

One of the messages says: WINDOWS\SYSTEM32\CONFIG\SYSTEM is either missing or corrupted.

Another one says "Can't find Config!"

I was assuming they were both related?!

 

[rockerfellerz]

Instead of re-installing, run the xp setup program and select the option to " repair installation " . This might do the trick. If you're going through Hell...keep going... (Winston Churchill)
RocKeRFelLerZ

 

[langleyl]

More Info: Actually, this my old computer. I sold it to my neighbor when I built two others for myself. So the problem is a little embarrassing... She thinks I sold her a lemon. While this system wasn't the latest and greatest, it is a very sound system that I never had any problems with for the six months I owned it! I built two more Solteks (SL-DRV5)and love them! The kicker here is that the one year parts & labor warranty is about to expire in about 15 days! lol If it's a MB problem, I'll send it back. If there's an easy and lasting fix, I'll go for that. But I can't for the life of me understand why it keeps eating this folder/file?! ALSO: When it reboots after eating the file, the computer starts beeping (POST-type beeps), and continues to beep for at least 5 minutes! I guess that's why I thought it a MB or BIOS problem?! But I'm no longer sure... And Microsofts solution for this problem (apparently it's not rare!) is a 4 step process that involves editing large chunks of the Registry... Not for the faint of heart. But hell, I can follow directions... but there is no indication as to what is doing this in the first place!?

 

[Snakeyeskm]

It could be a corrupted system file.
If the repair did not work Go to start, accessories, command prompt, type sfc/scannow and hit enter
with the xpcd in the cdrom.
Best of luck Zero Mistakes = Zero Experience
And Boy do I have experience !

 

[KimberTech]

If you turn on the computer and you get beeping, you have a hardware problem.
If you have warranty that will deal with that...go for it.

If you post the type of beeps we can probably tell you what the error relates to.
They are called BIOS post codes. Kimber

The more I learn,I realize how much more there is to know!