Whenever I schedule Error Checking with the option to fix errors for drive
C: and restart the computer, it completes the chkdsk but then restarts the
computer again after flashing a blue screen. Then it gives me a screen where
I can start normally or boot the last known good configuration. If I boot
normally it does chkdsk again and then restarts again. But if I choose last
known good, it launches XP. I don't know what the blue screen says because
it flashes for only a fraction of a second. And I don't know if it's because
I deleted some files by mistake or because I scheduled chkdsk twice. This
problem is only on drive C, not the other drives. I've spent hours googling
this problem but could not find anything. Any help will be appreciated.

"RJ" <(E-Mail Removed)> wrote:

>Whenever I schedule Error Checking with the option to fix errors for drive
>C: and restart the computer, it completes the chkdsk but then restarts the
>computer again after flashing a blue screen. Then it gives me a screen where
>I can start normally or boot the last known good configuration. If I boot
>normally it does chkdsk again and then restarts again. But if I choose last
>known good, it launches XP. I don't know what the blue screen says because
>it flashes for only a fraction of a second. And I don't know if it's because
>I deleted some files by mistake or because I scheduled chkdsk twice. This
>problem is only on drive C, not the other drives. I've spent hours googling
>this problem but could not find anything. Any help will be appreciated.
>

1. To find information about the problem that triggers the restarts:
Right-click on "My Computer" and select Manage.
Click on the + sign in front of the Event Viewer category to show the
sub-categories.
Browse through the System and Application sub-categories to locate
error records (most likely red flagged) with date and time stamps that
match your CHKDSK problems. Double click on an error record to see
the details of that error. Post the information back here if you
need help with it.

2. To put an end to the restarts:
Open Control Panel - System - Advanced and click on the Settings
button in the Startup and Recovery (bottom) section. In the Startup
and Recovery window click on the checkbox for "Automatically restart"
to clear it then click on Apply and OK as needed to exit.

Next time you run CHKDSK on drive C: you will probably receive a Blue
Screen Of Death STOP error message and your computer may lock up,
requiring a manual power off and restart. If that does happen then
the contents of the STOP message, including the STOP code, all 4 of
the parameters associated with it, and any file or module names
mentioned will be a direct clue as to the underlying cause of your
problems. Post that information back here.

3. To possibly fix the problem.
Open a Command Prompt window and enter the following command:

CHKDSK C: /F

This will require a shutdown and restart of your computer. If the
problem is being caused by some sort of anomoly with your hard drive
then this should find and hopefully fix it.

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."

Thanks for the useful info. I see a DCOM error message, it says "The service
cannot be started either because it is disabled or has no enabled devises"
attempting to start service SENS with arguments "" in order to run the
server..and it gives the registry location of SENS.
I unchecked Auto Restart and saw the blue screen. The Stop code is 71
(preceded and followed by lots of zeros) and it says
Session5_Initialization_Failed. Check to make sure any hardware or software
is properly installed.
This blue screen happens only when I do chkdsk c: /f and I have to boot the
Last Known Good Config to get to Windows.
I also tried reinstalling WinXP with my CD which came with the SP32 pack and
it did not copy many files from the i386 folder on the CD, mostly files with
..ex_ and .dl_ extensions. I'm able to manually copy these files but then I
don't get the .exe and .dll extensions (it ends with a dash). I think Setup
extracts these files? Anyway, Setup didn't copy many files and I had to skip
those to complete setup. Is this a hardware problem?

"Ron Martell" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> "RJ" <(E-Mail Removed)> wrote:
>
> >Whenever I schedule Error Checking with the option to fix errors for
drive
> >C: and restart the computer, it completes the chkdsk but then restarts
the
> >computer again after flashing a blue screen. Then it gives me a screen
where
> >I can start normally or boot the last known good configuration. If I boot
> >normally it does chkdsk again and then restarts again. But if I choose
last
> >known good, it launches XP. I don't know what the blue screen says
because
> >it flashes for only a fraction of a second. And I don't know if it's
because
> >I deleted some files by mistake or because I scheduled chkdsk twice. This
> >problem is only on drive C, not the other drives. I've spent hours
googling
> >this problem but could not find anything. Any help will be appreciated.
> >
>
> 1. To find information about the problem that triggers the restarts:
> Right-click on "My Computer" and select Manage.
> Click on the + sign in front of the Event Viewer category to show the
> sub-categories.
> Browse through the System and Application sub-categories to locate
> error records (most likely red flagged) with date and time stamps that
> match your CHKDSK problems. Double click on an error record to see
> the details of that error. Post the information back here if you
> need help with it.
>
> 2. To put an end to the restarts:
> Open Control Panel - System - Advanced and click on the Settings
> button in the Startup and Recovery (bottom) section. In the Startup
> and Recovery window click on the checkbox for "Automatically restart"
> to clear it then click on Apply and OK as needed to exit.
>
> Next time you run CHKDSK on drive C: you will probably receive a Blue
> Screen Of Death STOP error message and your computer may lock up,
> requiring a manual power off and restart. If that does happen then
> the contents of the STOP message, including the STOP code, all 4 of
> the parameters associated with it, and any file or module names
> mentioned will be a direct clue as to the underlying cause of your
> problems. Post that information back here.
>
> 3. To possibly fix the problem.
> Open a Command Prompt window and enter the following command:
>
> CHKDSK C: /F
>
> This will require a shutdown and restart of your computer. If the
> problem is being caused by some sort of anomoly with your hard drive
> then this should find and hopefully fix it.
>
> Good luck
>
> Ron Martell Duncan B.C. Canada
> --
> Microsoft MVP (1997 - 2006)
> On-Line Help Computer Service
> http://onlinehelp.bc.ca
>
> "Anyone who thinks that they are too small to make a difference
> has never been in bed with a mosquito."

Looks like Ron Martell went off the radar. Here's the latest in an effort to
revive this thread. Any MVP's or experts out there, feel free to add your
two cents:

I tried overinstalling XP (rather than a clean install) and kept getting
file copy errors. Ran memtest for 8 hours, no errors in memory or mb. Took
it to the shop and the guy said it's probably a software problem and it
usually happens when you overinstall. He said to reformat and do a fresh
install and if it still doesn't work, it's a hardware problem. Since I don't
want to do that right away, are there any ways to troubleshoot software
configuration problems?



"RJ" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Thanks for the useful info. I see a DCOM error message, it says "The
service
> cannot be started either because it is disabled or has no enabled devises"
> attempting to start service SENS with arguments "" in order to run the
> server..and it gives the registry location of SENS.
> I unchecked Auto Restart and saw the blue screen. The Stop code is 71
> (preceded and followed by lots of zeros) and it says
> Session5_Initialization_Failed. Check to make sure any hardware or
software
> is properly installed.
> This blue screen happens only when I do chkdsk c: /f and I have to boot
the
> Last Known Good Config to get to Windows.
> I also tried reinstalling WinXP with my CD which came with the SP32 pack
and
> it did not copy many files from the i386 folder on the CD, mostly files
with
> .ex_ and .dl_ extensions. I'm able to manually copy these files but then I
> don't get the .exe and .dll extensions (it ends with a dash). I think
Setup
> extracts these files? Anyway, Setup didn't copy many files and I had to
skip
> those to complete setup. Is this a hardware problem?
>
> "Ron Martell" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > "RJ" <(E-Mail Removed)> wrote:
> >
> > >Whenever I schedule Error Checking with the option to fix errors for
> drive
> > >C: and restart the computer, it completes the chkdsk but then restarts
> the
> > >computer again after flashing a blue screen. Then it gives me a screen
> where
> > >I can start normally or boot the last known good configuration. If I
boot
> > >normally it does chkdsk again and then restarts again. But if I choose
> last
> > >known good, it launches XP. I don't know what the blue screen says
> because
> > >it flashes for only a fraction of a second. And I don't know if it's
> because
> > >I deleted some files by mistake or because I scheduled chkdsk twice.
This
> > >problem is only on drive C, not the other drives. I've spent hours
> googling
> > >this problem but could not find anything. Any help will be appreciated.
> > >
> >
> > 1. To find information about the problem that triggers the restarts:
> > Right-click on "My Computer" and select Manage.
> > Click on the + sign in front of the Event Viewer category to show the
> > sub-categories.
> > Browse through the System and Application sub-categories to locate
> > error records (most likely red flagged) with date and time stamps that
> > match your CHKDSK problems. Double click on an error record to see
> > the details of that error. Post the information back here if you
> > need help with it.
> >
> > 2. To put an end to the restarts:
> > Open Control Panel - System - Advanced and click on the Settings
> > button in the Startup and Recovery (bottom) section. In the Startup
> > and Recovery window click on the checkbox for "Automatically restart"
> > to clear it then click on Apply and OK as needed to exit.
> >
> > Next time you run CHKDSK on drive C: you will probably receive a Blue
> > Screen Of Death STOP error message and your computer may lock up,
> > requiring a manual power off and restart. If that does happen then
> > the contents of the STOP message, including the STOP code, all 4 of
> > the parameters associated with it, and any file or module names
> > mentioned will be a direct clue as to the underlying cause of your
> > problems. Post that information back here.
> >
> > 3. To possibly fix the problem.
> > Open a Command Prompt window and enter the following command:
> >
> > CHKDSK C: /F
> >
> > This will require a shutdown and restart of your computer. If the
> > problem is being caused by some sort of anomoly with your hard drive
> > then this should find and hopefully fix it.
> >
> > Good luck
> >
> > Ron Martell Duncan B.C. Canada
> > --
> > Microsoft MVP (1997 - 2006)
> > On-Line Help Computer Service
> > http://onlinehelp.bc.ca
> >
> > "Anyone who thinks that they are too small to make a difference
> > has never been in bed with a mosquito."
>
>

"RJ" <(E-Mail Removed)> wrote:

>Looks like Ron Martell went off the radar. Here's the latest in an effort to
>revive this thread. Any MVP's or experts out there, feel free to add your
>two cents:
>
>I tried overinstalling XP (rather than a clean install) and kept getting
>file copy errors. Ran memtest for 8 hours, no errors in memory or mb. Took
>it to the shop and the guy said it's probably a software problem and it
>usually happens when you overinstall. He said to reformat and do a fresh
>install and if it still doesn't work, it's a hardware problem. Since I don't
>want to do that right away, are there any ways to troubleshoot software
>configuration problems?
>

Sorry for the delay in replying. I have been preoccupied with some
personal health issues and haven't had as much time as usual for
digging into issues like this.

I don't have a ready answer "off the top of my head" but will do some
checking and get back to you in a day or so, hopefully with
substantive.

Your "Session5_Initialization_Failed" error is really a rare beastie
and there is very little reference material available with regards to
it.

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."

"RJ" <(E-Mail Removed)> wrote:

>Looks like Ron Martell went off the radar. Here's the latest in an effort to
>revive this thread. Any MVP's or experts out there, feel free to add your
>two cents:
>
>I tried overinstalling XP (rather than a clean install) and kept getting
>file copy errors. Ran memtest for 8 hours, no errors in memory or mb. Took
>it to the shop and the guy said it's probably a software problem and it
>usually happens when you overinstall. He said to reformat and do a fresh
>install and if it still doesn't work, it's a hardware problem. Since I don't
>want to do that right away, are there any ways to troubleshoot software
>configuration problems?
>

I found some references on the web to your error.

One site has several reports where this error was fixed by booting to
the XP Recovery Console or with a bootable CD (Bart's PE Builder) and
replacing the file ntdll.dll in the system32 folder with a new copy.

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."

thanks Ron. Hope your health situation is under control.

"Ron Martell" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> "RJ" <(E-Mail Removed)> wrote:
>
> >Looks like Ron Martell went off the radar. Here's the latest in an effort
to
> >revive this thread. Any MVP's or experts out there, feel free to add your
> >two cents:
> >
> >I tried overinstalling XP (rather than a clean install) and kept getting
> >file copy errors. Ran memtest for 8 hours, no errors in memory or mb.
Took
> >it to the shop and the guy said it's probably a software problem and it
> >usually happens when you overinstall. He said to reformat and do a fresh
> >install and if it still doesn't work, it's a hardware problem. Since I
don't
> >want to do that right away, are there any ways to troubleshoot software
> >configuration problems?
> >
>
> I found some references on the web to your error.
>
> One site has several reports where this error was fixed by booting to
> the XP Recovery Console or with a bootable CD (Bart's PE Builder) and
> replacing the file ntdll.dll in the system32 folder with a new copy.
>
> Ron Martell Duncan B.C. Canada
> --
> Microsoft MVP (1997 - 2006)
> On-Line Help Computer Service
> http://onlinehelp.bc.ca
>
> "Anyone who thinks that they are too small to make a difference
> has never been in bed with a mosquito."