Blue screen during boot [w/ screenshot pic]

[runallday400j50]

<A TARGET="_blank" HREF="http://i19.photobucket.com/albums/b171/soccergeek0303/HPIM2719.jpg">screenshot[/url]

thats the screen i get when i turn it on, after the winXP logo comes up for a sec.
Im using a parallel ATA as a primary master and i believe my jumpers are set correctly.
All connections seem to be fine and have swapped cables too to check cable problem. but dont think it is the cable problem bc if it was, i dont think the winXP logo wouldve shown up since it wouldnt detect any HD. by the way.. the only component (besides the essentials) connected to this computer is the HD
i dont get whats wrong with it. any help and/or advice would be appreciated, thanks!

[patio]

DLoad and run the diagnostics from the drive manuf. website...the files are used to create a bootable CD/floppy.
I'd still replace the IDE cable with a new one.
If it's the only HDD it should be jumpered as master and hooked up to the end connector of the IDE cable.

[dahlarbear]

1.  Jumper(s).

If it's the only HDD it should be jumpered as master and hooked up to the end connector of the IDE cable.

Or jumpered as "single" if that is an option.

2.  Incorrect Cable.

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. For more information about 0x7B Stop messages, see "Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE" earlier in this appendix.

Microsoft KB articles:
STOP 0x000000ED Error Message When Volume on IDE Drive with Caching Enabled Is Mounted
STOP 0x000000ED UNMOUNTABLE_BOOT_VOLUME

3.  Damaged File System:
STOP 0x000000ED UNMOUNTABLE_BOOT_VOLUME

Taken from the above Microsoft link.  Note the second parameter of your STOP error message.

Method 2: Damaged File System
If the second parameter (0xbbbbbbbb) of the Stop error is 0xC0000032, the file system is damaged.

If this is the case, restart the computer to the Recovery Console, and then use the chkdsk /r command to repair the volume. After you repair the volume, check your hardware to isolate the cause of the file system damage.

To do this, follow these steps: 1.   Start your computer by using the Windows startup disks, or with the Windows installation disk if your computer can start from the CD drive.
2.   When the Welcome to Setup screen appears, press R to select the repair option.
3.   If you have a dual-boot or multiple-boot computer, select the Windows installation that you want to access from the Recovery Console.
4.   Type the administrator password when you are prompted to do this.

Note If no administrator password exists, press ENTER.
5.   At the command prompt, on the drive where Windows is installed, type chkdsk /r, and then press ENTER.
6.   At the command prompt, type exit, and then press ENTER to restart your computer.

If this procedure does not work, repeat it and use the fixboot command in step 5 instead of the chkdsk /r command.

4.  Take it slow and easy.  Let us know what the disk drive diagnostics show.