I know this has been posted here and all over the internet in the past...and that's where my problem lies actually.
i can't find a solution that works!
My problem:
After going through the installation of windows XP Pro on a SATA HDD and i am using the Latest Nvidia SATA controller during installation (pressing F6, etc.) windows installs fine. (i have an nForce motherboard)
After the install, when windows is booting up (screen with the logo and a bar below it) it loads for about 2 seconds, then gives me a BSOD with the 0x0000007B error.
I've been looking non-stop for a fix for the past 14 hours for a solution, but couldn't find anybody who has the same problem as me actually...
I've tried re-installing from scratch. I've tried repairing windows. Both of those methods don't work...i really can't think of what else it could be. It can't be the bios because windows installs just fine...it's after the installation that it gives me the error.
I've also tried to toggle the RAM, but that doesn't do anything...
my Specs:
EVGA 790i Ultra SLI Mobo
Seagate Baracude 200GB HDD
OCZ 4GB DDR3 RAM
EVGA 9800 GTX Video Card
Intel Q6700 CPU
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.
