I have a machine in my "shop" for repair. The owner had complained of BSOD
and was unable to boot to the desktop.
After running it here for over a week now I could not repeat the problem..so
think it *might* have been a fluke or possibly associated with some
periphery device such as a printer or scanner.

*However*

Upon running chkdsk (audit only) from within the OS...problems are found
every time...
and are different with each run.

Running chkdsk /f or chkdsk /r ...upon reboot has never yet found any
problem.

I have only seen this situation once before and "fixed" it by slightly
underclocking the RAM.

On this machine...*nothing* I have done has had any affect. It has no manual
settings but I have been able to "underclock" it by putting in a slower CPU.
I've also tried different RAM and even RAM rated at a higher speed than the
locked bus setting.

As a matter of fact...except for the mobo itself I have replaced *every*
part in the machine...
including the harddrive!

(FWIF: all memory diagnostics and mfg HD diagnostics turned up fine)

Since the machine runs just fine I guess all I can do is return it to the
owner and see if it happens again.
If any future problems occur (not associated with a periphery device) I
guess it will be time for a new machine.

Has anyone else seen this situation?

Try clearing the CMOS,if the hd errors remaine no matter which hd is
used,then the fault(s) are probably in the controller.Try switching the IDE
connection to the hd,also,open event viewer for errors/warnings (try 1st),
a corrupted controller will run off and on for awhile,but should show
problems
in event viewer 1st.

"philo" wrote:

> I have a machine in my "shop" for repair. The owner had complained of BSOD
> and was unable to boot to the desktop.
> After running it here for over a week now I could not repeat the problem..so
> think it *might* have been a fluke or possibly associated with some
> periphery device such as a printer or scanner.
>
> *However*
>
> Upon running chkdsk (audit only) from within the OS...problems are found
> every time...
> and are different with each run.
>
> Running chkdsk /f or chkdsk /r ...upon reboot has never yet found any
> problem.
>
> I have only seen this situation once before and "fixed" it by slightly
> underclocking the RAM.
>
> On this machine...*nothing* I have done has had any affect. It has no manual
> settings but I have been able to "underclock" it by putting in a slower CPU.
> I've also tried different RAM and even RAM rated at a higher speed than the
> locked bus setting.
>
> As a matter of fact...except for the mobo itself I have replaced *every*
> part in the machine...
> including the harddrive!
>
> (FWIF: all memory diagnostics and mfg HD diagnostics turned up fine)
>
> Since the machine runs just fine I guess all I can do is return it to the
> owner and see if it happens again.
> If any future problems occur (not associated with a periphery device) I
> guess it will be time for a new machine.
>
> Has anyone else seen this situation?
>
>
>

"Andrew E." <(E-Mail Removed)> wrote in message
news:68701D20-100A-4AD4-8317-(E-Mail Removed)...
> Try clearing the CMOS,if the hd errors remaine no matter which hd is
> used,then the fault(s) are probably in the controller.Try switching the
IDE
> connection to the hd,also,open event viewer for errors/warnings (try
1st),
> a corrupted controller will run off and on for awhile,but should show
> problems
> in event viewer 1st.
>


Thanks for the reply...
I did look in event viewer and found nothing out of the ordinary.

I suppose the controller on the mobo could be bad and I could possibly try
the 2nd channel or add a PCI controller...
the thing is that there has *never* been an error when running chkdsk /f.

Errors are *only* seen when running chkdsk in the audit-only mode from
within the OS

"philo" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
>
> "Andrew E." <(E-Mail Removed)> wrote in message
> news:68701D20-100A-4AD4-8317-(E-Mail Removed)...
> > Try clearing the CMOS,if the hd errors remaine no matter which hd is
> > used,then the fault(s) are probably in the controller.Try switching the
> IDE
> > connection to the hd,also,open event viewer for errors/warnings (try
> 1st),
> > a corrupted controller will run off and on for awhile,but should show
> > problems
> > in event viewer 1st.
> >
>
>
> Thanks for the reply...
> I did look in event viewer and found nothing out of the ordinary.
>
> I suppose the controller on the mobo could be bad and I could possibly try
> the 2nd channel or add a PCI controller...
> the thing is that there has *never* been an error when running chkdsk /f.
>
> Errors are *only* seen when running chkdsk in the audit-only mode from
> within the OS
>
>

As I expected the current system will not boot from an add-in PCI controller
nor from the 2nd IDE channel...
so I'm now performing a fresh install using a PCI controller ...
I'll post back with the results when I'm done



--
Posted via a free Usenet account from http://www.teranews.com

>
> As I expected the current system will not boot from an add-in PCI
controller
> nor from the 2nd IDE channel...
> so I'm now performing a fresh install using a PCI controller ...
> I'll post back with the results when I'm done
>
>



Fresh install using a PCI controller. HD is not on the mobo IDE channel

Identical problem!!!!

There has to be some (perhaps minor ? ) glitch in the mobo