System32\config\system is missing....

[orion23]

Ok

This is a fairly new install (1 or 2 months) XP MCE 2005

About 2 days ago, I started getting BSOD for the 1st time ever.

A few times that I've attempted to restart the PC, I get the error System32\config\system is missing....
I've fixed it a few times already using the recovery console.

Tired of this I decided to do a new install under a different drive. But this new installation shows even more problems.

1. Trying to install windows would fail because setup couldn't find a file in the disk (happened many times until I was able to install windows)

2. Right after installations I would get weird errors about "service pack installer had to shut down" and "internet explorer has caused an error"

3. Memory dump and BSOD (something about a memory failure)

4. New drivers that I just downloaded for this istallation would get corrupted after download.

5. A few installations would give me an error and could not finish installing

6. After I would restart from a crash, I get a message about a registry file or section that had to be recovered from a previous log or repair.

And this is with the NEW INSTALLATION

Please help!

 

[dball3]

The only thing i have is if your booting off of your maxtor drives that may be the problem. Compatibility issue between the nf4 and maxtor drives, you might be able to get a firmware patch for the drives or you can just use a WD drive as your boot drive.

 

[orion23]

The new installation went to the WD drive and that one has more problems than the old one.

Someone please help me!

 

[dclive]

Originally posted by: orion23
The new installation went to the WD drive and that one has more problems than the old one.

Someone please help me!

It's typically hardware if you can repro the problems with a new Windows installation. I'd suggest calling your system vendor to have them repair it.

 

[ivwshane]

I would run a memory test to see if you memory is bad. Random issues like that can be caused by bad ram.


I like to use memtest86 for testing memory.

 

[orion23]

Originally posted by: ivwshane
I would run a memory test to see if you memory is bad. Random issues like that can be caused by bad ram.


I like to use memtest86 for testing memory.

Cool. Thanks a lot guys.

I downloaded memtest, created the bootable disc using the image and right away my memory failed. One stick that is.
3 out of 4 work. Completing the test with 3 sticks right now and we'll see what happens once I load!

 

[ivwshane]

Hopefully you bought yourself some memory that has a lifetime warranty on it


At least you know what the problem is.

 

[orion23]

I called kingston and they are replacing it for me.

I should get the new kit by friday or monday.

Thanks everyone!