Blue sceen with stop error codes have appeared tried reinstalling windows but has not worked fitted new hard drive but blue sceen is still there with error codes

Hi,
I see your hard drive stopped working, any errors on the Hard drive when trying to turn the system on? do you get a blue screen? or just a black screen when the system is turned on?
Try going into safe mode, turn the computer ON then keep on tapping F8 to get the options menu select safe mode see if windows will boot p from there then you can back up any files you need and most likely reinstalling windows will be best to avoid the problem from happening again.
Also reinstalling windows will give you more details if the hard drive the the one that caused it to top or a different device.
If reinstalling stops and gives you a blue screen then most probably the hard drive is faulty or shall I say not anymore bootable, but if it works on safemode then you can try reinstalling windows see if windows installs then great, but if it result to a blue screen you will have to find out what is causing that...
this can be a faulty RAM on the system or a faulty Video Card if your video card is an expansion video card not a built in video card.
Also if you hear a clicking noise from the Hard Drevie then the problem is the HDD itself and needs replacing.

The blue screen signals that several critical files from Windows are corrupted. It's too late to repair that, you will have to completely reinstall so use the recovery cd that came with the pc when you bought it.

I had a similar problem but I can't recall if it was the same error number as in your message---what I did was used the recovery console and re-wrote my master boot record (MBR) my error was in the MBR causing my computer not to boot up in the first place. Your bootable cd should give you an option to use the recovery console before you reinstall, take it and use "fixmbr" at your dos prompt. XP works like that, but I've never had that problem with vista yet....it's worth a try if vista does the same.

If you are running Windows XP, the boot to the XP CD, press R when prompted to access the Recovery Console, then run the command CHKDSK /R at the C:\windows\system32\ prompt
If you get indications of recovering lost allocation units, then the disk surface of the HDD is likely bad and the HDD will need to be replaced.
If running Windows Vista or Windows 7, boot to the Windows DVD and select REPAIR MY COMPUTER

In Figure 2-2 you can also see that the Windows service SPCMDCON.SYS has failed. From the BSOD, you should be able to gather the following information:
•The stop error number, which uniquely identifies the error
•The stop error parameters, which provide additional information relating to the specific stop error number
•Driver information is available if the source of the problem relates to drivers
Armed with this information, you are able to search online to establish the problem and hopefully a resolution.
In addition to the information available on the blue screen, if the system is able to be rebooted after the BSOD, either normally or using Safe Mode, it is useful to take a look in the System Event Log and view the error message. For example, a faulty driver during boot up usually has the stop error code STOP: 0x00000050 and an Error EventID of 1003.
If your system refuses to reboot successfully, or is trapped within a perpetual BSOD that restarts over and over again, you should take the following steps. Press F8 after the BIOS screen appears. From Advanced Boot Options, select Disable automatic restart on system failure, as shown in Figure 2-3. This allows you to read and make note of the information contained on the BSOD. You can then allow Windows to attempt a reboot. If the perpetual loop reoccurs, select another option, such as Safe Mode, from the Advanced Boot Options menu.
If your system refuses to reboot successfully, or is trapped within a perpetual BSOD that restarts over and over again, you should take the following steps. Press F8 after the BIOS screen appears. From Advanced Boot Options, select Disable automatic restart on system failure, as shown in Figure 2-3. This allows you to read and make note of the information contained on the BSOD. You can then allow Windows to attempt a reboot. If the perpetual loop reoccurs, select another option, such as Safe Mode, from the Advanced Boot Options menu.



To disable the system from automatically rebooting, take the following steps:
1.Click Start, right-click Computer, and select Properties.
2.Click Advanced System Settings.
3.In the System Properties dialog box, click the Advanced tab. Under Startup and Recovery, click Settings.
4.In the System Failure box, clear the Automatically Restart check box.
These steps can also be configured if the system is booted in Safe Mode. There are over 300 unique stop codes, and most are quite rare. The full list
can be found on MSDN within the Bug Checks (Blue Screens) reference at
https://msdn.microsoft.com/en-us/library/windows/hardware/hh994433(v=vs.85).aspx.

It sounds like you drive has bad sectors. You can replace it with any 40-250GB ATA 2.5 inch drive. If you want your data back, you can still ready you data with tools like ddrescue and create an image file. Then you read the image file with a file carving utility like photorec. It's not quite that easy, since those are command line tool, but your geeky friend will help you with this. If you want somebody else to do it for you there is Data Recovery NYC. Also there is good information on hddguru.com.

You need to reinstall Windows, it's toast.

The blue screen during reformatting is not an issue with the motherboard. The issue is with the hard drive. Find or purchase a new hard drive and try to reinstall Windows on the new drive.

This is due to a hardware conflict.
The system drivers on the hard drive are for the old mother board and devices,You will have to reinstall OS while it is install on the new mother board,The computer cannot boot to a drive that is loaded to another system unless all the devices and drive are identical.

Please rate this a fixya

its a Windows Error Mostly from the software not the hard drive