|
 |
 | | Hal.dll is corrupt or missing |
|
 |
 Posted: Sat May 24, 2008 9:56 pm |
 |
|
| paul68 |
| Shaved Ape |
 |
| |
| Joined: 15 Nov 2005 |
Posts: 2064
Karma: +21
|
| Location: Wer'e not from around here man! |
|
|
|
|
 |
|
If you come across this, just set your PC on fire. Then buy a new one.
 |
|
|
|
|
|
|
|
| Posted: Sun May 25, 2008 7:31 am |
|
|
| Raven |
| Google Meister |
 |
| |
| Joined: 24 Oct 2005 |
Posts: 2906
Karma: -16
|
| Location: Detroit, MI, USA, North America, Earth, Sol, Orian's Arm, Milkyway, Uni Alpha-Prime |
|
|
|
|
|
|
Personally, i just don't trust anything on my computer named Hal...
But:
http://pcsupport.about.com/od/findbyerrormessage/a/missinghaldll.htm
| Quote: | Missing Or Corrupt Hal.dll Error Resolution
Steps to Resolve the Missing Or Corrupt Hal.dll Error in Windows XP
By Tim Fisher, About.com
Error Message
There are few different ways that the "missing or corrupt hal.dll" error may present itself, with the first listing being the most common:
"Windows could not start because the following file is missing or corrupt:
<Windows root>\system32\hal.dll.
Please re-install a copy of the above file."
Winnt_root>\System32\Hal.dll missing or corrupt:
Please re-install a copy of the above file."
"Cannot find \Windows\System32\hal.dll"
"Cannot find hal.dll"
The "missing or corrupt hal.dll" error displays shortly after the computer is first started. Windows XP has not yet fully loaded when this error message appears.
Cause
Causes of the "missing or corrupt hal.dll" error include, naturally, a damaged hal.dll file or a hal.dll file that has been deleted or moved from its intended location. Additional causes may include a damaged or missing boot.ini file or possibly a physically damaged hard drive.
Resolution
Restart the PC. The hal.dll error could be a fluke.
Run Windows XP System Restore from a command prompt. If this doesn't work or you're receiving the hal.dll error message before you're able to complete this process, move on to Step 3.
Repair or replace the boot.ini file. This will work if the cause of the problem is actually Windows XP's boot.ini file and not the hal.dll file, which is often times the case.
Write a new partition boot sector to the Windows XP system partition. If the partition boot sector has become corrupt or isn't properly configured, you may receive the hal.dll error.
Restore the hal.dll file from the Windows XP CD. If the hal.dll file is truly the cause of the problem, restoring it from the original Windows XP CD may do the trick.
Perform a repair installation of Windows XP. This type of installation should replace any missing or corrupt files. Continue troubleshooting if this does not resolve the issue.
Perform a clean installation of Windows XP. This type of installation will completely remove Windows XP from your PC and install it again from scratch. While this will almost certainly resolve any hal.dll errors, it is a time consuming process due to the fact that all of your data must be backed up and then later restored.
If you can't gain access to your files to back them up, understand that you will lose them all if you continue with a clean installation of Windows XP.
Finally, if all else has failed, including the clean installation from the last step, you're most likely facing a hardware issue with your hard drive. Replace the hard drive and then perform a new installation of Windows XP.
Applies To
This issue applies to the Windows XP operating system, including Windows XP Professional and Windows XP Home Edition.
Still Having Hal.dll Issues?
Let a community of PC support enthusiasts help out! Post the details of your problem in the Focus on PC Support Forums. Be sure to let us know what steps you've already taken to resolve the "missing or corrupt hal.dll" issue. |
http://www.dll-doctor.com/landing/dll2/haldll.php?t202kw=hal.dll&c=5&m=e&lpip=2263&gclid=CPD-7YfTwZMCFQUjGgodB2j3CQ
| Quote: | Hal.dll - How To Fix It Correctly
Jason Biddle, MCSE Certified PC Tech
Friday May 23, 2008, 4:32 PM EST
As the "computer guy" in the family, everyone calls me when something goes wrong. Last night I got one of those frantic calls from Mom.
Her computer kept having "Missing, Damaged and Corrupt Hal.dll" problems and she was pretty upset. Unfortunately, DLL problems are very common but not easy to fix correctly.
Hal.dll and other DLL (Dynamic Link Library) files are "shared" by all computer programs. When a program runs on your computer, it tries to lookup the required DLL file locations in your Windows Registry - the "phonebook" of DLL files.
When you install and uninstall programs, sometimes the "addresses" of these shared DLL files get changed.
This is where the problem begins.
The Registry goes to "lookup" the file in the old location but it's not there anymore. This triggers a "Missing, Damaged, or Corrupted DLL Error".
Because the name of the DLL file is often in error message, most people think they can fix Hal.dll simply by replacing it. They search and download it from the Internet, find where it goes in their system, and get rid of the old file. Fixed, right?
Wrong. For several reasons.
First, DLL errors come in packs. One DLL error is a warning sign that there are hundreds more - it's nearly impossible to find and replace them all... unless you've got a few free days on your hands.
Second, after you replace a DLL file you need to update its new location in the Registry. Have you edited your Registry lately? Me either, and I repair PCs for a living!
Editing your Registry is extremely risky - just one mistake can cause permanent system damage. Because of this, most PC techs won't touch it and Microsoft strongly advises against it.
Obviously, this was a big problem with no easy solution until...
Recently, a group of smart Canadian programmers decided to automate DLL repair process by designing Registry cleaning software.
The software scans thousands of DLL entries, replacing any damaged or missing files and updating their Registry locations. It does in seconds what used to take days - all without the risk of system damage.
Now, whenever someone calls me with DLL problems I always tell them to run a free Registry scan. You save time chasing down files and don't have to worry about damaging your PC in the process. It's the new "secret tool" of PC technicians.
If you're sick of fighting DLL problems, take 30 seconds to run a free registry scan. Get rid of your headache and get on with your life. |
|
|
_________________
"The most beautiful experience we can have is the mysterious. It is the fundamental emotion that stands at the cradle of true art and true science. Whoever does not know it and can no longer wonder, no longer marvel, is as good as dead, and his eyes are dimmed." |
|
|
|
|
|
|
| Posted: Sun May 25, 2008 11:03 am |
|
|
| paul68 |
| Shaved Ape |
|
| |
| Joined: 15 Nov 2005 |
Posts: 2064
Karma: +21
|
| Location: Wer'e not from around here man! |
|
|
|
|
|
|
I have spent almost two days on this Raven.
1. Most of those fixes you see online are bullshit. They might work for one out of 20 people. In 90% of the cases, they dont work. You either get "access denied" when trying to use recovery console to rewrite files, or, "enumeration error", or, your system just plain doesnt recognize anything and wont access any of it for nothing.
2. Even if you do get it working and booting up again, in about 60-70% of cases, IT HAPPENS AGAIN WITHIN HOURS OR DAYS!!!
3. Hal is the code that lets your hardware communicate with your system. Without it NOTHING WORKS right. CD erros, floppy error, HDD errors and the like. Might seem like its working, till you try to do someting, then you get "cannot" errors.
4. If I see one more website or person claim all you have to do is run this or that, or "just go to start menu, then control panel, then edit yadda yadda yadda", I swear I'm going to make the news as one of those guys who drove 1200 miles to knock on someones door! Without Hal, nothing boots. You dont get windows, you get black error screen, and that is it. The only access is by bootable floppy, (almost worthless), or Windows Xp or 2000 Install disk, (next to almost worthless).
That second bit you posted Raven? The guy is a moron. If folks like him are "certified" and make a living fixing Pc's, then I am in the wrong business and could make a killing.
"Because the name of the DLL file is often in error message, most people think they can fix Hal.dll simply by replacing it. They search and download it from the Internet, find where it goes in their system, and get rid of the old file. Fixed, right?
Wrong. For several reasons.
First, DLL errors come in packs. One DLL error is a warning sign that there are hundreds more - it's nearly impossible to find and replace them all... unless you've got a few free days on your hands.
Second, after you replace a DLL file you need to update its new location in the Registry. Have you edited your Registry lately? Me either, and I repair PCs for a living!
Editing your Registry is extremely risky - just one mistake can cause permanent system damage. Because of this, most PC techs won't touch it and Microsoft strongly advises against it."
Before I even begin to shred him, let me say, the registry aint nothing. Long as you understand how code works, you can edit it.
First, Hal is not a common DLL shared with any apps. It is a system DLL with only one job, to work as a go between for your system and it's hardware.
Second, Hal cannot simply just be replaced, not because it's a "pack" of dll errors here. It's because Hal is a specialty DLL. Everytime you change hardware, or configure something, it is changed by your system, so it can communicate with everything. This makes Hal different in every PC, every OS. You cant simply just overwrite it with a downloaded copy, and expect it to work. It has to be configured by an install prog to work with your unique system before it can be copied. Sometimes just copying works, and you can boot then fix the hardware errors, other times, nope.
Third, this entire problem HAS NOTHING TO DO WITH THE REGISTRY. Man this guy is an idiot. How the fuck are you supposed to run a "free registry scan", or "registry doctor", when YOU CANT BOOT YOUR FUCKING PC? Which goes to show, he has absolutely no clue what Hal.Dll does, and is probably hawking this "free" crap for someone.
The main root problem, is that for some reason, the system loses track of Hal.dll. It then tries to find it elsewhere, and can't. So for some other reason, it then changes the Boot.ini file to reflect the change in hal.dll. So, your system ends up basically having no boot.ini file, or a corrupted boot.ini, resluting in your pc looking for a non existent boot partition.
So, just fix the boot.ini file right?
Wrong!! Because.........."Access denied" "Unable to write", Unable to copy file", Enumeration error"!!!
Aaaaaagggggghhhhhhh.
I am seriously beginning to think this is caused by some sort of malware or virus. There is some talk out there of a boot sector virus that survives formatting, and literally deletes hal.dll somehow. If so, it would be one of the nastiest little bastards ever.
I have looked at literally hundreds of websites, MB's, and I can find no single common denominators, beside Hal.dll being missing, the boot.ini file being corrupted. Other than that, this problem appears to simply just appear out of the blue, for no reason. It is also apparently well known and common. Which leads me to wonder why the hell such a serious problem has not been addressed by Microsoft with a patch, recovery program, or something.
Folks basically turn off their PC, turn it on, and *poof*, Hal is either missing or corrupt, please replace".
It happens on brand new PC's, 2-5 year old pc's that never had a problem, no new installs, nothing, just one day *poof*. It happens when new hardware is added, new software is added, it happens when nothing is added.
The ONLY common factor, is that it ONLY happens after shutdown, and in most cases, there was no apparent problems before shutdown.
Anyhoo. I am about to go do battle with the other PC again. After waiting all night for CHKDSK to finish, which it did successfuly recovering a few errors, I am goint o try again to rewrite the boot ini and Hal.dll.
If this dont work, I'll try a recover installation of XP, which it would not let me do last night since it couldnt find any damn OS at all. And if that fails, it's format time, which really sucks, since bye by all data.
Only other option is to slave the HDD to my pc, recover data, and try rewriting the files that way. Which I am extremely reluctant to do as I'd hate to have this problem arise in my Pc. |
|
|
|
|
|
|
|
| Posted: Sun May 25, 2008 4:26 pm |
|
|
| paul68 |
| Shaved Ape |
|
| |
| Joined: 15 Nov 2005 |
Posts: 2064
Karma: +21
|
| Location: Wer'e not from around here man! |
|
|
|
|
|
|
"Runs in circles, straightlines into wall"
**THUD**
 |
|
|
|
|
| Posted: Sat May 31, 2008 9:19 am |
|
|
| paul68 |
| Shaved Ape |
|
| |
| Joined: 15 Nov 2005 |
Posts: 2064
Karma: +21
|
| Location: Wer'e not from around here man! |
|
|
|
|
|
|
JUst an update.
The PC is still comatose. I've gotten XP loaded onto it on a second partition I created so I can access the original files. Trying to reload XP as a repair install results in "Lasass.exe object not found" now which is even worse the the Hal.dll error. It now goes into an endless bootloop to setup when trying to boot from the original OS. I have done everything under the sun except rewrite windows manually. Waiting on a factory restore disk from Sony, and saved all the file for reinstall. In all seriousness, if you get the Hal.dll error, just save your files, and do a format reload. |
|
|
|
|
|
|
|
| Posted: Sat May 31, 2008 11:25 am |
|
|
| asmodee |
|
|
| |
| Joined: 17 Oct 2007 |
Posts: 929
Karma: +18
|
|
|
|
|
|
|
|
I have to fix this one every now and then, but not often enough to remember off the top of my head how to do it. For most of these boot up errors you either have to run chkdsk /r from the recovery console or copy a file back to the proper place. According to Microsoft, this file would be ntkrnlmp.exe. Microsoft's instructions are here:
http://support.microsoft.com/kb/314477
I'm sure you've already been there, though. Whenever I have to copy a file I either hook the hard drive up to another computer so I can copy it without having to use the nearly useless recovery console or I boot from a BartPE CD, which basically runs Windows off from a CD in a very limited fashion. It's extremely slow, but it will give you access to all your files and directories to copy things over.
http://www.nu2.nu/pebuilder/
It is generally easiest to hook the hard drive up as a second hard drive on a working computer to do whatever you need to get done. If the hard drive is an ATA laptop hard drive you will need an adapter.
http://www.newegg.com/Product/ProductList.aspx?Submit=ENE&DEPA=0&Description=laptop+hard+drive+adaptor&x=0&y=0
Hope something helps here, anyway. Lastly, here's the contents of a standard boot.ini file for a computer without a recovery or repair partition. Check the boot.ini and make sure it has something similar. If it has a recovery partition then there will be additional lines as well.
| Quote: |
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
|
Note that it is 5 lines. That last one may show up here split. I hope some of this helps, anyway. |
|
_________________
Yes, I LOVE to talk while I fight! What shall we talk about? Wounds? Scars? Hot, dirty monkey love? |
|
|
|
|
|
|
| Posted: Sat May 31, 2008 4:32 pm |
|
|
| paul68 |
| Shaved Ape |
|
| |
| Joined: 15 Nov 2005 |
Posts: 2064
Karma: +21
|
| Location: Wer'e not from around here man! |
|
|
|
|
|
|
"I have to fix this one every now and then, but not often enough to remember off the top of my head how to do it. For most of these boot up errors you either have to run chkdsk /r from the recovery console or copy a file back to the proper place. According to Microsoft, this file would be ntkrnlmp.exe. Microsoft's instructions are here:"
Did that. No help. Also rewrote boot.ini. Also went into the windows backup copies and copied them to the startup files. No go. Also recopied the config files. Zilch. Ran bootcfg /rebuild, did attrib -h -r -s etc etc. replaced hal.dll with a backup, then a new copy. Replaced lsass. Nothing.
With windows installed on the new partition, I can run the PC no problem. The original drive is then accessable. You just cant boot from it, or run any integrated programs. Easier than switching HDD's.
My last hope was to do a repair install. That went well, until setup restarted the pc to finish the setup, whence the Lsass.exe error appeared. Apparently, Lsass is a windows security feature, which if your'e computer loses the original version in XP, can lock you out completely with format your only real option OR, it conflicts with the new install you are trying to run. Something like that. I'm so burnt on it now it's all a jumbled mess in my head.
I just burned a disc with all the user created files we want saved, and ordered a reinstall disk from the factory to put it into as bought condition, special order programs and all. Or so they say.
Thanks anyways. |
|
|
|
|
|
|
|
| Posted: Mon Jun 02, 2008 10:02 am |
|
|
| asmodee |
|
|
| |
| Joined: 17 Oct 2007 |
Posts: 929
Karma: +18
|
|
|
|
|
|
|
|
| Don't feel bad, man. I have days like that. I call them week days. |
|
_________________
Yes, I LOVE to talk while I fight! What shall we talk about? Wounds? Scars? Hot, dirty monkey love? |
|
|
|
| Posted: Thu Jun 05, 2008 5:57 pm |
|
|
| paul68 |
| Shaved Ape |
|
| |
| Joined: 15 Nov 2005 |
Posts: 2064
Karma: +21
|
| Location: Wer'e not from around here man! |
|
|
|
|
|
|
Repaired, finally. All I had to do, was contact Sony, order an original installation cd set, then reinstall the entire system.  |
|
|
|
|
| Posted: Thu Jun 05, 2008 7:00 pm |
|
|
| Raven |
| Google Meister |
|
| |
| Joined: 24 Oct 2005 |
Posts: 2906
Karma: -16
|
| Location: Detroit, MI, USA, North America, Earth, Sol, Orian's Arm, Milkyway, Uni Alpha-Prime |
|
|
|
|
|
|
| you didn't have an istallation CD? damn, i was wondering why you didn't just reinstall awhile ago... |
|
_________________
"The most beautiful experience we can have is the mysterious. It is the fundamental emotion that stands at the cradle of true art and true science. Whoever does not know it and can no longer wonder, no longer marvel, is as good as dead, and his eyes are dimmed." |
|
|
|
| Posted: Thu Jun 05, 2008 9:18 pm |
|
|
| paul68 |
| Shaved Ape |
|
| |
| Joined: 15 Nov 2005 |
Posts: 2064
Karma: +21
|
| Location: Wer'e not from around here man! |
|
|
|
|
|
|
| Well, I prefer repairs. "Usually" I can fix most any problem, in less than an hour. The repair install, which basically was a fresh OS installation, took an hour. Then 2 hours getting all the updates, settings programs bacl as they should be. Plus you lose anything not backed up. |
|
|
|
|
| Posted: Fri Jun 06, 2008 5:14 am |
|
|
| Raven |
| Google Meister |
|
| |
| Joined: 24 Oct 2005 |
Posts: 2906
Karma: -16
|
| Location: Detroit, MI, USA, North America, Earth, Sol, Orian's Arm, Milkyway, Uni Alpha-Prime |
|
|
|
|
|
|
| i prefer repairs too, but not when it's taken me a week to figure the shit out... |
|
_________________
"The most beautiful experience we can have is the mysterious. It is the fundamental emotion that stands at the cradle of true art and true science. Whoever does not know it and can no longer wonder, no longer marvel, is as good as dead, and his eyes are dimmed." |
|
|
|
| Skeptomania - Paranormal / UFOs, etc. Forum Index -> TECH TIPS |
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
All times are GMT - 5 Hours
Page 1 of 1
|
|
|
|
Powered by phpBB © 2001-2003 phpBB Group
|
