J
Jason Mills
Can some explain what would cause a (and this isn't the whole message)
"hal.dll is missing or corrupt, please replace or reinstall" (or something
to that effect). Here's my story. I have DFI Lanarty NF3 250GB
motherboard, and I'm running a mirrored raid across two serial ATA hard
drives. I recently upgraded the BIOS to a newer version. After the
upgrade, and subsequent reboot, everything worked fine. Upon rebooting and
re-entering the BIOS, and switch the BIOS to the Optomized defaults, and
clicking off a few defaults such as onboard sound, and re-enabling the raid
(comes off by default), saving, and rebooting, I got the above message, and
no apparent way to fix it, other than to reinstall the OS? I found several
possible fixes on Microsoft.com, however, all of them seemed to only be
designed at IDE connected drives? While one "fix" did change the error I
got, it did not fix the problem. In the state I was left with, the system
would not get to any point beyond the above error, which does not allow for
access to safe mode. I tried several things as suggested by Microsofts tech
site, using the recovery console and nothing fixed the problem, other than a
complete OS reinstall. I've since gotten back up in running, but would like
anyones input on how to avoid this happening, and what may have caused it?
I'm a system tweaker, and its frustrating for this kind of unexplained stuff
to happen, and now I'm leary about doing future updates. Thanks again for
help or ideas that are provided!
Regards,
Jason
"hal.dll is missing or corrupt, please replace or reinstall" (or something
to that effect). Here's my story. I have DFI Lanarty NF3 250GB
motherboard, and I'm running a mirrored raid across two serial ATA hard
drives. I recently upgraded the BIOS to a newer version. After the
upgrade, and subsequent reboot, everything worked fine. Upon rebooting and
re-entering the BIOS, and switch the BIOS to the Optomized defaults, and
clicking off a few defaults such as onboard sound, and re-enabling the raid
(comes off by default), saving, and rebooting, I got the above message, and
no apparent way to fix it, other than to reinstall the OS? I found several
possible fixes on Microsoft.com, however, all of them seemed to only be
designed at IDE connected drives? While one "fix" did change the error I
got, it did not fix the problem. In the state I was left with, the system
would not get to any point beyond the above error, which does not allow for
access to safe mode. I tried several things as suggested by Microsofts tech
site, using the recovery console and nothing fixed the problem, other than a
complete OS reinstall. I've since gotten back up in running, but would like
anyones input on how to avoid this happening, and what may have caused it?
I'm a system tweaker, and its frustrating for this kind of unexplained stuff
to happen, and now I'm leary about doing future updates. Thanks again for
help or ideas that are provided!
Regards,
Jason