Almost every time I reboot my Win2K/SP4 system, CHKDSK runs because
Win2K detected a "corrupt ntfs filesystem" on the boot disk. Every
once in a while I get a BSOD instead, in which case I have to move the
bad disk to D: and run CHKDSK manually from inside Win2K.

In both instances CHKDSK fixes the problem(s) and my disk is good to
go. What I would like to know is what is causing this. The entries in
Event Viewer do not help any.

When I have to run CHKDSK on a disk that resulted in a BSOD, the
repair entails fixing multitudinous "file descriptors" - what looks
like literally hundreds of them.

When I run the Defrag utility that comes with Win2K, there are two
entries for the boot disk

System Disk
System Disk (C

The parameters are identical and Defrag will operate on either of
them. There is also a pair for the Backup disk D: I have never seen
any double drive configurations before like this.

What is wrong and how do I fix it?



--

"It has been said that politics is the second oldest profession.
I have learned that it bears a striking resemblance to the first."
--Ronald Reagan

The drive may have failed. I'd download and run a disk diagnostic utility
from the drive manufacturer's web site.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Bob"wrote:
| Almost every time I reboot my Win2K/SP4 system, CHKDSK runs because
| Win2K detected a "corrupt ntfs filesystem" on the boot disk. Every
| once in a while I get a BSOD instead, in which case I have to move the
| bad disk to D: and run CHKDSK manually from inside Win2K.
|
| In both instances CHKDSK fixes the problem(s) and my disk is good to
| go. What I would like to know is what is causing this. The entries in
| Event Viewer do not help any.
|
| When I have to run CHKDSK on a disk that resulted in a BSOD, the
| repair entails fixing multitudinous "file descriptors" - what looks
| like literally hundreds of them.
|
| When I run the Defrag utility that comes with Win2K, there are two
| entries for the boot disk
|
| System Disk
| System Disk (C
|
| The parameters are identical and Defrag will operate on either of
| them. There is also a pair for the Backup disk D: I have never seen
| any double drive configurations before like this.
|
| What is wrong and how do I fix it?
|
|
|
| --
|
| "It has been said that politics is the second oldest profession.
| I have learned that it bears a striking resemblance to the first."
| --Ronald Reagan

On Sun, 05 Feb 2006 17:05:08 GMT, (E-Mail Removed) (Bob) wrote:

>Almost every time I reboot my Win2K/SP4 system,


You should describe this system, concise list of all major
components including the HDD(s).

>CHKDSK runs because
>Win2K detected a "corrupt ntfs filesystem" on the boot disk. Every
>once in a while I get a BSOD instead, in which case I have to move the
>bad disk to D: and run CHKDSK manually from inside Win2K.

Have you ran the HDD manufacturer's utilities?

>
>In both instances CHKDSK fixes the problem(s) and my disk is good to
>go. What I would like to know is what is causing this. The entries in
>Event Viewer do not help any.
>
>When I have to run CHKDSK on a disk that resulted in a BSOD, the
>repair entails fixing multitudinous "file descriptors" - what looks
>like literally hundreds of them.
>
>When I run the Defrag utility that comes with Win2K, there are two
>entries for the boot disk
>
>System Disk
>System Disk (C
>
>The parameters are identical and Defrag will operate on either of
>them. There is also a pair for the Backup disk D: I have never seen
>any double drive configurations before like this.
>
>What is wrong and how do I fix it?

See what's showing up in Disk Management.

Bob wrote:
> Almost every time I reboot my Win2K/SP4 system, CHKDSK runs because
> Win2K detected a "corrupt ntfs filesystem" on the boot disk. Every
> once in a while I get a BSOD instead, in which case I have to move the
> bad disk to D: and run CHKDSK manually from inside Win2K.
>
> In both instances CHKDSK fixes the problem(s) and my disk is good to
> go. What I would like to know is what is causing this. The entries in
> Event Viewer do not help any.
>
> When I have to run CHKDSK on a disk that resulted in a BSOD, the
> repair entails fixing multitudinous "file descriptors" - what looks
> like literally hundreds of them.
>
> When I run the Defrag utility that comes with Win2K, there are two
> entries for the boot disk
>
> System Disk
> System Disk (C
>
> The parameters are identical and Defrag will operate on either of
> them. There is also a pair for the Backup disk D: I have never seen
> any double drive configurations before like this.
>
> What is wrong and how do I fix it?

This is certainly not conclusive, but I have seen this exact behavior
from an underpowered system. Use a power supply calculator, like the
one linked below, to compare your component load to your supply's
rating. Even if that suggests that you have enough juice, it's possible
that your power supply is not living up to its rating. Someone here can
probably comment on the quality of your supply, based upon its brand name.

http://www.jscustompcs.com/power_supply/

Bob wrote:
> The parameters are identical and Defrag will operate on either of
> them. There is also a pair for the Backup disk D: I have never seen
> any double drive configurations before like this.

I think you have to have a close look at your partitioning. Looks to me
like your partition table has some serious errors. I don't think chkdsk
is able to fix those kinds of errors either, you should probably look
into something like fix-it utilities or partition magic. In any case:
BACK UP YOUR DATA OFTEN until you've fixed this problem.

Mark.

"Bob" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Almost every time I reboot my Win2K/SP4 system, CHKDSK runs because
> Win2K detected a "corrupt ntfs filesystem" on the boot disk. Every
> once in a while I get a BSOD instead, in which case I have to move the
> bad disk to D: and run CHKDSK manually from inside Win2K.
>
> In both instances CHKDSK fixes the problem(s) and my disk is good to
> go. What I would like to know is what is causing this. The entries in
> Event Viewer do not help any.
>
> When I have to run CHKDSK on a disk that resulted in a BSOD, the
> repair entails fixing multitudinous "file descriptors" - what looks
> like literally hundreds of them.
>
> When I run the Defrag utility that comes with Win2K, there are two
> entries for the boot disk
>
> System Disk
> System Disk (C
>
> The parameters are identical and Defrag will operate on either of
> them. There is also a pair for the Backup disk D: I have never seen
> any double drive configurations before like this.
>
> What is wrong and how do I fix it?
>
>
>
> --
>
> "It has been said that politics is the second oldest profession.
> I have learned that it bears a striking resemblance to the first."
> --Ronald Reagan
could be memory errors - run memtest

On Sun, 05 Feb 2006 19:17:17 GMT, kony <(E-Mail Removed)> wrote:

>Have you ran the HDD manufacturer's utilities?

Not all of them. I have both the DLG Tools and Diags. I will run the
diags next.

I periodically swap three identical disks (80GB WD) into the boot disk
tray, and each of them shows the same behavior.

>>System Disk
>>System Disk (C

>>The parameters are identical and Defrag will operate on either of
>>them. There is also a pair for the Backup disk D: I have never seen
>>any double drive configurations before like this.

>>What is wrong and how do I fix it?

>See what's showing up in Disk Management.

I see only one disk. The same for Device Manager - Disk Drives.



--

"It has been said that politics is the second oldest profession.
I have learned that it bears a striking resemblance to the first."
--Ronald Reagan

On Sun, 05 Feb 2006 20:24:29 GMT, Grinder <(E-Mail Removed)>
wrote:

>This is certainly not conclusive, but I have seen this exact behavior
>from an underpowered system. Use a power supply calculator, like the
>one linked below, to compare your component load to your supply's
>rating. Even if that suggests that you have enough juice, it's possible
>that your power supply is not living up to its rating. Someone here can
>probably comment on the quality of your supply, based upon its brand name.

>http://www.jscustompcs.com/power_supply/

198 watts.

The PSU I have is rated at 350 watts.

This is not an exotic machine: Celeron D, 2 sticks of DDR RAM, onboard
(MCI Mainboard) video, sound, NIC, two WD 80 GB HDs and an NEC 3540
DVD burner.

I used to get a lot of errors with the USR Journal but that has
quieted down.

Event Viewer shows that the detection of this corruption occurs at
shutdown. IOW, the entry I find when I fix the disk and reboot is
timed exactly with when I shut down.


--

"It has been said that politics is the second oldest profession.
I have learned that it bears a striking resemblance to the first."
--Ronald Reagan

On Mon, 06 Feb 2006 06:21:14 GMT, "Sleepy" <(E-Mail Removed)> wrote:

>could be memory errors - run memtest

I will.


--

"It has been said that politics is the second oldest profession.
I have learned that it bears a striking resemblance to the first."
--Ronald Reagan

Bob wrote:
> Grinder <(E-Mail Removed)> wrote:
>
>> This is certainly not conclusive, but I have seen this exact
>> behavior from an underpowered system. Use a power supply
>> calculator, like the one linked below, to compare your component
>> load to your supply's rating. Even if that suggests that you
>> have enough juice, it's possible that your power supply is not
>> living up to its rating. Someone here can probably comment on
>> the quality of your supply, based upon its brand name.
>
>> http://www.jscustompcs.com/power_supply/
>
> 198 watts.
>
> The PSU I have is rated at 350 watts.
>
> This is not an exotic machine: Celeron D, 2 sticks of DDR RAM,
> onboard (MCI Mainboard) video, sound, NIC, two WD 80 GB HDs and
> an NEC 3540 DVD burner.
>
> I used to get a lot of errors with the USR Journal but that has
> quieted down.
>
> Event Viewer shows that the detection of this corruption occurs
> at shutdown. IOW, the entry I find when I fix the disk and
> reboot is timed exactly with when I shut down.

Given that you have a NTFS system you are probably using an
ever-suspect Windoze system. My guess would be that the system
isn't smart enough to wait for pending file system writes to
complete before shutting down. Maybe simply waiting a minute or so
with a totally inactive system before powering down would do it.

Alternatively, unless you are using ECC memory, you may have the
odd bad memory bit. This is much less likely than sloppy OS
programming.

--
"If you want to post a followup via groups.google.com, don't use
the broken "Reply" link at the bottom of the article. Click on
"show options" at the top of the article, then click on the
"Reply" at the bottom of the article headers." - Keith Thompson
More details at: <http://cfaj.freeshell.org/google/>
Also see <http://www.safalra.com/special/googlegroupsreply/>