Move hard drive from Intel motherboard to AMD blue screened

[mxnerd]

I wanted to move a Windows 2003 x64 installation on Intel P35 motherboard to AMD motherboard, but it blue screened before Windows was fully loaded, it showed disk.sys is the offending file, the reason I'm changing the motherboard is the PCI slots on the Intel board are all dead.

I did not turn on the RAID function on AMD motherboard (785G chipset) and was just using native IDE mode and it still blue screened.

I suspect that it's the driver problem. Is there any way to install or extract AMD chipset with RAID support files on the still functioning INTEL motherboard and move the hard drive over to the new AMD board without reinstalling Windows?

I googled but can't find the solution. Thanks!

 

[RU482]

I've had luck going between Intel platforms, but never going between AMD and Intel platforms. meh

 

[mxnerd]

Problem solved!

Found this Gigabyte GA-MA785GM-US2H motherboard has SATA0-SATA3, SATA4 & eSATA. Where SATA0-SATA3 use OnChip SATA Controller, yet SATA4 & eSATA seems using another SATA controller. Maybe someone can tell me what these controllers are?

When I put the boot disk on SATA0-SATA3, even in native IDE mode, the system always BSOD at last moment. When I put the disk on SATA4 port, the system finally boot without problem and I was able to install the drivers.

Really wonder why the system won't boot even in native IDE mode when it's on SATA0-SATA3.

 

[Elixer]

I wanted to move a Windows 2003 x64 installation on Intel P35 motherboard to AMD motherboard, but it blue screened before Windows was fully loaded, it showed disk.sys is the offending file, the reason I'm changing the motherboard is the PCI slots on the Intel board are all dead.

The way you did it is a very bad way to do it. I would not be surprised if you have issues down the road.
What you should have done is mirror it, then run a repair install on it.
Another way is to use sysprep, and have all the needed drivers on the new install CD/DVD/whatever.

 

[RebateMonger]

Really wonder why the system won't boot even in native IDE mode when it's on SATA0-SATA3.

Because it was probably loading the disk controller manufacturer's driver rather than the "Generic" IDE driver.

The "easy" way to change from one IDE controller to another is to enter Windows in the "old" system and "upgrade" the disk controller driver to the generic Microsoft IDE driver. Then you shut down the system and attach the disk to the new motherboard/IDE controller. It'll load the generic IDE driver that will work well enough to boot Windows on the new disk controller.

I haven't used an AMD processor since 1987, so I can't tell you what issues you might have in changing CPUs.

 

[mxnerd]

The way you did it is a very bad way to do it. I would not be surprised if you have issues down the road.
What you should have done is mirror it, then run a repair install on it.
Another way is to use sysprep, and have all the needed drivers on the new install CD/DVD/whatever.

Thanks. I will take that as advice.

 

[mxnerd]

Because it was probably loading the disk controller manufacturer's driver rather than the "Generic" IDE driver.

The "easy" way to change from one IDE controller to another is to enter Windows in the "old" system and "upgrade" the disk controller driver to the generic Microsoft IDE driver. Then you shut down the system and attach the disk to the new motherboard/IDE controller. It'll load the generic IDE driver that will work well enough to boot Windows on the new disk controller.

When I check the old installation, the generic Microsoft IDE driver is already installed.

After I installed the WebPAM RAID utility for AMD, I found that the controller for SATA0-SATA3 is actually Promise SATA controller. Maybe that's why even though in BIOS you can set it to support native IDE, yet in reality it does not. SATA port 4 does support native IDE mode, though.