1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

System32 issue, now Hal.dll problem!!!

Discussion in 'PC hardware help' started by Gregerss, Feb 6, 2009.

  1. Gregerss

    Gregerss Member

    Joined:
    Oct 24, 2007
    Messages:
    13
    Likes Received:
    0
    Trophy Points:
    11
    Hey guys.
    Can anyone help please.
    A friend of mines PC has stopped working.
    They just turned it on the other day and aswell as the computer constantly beeping at them this error message came up windows/system32/config/system

    I've looked around on here and a lot of you said about just putting the XP disk that came with it in and repair in repair console.
    I done this for her and then a new problem came up.
    It wouldn't start at all, just kept beeping.
    So I put the disk back in and it's now saying hal.dll file is missing and it can't read it from the disk.
    I've looked on here for hal.dll solutions and they all look to complicated to me, has anyone got a simpletons method for me!!!

    PLEASE!!!

    Cheers guys.
     
  2. Gregerss

    Gregerss Member

    Joined:
    Oct 24, 2007
    Messages:
    13
    Likes Received:
    0
    Trophy Points:
    11
    Anyone???????
     
  3. ddp

    ddp Moderator Staff Member

    Joined:
    Oct 15, 2004
    Messages:
    39,167
    Likes Received:
    136
    Trophy Points:
    143
  4. Gregerss

    Gregerss Member

    Joined:
    Oct 24, 2007
    Messages:
    13
    Likes Received:
    0
    Trophy Points:
    11
    Yeh I know, sorry about that!:)

    After reading that I still have one question, How can I do any of that if I can't even get windows to start though??
    Without the disk it just bleeps constantly and doesn't boot and if I put the disk in I just get the message about the hal.dll missing/corrupt.

    Why doesn't the disk just fix it damn it!!!!!
     
  5. ddp

    ddp Moderator Staff Member

    Joined:
    Oct 15, 2004
    Messages:
    39,167
    Likes Received:
    136
    Trophy Points:
    143
    change in the boot order in the bios so that the rom drive boots up before the hard drive.
     
  6. jony218

    jony218 Guest

    First make a bartpe bootcd, all you need is the windows installtion cd and the bartpe program (free download). It takes 10 minutes to make. You can also use the windows installation cd and go to the dos command line, but it is more complicated.

    Next bootup with the bartpe bootcd. Go to the command line and type only what is in the parenthesis (chkdsk c: /f). This will fix any system files that are corrupted.

    The problem you describe occurs when the computer has an abnormal shutdown, while the hard drive was still writing to the hard drive. this corrupts the system files and you get all these errors.

    Chkdsk will usually fix this problem and make your computer bootable again. It has always worked for me. This is a quick fix.

    If chkdsk doesn't work, there are other programs that can be tried. "Testdisk" is a free hard drive repair/recovery program. Testdisk has more powerful partition repair tools. In worst case scenario all the data in the hard drive is safe and can be recovered. A few corrupted files will make the entire drive look like it's damaged beyond repair, but the drive is ok.
     

Share This Page