Unable to boot Windows partition

[commondork]

I built a new system last night.

Gigabyte GA-MA770-UD3 (Rev. 1.0)
AMD Athlon X2 7850 Black Edition Kuma 2.8GHz Socket AM2+
G.SKILL 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 1066 (Dual Channel)
BFG Tech LS SERIES LS-550 550W
EVGA 512-P3-N871-AR GeForce 9800 GTX+ 512MB 256-bit

I am using two older SATA 1.5GBs drives. One has Windows XP SP3 and Ubuntu 9 in a dual-boot configuration. The other drive is NTFS formatted and is used for general storage.

Everything was installed without issue and the system POSTed on first boot. Temps looked good (27C for system and 32C for CPU).

I tried to boot into Windows from the GRUB menu so I could install the new motherboard and video drivers. The system produced a BSOD while booting. I rebooted and attempted to boot into Ubuntu. The system booted Ubuntu quickly but it wasn't able to establish a network connection due to the new network controller. I was able to mount my Windows XP partition and view/use files in the partition within Linux.

I believe there is a fix for this BSOD problem for new Windows XP installations (http://www.gigabyte.com.tw/Support/Motherboard/Driver_Model.aspx?ProductID=2982&ost=xp#anchor_os) but is there a fix for systems with previously existing Windows XP installations?

I would like to resolve this problem without having to reinstall Windows or Ubuntu (I haven't backed up in a while 😗 )

Thanks guys and gals!

 

[kubes]

What is the BSOD that your getting?

link to help you identify what BSOD

 

[commondork]

This is what the BSOD says:

"A problem has been detected and Windows has been shut down to prevent damage to your computer.

If this is the first time you've seen this error screen, restart your computer. If this screen appears again, follow these steps:

Check for viruses on your computer. Remove any newly installed hard drives or hard drive controllers. Check your hard drive to make sure it is properly configured and terminated. Run CHKDSK /F to check for hard drive corruption, and then restart your computer.

Technical information:

*** STOP: 0x0000007B (0xBA4C7528, 0xC0000034, 0x00000000, 0x00000000)"

That's all.

 

[kubes]

The Stop 0x7B message indicates that Windows XP has lost access to the system partition or boot volume during the startup process. Installing incorrect device drivers when installing or upgrading storage adapter hardware typically causes stop 0x7B errors. Stop 0x7B errors could also indicate possible virus infection.

The second parameter is very important because it can indicate whether the 0x7B Stop message was caused by file system issues or problems with storage hardware and drivers. Values of 0xC000034 or 0xC000000E typically indicate:

• Disks or storage controllers that are failing, defective, or improperly configured.

• Storage-related drivers or programs (tape management software, for example) that are not fully compatible with Windows XP Professional.

Possible Resolutions:

• During I/O system initialization, the controller or driver for the startup device (typically the hard disk) might have failed to initialize the necessary hardware. File system initialization might have failed because of disk or controller failure, or because the file system did not recognize the data on the boot device.

• Repartitioning disks, adding new disks, or upgrading to a new disk controller might cause the information in the Boot.ini file, or Boot Manager, to become outdated. If this Stop message occurs after installing new disks to your system, edit the Boot.ini file or adjust the Boot Manager parameters to allow the system to start. If the error occurs after upgrading the disk controller, verify that the new hardware is functioning and correctly configured.

• Verify that the system firmware and disk controller BIOS settings are correct and that the storage device was properly installed. If you are unsure, consult your computer's documentation about restoring default firmware settings or configuring your system to auto-detect settings. If the error occurs during Windows XP Professional setup, the problem might be due to unsupported disk controller hardware. In some cases, drivers for new hardware are not in the Windows XP Professional Driver.cab library, and you need to provide additional drivers to complete the Windows XP setup successfully. If this is the case, follow the hardware manufacturer's instructions when installing drivers. Periodically check for driver and firmware updates.

• Hard disk corruption can also cause this Stop message. For more information about checking hard disk integrity, see the instructions provided in "Stop 0x00000024 or NTFS_FILE_SYSTEM" earlier in this list.

• Problems that cause 0x7B errors might also cause Stop 0xED errors. For more information about 0xED Stop messages, see "Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE" later in this list.

Where i got the information from

 

[kubes]

To paraphrase what the above is saying, I would interupt that you will need to do a reformat of the hard drive.

I'm assuming you've tried booting into safe mode?

Maybe to get your data back throw the old hard drives into your old rig and save things to disk or whatever you can think of ect... or if you have another computer lieing around throw them in as extra drives and grab the info off them that way.

 

[commondork]

So there is absolutely no way of installing the new SATA controller driver on a current Windows installation?

I am able to load SATA RAID controller drivers from the Gigabyte website (linked to previously) while booting Windows from CD (F6) so that Windows (from CD) recognizes the drive. I can then enter repair mode and see my Windows partition and navigate through it successfully. The problem is that the SATA controller driver doesn't take to the partition so when rebooting I am presented with the same BSOD. Is there a way I can install this driver from the repair console via floppy disk?

Booting to Safe Mode produces the same BSOD as Windows still won't recognize the controller.

 

[kubes]

I have not done this so i'm not sure of the sucess you might get but here is a quick link to a person that has put together a walk through on how to get around your problem. The Link . Might want to give it a shot. Report back and let us know how it goes.

 

[commondork]

I don't think that process will work step-by-step due to different SATA driver files but the slipstreaming idea should work since I can install my SATA controller drivers through the Windows CD and then just repair the partition. Since the new slipstreamed CD will have SP3 it shouldn't affect my system much. I will try that later this afternoon, thanks!

 

[kubes]

Ya, this is probally going to take some rigging up. Sorry I can't be more helpful on what to do, but I have not actually encoutered this problem before so I do not have first hand experince on how to help you. I'll do my best to hold your hand through the entire process though. I'll give you my two cents if you keep reporting back and maybe give you ideas on what to try next as you hit bumps. I'm pretty sure this can be done, but its just not going to be easy.

PS: I do feel kinda dumb because i feel like this is something I should know haha.