XP Serious Error After chkdsk /f

Both of my XP systems are updated regularly, and when they were as SP2
machines, whenever I did a chkdsk /f command to clean up the disk, it always
knarls everything and and in addition to not cleaning up the errors on the
disk, the system reboots and recovers from a "Serious Error". The system
takes me to a page where it says I have a rogue device driver, which I do
not. All of my drivers are signed on both systems. Hardware failure is not
the culprit either, as both systems have newer drives in them. After
installing SP3, the situation is the same.

Why is this occurring?

thecreator
Sun May 11 06:50:16 PDT 2008

Hi JBL,

I don't know why it is occurring, but I have never experienced it. This
is what I always do and works 100 percent of the time for me.

First, I manually use Explore and go into My \Temp Folders and delete
all files and sub-folders of those \Temp Folders. Do not worry about which
files or sub-folders not to remove, because any file would be recreated, if
needed.

Then, I run Disk Cleanup and check everything except for the Catalog
Files for the Indexer. Now I did OK.

Now, since you are having so many problems with Chkdsk, I would, first
download and run a Registry Cleaner, like TuneUp Utilities 2008 from
http://www.tune-up.com/download/ .

Once installed and you then run the Register Cleaner, I would then
Schedule a Chkdsk /R, by right-clicking the operating system's partition in
My Computer. Click Properties, Click Tools and click Check Now and check
both options and click OK. And answer yes to Schedule. Reboot to run.

After doing all that, I would then defrag the Hard Drive partition.


--
thecreator

"JBL" <jbl2002@alltel.net> wrote in message
news:%23X2zjn2sIHA.4544@TK2MSFTNGP04.phx.gbl...
> Both of my XP systems are updated regularly, and when they were as SP2
> machines, whenever I did a chkdsk /f command to clean up the disk, it
> always knarls everything and and in addition to not cleaning up the errors
> on the disk, the system reboots and recovers from a "Serious Error". The
> system takes me to a page where it says I have a rogue device driver,
> which I do not. All of my drivers are signed on both systems. Hardware
> failure is not the culprit either, as both systems have newer drives in
> them. After installing SP3, the situation is the same.
>
> Why is this occurring?

DL
Sun May 11 07:09:03 PDT 2008

Because they are newish or even new drives doesnt mean they dont have a
problem.
If you keep finding errs when using chkdsk then you have a hw problem.
Use disk checking utility available on the hd manu site.
Run a memory test www.memtest.org
A problem psu can also cause disk problems.
Installing sp3 or anything else is not going to cure a hw problem

"JBL" <jbl2002@alltel.net> wrote in message
news:%23X2zjn2sIHA.4544@TK2MSFTNGP04.phx.gbl...
> Both of my XP systems are updated regularly, and when they were as SP2
> machines, whenever I did a chkdsk /f command to clean up the disk, it
> always knarls everything and and in addition to not cleaning up the errors
> on the disk, the system reboots and recovers from a "Serious Error". The
> system takes me to a page where it says I have a rogue device driver,
> which I do not. All of my drivers are signed on both systems. Hardware
> failure is not the culprit either, as both systems have newer drives in
> them. After installing SP3, the situation is the same.
>
> Why is this occurring?

Gerry
Sun May 11 07:51:42 PDT 2008

Using any Registry Cleaner can be a bad move and not to be recommended.

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
thecreator wrote:
> Hi JBL,
>
> I don't know why it is occurring, but I have never experienced it.
> This is what I always do and works 100 percent of the time for me.
>
> First, I manually use Explore and go into My \Temp Folders and
> delete all files and sub-folders of those \Temp Folders. Do not worry
> about which files or sub-folders not to remove, because any file
> would be recreated, if needed.
>
> Then, I run Disk Cleanup and check everything except for the
> Catalog Files for the Indexer. Now I did OK.
>
> Now, since you are having so many problems with Chkdsk, I would,
> first download and run a Registry Cleaner, like TuneUp Utilities 2008
> from http://www.tune-up.com/download/ .
>
> Once installed and you then run the Register Cleaner, I would then
> Schedule a Chkdsk /R, by right-clicking the operating system's
> partition in My Computer. Click Properties, Click Tools and click
> Check Now and check both options and click OK. And answer yes to
> Schedule. Reboot to run.
> After doing all that, I would then defrag the Hard Drive partition.
>
>
>
> "JBL" <jbl2002@alltel.net> wrote in message
> news:%23X2zjn2sIHA.4544@TK2MSFTNGP04.phx.gbl...
>> Both of my XP systems are updated regularly, and when they were as
>> SP2 machines, whenever I did a chkdsk /f command to clean up the
>> disk, it always knarls everything and and in addition to not
>> cleaning up the errors on the disk, the system reboots and recovers
>> from a "Serious Error". The system takes me to a page where it says
>> I have a rogue device driver, which I do not. All of my drivers are
>> signed on both systems. Hardware failure is not the culprit either,
>> as both systems have newer drives in them. After installing SP3,
>> the situation is the same. Why is this occurring?

Gerry
Sun May 11 08:00:27 PDT 2008

JBL

You should not have installed SP3 if you had an existing problem.

Before running chkdsk it is advisable to run Disk CleanUp first.

In order to offer to advise we need to see a complete copy of the Error
Report. Look in the System Log in Event Viewer and post a copy.

You can access Event Viewer by selecting Start, Control Panel,
Administrative Tools, and Event Viewer. When researching the meaning
of the error, information regarding Event ID, Source and Description
are important.

HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/kb/308427/en-us

A tip for posting copies of Error Reports! Run Event Viewer and double
click on the error you want to copy. In the window, which appears is a
button resembling two pages. Click the button and close Event
Viewer.Now start your message (email) and do a paste into the body of
the message. Make sure this is the first paste after exiting from
Event Viewer.

You might find HD Tune gives you a clearer picture of what is going on.
HD Tune only gives information and does not fix any problems.

Download and run it and see what it turns up.
http://www.hdtune.com/

Select the Info tabs and place the cursor on the drive under Drive
letter and then double click the two page icon ( copy to Clipboard )
and copy into a further message.

Select the Health tab and then double click the two page icon ( copy to
Clipboard ) and copy into a further message. Make sure you do a full
surface scan with HD Tune.


--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



JBL wrote:
> Both of my XP systems are updated regularly, and when they were as SP2
> machines, whenever I did a chkdsk /f command to clean up the disk, it
> always knarls everything and and in addition to not cleaning up the
> errors on the disk, the system reboots and recovers from a "Serious
> Error". The system takes me to a page where it says I have a rogue
> device driver, which I do not. All of my drivers are signed on both
> systems. Hardware failure is not the culprit either, as both systems
> have newer drives in them. After installing SP3, the situation is
> the same.
> Why is this occurring?

Ken
Sun May 11 08:45:13 PDT 2008

On Sun, 11 May 2008 15:51:42 +0100, "Gerry" <gerry@nospam.com> wrote:

> Using any Registry Cleaner can be a bad move and not to be recommended.


If JBL wants another opinion, I completely agree with Gerry. Stay away
from registry cleaners. They are far more likely to cause a problem
than to cure one.


> ~~~~~~~~~~~~~~~~~~~
> thecreator wrote:
> > Hi JBL,
> >
> > I don't know why it is occurring, but I have never experienced it.
> > This is what I always do and works 100 percent of the time for me.
> >
> > First, I manually use Explore and go into My \Temp Folders and
> > delete all files and sub-folders of those \Temp Folders. Do not worry
> > about which files or sub-folders not to remove, because any file
> > would be recreated, if needed.
> >
> > Then, I run Disk Cleanup and check everything except for the
> > Catalog Files for the Indexer. Now I did OK.
> >
> > Now, since you are having so many problems with Chkdsk, I would,
> > first download and run a Registry Cleaner, like TuneUp Utilities 2008
> > from http://www.tune-up.com/download/ .
> >
> > Once installed and you then run the Register Cleaner, I would then
> > Schedule a Chkdsk /R, by right-clicking the operating system's
> > partition in My Computer. Click Properties, Click Tools and click
> > Check Now and check both options and click OK. And answer yes to
> > Schedule. Reboot to run.
> > After doing all that, I would then defrag the Hard Drive partition.
> >
> >
> >
> > "JBL" <jbl2002@alltel.net> wrote in message
> > news:%23X2zjn2sIHA.4544@TK2MSFTNGP04.phx.gbl...
> >> Both of my XP systems are updated regularly, and when they were as
> >> SP2 machines, whenever I did a chkdsk /f command to clean up the
> >> disk, it always knarls everything and and in addition to not
> >> cleaning up the errors on the disk, the system reboots and recovers
> >> from a "Serious Error". The system takes me to a page where it says
> >> I have a rogue device driver, which I do not. All of my drivers are
> >> signed on both systems. Hardware failure is not the culprit either,
> >> as both systems have newer drives in them. After installing SP3,
> >> the situation is the same. Why is this occurring?
>

--
Ken Blake, Microsoft MVP - Windows Desktop Experience
Please Reply to the Newsgroup

Jeff
Sun May 11 12:21:05 PDT 2008

Thanks for everyone's feedback. In fact I can't remember when I have ever
had a totally clean disk as reported by chkdsk in XP...Ever.

I realize that SP3 would not solve any hardware issues, but this issue has
been around for so long I guess I wasn't concerned - It's highly unlikely
that both of my machines have bad hard drives, no matter how old they are.
With that said, I will post a few of the events that look suspect to me and
I would like to thank everyone in advance for any comments they might add:

1) Driver Microsoft XPS Document Writer required for printer Microsoft XPS
Document Writer is unknown. Contact the administrator to install the driver
before you log in again.
2) Error code c000021a, parameter1 e1317a00, parameter2 c0000006, parameter3
7c96149b, parameter4 002efb94.

3) The System Restore filter encountered the unexpected error '0xC0000369'
while processing the file 'ntuser.ini' on the volume 'HarddiskVolume1'. It
has stopped monitoring the volume.


"Gerry" <gerry@nospam.com> wrote in message
news:u47VKf3sIHA.3680@TK2MSFTNGP05.phx.gbl...
> JBL
>
> You should not have installed SP3 if you had an existing problem.
>
> Before running chkdsk it is advisable to run Disk CleanUp first.
>
> In order to offer to advise we need to see a complete copy of the Error
> Report. Look in the System Log in Event Viewer and post a copy.
>
> You can access Event Viewer by selecting Start, Control Panel,
> Administrative Tools, and Event Viewer. When researching the meaning
> of the error, information regarding Event ID, Source and Description
> are important.
>
> HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
> http://support.microsoft.com/kb/308427/en-us
>
> A tip for posting copies of Error Reports! Run Event Viewer and double
> click on the error you want to copy. In the window, which appears is a
> button resembling two pages. Click the button and close Event
> Viewer.Now start your message (email) and do a paste into the body of
> the message. Make sure this is the first paste after exiting from
> Event Viewer.
>
> You might find HD Tune gives you a clearer picture of what is going on.
> HD Tune only gives information and does not fix any problems.
>
> Download and run it and see what it turns up.
> http://www.hdtune.com/
>
> Select the Info tabs and place the cursor on the drive under Drive
> letter and then double click the two page icon ( copy to Clipboard )
> and copy into a further message.
>
> Select the Health tab and then double click the two page icon ( copy to
> Clipboard ) and copy into a further message. Make sure you do a full
> surface scan with HD Tune.
>
>
> --
>
>
>
> Hope this helps.
>
> Gerry
> ~~~~
> FCA
> Stourport, England
> Enquire, plan and execute
> ~~~~~~~~~~~~~~~~~~~
>
>
>
> JBL wrote:
>> Both of my XP systems are updated regularly, and when they were as SP2
>> machines, whenever I did a chkdsk /f command to clean up the disk, it
>> always knarls everything and and in addition to not cleaning up the
>> errors on the disk, the system reboots and recovers from a "Serious
>> Error". The system takes me to a page where it says I have a rogue
>> device driver, which I do not. All of my drivers are signed on both
>> systems. Hardware failure is not the culprit either, as both systems
>> have newer drives in them. After installing SP3, the situation is
>> the same.
>> Why is this occurring?
>
>

Gerry
Mon May 12 11:01:49 PDT 2008

Jeff

These Error Reports from Event Viewer are incomplete! Have they occurred
more than once? Have they occurred in the last 48 hours?

Microsoft XPS Document Writer -Is this the Error?

Event Type: Error
Event Source: TermServDevices
Event Category: None
Event ID: 1111
Date: 4/6/2007
Time: 8:28:03 AM
User: N/A
Computer: SERVER1
Description:
Driver Microsoft XPS Document Writer required for printer
Microsoft XPS Document Writer is unknown. Contact the
administrator to install the driver before you log in again

What exactly is your operating system?

Error code c000021a

Background information on Stop Error code:
http://msdn2.microsoft.com/en-us/library/ms797159.aspx

This occurs when Windows switches into kernel mode and a user-mode
subsystem, such as Winlogon or the Client Server Runtime Subsystem
(CSRSS), is compromised. Security can no longer be guaranteed. Because
Win XP can't run without Winlogon or CSRSS, this is one of the few
situations where the failure of a user-mode service can cause the system
to stop responding. This Stop message also can occur as a result of
malware infestation or when the computer is restarted after a system
administrator has modified permissions so that the SYSTEM account no
longer has adequate permissions to access system files and folders.
http://aumha.org/a/stop.htm

We need to establish whether this any link between the first two errors.
Seeing the complete error reports would help.

What drives is System Restore monitoring? What is HarddiskVolume1? Is it
a removable drive?


--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
Jeff Lloyd wrote:
> Thanks for everyone's feedback. In fact I can't remember when I have
> ever had a totally clean disk as reported by chkdsk in XP...Ever.
>
> I realize that SP3 would not solve any hardware issues, but this
> issue has been around for so long I guess I wasn't concerned - It's
> highly unlikely that both of my machines have bad hard drives, no
> matter how old they are. With that said, I will post a few of the
> events that look suspect to me and I would like to thank everyone in
> advance for any comments they might add:
> 1) Driver Microsoft XPS Document Writer required for printer
> Microsoft XPS Document Writer is unknown. Contact the administrator
> to install the driver before you log in again.
> 2) Error code c000021a, parameter1 e1317a00, parameter2 c0000006,
> parameter3 7c96149b, parameter4 002efb94.
>
> 3) The System Restore filter encountered the unexpected error
> '0xC0000369' while processing the file 'ntuser.ini' on the volume
> 'HarddiskVolume1'. It has stopped monitoring the volume.
>
>
> "Gerry" <gerry@nospam.com> wrote in message
> news:u47VKf3sIHA.3680@TK2MSFTNGP05.phx.gbl...
>> JBL
>>
>> You should not have installed SP3 if you had an existing problem.
>>
>> Before running chkdsk it is advisable to run Disk CleanUp first.
>>
>> In order to offer to advise we need to see a complete copy of the
>> Error Report. Look in the System Log in Event Viewer and post a
>> copy. You can access Event Viewer by selecting Start, Control Panel,
>> Administrative Tools, and Event Viewer. When researching the meaning
>> of the error, information regarding Event ID, Source and Description
>> are important.
>>
>> HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
>> http://support.microsoft.com/kb/308427/en-us
>>
>> A tip for posting copies of Error Reports! Run Event Viewer and
>> double click on the error you want to copy. In the window, which
>> appears is a button resembling two pages. Click the button and close
>> Event Viewer.Now start your message (email) and do a paste into the
>> body of the message. Make sure this is the first paste after exiting
>> from Event Viewer.
>>
>> You might find HD Tune gives you a clearer picture of what is going
>> on. HD Tune only gives information and does not fix any problems.
>>
>> Download and run it and see what it turns up.
>> http://www.hdtune.com/
>>
>> Select the Info tabs and place the cursor on the drive under Drive
>> letter and then double click the two page icon ( copy to Clipboard )
>> and copy into a further message.
>>
>> Select the Health tab and then double click the two page icon (
>> copy to Clipboard ) and copy into a further message. Make sure you
>> do a full surface scan with HD Tune.
>>
>>
>> --
>>
>>
>>
>> Hope this helps.
>>
>> Gerry
>> ~~~~
>> FCA
>> Stourport, England
>> Enquire, plan and execute
>> ~~~~~~~~~~~~~~~~~~~
>>
>>
>>
>> JBL wrote:
>>> Both of my XP systems are updated regularly, and when they were as
>>> SP2 machines, whenever I did a chkdsk /f command to clean up the
>>> disk, it always knarls everything and and in addition to not
>>> cleaning up the errors on the disk, the system reboots and recovers
>>> from a "Serious Error". The system takes me to a page where it
>>> says I have a rogue device driver, which I do not. All of my
>>> drivers are signed on both systems. Hardware failure is not the
>>> culprit either, as both systems have newer drives in them. After
>>> installing SP3, the situation is the same.
>>> Why is this occurring?