Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works

XP Repair Help.

  • Please log in to reply



    New Member

  • Member
  • Pip
  • 2 posts
Hello, earlier today while gaming on my operating HDD, I encountered a momentary BSOD and then an instant reboot - But got the hal.dll corrupt / missing error.

Firstly, I ran chkdsk. No problems whatsoever.. However, strangely, it took almost 2 hours to run the scan, and yet my operating HDD is only 320 GB.

For whatever reason, I don't have the standard Repair Install option in the XP CD.. Only the repair console, and the option of either formatting and re-installing, or installing a parallel Windows folder on the same partition.

I installed the second copy of Windows on the drive, and overwrote the old hal.dll with the new one.

I've heard the hal.dll error is caused by one of two things, one being hal.dll being corrupt of missing, the other being a problematic boot.ini, so, for good measure, I created a new boot.ini, yet I'm still have the hal.dll error.

If I try to log onto the new copy of Windows on the same drive, I get in fine.

Any suggestions?

And secondly, is it possible to get to the recovery installer if it's not displayed by default?


After doing the parallel installation and grabbing the apparently corrupt hal.dll, and fixing the boot.ini, I left a back-up copy of the original Windows folder in C:\ under the name of Windows1 (As the parallel install had been Windows0.)

However, when I went to double-check the boot.ini through the recovery console, the only Windows installation it reported on that drive was the parallel install, stuffed away in the recycle bin.

Edit 2: Taking the parallel copy out of the recycle bin, and booting to it, I was then able to start an XP re-install on the drive and successfully get to the repair screen.. But only the parallel copy was displayed.

Is it possible to force the installer to recognize the other installation?

Edited by Deiz, 29 June 2007 - 02:21 PM.

  • 0




    New Member

  • Topic Starter
  • Member
  • Pip
  • 2 posts

Totally stumped here.

Just ran CHKDSK again and it did find a small problem.. And again, took nearly 2 hours to complete.
  • 0

Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP