hal.dll error

VonVulcan · Post by **VonVulcan** » Mon Jan 05, 2009 9:35 pm

So, I searched it and found several options to repair or replace the file, or a damaged boot.ini however, I can't get the computer to boot far enough to do any of the recommended repairs. My daughter brought it over from a friend that gave it to her. It's boot logo is MSI and the restore disk is in the cdrom however when I try and boot from it, the system will shut down at random points in the process and try to reboot.

Hardware failure?

AceCombat · Post by **AceCombat** » Mon Jan 05, 2009 10:25 pm

you tried using a XP CD or anything to repair it?

woodchip · Post by **woodchip** » Tue Jan 06, 2009 11:29 am

Can't get into safe mode either?

Krom · Post by **Krom** » Tue Jan 06, 2009 12:24 pm

Odds are if hal.dll is toast you are going to have to repair install from the XP CD since I'm pretty sure windows can not start at all without it.

Boot off your XP disk, and proceed as if you were installing windows normally (don't use automated system recovery), after searching for existing windows installations it should prompt you to press R for a repair install. It will delete and replace all windows files while preserving your programs, documents and configuration and should get windows booting again.

captain_twinkie · Post by **captain_twinkie** » Tue Jan 06, 2009 1:14 pm

Or you could try

http://support.microsoft.com/kb/945380

VonVulcan · Post by **VonVulcan** » Tue Jan 06, 2009 8:26 pm

Can't get into safe mode. I did make a msdos boot disk on a floppy from a different puter. Sometimes it will boot to A:\\ sometimes it just loops the post screen.
Can't get it to switch to C: (says invalid drive) if it does boot to A:
Seems to be completely unstable.
Will try a winxp cd repair or reinstall next if it will stay running.

Thanks!

Krom · Post by **Krom** » Tue Jan 06, 2009 9:47 pm

If you are concerned that there is a hardware failure that caused this, inspect the inside of the machine for loose cables and connections (better safe than sorry). Also you could download a Linux live CD distro such as ubuntu and see how well it runs to verify if everything is working properly.

EngDrewman · Post by **EngDrewman** » Wed Jan 07, 2009 2:49 am

To try to boot windows to see if it is a hardware or software issue, try the boot disk at this site. It's meant for a different type of error, but if your win installation is still bootable, it will start it up.

If that doesn't do the trick, then try booting a live CD of Ubuntu or PCLinuxOS to see if your hardware is working. If your hardware is ok, then run the repair cycle on your win XP cdrom.

AlphaDoG · Post by **AlphaDoG** » Wed Jan 07, 2009 5:46 am

http://www.ultimatebootcd.com/download.html

That thing there is your friend. Keep one handy at all times.

VonVulcan · Post by **VonVulcan** » Wed Jan 07, 2009 8:57 pm

Krom, I opened it up, blew it out and checked wires, connections ect. Removed the mem and vid card. Re installed them and it seemed to get my a little further in the process. I finally got it to boot the recovery CD and there was no option to repair, just reinstall... so I think go ahead, nothing on here that works anyway. Several attempts get to the setting up windows part and I get the old BSOD. On multiple attempts.

So I am digging around in my old CD pile and run across Memtest86+ boot disk some of you guys told me to get a year or so ago. After running for about 1/2 hr. it is showing errors. Failing address. The puter has only one 512m stick in it so I guess I will get some different memory and see what happens.

Krom · Post by **Krom** » Wed Jan 07, 2009 10:42 pm

I've seen memtest throw errors on good memory because of a bad CPU before, so if you know you have a good stick of memory operating well within tolerances and it still throws errors I would investigate more than just the mainboard. A system working properly should show zero errors in memtest even when tested continually for days so you are making some progress, now to find what is causing it exactly.

When dusting and other simple fixes fail, for most cases like this I usually have to resort to the only reliable way to find out what exactly is causing the problem: Swap pretty much every single part from the bad computer one at a time into a similar but good computer. When the good computer gets the same symptoms, you have found the culprit. Unless I have a hunch it is a specific component already I usually work my way from easier to replace components to the harder to replace ones. Starting by removing/disconnecting non-essential devices (anything that doesn't need to be there to POST) and testing it, then individually testing the memory, video card, PSU, drives and then the CPU last. If they all work in the good computer error free then you know the mainboard is bad.

Also there should be some caution applied to how you do that type of testing, for instance don't test the PSU from the bad computer in the good one, test the bad computer with a known good PSU instead. Disconnect drives with important or valuable data from both computers and don't reconnect them till you are done. When moving the CPU from one computer to another even if it is only for a 30 second POST test, use a proper coating of thermal compound (that's why I keep a tube of arctic silver around). And as always, take precautions to avoid static discharge.