Computer woes...hal.dll corrupted

[Leright]

When my computer attempts to boot into windows I get the error "hal.dll is missing or corrupted - please reinstall the file..." I think this is due to my SP2 installation...apparently this is a common problem...fucking Microsoft.

Well, in order to do this I need to get into the recovery console, but I am not able to do this either, because of this error...I also tried booting from the windows XP disk into serup, and I get a different freaking error or BSOD every time I try it. It pisses me off. So that means a repair or formar/reinstall is not an option. the weird thing is the CD is 100% fine, because it works on all of my other computers except for my main rig.

So what should I do...because of this, I am tempted to just go and build a brand new machine since it is about that time anyways...

Update: I was able to get the windows CD to the point where it could be formatted, and that went fine...however, when the windows CD attempted to copy then ecessary files to begin the installation it crashes like crazy...what gives? this is really pissing me off...Just when I need when school is going to be starting in like 1 week.

[abudhu]

Do you have another HD? My thought would be to set that as Master, boot from that one. Insert Windows XP Cd. Find that .dll and copy it over to the failing drive. Remove good Drive. Reset failing drive as master and boot again. If that doesn't work then I'd say put that other HD in, copy your files, and format that sucka'

---
Edit: N/m you already Formatted the drive and f*ed the installation. Hahah. Guess my plan wont work at all anymore.
I guess what you should do then is go get the Diagnostic disk that works for you HD And Hopefully it has a re-write boot sectors/all sectors kind of deal. Re-Writes 0's and 1's. And then try installing windows all over.

Note that doing that is going to take a WHILE. When I did it on my IBM Desk(Death)Star 40GB it took a couple hours to re-write all the sectors.

[Leright]

Do you have another HD? My thought would be to set that as Master, boot from that one. Insert Windows XP Cd. Find that .dll and copy it over to the failing drive. Remove good Drive. Reset failing drive as master and boot again. If that doesn't work then I'd say put that other HD in, copy your files, and format that sucka'

---
Edit: N/m you already Formatted the drive and f*ed the installation. Hahah. Guess my plan wont work at all anymore.
I guess what you should do then is go get the Diagnostic disk that works for you HD And Hopefully it has a re-write boot sectors/all sectors kind of deal. Re-Writes 0's and 1's. And then try installing windows all over.

Note that doing that is going to take a WHILE. When I did it on my IBM Desk(Death)Star 40GB it took a couple hours to re-write all the sectors.

Well, hal.dll is specific the the hardware in the computer, so you can't just copy any old hal.dll over...or atleast that was my understanding. And I didn't really have another computer to boot and copy the dll...only have my laptop.

I finally got to my parents house though, and I am using their computer to do a low level format on the drive. HOPEFULLY, that does the trick. If it does, I will be a happy man...

[Leright]

ok, well, I just finished low level formatting, and it STILL did it. I also tried another windows disk that is known to work, and it did the exact same freaking thing. :mad: What gives? Could it possibly be the hard drive? I'm getting to the point where I believe it is. Maybe I will go to CC tomorrow and get a new one...maybe that will do the trick.

I really hope it does.

[abudhu]

Well I didn't know what Hal.dll was :)

Try what I said in my earlier Edit. Re-Write/Format all sectors of the drive.

If it still fails then I'd say RMA that drive.

[Leright]

Well I didn't know what Hal.dll was :)

Try what I said in my earlier Edit. Re-Write/Format all sectors of the drive.

If it still fails then I'd say RMA that drive.

ILike I said, I've done a low leve lformat. :( That failed. The hard drive is out of warranty I am pretty sure. I may go and pick up another one tomorrow...

God damn, this sucks ass. I like software problems a lot more than hardware problems...with hardware problems, you usually haven't got a clue where the problem lies...however, with software problems, it doesn't matter if you don't know where the problem lies...you can always do a format and reinstall. lol :D

edit: I sure wish I had a spare hard drive lying around that I could use...that would be really helpful in a time like this...right now I am jus treally determined to get to the bottom of this issue.

[abudhu]

Wow...if a Low-Level failed then damn...that HD must suck :)

You say the Windows CD is working on other comps..so I don't see how it could be the Software.

Oh..well if you are at your Parents house, couldnt you just steal their HD for a few hours... :confused:

At this point I'd say buy a new HD. Unless someone else knows of a solution

[Leright]

wait...I just had a thought....the part of the windows installation that fails is where information is copied into RAM...not the HDD...so why would the hard drive be the problem in the installation? hmmm....this thought does nothing more than worsen my situation. :( :mad:

Is this right? The error messages and BSODs occur before the format process in the install sequence...it is when hard drive drivers and such are loaded...these files are put into memory and not on the hard drive. I know this because the next step is to FORMAT The hard drive!

.....

[Leright]

Wow...if a Low-Level failed then damn...that HD must suck :)

You say the Windows CD is working on other comps..so I don't see how it could be the Software.

Oh..well if you are at your Parents house, couldnt you just steal their HD for a few hours... :confused:

At this point I'd say buy a new HD. Unless someone else knows of a solution

I know. It isn't software issue...I am just saying how I like software issues more because there is always an ultimate fix for every problem....a format and reinstall! lol

:D

[abudhu]

wait...I just had a thought....the part of the windows installation that fails is where information is copied into RAM...not the HDD...so why would the hard drive be the problem in the installation? hmmm....this thought does nothing more than worsen my situation. :( :mad:

Is this right? The error messages and BSODs occur before the format process in the install sequence...it is when hard drive drivers and such are loaded...these files are put into memory and not on the hard drive. I know this because the next step is to FORMAT The hard drive!

.....

Haha. Never thought of that. Do you have any RAM to swap with for the time being?

[Leright]

Haha. Never thought of that. Do you have any RAM to swap with for the time being?

maybe. I just want to repeatedly bash my head on my desk (until I am unconscious)...

I really really hate computers (or atleast I hate troubleshooting them..they are cool when they are working). :p

[Leright]

hmm...well, how much do you think I can get for a system (that doesn't work...but could be scrapped for parts) with the following specs:

lian li pc60 case (some scratches)
green neon light
tyan tiger MP rev. 3 mobo
dual athlon MP 1600+ processors
geforce 6800nu 128mb
512 megs pc2100 ram
4 port firewire card
4 port usb 2.0 card
leadtek tv2000xp vid cap card
turtle beach santa cruz
350 watt antec true power power supply
standard cd rom drive (52x)
ethernet card
wifi card
hard drive (possibly dead)


hmmm...think I can get like 400 for all of this shit?

BTW, if the memory is dead, wouldn't it not post after failing the mem test? Usually hardware is an all or nothing thing...if it is dead it usually will not work at all. Just a guess...

[M1ster_R0gers]

hal.dll = hardware abstraction layer. you have a problem with your ram. I have had this error many times, and it usually comes from crazy overclocking. Problem is once you screw that file up a reinstall is in order. I would suggest memtest86 overnight before you waste more of your time.

[Leright]

hal.dll = hardware abstraction layer. you have a problem with your ram. I have had this error many times, and it usually comes from crazy overclocking. Problem is once you screw that file up a reinstall is in order. I would suggest memtest86 overnight before you waste more of your time.

I know exactly what hal means. And yeah, we have narrowed it down to the RAM. I will have to get memtest. Thanks for the advice.

However, I did no overclocking...I have a tyan server mobo so OCing is a big no no. :D

[Leright]

It turns out it WAS the memory. I pulled out one of the sticks of ram and it worked fine.

Also also, in the initial stage of the windows setup, the hard drive IS being accessed...so I guess it could have been the hard drive as well...

maybe I will go to CC and get some new memory.

Thanks a lot for the help guys.