Groups

    Help from a computer Wizard needed! Error message "systemRootsystem32configSOFTWARE"

    Ok just logged onto the "family computer" and after booting it up, after the Windows XP loading screen, a blue screen followed with the following message:

    STOP: c0000218 {Registry File Failure}
    The registry cannot load the hive (file):
    systemRootsystem32configSOFTWARE
    or its log or alternate.
    It is corrupt, absent, or not writable.

    Beginning dump of physical memory
    Physical memory dump complete.
    Contact your system administrator or technical support group for further assistance.

    I have no idea what has been done as I rarely use that PC, does anybody else have any idea what the solution is to fix this problem?

    Any help would be greatly appreciated

    Thanks
    Alex

    12 Comments

    Do you have the operating system CD/DVD for the system? If so I'd boot from that and attempt a repair install, the error basically means a core part of the operating system is corrupted. It may be that the hard drive is failing and this is just the first sign but it's difficult to tell remotely without further information.

    John

    put it the windows disc, then follow the instructions to repair the instalation.

    i used to have a problem with my last laptop blue screening all the time.
    it just needed more memory which cost me about 12 quid

    I've just had a similar problem . I had been using this PC on the 20th sep , next day I turned it on and BSOD and hard drive wipe out . Lost all the stuff on the drive , but had most backed up , so i wasn't really bothered .But certainly dont know what's causing the problems like this .The recovery mode doesn't always work and you may end up having to format the drive and start again ,thats if the drive is OK .
    Do you have important stuff on the drive ? .

    As John said it sounds like the registry is corrupted which could just be a corrupted file or the hard drive is dying,The big question is do you have anything important on it that you need to keep and do you have a recovery disk or windows disk ?.

    try safe mode f8 on bootup

    Take a backup and then reinstall - also check the smart status of your harddrive

    it is a corrupt registry file. there is a proceedure to fix it but it's complicated

    Edit: here support.microsoft.com/def…545

    Original Poster

    Thanks for the advice, the PC is around 3 years old, it certainly isn't a ye olde PC, only thing I know for sure is that it has 1gig of RAM
    There isnt really much important stuff on there, more of a PC just for net browsing for the rest of the family

    One thing that they have told me is that the PC has a habit of restarting itself, even though you have selected for it to shut down, sometimes it does this, sometimes it doesnt, so then they turn it of by the plug! Which they have done for a good few months now, I'm guessing that it may have finally taken its toll on the PC

    Only lucky thing is that I don't use that PC

    remember ,some of the microsoft updates cause a re-start ,you normally get a green shield on the taskbar as oposed to the gold one .I've seen pc's just reboot after one of these criticle updates.
    If the PC is just switched off at the mains instead of closeing down normally , this can damage system files as well as cause bad sectors on the HDD [,seen this happen after power cuts ] , both problems can be associated with the BSOD [blue screen of death ].

    avfc456;6378464

    One thing that they have told me is that the PC has a habit of restarting … One thing that they have told me is that the PC has a habit of restarting itself, even though you have selected for it to shut down, sometimes it does this, sometimes it doesnt, so then they turn it of by the plug! Which they have done for a good few months now, I'm guessing that it may have finally taken its toll on the PC



    This error can be a result of the machine being powered down while it was still running, each time this is done it risks corrupting part of the Windows system which will cause an error like this. bruffterman's advice is spot on and is the normal fix I'd recommend (I've seen on quite a few work machines with impatient users) although it's a little fiddly if you're not used to booting into a command line like that, a repair install should offer a similar fix but it's a bit more user friendly.

    John

    Banned

    VERY VERY easy to fix if you know how.

    You need to boot up with BART or boot up to another HDD & copy files from the snapshot folder into the sys 32 config folder..

    Dont try F8 etc, that will not work, people are just guessing
    Post a comment
    Avatar
    @
      Text
      Top Discussions
      1. What would be HELL to you?1416
      2. I want to talk about the WEATHER no politics no religion19047119
      3. love affairs1751
      4. What do you feel like whinging about today?1927365

      See more discussions