error can't find file after reboot

[Russell]

I have tried reinstalling XP Pro several times on a
machine after installing another main board. It does not
matter whether you use FAT32 or NTFS when you install. I
have tried another HDD (new) but still get the same error.
This happens whether windows is activated or not it makes
no difference.

Can't find C:\windows\system32\config\system -- file is
either missing or corrupt.

Could this be a motherboard problem? I am leaning toward a
motherboard problem but not sure.

Thanks for your help

 

[dev]

Russell said:

I have tried reinstalling XP Pro several times on a
machine after installing another main board. It does not
matter whether you use FAT32 or NTFS when you install. I
have tried another HDD (new) but still get the same error.
This happens whether windows is activated or not it makes
no difference.

Can't find C:\windows\system32\config\system -- file is
either missing or corrupt.

Could this be a motherboard problem? I am leaning toward a
motherboard problem but not sure.

Try a boot into Safe Mode, by hitting F8 just before the "Starting
Windows" screen would appear (takes a bit of practice).
Choose LAST GOOD.

If that isn't applicable, use a working PC to read these sites...

How to Recover from a Corrupted Registry
http://support.microsoft.com/default.aspx?scid=kb;en-us;q307545
describes a three-step process to extract a copy of the registry
from the System Restore SVI folder.

http://WWW.WEBTREE.CA/windowsxp/ (repair console/restore tutorial)
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q314874
http://www.kellys-korner-xp.com/xp_sys32.htm

After your system is restored, the ERUNT utility available here may
make it easier to fix the problem if it recurs...
http://HOME.T-ONLINE.DE/home/lars.hederer/erunt

If the problem persists, try swapping current RAM (even if it checks
good) for a single, high-quality 512Mb chip. XP reportedly is sensitive
to memory timing.

 

[Russell]

http://support.microsoft.com/default.aspx?scid=kb;en-
us;q307545

This is the exact message i am getting. what is the cause
for it on a clean install??