Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

Changed Mobo, XP now in Reboot Loop


  • Please log in to reply

#1
aliengreen

aliengreen

    Member

  • Member
  • PipPip
  • 19 posts
Hello GtG,

I originally had an ASUS P4P800-E Deluxe motherboard running a Pentium 4 3.0Ghz Socket 478 CPU, and changed to a Gigabyte GA-8IG1000MX when I accidentally fried the former. However, I could no longer get Windows XP to boot up. According to what I've researched on the Internet so far, and asking tech support at the PC shop where I bought the motherboard as well, I seem to get the same advice in general--run the XP installation CD and use the 'Repair' function to "reset" XP to the new motherboard. There's one problem though, I get this message sometime during the setup process-- "File hal.dll could not be loaded. The error code is 7. Setup cannot continue. Press any key to exit." What gives? Any help would be much, much appreciated.

Specs:
Pentium 4 3.0Ghz Socket 478
Gigabyte GA-8IG1000MX
4 x 512Mb Dual Channel DDR400 PC3200
40Gb Seagate 7200 IDE HDD
200Gb Seagate 7200 IDE HDD
160Gb Seagate SATA HDD
On board VGA
  • 0

Advertisements


#2
Neil Jones

Neil Jones

    Member 5k

  • Member
  • PipPipPipPipPipPipPipPip
  • 8,476 posts
Under XP you cannot change the board and expect it to boot. It needs a Windows Repair from your XP CD.
Your error would suggest there's an issue with that motherboard. Where did you get that 478 board from? It's not a current model.
  • 0

#3
aliengreen

aliengreen

    Member

  • Topic Starter
  • Member
  • PipPip
  • 19 posts
Thanks Neil, got the mobo from a surplus shop selling used boards. I felt bad about throwing away a good performing unit that just needed a mobo change, so there. There's a problem using the Recovery Console from the XP CD as you suggested, because I keep getting the Blue Screen of Death everytime i run it (0x07E Stop message). Would you recommend Flashing the BIOS instead?
  • 0

#4
Neil Jones

Neil Jones

    Member 5k

  • Member
  • PipPipPipPipPipPipPipPip
  • 8,476 posts
If the board is faulty flashing the BIOS isn't going to solve anything. I'd argue that board is defective, and this is the risk you take when you buy second-hand components. You'd have probably been better off replacing the board, processor and memory, getting a huge performance boost at the same time.
  • 0

#5
aliengreen

aliengreen

    Member

  • Topic Starter
  • Member
  • PipPip
  • 19 posts
I agree on that point. Isn't it just funny how when saving on stuff you end up paying for more? Anyway, I've been planning on giving this unit to the kids eventually, so I'm not just about to give up yet. I took out the other RAM sticks and Hard Drives as well, basically seeing if a barebones setup would work, and looks like it might pull through. Now I just need to get past this setup error "File hal.dll could not be loaded.Error code is 7" and then I could get to the "Welcome to Setup" screen, where the repair console is located. My theory on this is I just need to let the old Windows XP recognize the new setup and maybe all will be well. Sadly, researching this problem on the Microsoft Support page turns up nothing. I am now considering a reformat and clean install instead.
  • 0

#6
123Runner

123Runner

    Member 4k

  • Member
  • PipPipPipPipPipPipPip
  • 4,527 posts
When changing boards and using the original OS on the hard drive,a repair XP is usually attemted. The best option is a complete reformat and reload of the OS (A fresh install).
This way the OS has the drivers for the new board.

Since your CD errors out, you could have a bad board or a dirty CD.

123runner
  • 0

#7
aliengreen

aliengreen

    Member

  • Topic Starter
  • Member
  • PipPip
  • 19 posts
Thanks for the suggestions folks. I finally pinned down the source of this humongous headache--bad memory modules. I took out 2 of my original 4 512Mb DDRs and it worked. I was then able to proceed with a clean install of XP. The motherboard is fine so far, and it's been a few days now without any hiccups (knock on wood). Oh but what a trip it has been! A lot of teeth-gnashing just trying to figure this one out. So, I just wanted to post this in case someone out there has a similar predicament in the future: when you are upgrading/swapping hardware and XP throws a fit, include the RAM in your system review checklist , especially if you get varying stop messages.

Again, thanks to all! :)
  • 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