Discussion Locked

HD corruption causing Windows slowdown?

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

A couple of days ago I decided to take my computer tower to school. After I got there (carried it on the bus :P) and set it up it wouldn't boot (said it "could not load OS"). I tried starting in save mode but it would hang while trying to load the system files (specifically on the file 'agp440.sys').

When I got back home I tried the Microsoft bug fix suggestion for the 'agp440.sys' (http://support.microsoft.com/default.aspx?scid=kb;en-us;324764) problem but it didn't help (safe mode just hung up on a different .sys file). I was suspecting some OS files got currupted.

Then I tried booting from the WinXP SP2 CD, pressed 'R' and then tried to run chkdsk /p and /r which took A WHILE (at first it was fast, but after getting to about 70% it went back to 50% and then took about 1.5hrs to finish).

I then reinstalled Windows XP SP2. It kinda worked...Windows started up fine, but it was VERY VERY SLOWWW (the first time it started it took about 20sec for the start menu to open after it was clicked). I restarted, it was better but it was still SLOW (the cursor would jump, took a while to open any program, etc). I quickly started backing up my data to my other HD, which also was SLOWW (transferring a 700MB file to my other HD took about 35min!). Burning CD's and DVD's was also 10 times slower (took 2hrs to burn a DVD which usually takes 15min).

I tried running hardware diagnostics tools such as PowerMax (both my HD's are Maxtor), Tuff-Lite (full hardware system tests) but they claimed all was fine!

I ran Defrag which found the HD to be rather fragmented (didn't defrag for 5 months). To Defrag the 80GB drive took about 8hrs! There was no improvement in symptoms afterwards.

I tried running ScanDisk, which went through the first 3 phases fine but was VERY slow on phase '4 out of 5' (checking file data)...it took about 2hrs to get to 13% at which point I gave up and stopped it.

Currently I?m running 'HDD Regenerator v1.41' which does a physical surface scan (and repair) for bad sectors. Currently it went through the first 20GB but found no bad sectors!

I'm running out of ideas!!!
Is my HD done for?? Would doing a clean format fix this? And even if that does work would it be dangerous to store data on it because it's 'unstable'??

---- My System Specs:
- P4 2.0Ghz 512K 400FSB S478
- motherboard: ABIT BD7II ATA100
- RAM: 512MB PC2100 266Mhz
- Video card: ATI Radeon 9600XT
- HD1 (OS on this one): MAXTOR 80GB
- HD2: MAXTOR 120GB
- OS: WinXP SP2 fully updated.
-----

HELP!!!

4 replies

by thechas

First off, Technical questions belong in the Technical Q&A section of TR.

Secondly, you have already done too much without correcting the root problem.

While it is gut instinct to suspect your hard drive with the symptoms you have, a more likely cause is a loose connection.

Check all of your internal connections.
Remove and reseat all plug in cards, RAM modules, and cables.

Check that the lever on the CPU socket is in the locked position.

While rare, another possible cause is a fractured solder joint on any of the circuit boards. The motherboard being at the most risk.

Unfortunately, if reseating connectors does not fix the problem, the easiest way to trouble-shoot this is to swap parts until you find the culprit.

Chas

by hal 9000

I would start looking for a loose or broken connection on the leads to the HDD's and start off by replacing the IDE lead and see if there is any improvement these 80 way leads do break from time to time and I've run across a few that just don't work right for no visible reason but when replaced everything is up and running properly.

If that happens cut the lead with something and bin it! It will save you a lot of grief latter when somehow it ends up in another computer.

While the Q & A would get you faster responses just at the moment it doesn't appear to be working properly as I've been unable to answer a few questions. So for the time being forget about it but generally you will get a faster response to any questions that you ask there as you'll get an auto-generated message telling you that someone has answered your question whenever someone places an answer. That way you are far more likely to get someone in your time zone to help you out which is just plain faster for you. Don't forget to rate every response and post your solution when and if you find one.

Col

by deepsand

This is a tech. problem, in search of a solution.

It properly belongs in "Technical Q&A," not in "Discussions." Please re-post there.

Not only will you be more likely to attract the attention of those seeking to provide answers, but you will also make it easier for those seeking discussions to find such.

Thank you.

by panzer_ace

FIXED!

I formatted and did a clean install of Windows...and all was good! Just proves that often formatting is the best (and easiest) fixing method.

I still have no idea what was wrong with it specifically (software problem for sure though). Here's my theory: When I brought it to school I guess all that shaking somehow managed to corrupt a few system files on the HD (that's why windows wouldn't start). After I reinstalled windows I guess those files were over-written but something else got messed up (drivers, file system, swap file...we'll never know).

Suggestion for similar problem of this type:
1. Do a virus scan, defrag if you need to.
2. check all hardware connections (especially IDE cables) and restore your BIOS setting to default.
3. check Hard drive for problems (ScanDisk or physical surface scan using programs like HDD Regenerator to find bad sectors)
4. If neither one helps, back up your data, format the drive and do a clean install of windows
5. If the problem still presists, well then there is something for sure wrong with your hardware. Try using the hard-drive in another computer, basically do a process of elimination until you find the culprit.

Thanks for all the help and suggestions everyone!

This discussion is closed to new replies.