MSI K9A Platinum and VIA drivers issue? XP 0x0000007B stop error.

Question

I get a Windows Stop error when trying to boot into Windows XP with new components. The SATA hard drive (and Windows XP installation) is from the old computer.
The new computer components are:
MB: MSI K9A Platinum, chipset: RD580 (North Bridge), SB600 (South Bridge)
CPU: AMD Athlon 64 x2 5600+, boxed (the cooler and fan came with the CPU).
Video: MSI Radeon 1950 XTX
The old (and working) computer setup is:
OS: XP Professional
MB: Abit AV8-3rd Eye, chipset: VIA K8T800Pro + VT8237
CPU: AMD Athlon 64 3500+
Video: Sapphire Radeon 9800Pro All-in-Wonder, videodriver: atidvag.dll version 6.14.10.6542
HD: Maxtor 6B200M0 SCSI Disk Device
BIOS: Phoenix 6.00PG 20.04.2005
System drivers with "via" in the name: VIAAGP1.SYS, viaide.sys, viasride.sys
VIA 4in1 (Hyperion) version: 4.55 (that can be found at HKEY_Local_Machine\Software\Via4in1Driver).
VIA 2.20e SATA/RAID driver was used when installing this computer setup.
The precise stop error is:
0x0000007B (0xba4c3528, 0xc0000034, 0x00000000, 0x00000000)
From many sites I have gathered that the error is related to Windows XP not being able to access a critical system drive. Most probably the SATA hard drive issue.
The problem probably is the VIA drivers of the old motherboard and/or the SATA driver.
First I should mention, that MSI K9A Platinum does not have a hard disk SATA driver. If it does, I have been unable to find one. Certainly no such floppy disk included, and no such driver in the MSI's Web page for this motherboard.
Second important point: I never used RAID. I did use VIA 2.20e SATA/RAID driver disk when installing Windows XP to the old computer.
Strange that the hard drive model is reported as a "SCSI Disk Device". It's not a SCSI drive however: it's a SATA disk.
I have tried to uninstal the motherboard chipset drivers (Hyperion v4.55), but there seems to be a bug here: the drivers should be uninstalled using the installation program, and select the uninstall option. However, I do not get the uninstallation option to choose at all! Yes, I'm using the normal installation mode, not the quick installation (although tried that, too). The Hyperion setup program just installs, and asks to reboot the computer. After rebooting and trying again, it still does not offer me an uninstallation choise.
I know how to install hard drive VIA SATA driver, but I have no idea how to uninstall it. And I'm afraid to do that without certainty that it IS the solution, since I could not access the hard drive any more in the old computer setup (and return to read this forum). Also, I do not have a floppy drive any more. Anyone know if there is an issue with K9A and XP having VIA SATA driver installed?
When I tried the new computer setup, I first tried the simplest possible hardware combination: there were no CD/DVD-drives, no (parallel)IDE hard drives, and no PCI cards, except the MSI video adapter.
My BIOS Setup experiments. None of these helped: got the same stop error each time.
1) I didn't much touch the BIOS setting first. Just tried to boot with the settings BIOS came with.
2) Next I disabled the integrated audio, LAN and IEE1394 devices and floppy drive and disabled all other choises except the SATA drive as a boot device.
3) Next I tried with the fail-safe BIOS defaults.
4) Cleared CMOS.
5) Changed OnChip SATA type from Native IDE to Legacy IDE. (Only one boot attempt with the setting as Legacy.)
6) Disabled PCI IDE BusMaster.
7) Never touched anything in the Cell Menu: so the settings are in minimum.
A step I have taken after the last attempt: run Windows XP hard drive error-checking tool to every logical drive with the fix option selected, and the system drive also with scan the bad sectors option selected.
My plans next are:
1) to install a newer Hyperion driver. If that would correct the no-unistallation-choice-bug,
2) to disable USB-devices in the BIOS (desperate),
3) to choose the Windows general video display driver (although I seriously doubt this is a display driver problem!).
4) to uninstall the Anti-Virus software (Avira Antivir).
I've read a numerous Web pages so far about the 0x0000007B stop error. Here are some links:
Quote
http://www.seagate.com/www/en-us/support/knowledge_base/
Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE
This Stop message, also known as Stop 0x7B, indicates that Windows XP Professional lost access to the system volume or boot volume during the startup process. This error always occurs while the system is starting and is often caused by one of the following:
    * Hardware problems
    * Corrupted or incompatible storage drivers
    * File system problems
    * Boot sector viruses
    * Outdated firmware
During I/O system initialization, this error can occur when:
    * The controller or driver for the startup device (typically the hard disk) failed to initialize the necessary hardware.
    * File system initialization failed because the system did not recognize the data on the boot device.
Quote
http://support.microsoft.com/kb/314082
You receive a Stop 0x0000007B error after you move the Windows XP system disk to another computer
SYMPTOMS
After you move the Microsoft Windows XP system (boot) disk to a backup computer, you may receive the following Stop error when you try to start the Windows XP-based backup computer:
STOP: 0x0000007B (0xF741B84C,0xC0000034,0x00000000,0x00000000)
CAUSE
This error may occur if the registry entries and the drivers for the mass storage controller hardware in the backup computer are not installed in Windows XP.
RESOLUTION
To resolve this error, use the same hardware for the backup computer.
Heh, heh! Very nice Microsoft, but I plan to update my computer, so I NEED to use different components
Quote
http://support.microsoft.com/kb/324103
Device Driver Issues
You may receive a "Stop 0x0000007B" error message in the following scenarios:
•   A device driver that the computer boot controller needs is not configured to start during the startup process.
•   A device driver that the computer boot controller needs is corrupted.
•   Information in the Windows XP registry (information related to how the device drivers load during startup) is corrupted.
Hardware Issues
You may receive a "Stop 0x0000007B" error message if there is a resource conflict between the boot controller and another controller or between SCSI devices. You may also receive this Stop error message if drive translation is not being performed or if drive translation was changed. To troubleshoot this issue:
1.   If an IRQ or I/O port address conflict exists between the boot controller and another controller, Windows XP either stops responding (hangs) or displays a "Stop 0x0000007B" error message. If you recently added new hardware, remove the new hardware or reconfigure it so that it does not conflict with the resources of any other installed controllers.
2.   If you are using a SCSI hard disk, check the SCSI chain for correct termination. Remove any unused SCSI devices or make sure that each SCSI ID is unique.
3.   Make sure that drive translation is turned on (if it is required) and that it has not been changed. For example, if you recently switched controllers, this issue may occur. For additional information about this issue, click the following article number to view the article in the Microsoft Knowledge Base: 314082.
Quote
http://support.microsoft.com/kb/316401/
SYMPTOMS
When you start your Microsoft Windows XP-based computer after you replace the motherboard on the computer, you may receive a Stop error message that is similar to the following:
STOP 0x0000007B INACCESSABLE_BOOT_DEVICE
CAUSE
This issue may occur if the new motherboard contains an embedded IDE controller that has a different chipset than the original motherboard.
RESOLUTION
Method 1: Perform an in-place upgrade of Windows XP [<- That means repair installation of Windows XP]
•   Do not use a repair or in-place upgrade if you suspect disk problems.
Method 2: Repartition and format your hard disk and reinstall Windows XP

Answer 1

Alright I got the situation over.
Quote from: Roskaposti on 19-May-07, 04:44:59
My plans next are:
1) to install a newer Hyperion driver. If that would correct the no-unistallation-choice-bug,
2) to disable USB-devices in the BIOS (desperate),
3) to choose the Windows general video display driver (although I seriously doubt this is a display driver problem!).
4) to uninstall the Anti-Virus software (Avira Antivir).
I did try all all the above, and none of them helped.
And by the way: after installing the new Hyperion (VIA chipset drivers), I was finally able to also uninstall. It also uninstalled the IDE SATA (I think) and PATA drivers.
But what I had to do, was to make a REPAIR installation of Windows XP.
So, I was wondering now afterwards: this is really, really silly. Why the hell we need to re-install Windows if we move the SYSTEM SATA drive to another computer? We don't have similar problem with parallel IDE drives. Whom should we thank here??
The issue is to insert the driver files and the information of the ide drivers Windows should use with the next boot. How can it be this difficult?
What you basically need is..
- the information about the new chipset's PCIIDE.SYS/[VENDOR_PROVIDED_FILE].SYS and ATAPIIDE.SYS inserted into the values in HKEY_LOCAL_MACHINE\SYSTEM\ControlSetXXX\Control\CriticalDeviceDatabase
- and the vendor's IDE drivers to the %SYSTEMROOT%/System32/drivers folder.
Maybe something else, I don't know. But the problem was, Windows didn't know how, or what drivers to use. That can't be so big problem you need to install the whole OS anew!