State Manager problem

My laptop hard disk was running constantly, even when no
application was in use (system monitor showed thousands of
files/sec being read and written). Unchecking statemgr in
the msconfig/startup solves that problem, and operation
appears normal, but I wonder if I am creating another
problem down the road. What does the state manager do,
can I leave it unchecked, or is there a better approach to
solving my original hyperactivity problem?

Noel
Sat Oct 18 17:19:42 CDT 2003

Unchecking the *Statemgr entry in MSCONFIG disables both System File
Protection, and System Restore - your system is now wide-open to a number of
problems.
I would suggest re-checking the *Statemgr entry, then following the advice
below.

Frequently this type of problem (hanging/multiple instances of, Winmgmt.exe)
is caused by a glitch in the PCHealth Data Collection service, and the
easiest workaround is to turn that service off (I know of no good use for
it, anyhow!).

To do this, Disable the entry in Scheduled Tasks, and UNcheck the PCHealth
entry in
MSCONFIG. -

HTH
--
Noel Paton (MS-MVP 2002-2004, Win9x)

Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm
Please read http://dts-l.org/goodpost.htm on how to post messages to NG's

"Jason" <jasonmarks@earthlink.net> wrote in message
news:017201c395c3$5506b490$a501280a@phx.gbl...
> My laptop hard disk was running constantly, even when no
> application was in use (system monitor showed thousands of
> files/sec being read and written). Unchecking statemgr in
> the msconfig/startup solves that problem, and operation
> appears normal, but I wonder if I am creating another
> problem down the road. What does the state manager do,
> can I leave it unchecked, or is there a better approach to
> solving my original hyperactivity problem?

Jason
Sat Oct 18 18:24:53 CDT 2003

Thanks, Noel, I'll try that.
>-----Original Message-----
>Unchecking the *Statemgr entry in MSCONFIG disables both
System File
>Protection, and System Restore - your system is now wide-
open to a number of
>problems.
>I would suggest re-checking the *Statemgr entry, then
following the advice
>below.
>
>Frequently this type of problem (hanging/multiple
instances of, Winmgmt.exe)
>is caused by a glitch in the PCHealth Data Collection
service, and the
>easiest workaround is to turn that service off (I know of
no good use for
>it, anyhow!).
>
>To do this, Disable the entry in Scheduled Tasks, and
UNcheck the PCHealth
>entry in
>MSCONFIG. -
>
>HTH
>--
>Noel Paton (MS-MVP 2002-2004, Win9x)
>
>Nil Carborundum Illegitemi
>http://www.btinternet.com/~winnoel/millsrpch.htm
>Please read http://dts-l.org/goodpost.htm on how to post
messages to NG's
>
>"Jason" <jasonmarks@earthlink.net> wrote in message
>news:017201c395c3$5506b490$a501280a@phx.gbl...
>> My laptop hard disk was running constantly, even when no
>> application was in use (system monitor showed thousands
of
>> files/sec being read and written). Unchecking statemgr
in
>> the msconfig/startup solves that problem, and operation
>> appears normal, but I wonder if I am creating another
>> problem down the road. What does the state manager do,
>> can I leave it unchecked, or is there a better approach
to
>> solving my original hyperactivity problem?
>
>
>.
>

Mike
Sat Oct 18 19:12:51 CDT 2003

Noel,
The state manager doesn't involve winmgmt.exe. What might be happening is
that Jason has an application running that is continuously modifying files
with an extension that is included in the list monitored by the state manager
and are thus being continuously archived to the _RESTORE\TEMP folder. You may
recall I mentioned to you last week about one such program.

Jason:
With the *StateMgr entry checked and the state manager (stmgr.exe) running
have a look at the C:\_RESTORE\TEMP folder and see if files are continuously
being archived there. To do this using Windows Explorer you have to first
enable the viewing of hidden and protected system files and folders. Tools |
Folder Options | View and check "Show hidden files and folders" and ALSO
UNcheck "Hide protected operating system files".

If this is the case what non Microsoft programs applications do you have
running at the time? Check whether, for example, any of them is continuously
modifying files such as perhaps those with a cfg extension.
--
Mike Maltby MS-MVP
mcmaltby@hotmail.com


Noel Paton <NoelDPspamless@btopenworld.com> wrote:

> Unchecking the *Statemgr entry in MSCONFIG disables both System File
> Protection, and System Restore - your system is now wide-open to a number
> of problems.
> I would suggest re-checking the *Statemgr entry, then following the advice
> below.
>
> Frequently this type of problem (hanging/multiple instances of,
> Winmgmt.exe) is caused by a glitch in the PCHealth Data Collection
> service, and the easiest workaround is to turn that service off (I know
> of no good use for it, anyhow!).
>
> To do this, Disable the entry in Scheduled Tasks, and UNcheck the PCHealth
> entry in
> MSCONFIG. -

Jason
Sat Oct 18 21:34:26 CDT 2003

Mike, I made the check you suggested. No files were being
archived to RESTORE/TEMP. However, two files were being
continuously modified in RESTORE/LOG. BTW, I don't have
any nonMS apps running; in fact, the problem happens even
when no apps at all are open.

Jason
>-----Original Message-----
>Noel,
>The state manager doesn't involve winmgmt.exe. What
might be happening is
>that Jason has an application running that is
continuously modifying files
>with an extension that is included in the list monitored
by the state manager
>and are thus being continuously archived to the
_RESTORE\TEMP folder. You may
>recall I mentioned to you last week about one such
program.
>
>Jason:
>With the *StateMgr entry checked and the state manager
(stmgr.exe) running
>have a look at the C:\_RESTORE\TEMP folder and see if
files are continuously
>being archived there. To do this using Windows Explorer
you have to first
>enable the viewing of hidden and protected system files
and folders. Tools |
>Folder Options | View and check "Show hidden files and
folders" and ALSO
>UNcheck "Hide protected operating system files".
>
>If this is the case what non Microsoft programs
applications do you have
>running at the time? Check whether, for example, any of
them is continuously
>modifying files such as perhaps those with a cfg
extension.
>--
>Mike Maltby MS-MVP
>mcmaltby@hotmail.com
>
>
>Noel Paton <NoelDPspamless@btopenworld.com> wrote:
>
>> Unchecking the *Statemgr entry in MSCONFIG disables
both System File
>> Protection, and System Restore - your system is now
wide-open to a number
>> of problems.
>> I would suggest re-checking the *Statemgr entry, then
following the advice
>> below.
>>
>> Frequently this type of problem (hanging/multiple
instances of,
>> Winmgmt.exe) is caused by a glitch in the PCHealth Data
Collection
>> service, and the easiest workaround is to turn that
service off (I know
>> of no good use for it, anyhow!).
>>
>> To do this, Disable the entry in Scheduled Tasks, and
UNcheck the PCHealth
>> entry in
>> MSCONFIG. -
>
>
>.
>

Mike
Sat Oct 18 21:52:13 CDT 2003

Jason,

How many files are there in the _RESTORE\TEMP folder? It could simply be that
there has been a build of files and the state manager is trying to catch up.
What happens is that the state manager has to check each archived file (*.CPY
files) for whether it will be needed for a restore operation and if so "cab"
them into FS*.cab files in the _RESTORE\ARCHIVE folder and deletes those not
required. This should normally happen at fairly regular intervals and take
just a second or so of cpu time BUT if the system has been running heavily for
a while there can be a build up of files and no cabbing taken place. On a few
occasions I have seen such a build up of files that it took the state manager
about an hour of cpu time to clear the _RESTORE\TEMP folder and cab or discard
the files. Compare that to in normal use the state manager using < 2 minutes
cpu time per 24 hours. [As measured on a PII 450]. If this is happening once
the TEMP folder is cleared the cpu usage and disk access will drop to
virtually nothing.
--
Mike Maltby MS-MVP
mcmaltby@hotmail.com


Jason <Jason@discussions.microsoft.com> wrote:

> Mike, I made the check you suggested. No files were being
> archived to RESTORE/TEMP. However, two files were being
> continuously modified in RESTORE/LOG. BTW, I don't have
> any nonMS apps running; in fact, the problem happens even
> when no apps at all are open.

Jason
Sat Oct 18 22:14:34 CDT 2003

There are 42 files (1.12MB) in the _RESTORE/TEMP folder.
What's odd to me in light of what you say is that some
files are very old, back to 4/2000, before I bought the
computer. Shouldn't the state manager have deleted or
cabbed these? Would it make sense for me to try to delete
them manually?

Jason
>-----Original Message-----
>Jason,
>
>How many files are there in the _RESTORE\TEMP folder? It
could simply be that
>there has been a build of files and the state manager is
trying to catch up.
>What happens is that the state manager has to check each
archived file (*.CPY
>files) for whether it will be needed for a restore
operation and if so "cab"
>them into FS*.cab files in the _RESTORE\ARCHIVE folder
and deletes those not
>required. This should normally happen at fairly regular
intervals and take
>just a second or so of cpu time BUT if the system has
been running heavily for
>a while there can be a build up of files and no cabbing
taken place. On a few
>occasions I have seen such a build up of files that it
took the state manager
>about an hour of cpu time to clear the _RESTORE\TEMP
folder and cab or discard
>the files. Compare that to in normal use the state
manager using < 2 minutes
>cpu time per 24 hours. [As measured on a PII 450]. If
this is happening once
>the TEMP folder is cleared the cpu usage and disk access
will drop to
>virtually nothing.
>--
>Mike Maltby MS-MVP
>mcmaltby@hotmail.com
>
>
>Jason <Jason@discussions.microsoft.com> wrote:
>
>> Mike, I made the check you suggested. No files were
being
>> archived to RESTORE/TEMP. However, two files were being
>> continuously modified in RESTORE/LOG. BTW, I don't have
>> any nonMS apps running; in fact, the problem happens
even
>> when no apps at all are open.
>
>
>.
>

Noel
Sun Oct 19 02:30:12 CDT 2003

Thanks, Mike - I must have been asleep at the keyboard, or something.

--
Noel Paton (MS-MVP 2002-2004, Win9x)

Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm
Please read http://dts-l.org/goodpost.htm on how to post messages to NG's

"Mike M" <No_Spam@Corned_Beef.Only> wrote in message
news:%239W99WdlDHA.2364@TK2MSFTNGP11.phx.gbl...
> Noel,
> The state manager doesn't involve winmgmt.exe. What might be happening
is
> that Jason has an application running that is continuously modifying files
> with an extension that is included in the list monitored by the state
manager
> and are thus being continuously archived to the _RESTORE\TEMP folder. You
may
> recall I mentioned to you last week about one such program.
>
> Jason:
> With the *StateMgr entry checked and the state manager (stmgr.exe) running
> have a look at the C:\_RESTORE\TEMP folder and see if files are
continuously
> being archived there. To do this using Windows Explorer you have to first
> enable the viewing of hidden and protected system files and folders.
Tools |
> Folder Options | View and check "Show hidden files and folders" and ALSO
> UNcheck "Hide protected operating system files".
>
> If this is the case what non Microsoft programs applications do you have
> running at the time? Check whether, for example, any of them is
continuously
> modifying files such as perhaps those with a cfg extension.
> --
> Mike Maltby MS-MVP
> mcmaltby@hotmail.com
>
>
> Noel Paton <NoelDPspamless@btopenworld.com> wrote:
>
> > Unchecking the *Statemgr entry in MSCONFIG disables both System File
> > Protection, and System Restore - your system is now wide-open to a
number
> > of problems.
> > I would suggest re-checking the *Statemgr entry, then following the
advice
> > below.
> >
> > Frequently this type of problem (hanging/multiple instances of,
> > Winmgmt.exe) is caused by a glitch in the PCHealth Data Collection
> > service, and the easiest workaround is to turn that service off (I know
> > of no good use for it, anyhow!).
> >
> > To do this, Disable the entry in Scheduled Tasks, and UNcheck the
PCHealth
> > entry in
> > MSCONFIG. -
>
>

Mike
Sun Oct 19 07:01:27 CDT 2003

Jason,

The 2000 date more than likely refers to the original modified date of the
file not the date it was placed in the _RESTOER\TEMP folder. You will see
that the original Win Me system files are all dated 8 June 2000. Don't try
and remove any files from the _RETORE folder or its sub-folders manually.
Instead flush the folder by cycling system restore of and then back on again.

With just 42 files in that folder and therefore as to why the state manager
continually is modifying the log files when the system is otherwise idle - I
just don't have a clue. Perhaps resetting system restore which clears the
folder and rebuilds the state manger's control files might solve the problem.
--
Mike Maltby MS-MVP
mcmaltby@hotmail.com


Jason Marks <Jason@discussions.microsoft.com> wrote:

> There are 42 files (1.12MB) in the _RESTORE/TEMP folder.
> What's odd to me in light of what you say is that some
> files are very old, back to 4/2000, before I bought the
> computer. Shouldn't the state manager have deleted or
> cabbed these? Would it make sense for me to try to delete
> them manually?

Joan
Sun Oct 19 13:38:38 CDT 2003

ROFL
At least you can't blame me for that one <g>
Joan

"Noel Paton" <NoelDPspamless@btopenworld.com> wrote in message
news:ON7oSLhlDHA.3316@tk2msftngp13.phx.gbl...
> Thanks, Mike - I must have been asleep at the keyboard, or something.
>
> --

Mike
Sun Oct 19 14:01:18 CDT 2003

Hi Joan,

Good hols?
--
Mike


Joan Archer <archer_joan@NOSPAM.com> wrote:

> ROFL
> At least you can't blame me for that one <g>

anonymous
Sun Oct 19 14:24:13 CDT 2003

Mike, per your last suggestion I disabled and then
reenabled system restore. Seems to have worked -- the old
temp files are all cleared out, only a couple there and in
logs from this morning, and state manager is not running
compulsively. I'll monitor to see if the temp files build
up again, but for now at least that seems to have solved
the problem. Thanks for all your help!

Jason

>-----Original Message-----
>Jason,
>
>The 2000 date more than likely refers to the original
modified date of the
>file not the date it was placed in the _RESTOER\TEMP
folder. You will see
>that the original Win Me system files are all dated 8
June 2000. Don't try
>and remove any files from the _RETORE folder or its sub-
folders manually.
>Instead flush the folder by cycling system restore of and
then back on again.
>
>With just 42 files in that folder and therefore as to why
the state manager
>continually is modifying the log files when the system is
otherwise idle - I
>just don't have a clue. Perhaps resetting system restore
which clears the
>folder and rebuilds the state manger's control files
might solve the problem.
>--
>Mike Maltby MS-MVP
>mcmaltby@hotmail.com
>
>
>Jason Marks <Jason@discussions.microsoft.com> wrote:
>
>> There are 42 files (1.12MB) in the _RESTORE/TEMP folder.
>> What's odd to me in light of what you say is that some
>> files are very old, back to 4/2000, before I bought the
>> computer. Shouldn't the state manager have deleted or
>> cabbed these? Would it make sense for me to try to
delete
>> them manually?
>
>
>.
>

Mike
Sun Oct 19 14:51:29 CDT 2003

Jason,

Ah well, I guess we'll never know the real cause of the problem but at least
it appears that having reset system restore and thus rebuilt the control files
has solved the problem. Let's both hope it stays that way.

Cheers and thanks for the feedback,
--
Mike


anonymous@discussions.microsoft.com <anonymous@discussions.microsoft.com>
wrote:

> Mike, per your last suggestion I disabled and then
> reenabled system restore. Seems to have worked -- the old
> temp files are all cleared out, only a couple there and in
> logs from this morning, and state manager is not running
> compulsively. I'll monitor to see if the temp files build
> up again, but for now at least that seems to have solved
> the problem. Thanks for all your help!

Noel
Sun Oct 19 15:42:26 CDT 2003

I can try - you woke me up!<g>

--
Noel Paton (MS-MVP 2002-2004, Win9x)

Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm
Please read http://dts-l.org/goodpost.htm on how to post messages to NG's

"Joan Archer" <archer_joan@NOSPAM.com> wrote in message
news:uPgy6AnlDHA.3700@TK2MSFTNGP11.phx.gbl...
> ROFL
> At least you can't blame me for that one <g>
> Joan
>
> "Noel Paton" <NoelDPspamless@btopenworld.com> wrote in message
> news:ON7oSLhlDHA.3316@tk2msftngp13.phx.gbl...
> > Thanks, Mike - I must have been asleep at the keyboard, or something.
> >
> > --
>
>

Joan
Mon Oct 20 05:49:27 CDT 2003

Yes thanks apart from the journey back on Saturday which was horrendous <g>
but the journey on Sunday back home was a joy clear roads all the way
through Wales.
Just trying to catch up now with emails and NG messages <g>
Joan

"Mike M" <No_Spam@Corned_Beef.Only> wrote in message
news:OYx7iNnlDHA.2772@TK2MSFTNGP10.phx.gbl...
> Hi Joan,
>
> Good hols?
> --
> Mike
>
>

Joan
Mon Oct 20 05:51:06 CDT 2003

*lol* Sorry, when I get the pictures sorted out and on to my PC I'll send
you the one from that Friday night at the hotel.
Joan

"Noel Paton" <NoelDPspamless@btopenworld.com> wrote in message
news:%23hSK$FolDHA.2068@TK2MSFTNGP09.phx.gbl...
> I can try - you woke me up!<g>
>
> --
> Noel Paton (MS-MVP 2002-2004, Win9x)
>

Jack
Wed Oct 22 12:19:36 CDT 2003

Very nice fix, Mike. You really are our SR / SFP expert.
--
Jack E. Martinelli 2002-04 MVP for Win9X / DTS
Help us help you: http://www.dts-L.org/goodpost.htm
Your cooperation is appreciated.
____
"Mike M" <No_Spam@Corned_Beef.Only> wrote in message
news:%23dyXlpnlDHA.3504@TK2MSFTNGP11.phx.gbl...
> Jason,
>
> Ah well, I guess we'll never know the real cause of the problem but at
least
> it appears that having reset system restore and thus rebuilt the
control files
> has solved the problem. Let's both hope it stays that way.
>
> Cheers and thanks for the feedback,
> --
> Mike
>
>
> anonymous@discussions.microsoft.com
<anonymous@discussions.microsoft.com>
> wrote:
>
> > Mike, per your last suggestion I disabled and then
> > reenabled system restore. Seems to have worked -- the old
> > temp files are all cleared out, only a couple there and in
> > logs from this morning, and state manager is not running
> > compulsively. I'll monitor to see if the temp files build
> > up again, but for now at least that seems to have solved
> > the problem. Thanks for all your help!
>
>

Mike
Wed Oct 22 12:32:27 CDT 2003

Thanks Jack, but only sometimes and when it works. :-)
--
Mike M


Jack E Martinelli <jemartin_ELIMINATE_@gis.net> wrote:

> Very nice fix, Mike. You really are our SR / SFP expert.

Noel
Wed Oct 22 14:59:47 CDT 2003

(which is 99% of the time!)

--
Noel Paton (MS-MVP 2002-2004, Win9x)

Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm
Please read http://dts-l.org/goodpost.htm on how to post messages to NG's

"Mike M" <No_Spam@Corned_Beef.Only> wrote in message
news:Omfl0IMmDHA.708@TK2MSFTNGP10.phx.gbl...
> Thanks Jack, but only sometimes and when it works. :-)
> --
> Mike M
>
>
> Jack E Martinelli <jemartin_ELIMINATE_@gis.net> wrote:
>
> > Very nice fix, Mike. You really are our SR / SFP expert.
>
>