Citizen Bob <spam@uce.gov> wrote
> Rod Speed <rod.speed.aaa@gmail.com> wrote

>> That sounds like some fundamental hardware problem
>> like the motherboard doesnt like the ram much.

>> I'd run memtest86 overnight every night because it
>> looks rather like the problem is rather intermittent.

> I have run it but not every night.

I'd run it every night for a few weeks, because it
looks like it might well be an intermittent problem.

>> You never did say it very clearly.

> I did many times earlier.

Nope, you never spelt it out that clearly before.

It wasnt initially clear that reformat to FAT32 had fixed just
SOME of the problems and not the duplicate entrys either.

> This thread has been recurring for several months now.
> Apparently you were not participating on this particular
> forum back then.

Its silly to rely memory of stuff that far back even if I was.
There's been a few more than just you with problems over that time.

>>> I have to reboot to run chkdsk, and that is when the
>>> corruption shows up. It does not show up unless I reboot.

>> Likely that is just because it isnt corrupted enough to affect normal ops.

> It is pretty corrupted when it BSODs.

Sure, I meant when it doesnt, just runs chkdsk itself at boot time.

> CHKDSK fusses about all sorts of things. I posted a file
> containing all the crap CHKDSK fixed and it is several
> pages long. Next time I get a BSOD, I will post it again.

Dont bother, I can find it using groups.google
and the detail really doesnt matter much.

>>> Ironically, if the corruption occurs, Win2K runs chkdsk for me at boot time.

>> Thats rather odd. That may be a coincidence tho, just that you are
>> only aware of the corruption when chkdsk is run and when 2K chooses
>> to run it, presumably because it decides that it wasnt shut down
>> properly, you see the corruption just because chkdsk has been run.

> There are entries in the Event Viewer - "corrupt ntfs volume, run chkdsk".

And that is something you should have said earlier too.

> Not very helpful.

Dunno, how soon those show up might well be useful info
about how soon you start seeing corruption after a cleanup.

> Nothing else seems to be wrong in EV.

> After a few days of running the "new" NTFS partition, the
> one made from the earlier FAT32, I finally got a corrupt
> disk. When it was booting it ran CHKDSK on its own.

When did the first EV entry show up in that sequence ?

> The only apparent problem was "blank space in the MFT".

Clearly something is screwing with the directory structures.

I'd personally do a clean install of 2K on a spare hard drive
and run that for days to see if that gets corrupted too. Basically
to see if the problem is with the hardware or a fucked 2K install.

It'd be hilarious if it turns out to be those removable drive bays that are doing it.