XP BOOT Problem

[MikeAuds]

On start up XP fails to load and halts at screen with - 'windows could not start etc ...

\WINDOWS\SYSTEM32\CONFIG\SYSTEM .... is not there or corrupted use repair to fix etc...

Unable to use any options when using F8 - all options result in the same response as above. Booting from CD goes through the pre-load and when it gets to "setting up windows" freezes at that point. Recovery Console is not pre-loaded. Anyone have a solution other than reformatting HDD and reloading from scratch .. thanks

 

[wolluf]

Sounds like a hardware problem. If so, you just need to isolate which bit of hardware is causing it (he said glibly). But, some history would be good (eg, has this just happened, what your machine's spec is, have you added/removed any hardware/software recently, had a major crash/virus attack etc).

 

[gargouille]

Is this a 1 of 1 try incident?

The file it says is corrupt deals with the registry.
You have little to lose formatting and trying again.

Otherwise, I'd also lean to hardware...specifically the hard drive.
You may have to acquire a boot disk and download the hd
mfr.'s diagnostics to test it out.
If that checks out okay, I'd download and run DocMemory from

http://www.simmtester.com/page/products/doc/download.asp

(free, by the way)

 

[linney]

An easy to follow recovery console description when unable to start computer due to corrupt registry.

http://www.mediaworkstation.com/htm/homeset1.htm

Click on Tutorial then the Charlie White article on XP crash.
This is a laymans version of Q307545 in simple language.



Cannot Start Windows XP if the System or Software Hive Is Missing or Damaged (Q303012)

http://support.microsoft.com/support/kb/articles/q303/0/12.asp

 

[gargouille]

Just a heads up, linney, MS is redoing their articles and the last link you provide is de-double-d!

 

[linney]

Thanks gargouille, here's what it use to say for what it is worth.


Cannot Start Windows XP if the System or Software Hive Is Missing or Damaged (Q303012)

--------------------------------------------------------------------------------
The information in this article applies to:


Microsoft Windows XP Home Edition
Microsoft Windows XP Professional


--------------------------------------------------------------------------------


SYMPTOMS
When you try to start or restart your Windows XP-based computer, you may receive one of the following error messages:

Windows XP could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM


Windows XP could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SOFTWARE


Stop: c0000218 {Registry File Failure} The registry cannot load the hive (file): \SystemRoot\System32\Config\SOFTWARE or its log or alternate





CAUSE
This issue can occur if the System or Software hive for the Windows XP installation is missing or damaged.



RESOLUTION
To resolve this issue, use one of the following methods.

Use the Recovery Console Tool
To restore a damaged registry hive, use the Recovery Console to restore the backup copy of the hive from the Repair folder. The Repair folder contains a copy of the system's registry hives that were created after the first successful startup of Windows XP.

WARNING : Although data should not be affected by the following procedure, you may need to restore changes you previously made to programs or system settings since the first time you successfully started Windows XP.

To replace the damaged registry hive and restore the backup copy of the hive from the Repair folder:
Start your computer to the Recovery Console.


Determine if the file that is mentioned in the "Symptoms" section of this article is present, and if it is, rename it:


In Recovery Console, change to the c:\Windows folder.


Type cd sytem32\config , and then press ENTER.


Type dir system , and then press ENTER.


If you cannot run the preceding command successfully (because the file is missing), skip to step 3. If you can run the preceding command successfully, type ren system system.bak , and then press ENTER.

NOTE : If the message that you received referred to the software file, replace "system" with "software" in the preceding command. For example, you would type ren software software.bak (instead of ren system system.bak ), and then press ENTER.


Type copy c:\windows\repair\system , and then press ENTER.

NOTE : If the message that you received referred to the software file, replace "system" with "software" in the preceding command. For example, you would type copy c:\windows\repair\software (instead of copy c:\windows\repair\system ), and then press ENTER. You should receive a "One file copied" informational message. For additional information about how to use Recovery Console during startup, click the article number below to view the article in the Microsoft Knowledge Base:
Q307654 HOW TO: Install and Use the Recovery Console for Windows XP
IMPORTANT : If you encounter problems when you run the preceding commands, you may need to use the Change Directory command ( cd ) one folder at a time before you run the preceding commands. For example, type cd system32 , press ENTER, type cd config , and then press ENTER.


Type exit , and then press ENTER to quit Recovery Console and restart the computer.


You Cannot Start from the Windows XP CD-ROM or Use Recovery Console
If you cannot start from the Windows XP CD-ROM or use Recovery Console and you are using the FAT file system (not the NTFS file system):
Use a startup disk from one of the following operating systems to start your computer to a command prompt:


Microsoft Windows Millennium Edition (Me)


Microsoft Windows 98


Microsoft Windows 95


At the command prompt, type c:\windows .


Follow the steps in the "Use the Recovery Console Tool" section of this article, beginning with step 2b (type cd sytem32\config , and then press ENTER).

IMPORTANT : After you complete the steps in the "Use the Recovery Console Tool" section of this article, remove the startup disk, and then restart the computer.


Use System Restore to Revert to the Most-Recent Restore Point
You may want to use System Restore to revert to the most-recent restore point if you have replaced the specific registry hive, but the issue has not been resolved. For additional information about how to use System Restore to revert to the most-recent restore point, click the article number below to view the article in the Microsoft Knowledge Base:
Q307545 How to Recover from a Corrupted Registry
Run a Repair Installation of Windows XP
You may need to run a repair installation. For additional information about how to do so, click the article number below to view the article in the Microsoft Knowledge Base:
Q312369 You May Lose Data or Program Settings After Reinstalling, Repairing, or Upgrading Windows XP



MORE INFORMATION
By default, the administrative password for Windows XP Home Edition is blank.

For additional information about how to use Recovery Console, click the article numbers below to view the articles in the Microsoft Knowledge Base:

Q307654 HOW TO: Access the Recovery Console During Startup
Q240831 How to Copy Files from Recovery Console to Removable Media
Q229716 Description of the Windows Recovery Console


--------------------------------------------------------------------------------
Published Jan 8 2002 9:30AM Issue Type kbprb
Last Modifed Feb 7 2002 12:42PM Additional Query Words
Keywords kbenv kberrmsg

--------------------------------------------------------------------------------

COMMENTS?

 

[MikeAuds]

Appreciate info from all .. I cannot use the 'Charlie White' solution because I cannot get to the select 'r' for repair option. That also applies to the Knowledge Base solution because am unable to load or access the 'Recovery Console'. After booting from the CD I can only get as far as where the initial files have been pre-loaded and the system is about to start windows setup. Being a NTFS file system I cannot access the contents of the HDD via a BOOT disk. I have run a HDD Factory Test which comes up okay but it may still be a hardware fault on the Drive. I will also change the memory in case that is faulty but will now have to FDISK the drive, reload and see what happens.
Thanks for your input