JimL said:
Don't know right now. Last night I moved the contents and
reformatted the partition. As of now HD Tune shows fewer bad blocks
than before the format.
I don't quite understand why the bad blocks would cause the thrashing
given that they are not on the system partition and, for that matter,
not used in the tiny amount of data on that partition.
Blocks being marked as Bad wouldn't cause thrashing. Blocks that are
questionable might, but it would take a lot of them. An extremely
fragmented drive (partition) might, but that's still not a given. And
while it's idle, unless you have a lot of background tasks running, it
would stop after a few minutes, too. Background tasks could be anything
from indexing to AV doing checks during idle times, anything else you
have that works during "idle" times.
But no, bad blocks wouldn't cause thrashing.
It's possible that the suggestion to get more memory is valid. Or
maybe just getting the new drive in will stop it ... Time will tell.
Or not.
Any chance you could move everything to a different drive? Using an
"image", NOT a clone, would not destroy data on the disk. The machine
would simply be returned to the state it was in at the time the image
was made. Any changes to that partition after that point would of
course be lost; it's like backing up in time.
Cloning is essentially the same, but everything on the intended
partition is replaced with whatever the machine is when the clone was
made. Cloning DOES the equivalent of a format to that partition.
The very first thing I did was get the company's utility. It
declared and still declares everything to be glorious. But that is
only a readout of SMART. Perhaps the fact that the bad blocks are
not being actually "called upon" keeps the SMART readout looking good.
Hmm, the mfr's utility SHOULD check the ENTIRE disk's surface! If it's
not doing that (it takes some time to do, also), it's either not the
right utility or they aren't supplying one.
What brand/model/size is the drive? Seems like you said 360G but
that's only part of the puzzle.
Silly questions:
-- How did killing pf, defrag, turning pf back on work; any help?
-- How about the tool MSConfig? Use it to boot up without any of the
background tasks running.
It might be worth your while to add a post to th is thread re-describing
the problem as precisely as you can and listing what you've tried in
troubleshooting.
Use bullet style as much as you can and put the prose elsewhere. You
would have less "I already did that" types of suggestions and by putting
it all together it might tick somethin in someone's memory and turn into
an "AHA" moment.
Twayne`