[RESOLVED] Windows XP won't boot--corrupt registry?
Page 1 of 3 123 LastLast
Results 1 to 15 of 36

Thread: [RESOLVED] Windows XP won't boot--corrupt registry?

  1. #1
    Join Date
    Oct 2005
    Location
    Los Angeles, CA, USA
    Posts
    59

    Resolved [RESOLVED] Windows XP won't boot--corrupt registry?

    Hi folks,

    I'm trying to recover my computer from a corrupt registry, I think. I did a quick search for similar situations, but most sounded slightly different, so here's my situation, and any and all suggestions are immensely appreciated.

    Problem: When my computer starts up and is about to boot into Windows XP, a screen comes up that says:

    Windows could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM
    You can attempt to repair this file by starting Windows Setup using the original Setup CD-ROM. Select "r" at the first screen to start repair.


    Background: Problem started while media player was ripping some music off of a CD. The computer spontaneously restarted while it was ripping, and I got the message above.

    What I've tried:

    1. Following its instructions, but no repair option is available using a Magnell Recovery CD (what the computer came with) or XP Pro CD. Perhaps b/s it's an OEM install?

    2. I loaded the repair console from the XP CD instead. But I can't make it do much. When I enter chkdsk, it says "The volume appears to contain one or more unrecoverable problems" and can't do it. "Fixboot" gives "FIXBOOT cannot find the syste drive, or the drive specified is not valid." Just hitting DIR makes it say "There is no floppy disk or CD in the drive." If I type "e:" it will switch to my other drive, but hitting DIR gives the exact same response. If I try to change directories (say, "cd windows") it also says "There is no floppy or CD in the drive."

    3. Someone suggested it might be faulty memory or hard drive, so I downloaded Western Digital's diagnostics and ran full tests on both my hard drives. Neither showed any problem. I also ran Memtest86 for 9 hours, and no errors occurred. That and the fact that both hard drives are responding identically in recovery console makes me think it's not a drive failure of some kind.

    4. I couldn't start in safe mode either (never got to the menu to select it).

    5. I downloaded something called "BartPE", which let me make a boot disk to boot the computer. Using that, I can get read/write access to all files on both my hard drives.

    6. I deleted (after backing up, of course) the System, Security, SAM, Software, and Default files in the Windows/System32/config folder, and replaced them with the seemingly equivalent files from a restore point file in the System Volume Information folder.

    7. This now lets me get to the menu where I can select safe mode, safe mode with networking, last known good configuration, etc. But selecting any of them still gives the original error message above, with one difference if I select Safe Mode--the error message has some files above it, so that it looks like this:

    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS\system32\ntoskrnl.exe
    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS\system32\hal.dll
    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS\system32\KDCOM.DLL
    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS\system32\BOOTVID.dll
    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS\system32\config\system
    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS\system32\config\system.alt

    Windows could not start because the following file is missing or corrupt:
    \WINDOWS\SYSTEM32\CONFIG\SYSTEM
    You can attempt to repair this file by starting Windows Setup using the original Setup CD-ROM.
    Select 'r' at the first screen to start repair.


    But there's still no repair option, and I still can't get into safe mode or anything else, except through the BartPE CD.

    Using the BartPE disk, I backed up all my files off of the hard drive. But I really want to salvage it if I can. I have had this problem once before (6 months ago) and restoring to the factory image was the only resolution I found.

    But I don't want to do that this time! I'll try whatever you suggest! Is there anything left to try?

    Here's my hardware, if it's needed at all...it's a pre-built ABS computer.

    AMD 64 3400 (754)
    Gigabyte GA-K8N Pro mobo
    1 gig Corsair RAM (XMS series, 2 x 512 DDR sticks, 32MX8 PC-3200)
    Windows XP Home (OEM install)
    Radeon 128 9800 Pro
    Soundblaster Audigy 2 ZS Platinum
    Antec 1000AMG case, with 530W Fortron Power supply
    Two Western Digital 120 GB SATA hard drives
    Sony DVD ROM
    Plextor CD burner (PX-W5224TA)
    Floppy drive
    8-in-1 card reader sort-of-deal
    Phone modem (PCI card)

    Any and all suggestions are immensely appreciated! I'm sorry this is so long, but I've been working all week at trying to figure out how to save this thing.

    Thank you!

  2. #2
    Join Date
    Feb 2000
    Location
    somewhere on the planet earth.
    Posts
    1,649
    what you can do is windows repair as it seems you have windows xp disk.
    how do i repair windows xp

    WARNING:it will force you to do all windows update again as it will basically will do reinstall of windows.

  3. #3
    Join Date
    Oct 2005
    Location
    Los Angeles, CA, USA
    Posts
    59
    Hey ylen13,

    I would happily, happily do a Repair installation, but there's no option for that when I use either the recovery CD that originally came with the computer or an XP MCE 2005 CD. I mean, I hit enter at the first blue screen, go past the EULA, and there's just no option for it, only one for doing a clean install.

    I was thinking it might be because it's an OEM installation? Anyway, thank you for the suggestion...any other ideas?

  4. #4
    Join Date
    Jun 2005
    Location
    Ft Myers FL
    Posts
    8,520
    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS\system32\config\system
    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS\system32\config\system.alt

    Windows could not start because the following file is missing or corrupt:
    \WINDOWS\SYSTEM32\CONFIG\SYSTEM
    It looks like your original config\system folder is still there, and the replacement is config\system.alt.

    Make sure you only have one system file in the config folder, if there's a system.alt choose which one is the wanted one and rename it system if necessary. Then reboot into Safe Mode w/Command Prompt, and when you get to the system.alt command enter "N" to bypass that. That should boot up--or go to the next blockage. You're going to do some tedious stuff, whether this way or by doing a repair/install.

  5. #5
    Join Date
    Aug 2001
    Location
    Keizer,Orygun USofA
    Posts
    10,636
    From what you say,I'd suggest this,(but only if you have a valid,full XP-disk and have the key code) Use the WD tool and low level format(wipe)both drives. Install XP fresh on drive #1.(be sure to have a floppy with your SATA drivers onboard and in the drive and the XP disk in the primary optical drive. During setup,it will tell you to press F-6 to install third party drivers. It should then access the floppy for those.(if not,check in bios to be sure SATA is enabled) It should offer to let you partition your drives next. I would suggest you create at least 2 partitions on each drive. When you are given the drives size(in MB's)you can backspace the MB's out and then enter ½ of the original amount. Then just follow instructions to do the rest.
    You will have to format your drives other than C:\ from Start>Settings>Ctrl Panel>Administrative tools>Computer management>Disk Management(left window).If you have files on your second drive that are accessible,I'd suggest you unplug it until your #1 drive is up n' runnin'. Be sure to have/and install,your basic drivers first i.e.:motherboard chipset>video drivers>sound drivers>modem drivers. If,that is, Windows does not find and install them for you(which I wouldn't advise)do not connect to the internet to stop Windows from doing this. And be sure to have the XP firewall running when/if you have to go online to get a third party firewall and/or antivirus program or needed drivers.

    The problem(s) you have now 'may' be fixable,but with the expense in time and as you have your files already backed up,this would be the easiest way and give you a squeaky clean install to go with...
    Stupid question? No such thing!
    Virtual Dr. to the rescue!
    Just ask. Bookmark your post for easy reference.
    ==================================

  6. #6
    Join Date
    Oct 2005
    Location
    Los Angeles, CA, USA
    Posts
    59
    Hey lgbpop, so I browsed into the config folder and there are three system-related files in there, as far as I can tell, and none of them are labeled "system.alt." They are: system.log, system.sav, and the restore system file I'd copied in there, which is still called _REGISTRY_MACHINE_SYSTEM. Do you think it's one of those? Which should I rename/delete? I'll try to whatever you suggest! I am so willing to do the tedius stuff! Thanks for the help!

  7. #7
    Join Date
    Oct 2005
    Location
    Los Angeles, CA, USA
    Posts
    59
    Hey Ridgerunr, thanks for the suggestion. That sounds like a clean install though--isn't it? If possible, I'd really like to avoid that. I know I'll have to do some tedious work to get past this (if it's possible at all), and if I can't figure it out by this weekend, I think I will definitely follow your instructions and just reformat it and do a clean install. Is there anyway I might still try to recover though? It's mainly because there are a bunch of programs on there with specific settings I'd really like to keep. Thanks! I've learned my lesson, after this I'm learning ALL about backing up my drive...

  8. #8
    Join Date
    Jun 2005
    Location
    Ft Myers FL
    Posts
    8,520
    Quote Originally Posted by bovinda
    Hey lgbpop, so I browsed into the config folder and there are three system-related files in there, as far as I can tell, and none of them are labeled "system.alt." They are: system.log, system.sav, and the restore system file I'd copied in there, which is still called _REGISTRY_MACHINE_SYSTEM. Do you think it's one of those? Which should I rename/delete? I'll try to whatever you suggest! I am so willing to do the tedius stuff! Thanks for the help!
    The one the computer sees as system.alt is the REGISTRY_MACHINE_SYSTEM file I believe. Don't delete anything, but try this:
    1) copy & paste the REGISTRY file you made; paste in the same place as the original.
    2) it appears the system file you deleted is actually gone. Rename the copy you just made and call it system. Just leave it there. Now try booting again with the command prompt as I suggested and see what happens. If this doesn't work, you can always restore the names.

    It's also possible that system.log or system.sav is actually what you think you deleted; you may have to open them to see which seems closest, then go from there.

    BTW--Welcome to VirtualDr!

  9. #9
    Join Date
    Oct 2005
    Location
    Los Angeles, CA, USA
    Posts
    59
    Hey lgbpop, thanks for the welcome!

    So I renamed _REGISTRY_MACHINE_SYSTEM to system, and went and tried booting into safe mode (with command prompt) again, and it went past the system file this time! Now it stops and hangs at another file. Basically, it started displaying like 30 files in the Windows/System32/Drivers folder. The last one it stops at and freezes at is

    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS\System32\Drivers\Mup.sys

    There are a bunch before that, but that's where it freezes. I tried pressing "n", but it won't skip past--it seems solidly frozen. What do you think? I'm excited to be making any progress at all! Let me know if you need a list of the files before that, I can type them out.
    Last edited by bovinda; October 20th, 2005 at 11:14 PM.

  10. #10
    Join Date
    Oct 2005
    Location
    Los Angeles, CA, USA
    Posts
    59
    Okay, last post for the night...after googling for a bit, it sounds like the mup.sys file may or may not be the culprit. Sounds like many people have tried switching it with mup.sys files from working systems and hasn't affected their problem (I haven't tried it yet though). Found a post on Anandtech suggesting that updating the BIOS might allow you to pass that point, and I figured I was going to update the BIOS anyway after all this in case it was the original culprit of my problem.

    So I went ahead and updated the BIOS to the most recent version. Now when I try to enter any Safe Mode, instead of hanging at the mup.sys file, it just reboots altogether, so it seems to be in a rebooting loop, huh?

    Anyone else have any suggestions? I will check back tomorrow morning. I am soooo wishing this was not an OEM install right now--from what I've read, that's what's not allowing me to do a repair install. What do you folks think? Anyway, keep those suggestions coming!

  11. #11
    Join Date
    Jun 2005
    Location
    Ft Myers FL
    Posts
    8,520
    See this thread; that's where I am too. Don't bother posting the file list, I have it written down....

    I may get a chance to work on it tonight or tomorrow, but that's back-burner stuff now. Gotta get the house ready before Wilma roars by this weekend. If I figure it out, I'll let you know. One hint: If you have access to another (working) XP machine, try adding the Mup.sys file from a proven working copy (rename the existing one, don't delete it!) before resorting to the default file off a CD--although it may be identical, it's way easier to find than digging through .cab file folders. Also, I think the Mup.sys file actually is the last good file to load, and the freeze point is at the next command in the boot sequence. I have the dump file with the command file name, but it's encrypted and need to know the decoder name to see what's next to replace.

  12. #12
    Join Date
    Jul 2004
    Location
    North West England.
    Posts
    9,568
    bovinda: lgbpop just asked me to add some instructions for a possible solution: Boot a working XP system in Command Prompt mode, and make a note of each file in the boot sequence, then you'll know what needs fixing when the system in question freezes.


    Liam
    Desktop:I5 2500K|Asus P8Z68-V|8GB Corsair Vengeance|1280MB Nvidia 560 TI PE|1TB Seagate/60GB OCZ SSD|LG Blu-ray Writer|Corsair 750W
    27" iMac:I5 2500S|12GB Crucial DDR3|ATI 1GB 6970|1TB|Superdrive|Mighty Mouse

  13. #13
    Join Date
    Apr 2000
    Location
    Friern Barnet, London, England
    Posts
    46,565
    Have a look on your recovery CD and tell us if there is a folder called I386 on it. If there is, then we can tell you how to boot into the normal Windows Setup and run a repair install.
    Nick.

  14. #14
    Join Date
    Oct 2005
    Location
    Los Angeles, CA, USA
    Posts
    59
    Hey lgbpop, thanks for the help, and take care man, Wilma sounds like a monster! I'll keep an eye on your thread too. Liam858, thanks for passing that along also, I will try that too.

    SuperSparks, there is a I386 folder on the recovery CD! I would so happily do that, just let me know what to do!

  15. #15
    Join Date
    Jul 2004
    Location
    North West England.
    Posts
    9,568
    No probs for passing on the info.

    Here is what to do with the recovery CD:

    Insert the disc with the i386 folder into the CD-ROM drive, and then go to Start|Run|type d:\i386\winnt32.exe /cmdcons (where d is the drive letter for the CD-ROM drive, change as applicable) A Windows Setup Dialog Box appears and describes the Recovery Console option to confirm the installation, click Yes, restart the computer. The next time that you start your computer, "Microsoft Windows Recovery Console" appears on the startup menu.

    Liam
    Desktop:I5 2500K|Asus P8Z68-V|8GB Corsair Vengeance|1280MB Nvidia 560 TI PE|1TB Seagate/60GB OCZ SSD|LG Blu-ray Writer|Corsair 750W
    27" iMac:I5 2500S|12GB Crucial DDR3|ATI 1GB 6970|1TB|Superdrive|Mighty Mouse

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •