XP crash
XP crash
I had a system hang earlier today and I had to hold the power button to get it to restart.
however upon restart, I got this message:
missing or corrupt file
\windows\system32\config\system
and it prompted me to use the recovery console to repair it.
at the recovery console there are no real options to repair this that I can find...I tried a chkdsk and even a chkdsk /r but neither helped.
I loaded the xp disc in to see if I could get to the repair screen, but it only gives me the option to:
set up windows
to create a partition
to delete the selected partition
it shows that I have a partition...it says:
c: partition1 (fat32) 76317 MB (38890 free)
does anyone have any suggestions on how to repair this? I dont want to lose my data
thanks for any help!
RM
however upon restart, I got this message:
missing or corrupt file
\windows\system32\config\system
and it prompted me to use the recovery console to repair it.
at the recovery console there are no real options to repair this that I can find...I tried a chkdsk and even a chkdsk /r but neither helped.
I loaded the xp disc in to see if I could get to the repair screen, but it only gives me the option to:
set up windows
to create a partition
to delete the selected partition
it shows that I have a partition...it says:
c: partition1 (fat32) 76317 MB (38890 free)
does anyone have any suggestions on how to repair this? I dont want to lose my data
thanks for any help!
RM
In my desperation I did a google search using the error above and found this page:
http://www.kellys-korner-xp.com/xp_sys32.htm
I followed the instructions and it repaired my windows (tho I have to reinstall my service pack 1 and critical updates....there were no system restore dates, tho I'm sure I had manually made one recently, and windows had to do the 'find new hardware' thing.).
At least I didnt lose my data.
Are there any precautions I can take to protect from this kind of situation in the future? (back up disk, etc...I have no idea...?)
I'll paste the solution below...hopefully this will help someone in the future.
RM
Cannot Start Windows XP if the System or Software Hive Is Missing or Damaged (Q303012)
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)
http://www.kellys-korner-xp.com/xp_sys32.htm
I followed the instructions and it repaired my windows (tho I have to reinstall my service pack 1 and critical updates....there were no system restore dates, tho I'm sure I had manually made one recently, and windows had to do the 'find new hardware' thing.).
At least I didnt lose my data.
Are there any precautions I can take to protect from this kind of situation in the future? (back up disk, etc...I have no idea...?)
I'll paste the solution below...hopefully this will help someone in the future.
RM
Cannot Start Windows XP if the System or Software Hive Is Missing or Damaged (Q303012)
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)
I agree w/ Warlock here -- NTFS is far more robust, you're a lot less likely to see this kind of "accident" w/ it. To do that try the following command line (got that from the W2k reference, XP should be the same -- check WXP help for "ntfs" if in doubt):ReadyMan wrote:Are there any precautions I can take to protect from this kind of situation in the future? (back up disk, etc...I have no idea...?)
convert c: /fs:ntfs
Personally I'm not trusting the XP system restore sheme so I'm using an USB 2.0 disk w/ DriveImage 7.0 once a week..
-
- Defender of the Night
- Posts: 13477
- Joined: Thu Nov 05, 1998 12:01 pm
- Location: Olathe, KS
- Contact:
I actually had that happen to me when installing the latest nForce2 drivers when they first came out. (lazy me didn't uninstall the old ones first) I was able to break back into windows by going into Debug mode (hit F8 to bring up the startup options BEFORE windows starts to load) and uninstalling them both, restarted and installed the latest ones.
I'm trying to remember why I went with fat32...I think it has to do with times in the past when I had virii, and needed to access dos to delete the various worms, etc (I cant remember exactly, but I think the trend micro systems virus cleaner needs you to go to Dos to do certain functions).
When I got hit with a virus, I had to do a reformat on my wife's machine (ntfs), but was able to fix it on my machine (fat32).
However, 'more robust' is a good thing. this is the first time I've had a situation like this...and I dont want to endure it again
I'm leaning toward converting the drive to ntfs....
When I got hit with a virus, I had to do a reformat on my wife's machine (ntfs), but was able to fix it on my machine (fat32).
However, 'more robust' is a good thing. this is the first time I've had a situation like this...and I dont want to endure it again
I'm leaning toward converting the drive to ntfs....
im almost similar.....two drives..one contains OS And less important software and files...Warlock wrote:thats y i have a drive just for the OS and a drive for all my Data, so if some thang happens i can blow the little 40gb and reinstall with no probs at all
second drive contains all the important apps, software and important files
I converted my drive to NTFS, did a chkdsk, and a defrag, and its running smooth and fast.
thanks for the input/suggestions.
I've got another HD sitting here that I ghosted about a year ago (I bought a copy of norton utilities that comes with ghost)...I'm thinking I should make a ghost image of my drive in its current state and copy it to my other HD (and just keep it around as a master copy).....but I cant remember how to do it (or how I did it)...
I'm approaching 40 and my mind is decomposing
(anyone have rundown on how to ghost to another HD?)
thanks for the input/suggestions.
I've got another HD sitting here that I ghosted about a year ago (I bought a copy of norton utilities that comes with ghost)...I'm thinking I should make a ghost image of my drive in its current state and copy it to my other HD (and just keep it around as a master copy).....but I cant remember how to do it (or how I did it)...
I'm approaching 40 and my mind is decomposing
(anyone have rundown on how to ghost to another HD?)
ntfs is some kind of closed m$ standard and they never released any info about it. so if you converted your system-partition to ntfs you cant access it with any other system to fix your os or do a image for that partition. good luck if you get a v-infection, boot-disks or linux boot-cds wont help you anymore cause mostly nothing can read and write ntfs.
your right jeff, ghost is an imagetool. you can make nice backups from your partition but not fix it. price: 70us$.
ntfsdos has no write capability, read only. ntfsdos professional can write, but is only avaible in the administratos pack, us$300+
that leaves alone the xp recovery console. imho using ntsf for the os-partition was never a good idea.
ntfsdos has no write capability, read only. ntfsdos professional can write, but is only avaible in the administratos pack, us$300+
that leaves alone the xp recovery console. imho using ntsf for the os-partition was never a good idea.
Yup. Depending on the version of ghost, you've got two options. Option one is to double click on the Ghost icon in your system tray and look for the "Clone" feature(in Ghost 2003, it's under the Ghost Advanced tab). Or you can have it create a boot disk and use their PC DOS interface to create a Ghost.ReadyMan wrote: (anyone have rundown on how to ghost to another HD?)
I like doing it this way. Create a stable platform, Ghost it to another drive then if everything gets hosed you can go back. The problem is still backing up files you've created since you created the Ghost image on the other drive. Might be nice to stick the Ghost drive into a removable tray.
NTFS is good. If ever you run into Win2k/XP problems again and need to reinstall JUST the OS, what you do is this:
Boot from CD
Once you boot from the CD, it gives you the option to Repair, Install or Quit
Select Install
It'll have you accept the EULA and then will scan for previously installed OSes
It'll detect your current installation of Windows and will give you another set of options.
Repair, Format or Quit
If you select Repair from this point, it will erase your current Windows files(including drivers) and reinstall fresh ones. It will not(read: should not) affect your other files. Again, it's always good to make a backup first before you start this, but that's the most convenient way to re-install Windows files. Worst case: call me.
Sorry for the long post.
Not true NTFS bases on HPFS that was developt by Mickeysoft for OS/2. You can get drivers for most other OS's, just use google. The DOS boot crap is pure legacy and done by virus scanner manufactors to make you buy the full version (which doesn't need DOS). AntiVir2k is free for personal use and won't require any DOS to clean up stuff.DigiJo wrote:ntfs is some kind of closed m$ standard and they never released any info about it. so if you converted your system-partition to ntfs you cant access it with any other system to fix your os or do a image for that partition. good luck if you get a v-infection, boot-disks or linux boot-cds wont help you anymore cause mostly nothing can read and write ntfs.
Since he's running an XP system, he can use the XP cd to boot into a console for fixing stuff
FAT was developt for FLOPPY DISKS and it shows.
My computer even doesn't have a floppy drive (name one reason why you'd need it), the HDDs are formated NTFS and I never was sorry about it.