I suggest that you trawl through this lot
http://www.eventid.net/display.asp?e...e=Disk&phase=1

In the above link it'll tell you about Event ID 51; you can then look up the others and put together a set of reasons that fit your combination.

I presume all the jumpers on the new disk are correctly set with regard to prefetch and buffering or whatever BIOS options you may be offered. There may also be a Windows drivers issue if you've changed drives.

Sounds like the drive isn't configured right, damaged, not installed right, or its some sort of fluke. Try physically reinstalling it, ensuring any jumpers are correctly set (most likely slave or cable select would suit you). If you have any questions on this, go ahead and give us your setup and hardware information (model number of your hdds and whatever hardware you can) and we should be able to help you. (Like is the drive PATA or SATA? Its your second drive in your system, right? Or are you replacing your C: drive? Those sorts of things )

Another possibility is that it is a bad drive. Its actually not that uncommon to receive a drive DOA (Dead on Arrival). I think it has something to do with how incredibly complicated and small the components are becoming, but its just a hunch. Since you presumably just purchased this drive, try returning it to the store or contacting the manufacturer for a replacement if you're still having trouble.

When dealing with your drive, make sure to ground yourself! Use an antistatic strap or antistatic gloves, or at the bare minimum, touch a metal part of your computer case for a few seconds. Don't work on carpet, and unplug your computer unless you can cut the power to your outlet, then you can leave it plugged in so its grounded better. Oh, and a common mistake- that I've made a lot- don't put hardware on the outside of antistatic bags unless you touch the bag to your computer case (or other grounded metal) for 10-15 seconds, because electricity builds up on it.

Just a few pointers, you've probably heard them countless times, but it doesn't hurt to reiterate.

Get back to us with an update!

--The Comodore

Well i have 250gb Sata Seagate hdd.
20gb primary partition and rest of them are logical drives with approx 53 gb each.
And i have configured it with DiscWizardSetup.And installed windows xp onto it.It ran very well for first 3-4 hours until i started transferring data to this from WD external hdd.And i had these types of errors on my old 80gb hdd also.
Few weeks ago i had a similar problem with my 200gb hdd and i replaced it.I have checked data cables.Tried 3 different data cables and power cables.Still windows xp is running slow.I am starting to assume that either my power supply is faulty or its becoz of RAM.Becoz same thing cant happen to three hdd?I have 450 watt power supply.
For more you can look at into this problem also which i am facing my config is also written there

http://www.daniweb.com/forums/thread102063-2.html

Well, you should follow the advice I gave you earlier becasue there is detailed information on each of the errors you are seeing. Also Microsoft have got articles on this in their knowledgebase.

I really think this is a cacheing problem. If it has affected more than one HDD then it's unlikely to be a hardware fault. There'll likely be a SATA setting or a BIOS setting or a Jumper or even an updated device driver that'll sort this lot out.

Can u tell me what kind of settings should i keep for BIOS?And i dont know much about jumper settings also.

Start here on this site and explore your options in depth.
http://www.seagate.com/ww/v/index.js...00dd04090aRCRD

Also follow up on my original advice regarding your event IDs.

You are going to have to take this problem into your own hands because you're in front of the PC and we're thousands of miles away. I've pointed you to the information sources.

Come back for further help.

If you didn't change anything, then the jumpers on your motherboard should be fine as they are.

For your hard drive settings, check out this website to help you with that

http://www.ehow.com/how_6031_change-...signation.html

You should do master on the original drive and slave on the new one, or do cable select on both and make sure that the original drive is at the end of your cable and the new one is on the second connector a bit further down.

This is all assuming you are using ATA cable (long, wide, flat, cabling that is usually grey) instead of SATA cabling (which is not nearly as wide, thicker, and usually red). If you're using SATA, just make sure you have your original drive plugged into the 0 port (or 1 if there is no 0) and the second one is further along the number line. Its pretty straightforward- you want your main (the one with your OS installed) hard drive to be the lowest down the list, and your second one to be after it, but before any other SATA devices.

Make sense? :p

Tell us if you have more questions!

--The Comodore

I have checked my hdd and one of my drive has 20kb bad sectors in it.grr i got this hdd yesterday.Thanks for your help guys.But still i am confused about my another problem thats related to windows xp i thought new hdd will help me but it didnt.Have to wait for few more days now to get the new replaced hdd.

grrr i formatted that hdd again and bad sectors removed wtf?

And i have now installed windows xp on that hdd and my pc is freezing again.

Got this error in the event viewer

event id = 17
source = W32time

desc =
"
Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer 'time.windows.com,0x1'. NtpClient will try the DNS lookup again in 15 minutes. The error was: A socket operation was attempted to an unreachable host. (0x80072751)
"


another error

source = haspnt
eventid= 3
desc = "The description for Event ID ( 3 ) in Source ( Haspnt ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: \Device\Hasp, 0xC0000034.."

system hangs with a beep sound.
Whats going on?