- #1
Physics_wiz
- 228
- 0
I don't know if placing this post in this section is appropriate or not but I will appreciate any help.
I built my computer last summer and got a 40 GB WD Hard drive for it. After a couple of months, the HD started clicking and freezing the computer and after a while the computer wouldn't even start. I found that I lost the reciept so I bought a new 80 GB WD Hard drive and it worked fine. after about a month or two it started doing the same thing! I am pretty sure that there is something wrong with my computer because two faulty WD hard drives in a row would be a really weird coincidence. I tried switching the IDE cables around but that didn't work. I put the HD in my brother's computer, then ran a disk check and it fixed it for a bit, but after a week or two in my computer it did the same thing again. Now it gives me the error: "Windows could not start because the file ntoskrnl.exe is missing or corrupt." I can probably format it and get it to work again for a while but I would like to hear what anyone has to say about it, because, like I said before, I don't think it's the hard drive's problem.
I'm running windows XP PRO
2.0 GHZ AMD athlon XP processor 2400+
256 MB of ram
I built my computer last summer and got a 40 GB WD Hard drive for it. After a couple of months, the HD started clicking and freezing the computer and after a while the computer wouldn't even start. I found that I lost the reciept so I bought a new 80 GB WD Hard drive and it worked fine. after about a month or two it started doing the same thing! I am pretty sure that there is something wrong with my computer because two faulty WD hard drives in a row would be a really weird coincidence. I tried switching the IDE cables around but that didn't work. I put the HD in my brother's computer, then ran a disk check and it fixed it for a bit, but after a week or two in my computer it did the same thing again. Now it gives me the error: "Windows could not start because the file ntoskrnl.exe is missing or corrupt." I can probably format it and get it to work again for a while but I would like to hear what anyone has to say about it, because, like I said before, I don't think it's the hard drive's problem.
I'm running windows XP PRO
2.0 GHZ AMD athlon XP processor 2400+
256 MB of ram
Last edited: