Data partition messed up!

I'm at my wits' end about a strange problem, and I'm wondering if anyone has any ideas I haven't thought of.

It seems that something about the file/folder structure on a large hard drive partition is messed up. My entire machine locks up occasionally; I have no choice but to turn it off and reboot. I believe it's when Windows is trying to access certain files/areas on the partition.

My system is Windows XP Pro, Pentium 4, 1.6 gHz

I will try to reconstruct the long string of events that got me to where I am:

I keep OS and data in separate partitions on the same hard drive. I recently bought a new hdd, like I do every year or two, and partitioned and formatted it same as the old one: with Windows installed in one small partition and all my data in the remaining large partition.

I then moved what used to be the primary hard drive to a secondary position and booted to the new installation of Windows XP on the new drive. I did occasionally hook up the old drive so I could grab some data off its data partition.

My first sign of trouble was Windows startup insisting on doing a consistency check on the old data partition on every bootup. The process made it just about all the way through and then froze. I could do nothing to free it except hit the power switch.

I was able to boot into Windows (either old or new) by bypassing the consistency check. It worked mostly ok, but eventually, I'd click the wrong file or application and the machine would freeze and I'd have to hit the power switch.

I disconnected the old hdd, and kept only the new one hooked up, and for weeks everything was fine, as long as I kept that old partition on the old drive out of the way. I guessed that there's some weird file structure problem on the old drive.

Then a few days ago I was doing some wholesale copying of data from the (suspect) data partition on the old drive to the (previously uncorrupted) data partition on the new drive, and the *new* operating system locked up when accessing data on the *new* hard drive partition, displaying the same behavior as the old one (grr).

It appears that whatever was causing the problem on the old drive was contagious and has now been spread to the new hard drive. My best guess is a file structure problem, but nothing I've run seems to be able to fix it. Everything just freezes.

It's an old computer so I considered hardware failure, but I've run full manufacturers' diagnostics on both hard drives and they appear to be fine. A RAM diagnostic says the memory is fine too.

I googled and made a list of things to check:
The partition doesn't need to be defragged.
I have run chkdsk and it freezes.
I doubt if it's malware, although when I run virus scans it freezes 19% in. I have Comodo firewall with Defense+ and Avast antivirus.
I couldn't find any folder/file names that might be too long.
If I boot to Partition Magic floppies, the partition looks fine.

I'm guessing I'll just have to reformat the partition, which would not be the end of the world. That *should* make the problem go away. I'm just afraid to then try to salvage data, because it seems to be data that is causing the corruption.

Does anyone know of a program or technique that can further diagnose and/or fix this?

Thanks,
Ted

 

Seriously you should allow chkdsk to complete (and your virus scanner).

Have you tried them in safe mode?

What errors do you get when they fail?

 

I would try running Chkdsk from the XP CD. Instructions on below link.
http://kb.wisc.edu/helpdesk/page.php?id=5097

 

Thanks for responding.

They don't fail, they freeze. I have left them sitting at 19% or 76% or whatever for literally days. They don't complete, they're stuck.

I have tried chkdsk every which way (command window, from dos boot floppy, etc.). I don't know of a way to run the virus scan outside of Windows.

Thanks

 

Can't imagine the result would be any different than running chkdsk from a boot floppy, but I haven't tried that, so I'll give it a shot. Thanks very much.

 

I ran chkdsk from XP CD, same result: it got to 69% and stopped.

Sounds like that partition is hosed (or at least one or more spots on it - at the moment it seems to be working ok). I can understand why shutting the computer off while chkdsk is repairing (updating) a file structure might be disastrous. But I wish I knew the original cause, what caused chkdsk to freeze in the first place.

Oh, one more strange thing: the old hdd has gotten so fouled up that the drive letters don't even show up anymore in Windows Explorer. I suppose interrupting chkdsk might cause this too. Or maybe that one's honestly a hardware failure.

Anyway, thank very much for your input.

Ted

 

If you go to disk manager you should be able to reassigned drive letters, but check them for errors if sucessful. I'm begininning to think it's a controller failure, have you tested the HD's on another computer( not as boot devices )?

 

Hmm, interesting thought, thanks. No, I haven't done that. I probably should have tried replacing the IDE cable too.