"STOP: 0x0000007B and ED" problem

I'm getting this blue screen error when trying to install XP pro on my step brothers comp with a new 160g HDD. It previoulsy had windows xp vista compatible (never heard of that, but whatever) and a 250g HDD.

"STOP: 0x0000007B (0xF78e1524, 0xc0000034, 0x00000000, 0x00000000)"

With the original HDD the blue screen goes by in a split second, and I think it said "0x000000ED" not 100% on that though since it goes by sooo fast... 80%positive it says ED. I've tried reformatting the original HDD with XP pro, and I get the 0x0000007B error instead of ED.

The problem started when i was showing him how to play Oblivion, and the game crashed. I couldn't ctrl-alt-dlt out of it, or get to windows at all, and I had to re-start manually. When I tried to start the comp back up again, I would get the quick blue screen, and the ED error. My older brother told me it might be the HDD, so I got a new one today, but that doesn't seem to be the problem.

The comp isn't that old... not sure how old. It's a dell dimension e520 he bought from his fathers friend. It apparently has different/better parts in it, but I don't think it does since the vid card looks stock, and the CPU is an intel core2 duo 1.86g. I think he might have overclocked the CPU, and it fried but I'm not sure.

Any ideas? Thanks for your time. Apologies if this is the wrong forum for the problem.

 

Here's some info. on 7B and ED:

Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE

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.



Stop 0x000000ED or UNMOUNTABLE_BOOT_VOLUME

The kernel mode I/O subsystem attempted to mount the boot volume and it failed. This error might also occur during an upgrade to Windows XP Professional on systems that use higher throughput ATA disks or controllers with incorrect cabling. In some cases, your system might appear to work normally after you restart.

Possible Resolutions:

• If using higher throughput ATA disks and controllers, those capable of data transfer rates above 33.3 megabytes per second, replace the standard 40-pin cable with an 80-pin cable. Using an 80-pin cable is optional for transfer rates up to and including 33.3 megabytes per second, but is mandatory for higher transfer rates. The additional grounded pins are required to avoid data loss.

• Some firmware enables you to force higher transfer rates even when you are using the incorrect cable type. Your firmware might issue a warning but allow the startup process to proceed. Restore the default firmware setting for ATA cable detection.

• Problems that cause 0xED errors might also cause Stop 0x7B errors.

 

I have fixed both of the above BSOD errors by running chkdsk. It may not be a permanent fix as these errors are usually the sign of a failing hard drive. But you may be able to boot into XP so that any data can be saved. So, boot to the Windows XP installation CD and press "R" to enter the Recovery Console when you are prompted. Enter the desired the XP install (usually by selecting the only install available by pressing "1"). Enter the Administrator password; if there is none, press Enter. When you get to the command prompt, type chkdsk c: /r and press Enter. This can take some time so be patient. I have seen chkdsk take over 6 hours, and there may be times when it appears to have locked up, or you may even see the percentage indicator go backwards (from 62% to 53% for example), it may go backwards several times.... don't worry, this is all normal. Let it finish. Whne it's done, type fixboot and press Enter. You'll get a warning asking if you're sure that you want to write a new boot sector, answer Yes. Whne this is done, type Exit, press Enter, and remove the XP disc and try to boot normally.
Good luck! I hope this helps!
:major

NOTE: the command chkdsk c: /r has a space before and after the "c:"....

 

Thanks a lot for the help everyone! I'll give some of those a shot and see what happens.

Thanks again for the help!