Upgraded Mobo and CPU, now won't boot

[UUVGuy]

I've done this before but without the problems I'm having now. Usually when I upgrade, I can either boot from the install CD and get a repair prior installation option which wipes out all the service packs for XP, or I can get into Safe Mode and install new drivers there until it will boot normally.
This time around however, the system will not boot into Safe Mode and the repair existing installation option doesn't appear when booting from the install CD.

The system is a dual boot Vista/XP Home. Neither OS will boot and I can't get the Safe Mode option when booting to XP. The Vista DVD is a legal copy of a 10 license Vista Business upgrade DVD that won't let me install from the DVD without being in a windows environment first. It did give me the option to repair the Vista installation but that hasn't worked either.

The system does work as I am now writing this with Ubuntu booted from the install CD and it's working fine. I don't want to loose all the program installs along with all the stuff in My Documents in either of the installs.

I have tried booting with only the XP HD connected and then with only the Vista HD running. The XP only option doesn't see the MBR on the drive because the Vista upgrade was installed first and that is the drive the boot file is on. If the Vista drive is solo, it won't boot into either normal or Safe Modes, I get a very brief BSOD and it reboots itself.
Any help would be appreciated.

Old system:
Intel D865PERL MOBO
Intel P4 2.4 GHz CPU
2 Gig 2 channel DDR
1 Seagate Barracuda 160 GB HD SATA Vista install
1 Western Digial 160 GB HD Sata Storage
1 Maxtor 80 GB HD PATA XP Install
PNY Nvidia GeForce FX5500 AGP GPU

New System:
MSI P7n SLI Platinum
Intel Q6600 2.4 GHz CPU
2 Gig 2Channel DDR2
Same HD's
EVGA Nvidia 9500GT PCI-E GPU

I know the upgrade is much different from the original install but I did a similar install on another machine with no problems.

 

[Turkbear]

Hi,
On thing..when powering up, get into the bios setup utility and change the setting that causes restarts after a BSOD -
If the BSOD stays up, you may see what's wrong.

( at least I think you can do that, it has been a while since I needed that)






To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[SimonDavies]

I have a feeling it's down to the fact that you're running completely different chipsets and the installation doesn't know anything about it.

I would guess that you get the initial loading screen (the one with the bitmap) and then it BSOD's? if so that's when the chipset would be loading and that's why it's failing.
You're trying to load an OS that's looking for the Intel chipset that now has the NV chipset, unless you can get the machine loaded into safe mode so that you can update the device drivers you're going to have issues.

I would suggest that in the interim you get a hold of an XP cd, boot from it and try doing a repair from that. If you can't do that try seeing if you can get into the recovery console and doing an fixmbr.

More info on fixmbr found here

http://pcsupport.about.com/od/termsf/p/fixmbr.htm

On the vista front are you hitting F8 as soon as the pc is POSTing? if so do that, it should bypass any attempt by the OS to load any device drivers. If you can get into safe mode that way I would do the same thing with regards to device drivers.

Simon

The real world is not about exam scores, it's about ability.

 

[UUVGuy]

Simon,
With XP it says that the system32\hal.dll file is missing or corrupt. I have re copied the file from the recovery console and still get the error. In the dual boot scenario, it won't let me F8 into Safe Mode for XP

I just recently upgraded another computer to a dual core CPU with XP and in order to get it to boot, it gave me an option to repair the current installation with the boot CD without going into Repair Console. It kept all my programs and other settings, it just wiped out all the updates and service packs. I had to reinstall them and then update the OS but with this install, it doesn't give me that option, it just tells me that it will wipe the current install. If I have to, I guess I'll reinstall XP into another directory and try and recover My Documents and the like and then reinstall all the other software. I was hoping to avoid that pain.

On the Vista front, I can F8 into safe mode but when it gets the crcchkdrive, the screen hangs for a few seconds and then BSODs. I'll have to take Turkbears advice and change my BIOS setting so it doesn't just reboot. I think if I can get into XP on the other drive, I might be able to do the repair from there since the Vista license only allows me to install from XP.

Before I do all this however, I may try reinstalling the old mobo and assorted bare bones eequipment, booting up, and uninstalling all the drivers. That should get me to the point of having generic drivers load on initial boot up when I re upgrade the equipment and hopefully allowing me into Safe Mode where I can install the Mobo drivers and the like.

 

[SimonDavies]

well the HAL is Hardware Abstraction Layer, chances are its the type of BIOS it's trying to associate with the machine (ACPI Multiprocessor CPU\Single CPU etc).

Going back to the old MB and removing old drivers should work, one bit of advice tho, you may be forced to reactivate the system if you have changed too many things on the pc (MS's way of making sure you don't install the same OS on more than one machine without paying for it).

Simon

The real world is not about exam scores, it's about ability.

 

[UUVGuy]

Yeah, I figured I'd have to reactivate it. I've had to do it on all the other machines I've done.

 

[UUVGuy]

Update,

Tried to uninstall the Intel drivers as well as the video card drivers and the like and then repair in new set up. No joy.
I was able to repair the XP portion but only with the original Intel Mobo setup. I guess the change over is too much for the system but my theory is that it's the Intel drivers as many of them won't uninstall. My plan now is to back up all my important files and the like in the original set up and then doing a clean install and going from there.
I find it ironic that the repair install option was available for XP when I put the system back together the way it was originally, but is not an option once the new setup is introduced. When I copied the hal.dll file from the install CD, I made the XP install unbootable, so this necessitated the XP repair from the original set up since that't the only way I could get it to boot. I did the exact same upgrade to another computer but it was running an ASUS mobo and an AMD CPU as an original set up. It booted into safe mode just fine and I was able to install all the new drivers without a problem. My new dual core machine was running with an Elitegroup mobo and a P4 CPU just like I had in this machine. Again, booted to safe mode with no issues. My suspicions lie with Intel's chipset and drivers.

 

[linney]

Can you clarify that the XP CD you failed to get the Repair option on was a commercially created CD and not one you have made yourself? This article prompts that question.

Unattended WinXP Installation loses Repair option

http://www.msfn.org/board/index.php?showtopic=20803

Can you get into XP with the new motherboard via these?

HOW TO: Create a Boot Disk for an NTFS or FAT Partition in Windows XP(Q305595)

http://support.microsoft.com/support/kb/articles/q305/5/95.asp

How to Use System Files to Create a Boot Disk to Guard Against Being Unable to Start Windows XP (Q314079)

http://support.microsoft.com/support/kb/articles/q314/0/79.asp

 

[UUVGuy]

linney,

The XP disk is a commercial copy that came with the original system. It is prior to SP-1a so it is not up to date by any means but has saved my bacon more than once.
I will try your other suggestions and see what happens and let y'all know.

Thanks for the tips, I really do appreciate it.

 

[UUVGuy]

Tried to boot from floppy as per instructions, no joy. If I have both drives installed for Vista and XP respectively, the floppy tries to boot into Vista and it gets as far as the crcdisk.dll file and then hangs.
If I disconnect the Vista drive and try to boot into XP, it BSODs.

The XP disc is not an unattended install, it's the OS install disc from the manufacturer back when I bought the computer in 03.

 

[linney]

Is the Boot.ini on the floppy pointing to the correct partition containing XP? Have a look at the multi parameter.

Information and Options of XP’s boot.ini File

http://samanathon.com/information-and-options-of-xp’s-bootini-file/

 

[allteltec]

With a dual boot system if you are using Windows boot.ini to dual boot, to get into save mode you need to high light the os to boot then hit Enter and F8 2ms later. You have to be real fast hitting F8 after hitting Enter.

 

[BadBigBen]

Infinite Boot Loop - Safe mode doesn't work (crcdisk.sys)

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=4022630&SiteID=17

Initial Boot after intall fails on crcdisk.sys

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=510682&SiteID=17

You can't get to the Repair option, probably due to the fact that it is a DUAL boot environment... (XP)
probably the only way to get that REPAIR option would be to rewrite the MBR of the BOOT drive... helpful here has been a DOS/WINDOWS XP BootDisk...

How to use FDISK:
FDISK /MBR rewrites the Master Boot Record

http://support.microsoft.com/?scid=kb;en-us;69013&x=8&y=13

You could also boot into a BartPE CD, then replace the following files(XP) found in the C:\WINDOWS\System32\Drivers folder:

ATAPI.SYS
INTELIDE.SYS
PCIIDE.SYS
PCIIDEX.SYS
with the ones from an original SP2 CD (Note: you will have to use the EXPAND command to do so)...

now here comes the hard part:

copy the following into notepad then save it out with a .REG extension (e.g. merge.reg)...

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\primary_ide_channel]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\secondary_ide_channel]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\*pnp0600]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\*azt0502]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\gendisk]
"ClassGUID"="{4D36E967-E325-11CE-BFC1-08002BE10318}"
"Service"="disk"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#cc_0101]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_0e11&dev_ae33]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1039&dev_0601]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase \pci#ven_1039&dev_5513]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1042&dev_1000]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_105a&dev_4d33]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0640]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0646]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0646&REV_05]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0646&REV_07]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0648]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0649]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1097&dev_0038]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10ad&dev_0001]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10ad&dev_0150]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5215]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5219]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5229]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1106&dev_0571]
"Service"="pciide"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_1222]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_1230]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2411]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2421]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7010]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7111]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7199]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

;Add driver for Atapi (requires Atapi.sys in Drivers directory)

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi]
"ErrorControl"=dword:00000001
"Group"="SCSI miniport"
"Start"=dword:00000000
"Tag"=dword:00000019
"Type"=dword:00000001
"DisplayName"="Standard IDE/ESDI Hard Disk Controller"
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
  52,00,49,00,56,00,45,00,52,00,53,00,5c,00,61,00,74,00,61,00,70,00,69,00,2e,\
  00,73,00,79,00,73,00,00,00

;Add driver for intelide (requires intelide.sys in drivers directory)

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IntelIde]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Tag"=dword:00000004
"Type"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
  52,00,49,00,56,00,45,00,52,00,53,00,5c,00,69,00,6e,00,74,00,65,00,6c,00,69,\
  00,64,00,65,00,2e,00,73,00,79,00,73,00,00,00


;Add driver for Pciide (requires Pciide.sys and Pciidex.sys in Drivers directory)

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PCIIde]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Tag"=dword:00000003
"Type"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
  52,00,49,00,56,00,45,00,52,00,53,00,5c,00,70,00,63,00,69,00,69,00,64,00,65,\
  00,2e,00,73,00,79,00,73,00,00,00

now import the Registry Hive (make a backup before changing them) and merge the above with it, and unload it out to the XP install...

How to edit the registry offline using BartPE boot CD ?

http://windowsxp.mvps.org/peboot.htm

Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."

 

[UUVGuy]

Thanks for all the tips y'all. I ended up just copying all my essential files to another drive and basically starting over.
I tried to reinstall over the top of my previous installations but I kept getting corrupt file errors whether it was Vista or XP. Once I simply did a completely clean install of XP and then the Vista upgrade, it worked. I now have to reinstall XP on another drive and get back my dual boot status. I'm keeping dual boot as there are things that I can do in XP that I'd have to spend a bunch of money on to upgrade the software for Vista that I'm not willing to do.

I will say this though, with the new mobo, etc, Vista runs much better now. With the old P4 system, it was very slow, almost painfully slow so I only used it occasionally. Now I plan on using Vista most of the time and only using XP for those things that only run there.

Again, thanks for all the help and I will file this stuff away for future use if/when I'll need it. This is a great community!

 

[linney]

Glad you are making progress again. If you don't want to dual boot you can always look at Virtual machines.

http://www.microsoft.com/downloads/...02-3199-48A3-AFA2-2DC0B40A73B6&displaylang=en