Monitor Processing?

  • Thread starter Thread starter aaaaa
  • Start date Start date
A

aaaaa

In XP SP3, is there a program or programs that I can install and run

to hopefully reveal resource (mainly time) hogs? Say, in the form of

a graph or some such?



Every so often my machine slows down suddenly and for long periods

(hours). I have looked at Task Manager, but that only shows (to me

anyway) the processes executing, but that's all.



Since I can shut down and re-boot to get things running at normal

speed again, I really would like to determine what the problem is.



a
 
aaaaa wrote:

> In XP SP3, is there a program or programs that I can install and run

> to hopefully reveal resource (mainly time) hogs? Say, in the form of

> a graph or some such?

>

> Every so often my machine slows down suddenly and for long periods

> (hours). I have looked at Task Manager, but that only shows (to me

> anyway) the processes executing, but that's all.




Open Task Manager

Click "View"

Click "Select columns"



Select what you want. In your case, CPU time and CPU useage might be nice.



--



dadiOH

____________________________



dadiOH's dandies v3.06...

....a help file of info about MP3s, recording from

LP/cassette and tips & tricks on this and that.

Get it at http://mysite.verizon.net/xico
 
On Feb 19, 7:33 am, aaaaa wrote:

> In XP SP3, is there a program or programs that I can install and run

> to hopefully reveal resource (mainly time) hogs?  Say, in the form of

> a graph or some such?

>

> Every so often my machine slows down suddenly and for long periods

> (hours).  I have looked at Task Manager, but that only shows (to me

> anyway) the processes executing,  but that's all.

>

> Since I can shut down and re-boot to get things running at normal

> speed again, I really would like to determine what the problem is.

>

> a




Try Process Explorer. It doesn't install anything and just runs on

demand.



It is Task Manager on steroids.



It is a little intimidating at first with all the information, but you

will learn to like it when you get the hang of it.



Check your system when it reboots, then check it when it is sluggish

and see what the problem really is.



http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx



Here is a sample output:



http://img693.imageshack.us/img693/9074/processexplorer.jpg
 
In news:c01tn51bauqrq5v8oj22ititnifa7uqjh0@4ax.com,

aaaaa typed:

> In XP SP3, is there a program or programs that I can install and run

> to hopefully reveal resource (mainly time) hogs? Say, in the form of

> a graph or some such?

>

> Every so often my machine slows down suddenly and for long periods

> (hours). I have looked at Task Manager, but that only shows (to me

> anyway) the processes executing, but that's all.

>

> Since I can shut down and re-boot to get things running at normal

> speed again, I really would like to determine what the problem is.

>

> a




Actually you can do it with Task Manager. Start Task Manager, then select

the cpu column. The click the CPU in the headers again; that will change the

order of the display from ascending to descending; now the processes using

the most cpu time will be at the top of the list and you can watch for the

hog that's causing you problems.



Jose mentioned Process Explorer, which is great, but a little intimidating

for the inexperienced. It's even better than Task Manager, but takes a

little effort to get figured out. Either one should assist you in uncovering

the hog.



HTH,



Twayne







--

--

Life is the only real counselor; wisdom unfiltered

through personal experience does not become a

part of the moral tissue.
 
On Fri, 19 Feb 2010 06:14:58 -0800 (PST), Jose

wrote:





>Try Process Explorer. It doesn't install anything and just runs on

>demand.

>

>It is Task Manager on steroids.

>

>It is a little intimidating at first with all the information, but you

>will learn to like it when you get the hang of it.

>

>Check your system when it reboots, then check it when it is sluggish

>and see what the problem really is.

>

>http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx

>

>Here is a sample output:

>

>http://img693.imageshack.us/img693/9074/processexplorer.jpg






Many thanks to both of you.
 
aaaaa wrote:

> In XP SP3, is there a program or programs that I can install and run

> to hopefully reveal resource (mainly time) hogs? Say, in the form of

> a graph or some such?

>

> Every so often my machine slows down suddenly and for long periods

> (hours). I have looked at Task Manager, but that only shows (to me

> anyway) the processes executing, but that's all.

>

> Since I can shut down and re-boot to get things running at normal

> speed again, I really would like to determine what the problem is.

>

> a




Do you have a Dell laptop ?



Some Dell laptops had a "throttling" problem, where for thermal control

reasons, the laptop slows the execution clock rate to almost nothing

(equivalent to 100MHz in some cases). The term coined at the time

was "ThrottleGate", as it was felt the problem was being

covered up by Dell. This PDF document tells you how to detect a

problem.



http://www.sigmirror.com/files/44490_iweoz/throttlegate.pdf



Throttling action Effective processing power (frequency)

1. Transition from state P0 to P1 2261 MHz

2. Transition from state P1 to P2 1596 MHz

3. Transition from state P2 to P3 798 MHz (with FSB frequency cut in half)

4. Clock Throttling at 7/8 of P3 700 MHz (with FSB frequency cut in half)

5. Clock Throttling at 6/8 of P3 600 MHz (with FSB frequency cut in half)

6. Clock Throttling at 5/8 of P3 500 MHz (with FSB frequency cut in half)

7. Clock Throttling at 4/8 of P3 400 MHz (with FSB frequency cut in half)

8. Clock Throttling at 3/8 of P3 300 MHz (with FSB frequency cut in half)

9. Clock Throttling at 2/8 of P3 200 MHz (with FSB frequency cut in half)

10. Clock Throttling at 1/8 of P3 100 MHz (with FSB frequency cut in half)



Task Manager shows you how your compute cycles are being

spent, but it doesn't tell you the effective clock rate right now.

Using 50% of 2261MHz is a lot different than using 50% of 100MHz.



Paul
 
OEM Software?

Is the term OEM strictly for hardware? I thought so.



Or, do software vendors release software copies which do not require

serial numbers or require a sn which applies to all copies of that

software installed on computers sold by a particular computer vendor?

In the latter case, how would one get said sn if he has to reinstall

the software and has no sn?



I have a friend in this bind. He bought a packaged program in

Florida, and now is back in NY, and cannot install it except as an

expired demo version. Does he need a paddle?



a
 
OEM Software?

He needs a paddle. He paid money for a trial/demo version that would have

been free (for a period of time) to begin with. He got ripped off.



Yes, there is such a thing as OEM software. Yes, most would require an

activation key.



Google is your friend: oem software definition



"aaaaa" wrote in message

news:vgptn554nh6hnbguksmvs1haf4se320ne1@4ax.com...

: Is the term OEM strictly for hardware? I thought so.

:

: Or, do software vendors release software copies which do not require

: serial numbers or require a sn which applies to all copies of that

: software installed on computers sold by a particular computer vendor?

: In the latter case, how would one get said sn if he has to reinstall

: the software and has no sn?

:

: I have a friend in this bind. He bought a packaged program in

: Florida, and now is back in NY, and cannot install it except as an

: expired demo version. Does he need a paddle?

:

: a
 
Re: OEM Software?

On Fri, 19 Feb 2010 13:51:39 -0600, "Tom Willett"

wrote:



>He needs a paddle. He paid money for a trial/demo version that would have

>been free (for a period of time) to begin with. He got ripped off.

>

>Yes, there is such a thing as OEM software. Yes, most would require an

>activation key.

>

>Google is your friend: oem software definition

>




Yeh - I thought of that after my post and found the same information

via Google. Wanted to remove my post, but couldn't.

Thanks for your response.



a
 
In news:hlmnrh$grq$1@speranza.aioe.org,

Paul typed:

> aaaaa wrote:

>> In XP SP3, is there a program or programs that I can install and run

>> to hopefully reveal resource (mainly time) hogs? Say, in the form of

>> a graph or some such?

>>

>> Every so often my machine slows down suddenly and for long periods

>> (hours). I have looked at Task Manager, but that only shows (to me

>> anyway) the processes executing, but that's all.

>>

>> Since I can shut down and re-boot to get things running at normal

>> speed again, I really would like to determine what the problem is.

>>

>> a


>

> Do you have a Dell laptop ?

>

> Some Dell laptops had a "throttling" problem, where for thermal

> control reasons, the laptop slows the execution clock rate to almost

> nothing (equivalent to 100MHz in some cases). The term coined at the

> time was "ThrottleGate", as it was felt the problem was being

> covered up by Dell. This PDF document tells you how to detect a

> problem.

>

> http://www.sigmirror.com/files/44490_iweoz/throttlegate.pdf

>

> Throttling action Effective processing power

> (frequency) 1. Transition from state P0 to P1 2261 MHz

> 2. Transition from state P1 to P2 1596 MHz

> 3. Transition from state P2 to P3 798 MHz (with FSB frequency cut

> in half) 4. Clock Throttling at 7/8 of P3 700 MHz (with FSB frequency

> cut

> in half) 5. Clock Throttling at 6/8 of P3 600 MHz (with FSB frequency

> cut

> in half) 6. Clock Throttling at 5/8 of P3 500 MHz (with FSB frequency

> cut

> in half) 7. Clock Throttling at 4/8 of P3 400 MHz (with FSB frequency

> cut

> in half) 8. Clock Throttling at 3/8 of P3 300 MHz (with FSB frequency

> cut

> in half) 9. Clock Throttling at 2/8 of P3 200 MHz (with FSB frequency

> cut

> in half) 10. Clock Throttling at 1/8 of P3 100 MHz (with FSB frequency

> cut

> in half)

> Task Manager shows you how your compute cycles are being

> spent, but it doesn't tell you the effective clock rate right now.

> Using 50% of 2261MHz is a lot different than using 50% of 100MHz.

>

> Paul




Interesting catch, Paul. Good going! Now if people would just adhere to

describing their systems, it'd make for better answers for sure!



Regards,



Twayne`

--

Life is the only real counselor; wisdom unfiltered

through personal experience does not become a

part of the moral tissue.
 
Back
Top