From: Eldorage on
This problem has started recently. No hardware changes. No major software
installs.

Almost every time I boot the computer, after the "Starting Windows" screen I
get a blue text screen with "Please wait......" and then it continues
printing more white dots (periods) for several lines. This can take up to 10
minutes sometimes, nearly filling the screen.

A search on Google suggested "fsutil query dirty C:" and "chkntfs C:", but
these always tell me that the volume is NOT dirty.

I am running Windows XP Pro with all the latest patches and all drivers are
the latest versions. C: is a raid0 stripe using two 500GB drives to make a
1000GB volume.

If you have any ideas on what the problem might be, or how to diagnose it,
please let me know.

From: news.verizon.net on
In my experience this can have several different causes:
you have a virus
run your virus check program

your memory is going bad
check your ram with memtest86, http://www.memtest86.com/, get the free
download and make a bootable disk

your system files are corrupt
from the run box type: sfc /scannow
this will restore your system files if errors are found

your hard disk is going bad
this is the least likely, if the cause, change HD

Jeff



"Eldorage" <eldorage(a)gmail.com> wrote in message
news:63liv35les6345b2dqc1omljdmcuqh59dn(a)4ax.com...
> This problem has started recently. No hardware changes. No major software
> installs.
>
> Almost every time I boot the computer, after the "Starting Windows" screen
> I
> get a blue text screen with "Please wait......" and then it continues
> printing more white dots (periods) for several lines. This can take up to
> 10
> minutes sometimes, nearly filling the screen.
>
> A search on Google suggested "fsutil query dirty C:" and "chkntfs C:", but
> these always tell me that the volume is NOT dirty.
>
> I am running Windows XP Pro with all the latest patches and all drivers
> are
> the latest versions. C: is a raid0 stripe using two 500GB drives to make a
> 1000GB volume.
>
> If you have any ideas on what the problem might be, or how to diagnose it,
> please let me know.
>