Hardware Monitor found an error

On Tue, 8 Apr 2008 18:24:20 -0500, "Rainy" <sweetwrapz@mchsi.com>
wrote:

> Let me say this back to you so you know I am understanding.. If the peak
> usage is 50 mb then that is all I might need in additional ram?


If the peak usage is that low, you don't need *any* additional RAM.
Even if average usage is that low, you'd probably not notice any
improvement by adding RAM.


> I will do
> this.. and write again after I have gathered some more data.. thanks Ken,
> Rainy
>
>
> "Ken Blake, MVP" <kblake@this.is.an.invalid.domain> wrote in message
> news:8htnv3941nbc2blce2qhfu78uqtffbqr3k@4ax.com...
> On Tue, 8 Apr 2008 17:13:58 -0500, "Rainy" <sweetwrapz@mchsi.com>
> wrote:
>
> > I ran the winxp pagefile usage monitor and here are the results.
> >
> > 5/8/2008 5:11:44 PM
> >
> > Pagefile Physical Location: C:\pagefile.sys
> > Current Pagefile Usage: 91 MB
> > Session Peak Usage: 240 MB
> > Current Pagefile Size: 1536 MB
> >
> > I finally was able to do something you experts have asked me to.
> > Whoopie!!!! lol
> >
> > I hope this helps you to help me.,. thanks, hugs Rainy
>
>
>
> Run it again, and while you are doing your heaviest graphics
> processing. Run it for a while, not just a short time, and keep track
> of current pagefile usage and session peak usage (don't worry about
> the pagefile size). Write down the numbers you see every few minutes,
> so you can see how they vary over the course of a day, or several
> hours.
>
> The more you use the page file, the more your performance will suffer.
> More RAM will decrease your pagefile usage by an equivalent amount. So
> if your peak usage doesn't exceed the 240MB reported above, 240MB more
> RAM is all you would really need. And if you use that 240MB of
> pagefile only seldom, that amount won't do a lot for you, and you
> don't really need it.
>
> In fact, assuming that you are more often near the 91MB than the 240,
> those numbers show fairly light page file usage.
>
> That's why it's important to monitor page file for a fairly long
> period, and while you're doing your most memory-intensive work. You
> don't want to fall into the trap of seeing a high peak usage (say 2GB)
> and think that you therefore need another 2GB of RAM. If that 2GB of
> page file use is only for a minute or two a day, and the rest of the
> day it's only 10MB, you shouldn't waste money on any more RAM.
>
>
> > "Ken Blake, MVP" <kblake@this.is.an.invalid.domain> wrote in message
> > newsmknv3dkqrnmuhofckqsro60k36hvck47e@4ax.com...
> > On Tue, 8 Apr 2008 14:13:43 -0500, "Rainy" <sweetwrapz@mchsi.com>
> > wrote:
> >
> > > Thank you for responding.. you have given me a lot of information..
> > > correcting my misinformation so I know how to proceed, it has been my
> > > intention to buy more ram.. so I will do this..
> >
> >
> > Before you buy more RAM, realize that very few people need more than
> > 1GB with Windows XP. Even that amount is more than most people need.
> > Read the following:
> >
> > How much RAM you need for good performance is *not* a
> > one-size-fits-all situation. You get good performance if the amount of
> > RAM you have keeps you from using the page file, and that depends on
> > what apps you run. Most people running a typical range of business
> > applications find that somewhere around 256-384MB works well, others
> > need 512MB. Almost anyone will see poor performance with less than
> > 256MB. Some people, particularly those doing things like editing large
> > photographic images, can see a performance boost by adding even more
> > than 512MB--sometimes much more.
> >
> > If you are currently using the page file significantly, more memory
> > will decrease or eliminate that usage, and improve your performance.
> > If you are not using the page file significantly, more memory will do
> > nothing for you. Go to
> > http://billsway.com/notes%5Fpublic/winxp%5Ftweaks/ and download
> > WinXP-2K_Pagefile.zip and monitor your pagefile usage. That should
> > give you a good idea of whether more memory can help, and if so, how
> > much more.
> >
> >
> >
> > > and if I have enough money
> > > after the move, I can have a tech look at it and see where the problems
> > > lie.., My son is pretty good with hard ware, but not with windows XP ..
> > > I
> > > have fixed his computer before. thanks to this group..
> > >
> > > I know what a power supply is but up til now had never heard of a power
> > > supply "system".. so I will check into that.. thanks for the technical
> > > input.. it's appreciated. thanks, Rainy
> > >
> > > w_tom" <w_tom1@usa.net> wrote in message
> > > news:9163b82c-edae-4213-8e50-ce7587ad6e27@m71g2000hse.googlegroups.com...
> > > On Apr 7, 7:44 pm, "Rainy" <sweetwr...@mchsi.com> wrote:
> > > > I'm thinking there is another reason why my computer was frozen. It
> > > > could
> > > > have been an out of resources situation. or one of the other things
> > > > that
> > > > have been listed in this thread.. I have tendency to open a lot of
> > > > windows
> > > > at the same time.. I have a gig of ram, but I am a graphics hog.. and
> > > > probably need more ram, I also need a larger drive, a couple of them..
> > > > ..
> > >
> > > 1 gbyte memory is constantly too small. When the computer needs
> > > more memory, it simply transfers code out to disk - virtual memory.
> > > If virtual memory is too small, then an OS announces the problem,
> > > enlarges virtual memory (on the disk) and keeps working. At no time
> > > will insufficient resources crash an OS. Reliability even in 1960
> > > mainframes demanded that an OS always keep working. If computer
> > > cannot provide the resources, then the OS stops or removes that
> > > program - and keeps working.
> > >
> > > Hardware reasons for freezing were listed previously. Niether
> > > insufficient memory nor a disk drive is on that list. Defective
> > > memory (in limited locations) can crash a computer. Insufficient
> > > resources could crash unreliable OSes such as Windows 9x/ME. But
> > > insufficient resources must never crash a true pre-emptive
> > > multitasking OS such as Windows NT based OSes.
> > >
> >
> > --
> > Ken Blake, Microsoft MVP - Windows Desktop Experience
> > Please Reply to the Newsgroup
> >
>
> --
> Ken Blake, Microsoft MVP - Windows Desktop Experience
> Please Reply to the Newsgroup
>

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

I see, thanks.. Rainy
"Ken Blake, MVP" <kblake@this.is.an.invalid.domain> wrote in message
news:535ov31es4o80oqns3nn5iv2v0ocbvurk7@4ax.com...
On Tue, 8 Apr 2008 18:24:20 -0500, "Rainy" <sweetwrapz@mchsi.com>
wrote:

> Let me say this back to you so you know I am understanding.. If the peak
> usage is 50 mb then that is all I might need in additional ram?


If the peak usage is that low, you don't need *any* additional RAM.
Even if average usage is that low, you'd probably not notice any
improvement by adding RAM.


> I will do
> this.. and write again after I have gathered some more data.. thanks Ken,
> Rainy
>
>
> "Ken Blake, MVP" <kblake@this.is.an.invalid.domain> wrote in message
> news:8htnv3941nbc2blce2qhfu78uqtffbqr3k@4ax.com...
> On Tue, 8 Apr 2008 17:13:58 -0500, "Rainy" <sweetwrapz@mchsi.com>
> wrote:
>
> > I ran the winxp pagefile usage monitor and here are the results.
> >
> > 5/8/2008 5:11:44 PM
> >
> > Pagefile Physical Location: C:\pagefile.sys
> > Current Pagefile Usage: 91 MB
> > Session Peak Usage: 240 MB
> > Current Pagefile Size: 1536 MB
> >
> > I finally was able to do something you experts have asked me to.
> > Whoopie!!!! lol
> >
> > I hope this helps you to help me.,. thanks, hugs Rainy
>
>
>
> Run it again, and while you are doing your heaviest graphics
> processing. Run it for a while, not just a short time, and keep track
> of current pagefile usage and session peak usage (don't worry about
> the pagefile size). Write down the numbers you see every few minutes,
> so you can see how they vary over the course of a day, or several
> hours.
>
> The more you use the page file, the more your performance will suffer.
> More RAM will decrease your pagefile usage by an equivalent amount. So
> if your peak usage doesn't exceed the 240MB reported above, 240MB more
> RAM is all you would really need. And if you use that 240MB of
> pagefile only seldom, that amount won't do a lot for you, and you
> don't really need it.
>
> In fact, assuming that you are more often near the 91MB than the 240,
> those numbers show fairly light page file usage.
>
> That's why it's important to monitor page file for a fairly long
> period, and while you're doing your most memory-intensive work. You
> don't want to fall into the trap of seeing a high peak usage (say 2GB)
> and think that you therefore need another 2GB of RAM. If that 2GB of
> page file use is only for a minute or two a day, and the rest of the
> day it's only 10MB, you shouldn't waste money on any more RAM.
>
>
> > "Ken Blake, MVP" <kblake@this.is.an.invalid.domain> wrote in message
> > newsmknv3dkqrnmuhofckqsro60k36hvck47e@4ax.com...
> > On Tue, 8 Apr 2008 14:13:43 -0500, "Rainy" <sweetwrapz@mchsi.com>
> > wrote:
> >
> > > Thank you for responding.. you have given me a lot of information..
> > > correcting my misinformation so I know how to proceed, it has been my
> > > intention to buy more ram.. so I will do this..
> >
> >
> > Before you buy more RAM, realize that very few people need more than
> > 1GB with Windows XP. Even that amount is more than most people need.
> > Read the following:
> >
> > How much RAM you need for good performance is *not* a
> > one-size-fits-all situation. You get good performance if the amount of
> > RAM you have keeps you from using the page file, and that depends on
> > what apps you run. Most people running a typical range of business
> > applications find that somewhere around 256-384MB works well, others
> > need 512MB. Almost anyone will see poor performance with less than
> > 256MB. Some people, particularly those doing things like editing large
> > photographic images, can see a performance boost by adding even more
> > than 512MB--sometimes much more.
> >
> > If you are currently using the page file significantly, more memory
> > will decrease or eliminate that usage, and improve your performance.
> > If you are not using the page file significantly, more memory will do
> > nothing for you. Go to
> > http://billsway.com/notes%5Fpublic/winxp%5Ftweaks/ and download
> > WinXP-2K_Pagefile.zip and monitor your pagefile usage. That should
> > give you a good idea of whether more memory can help, and if so, how
> > much more.
> >
> >
> >
> > > and if I have enough money
> > > after the move, I can have a tech look at it and see where the
> > > problems
> > > lie.., My son is pretty good with hard ware, but not with windows XP
> > > ..
> > > I
> > > have fixed his computer before. thanks to this group..
> > >
> > > I know what a power supply is but up til now had never heard of a
> > > power
> > > supply "system".. so I will check into that.. thanks for the technical
> > > input.. it's appreciated. thanks, Rainy
> > >
> > > w_tom" <w_tom1@usa.net> wrote in message
> > > news:9163b82c-edae-4213-8e50-ce7587ad6e27@m71g2000hse.googlegroups.com...
> > > On Apr 7, 7:44 pm, "Rainy" <sweetwr...@mchsi.com> wrote:
> > > > I'm thinking there is another reason why my computer was frozen. It
> > > > could
> > > > have been an out of resources situation. or one of the other things
> > > > that
> > > > have been listed in this thread.. I have tendency to open a lot of
> > > > windows
> > > > at the same time.. I have a gig of ram, but I am a graphics hog..
> > > > and
> > > > probably need more ram, I also need a larger drive, a couple of
> > > > them..
> > > > ..
> > >
> > > 1 gbyte memory is constantly too small. When the computer needs
> > > more memory, it simply transfers code out to disk - virtual memory.
> > > If virtual memory is too small, then an OS announces the problem,
> > > enlarges virtual memory (on the disk) and keeps working. At no time
> > > will insufficient resources crash an OS. Reliability even in 1960
> > > mainframes demanded that an OS always keep working. If computer
> > > cannot provide the resources, then the OS stops or removes that
> > > program - and keeps working.
> > >
> > > Hardware reasons for freezing were listed previously. Niether
> > > insufficient memory nor a disk drive is on that list. Defective
> > > memory (in limited locations) can crash a computer. Insufficient
> > > resources could crash unreliable OSes such as Windows 9x/ME. But
> > > insufficient resources must never crash a true pre-emptive
> > > multitasking OS such as Windows NT based OSes.
> > >
> >
> > --
> > Ken Blake, Microsoft MVP - Windows Desktop Experience
> > Please Reply to the Newsgroup
> >
>
> --
> Ken Blake, Microsoft MVP - Windows Desktop Experience
> Please Reply to the Newsgroup
>

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

Hi, Most of the time Paint Shop pro was running, and when the page usage was
the highest, I had The Font Thing, Paint shop Pro and Itunes.up. so it
doesn't look like I need more ram.. thanks for all the help I did have one
last question .. If I changed the pagefile size, could that benefit me?
Thanks so much Rainy

4/9/2008 7:18:56 PM

Pagefile Physical Location: C:\pagefile.sys
Current Pagefile Usage: 102 MB
Session Peak Usage: 240 MB
Current Pagefile Size: 1536 MB

4/9/2008 3:45:16 PM

Pagefile Physical Location: C:\pagefile.sys
Current Pagefile Usage: 99 MB
Session Peak Usage: 240 MB
Current Pagefile Size: 1536 MB

4/9/2008 3:29:32 PM

Pagefile Physical Location: C:\pagefile.sys
Current Pagefile Usage: 152 MB The Font viewer along with paint shope pro
were being used
Session Peak Usage: 240 MB
Current Pagefile Size: 1536 MB

4/9/2008 3:29:20 PM

Pagefile Physical Location: C:\pagefile.sys
Current Pagefile Usage: 148 MB The Font viewer along with paint shope pro
were being used
Session Peak Usage: 240 MB
Current Pagefile Size: 1536 MB

4/9/2008 1:24:09 PM

Pagefile Physical Location: C:\pagefile.sys
Current Pagefile Usage: 163 MB Paint Shop Pro, Itunes, and The Font Thing
were being used
Session Peak Usage: 240 MB
Current Pagefile Size: 1536 MB

4/9/2008 9:45:36 AM

Pagefile Physical Location: C:\pagefile.sys
Current Pagefile Usage: 154 MB The Font viewer along with paint shope pro
were being used
Session Peak Usage: 240 MB
Current Pagefile Size: 1536 MB

4/9/2008 9:42:32 AM

Pagefile Physical Location: C:\pagefile.sys
Current Pagefile Usage: 153 MB The Font viewer along with paint shope pro
were being used
Session Peak Usage: 240 MB
Current Pagefile Size: 1536 MB

4/9/2008 9:00:21 AM

Pagefile Physical Location: C:\pagefile.sys
Current Pagefile Usage: 152 MB The Font viewer along with paint shope pro
were being used..
Session Peak Usage: 240 MB
Current Pagefile Size: 1536 MB

4/9/2008 7:17:16 AM

Pagefile Physical Location: C:\pagefile.sys
Current Pagefile Usage: 100 MB
Session Peak Usage: 240 MB
Current Pagefile Size: 1536 MB

4/9/2008 6:49:09 AM

Pagefile Physical Location: C:\pagefile.sys
Current Pagefile Usage: 98 MB
Session Peak Usage: 240 MB
Current Pagefile Size: 1536 MB

4/8/2008 11:25:52 PM

Pagefile Physical Location: C:\pagefile.sys
Current Pagefile Usage: 96 MB
Session Peak Usage: 240 MB
Current Pagefile Size: 1536 MB

4/8/2008 10:44:35 PM

Pagefile Physical Location: C:\pagefile.sys
Current Pagefile Usage: 143 MB The Font viewer along with paint shope pro
were being used
Session Peak Usage: 240 MB
Current Pagefile Size: 1536 MB

4/8/2008 9:44:07 PM

Pagefile Physical Location: C:\pagefile.sys
Current Pagefile Usage: 100 MB
Session Peak Usage: 240 MB
Current Pagefile Size: 1536 MB

4/8/2008 7:47:21 PM

Pagefile Physical Location: C:\pagefile.sys
Current Pagefile Usage: 95 MB
Session Peak Usage: 240 MB
Current Pagefile Size: 1536 MB

4/8/2008 7:40:05 PM

Pagefile Physical Location: C:\pagefile.sys
Current Pagefile Usage: 101 MB
Session Peak Usage: 240 MB
Current Pagefile Size: 1536 MB

4/8/2008 6:45:19 PM

Pagefile Physical Location: C:\pagefile.sys
Current Pagefile Usage: 91 MB
Session Peak Usage: 240 MB
Current Pagefile Size: 1536 MB

4/8/2008 6:30:41 PM

Pagefile Physical Location: C:\pagefile.sys
Current Pagefile Usage: 91 MB
Session Peak Usage: 240 MB
Current Pagefile Size: 1536 MB

4/8/2008 6:27:35 PM

Pagefile Physical Location: C:\pagefile.sys
Current Pagefile Usage: 91 MB
Session Peak Usage: 240 MB
Current Pagefile Size: 1536 MB

4/8/2008 5:36:10 PM

Pagefile Physical Location: C:\pagefile.sys
Current Pagefile Usage: 102 MB
Session Peak Usage: 240 MB
Current Pagefile Size: 1536 MB

4/8/2008 5:11:44 PM

Pagefile Physical Location: C:\pagefile.sys
Current Pagefile Usage: 91 MB
Session Peak Usage: 240 MB
Current Pagefile Size: 1536 MB



"Ken Blake, MVP" <kblake@this.is.an.invalid.domain> wrote in message
news:39unv396436oe584be7ec3a9ke3rg8jmbq@4ax.com...
On Tue, 8 Apr 2008 17:18:05 -0500, "Rainy" <sweetwrapz@mchsi.com>
wrote:

> I also wanted you to know what was running at the time I ran those vbs
> files..
>
> Incredimail, Sygate, Gadwins Printscreen, Yahoo Messenger, Aim, AVG and
> Unlocker..


See my previous message, Rainy. You need to run it while running your
Graphics software.


> "Ken Blake, MVP" <kblake@this.is.an.invalid.domain> wrote in message
> newsmknv3dkqrnmuhofckqsro60k36hvck47e@4ax.com...
> On Tue, 8 Apr 2008 14:13:43 -0500, "Rainy" <sweetwrapz@mchsi.com>
> wrote:
>
> > Thank you for responding.. you have given me a lot of information..
> > correcting my misinformation so I know how to proceed, it has been my
> > intention to buy more ram.. so I will do this..
>
>
> Before you buy more RAM, realize that very few people need more than
> 1GB with Windows XP. Even that amount is more than most people need.
> Read the following:
>
> How much RAM you need for good performance is *not* a
> one-size-fits-all situation. You get good performance if the amount of
> RAM you have keeps you from using the page file, and that depends on
> what apps you run. Most people running a typical range of business
> applications find that somewhere around 256-384MB works well, others
> need 512MB. Almost anyone will see poor performance with less than
> 256MB. Some people, particularly those doing things like editing large
> photographic images, can see a performance boost by adding even more
> than 512MB--sometimes much more.
>
> If you are currently using the page file significantly, more memory
> will decrease or eliminate that usage, and improve your performance.
> If you are not using the page file significantly, more memory will do
> nothing for you. Go to
> http://billsway.com/notes%5Fpublic/winxp%5Ftweaks/ and download
> WinXP-2K_Pagefile.zip and monitor your pagefile usage. That should
> give you a good idea of whether more memory can help, and if so, how
> much more.
>
>
>
> > and if I have enough money
> > after the move, I can have a tech look at it and see where the problems
> > lie.., My son is pretty good with hard ware, but not with windows XP ..
> > I
> > have fixed his computer before. thanks to this group..
> >
> > I know what a power supply is but up til now had never heard of a power
> > supply "system".. so I will check into that.. thanks for the technical
> > input.. it's appreciated. thanks, Rainy
> >
> > w_tom" <w_tom1@usa.net> wrote in message
> > news:9163b82c-edae-4213-8e50-ce7587ad6e27@m71g2000hse.googlegroups.com...
> > On Apr 7, 7:44 pm, "Rainy" <sweetwr...@mchsi.com> wrote:
> > > I'm thinking there is another reason why my computer was frozen. It
> > > could
> > > have been an out of resources situation. or one of the other things
> > > that
> > > have been listed in this thread.. I have tendency to open a lot of
> > > windows
> > > at the same time.. I have a gig of ram, but I am a graphics hog.. and
> > > probably need more ram, I also need a larger drive, a couple of them..
> > > ..
> >
> > 1 gbyte memory is constantly too small. When the computer needs
> > more memory, it simply transfers code out to disk - virtual memory.
> > If virtual memory is too small, then an OS announces the problem,
> > enlarges virtual memory (on the disk) and keeps working. At no time
> > will insufficient resources crash an OS. Reliability even in 1960
> > mainframes demanded that an OS always keep working. If computer
> > cannot provide the resources, then the OS stops or removes that
> > program - and keeps working.
> >
> > Hardware reasons for freezing were listed previously. Niether
> > insufficient memory nor a disk drive is on that list. Defective
> > memory (in limited locations) can crash a computer. Insufficient
> > resources could crash unreliable OSes such as Windows 9x/ME. But
> > insufficient resources must never crash a true pre-emptive
> > multitasking OS such as Windows NT based OSes.
> >
>
> --
> Ken Blake, Microsoft MVP - Windows Desktop Experience
> Please Reply to the Newsgroup
>

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

Just wanted you to know that I found the problem.. It was not a hard ware
problem.. but dirt* or rather tons of dust in the tower.. Normally I clean
my tower often, but have overlooked it for some time.. Lots of things
going on in my life at the moment, so I just didn't think about it.. When
I was reading a thread online for someone having the same problem, they
mentioned dirt.. so I immediately went to Walmart and bought a can of air,
and a new *surge protector, since mine was only showing one yellow light and
one green one.. The new one has all lights showing..but I don't know if that
was part of the problem or not.

I like to update my request for others reading the thread.. thanks for all
the help.. hugs Rainy


"Ken Blake, MVP" <kblake@this.is.an.invalid.domain> wrote in message
news:39unv396436oe584be7ec3a9ke3rg8jmbq@4ax.com...
On Tue, 8 Apr 2008 17:18:05 -0500, "Rainy" <sweetwrapz@mchsi.com>
wrote:

> I also wanted you to know what was running at the time I ran those vbs
> files..
>
> Incredimail, Sygate, Gadwins Printscreen, Yahoo Messenger, Aim, AVG and
> Unlocker..


See my previous message, Rainy. You need to run it while running your
Graphics software.


> "Ken Blake, MVP" <kblake@this.is.an.invalid.domain> wrote in message
> newsmknv3dkqrnmuhofckqsro60k36hvck47e@4ax.com...
> On Tue, 8 Apr 2008 14:13:43 -0500, "Rainy" <sweetwrapz@mchsi.com>
> wrote:
>
> > Thank you for responding.. you have given me a lot of information..
> > correcting my misinformation so I know how to proceed, it has been my
> > intention to buy more ram.. so I will do this..
>
>
> Before you buy more RAM, realize that very few people need more than
> 1GB with Windows XP. Even that amount is more than most people need.
> Read the following:
>
> How much RAM you need for good performance is *not* a
> one-size-fits-all situation. You get good performance if the amount of
> RAM you have keeps you from using the page file, and that depends on
> what apps you run. Most people running a typical range of business
> applications find that somewhere around 256-384MB works well, others
> need 512MB. Almost anyone will see poor performance with less than
> 256MB. Some people, particularly those doing things like editing large
> photographic images, can see a performance boost by adding even more
> than 512MB--sometimes much more.
>
> If you are currently using the page file significantly, more memory
> will decrease or eliminate that usage, and improve your performance.
> If you are not using the page file significantly, more memory will do
> nothing for you. Go to
> http://billsway.com/notes%5Fpublic/winxp%5Ftweaks/ and download
> WinXP-2K_Pagefile.zip and monitor your pagefile usage. That should
> give you a good idea of whether more memory can help, and if so, how
> much more.
>
>
>
> > and if I have enough money
> > after the move, I can have a tech look at it and see where the problems
> > lie.., My son is pretty good with hard ware, but not with windows XP ..
> > I
> > have fixed his computer before. thanks to this group..
> >
> > I know what a power supply is but up til now had never heard of a power
> > supply "system".. so I will check into that.. thanks for the technical
> > input.. it's appreciated. thanks, Rainy
> >
> > w_tom" <w_tom1@usa.net> wrote in message
> > news:9163b82c-edae-4213-8e50-ce7587ad6e27@m71g2000hse.googlegroups.com...
> > On Apr 7, 7:44 pm, "Rainy" <sweetwr...@mchsi.com> wrote:
> > > I'm thinking there is another reason why my computer was frozen. It
> > > could
> > > have been an out of resources situation. or one of the other things
> > > that
> > > have been listed in this thread.. I have tendency to open a lot of
> > > windows
> > > at the same time.. I have a gig of ram, but I am a graphics hog.. and
> > > probably need more ram, I also need a larger drive, a couple of them..
> > > ..
> >
> > 1 gbyte memory is constantly too small. When the computer needs
> > more memory, it simply transfers code out to disk - virtual memory.
> > If virtual memory is too small, then an OS announces the problem,
> > enlarges virtual memory (on the disk) and keeps working. At no time
> > will insufficient resources crash an OS. Reliability even in 1960
> > mainframes demanded that an OS always keep working. If computer
> > cannot provide the resources, then the OS stops or removes that
> > program - and keeps working.
> >
> > Hardware reasons for freezing were listed previously. Niether
> > insufficient memory nor a disk drive is on that list. Defective
> > memory (in limited locations) can crash a computer. Insufficient
> > resources could crash unreliable OSes such as Windows 9x/ME. But
> > insufficient resources must never crash a true pre-emptive
> > multitasking OS such as Windows NT based OSes.
> >
>
> --
> Ken Blake, Microsoft MVP - Windows Desktop Experience
> Please Reply to the Newsgroup
>

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

On Apr 16, 8:21*am, "Rainy" <sweetwr...@mchsi.com> wrote:
> Just wanted you to know that I found the problem.. It was not a hard ware
> problem.. but dirt* or rather tons of dust in the tower.. Normally I clean
> my tower often, but have overlooked it for some time.. Lots of things
> going on in my life at the moment, so I just didn't think about it.. When
> I was reading a thread online for someone having the same problem, they
> mentioned dirt.. so I immediately went to Walmart and bought a can of air,
> and a new *surge protector, since mine was only showing one yellow light and
> one green one.. The new one has all lights showing..but I don't know if that
> was part of the problem or not.

The dirt has to be so thick that (for example) no holes existed in
the heatsink). If not, then you may have only cured a symptom -
heating being a diagnostic tool to find defective hardware. This
summer is a good time to locate defective hardware. Operate the
computer in a room that is 100 degrees F. Best is to execute
diagnostics. No matter what the computer executes, it must work
perfectly fine even in that 100 degree room. If not, then you still
have defective hardware.

Any computer that works just fine in 100 degrees should also work
just fine with dirt in a 70 degree room. Unfortunately many clean a
computer, see no problem, then blame the dirt - also called curing
symptoms. Any desktop or laptop must work happy and fine all day in a
100 degree room. If not, then heat is the diagnostic tool to find
defective hardware.

thanks for your input... I just hope it holds out until I move.. Rainy
"w_tom" <w_tom1@usa.net> wrote in message
news:7e59fc34-1a1b-4199-a340-4f833808f645@a23g2000hsc.googlegroups.com...
On Apr 16, 8:21 am, "Rainy" <sweetwr...@mchsi.com> wrote:
> Just wanted you to know that I found the problem.. It was not a hard ware
> problem.. but dirt* or rather tons of dust in the tower.. Normally I clean
> my tower often, but have overlooked it for some time.. Lots of things
> going on in my life at the moment, so I just didn't think about it..
> When
> I was reading a thread online for someone having the same problem, they
> mentioned dirt.. so I immediately went to Walmart and bought a can of air,
> and a new *surge protector, since mine was only showing one yellow light
> and
> one green one.. The new one has all lights showing..but I don't know if
> that
> was part of the problem or not.

The dirt has to be so thick that (for example) no holes existed in
the heatsink). If not, then you may have only cured a symptom -
heating being a diagnostic tool to find defective hardware. This
summer is a good time to locate defective hardware. Operate the
computer in a room that is 100 degrees F. Best is to execute
diagnostics. No matter what the computer executes, it must work
perfectly fine even in that 100 degree room. If not, then you still
have defective hardware.

Any computer that works just fine in 100 degrees should also work
just fine with dirt in a 70 degree room. Unfortunately many clean a
computer, see no problem, then blame the dirt - also called curing
symptoms. Any desktop or laptop must work happy and fine all day in a
100 degree room. If not, then heat is the diagnostic tool to find
defective hardware.

On Apr 16, 11:14*pm, "Rainy" <sweetwr...@mchsi.com> wrote:
> thanks for your input... I just hope it holds out until I move.. *

Interesting concept. Normally the failing computer gets moved out.
Instead, you intend to move out before the computer fails. Leave it
for the next owner to suffer failure. Problem solved.

I don't think so.. lol My whole computer is not failing, I will replace
components if I need to.. but not leave it.. it's the only computer I have
and very little money to replace it.. Problem might be solved for you, but
not for me hugs Rainy
"w_tom" <w_tom1@usa.net> wrote in message
news:29c8e078-af87-4e81-9464-ab5965369ec8@f36g2000hsa.googlegroups.com...
On Apr 16, 11:14 pm, "Rainy" <sweetwr...@mchsi.com> wrote:
> thanks for your input... I just hope it holds out until I move..

Interesting concept. Normally the failing computer gets moved out.
Instead, you intend to move out before the computer fails. Leave it
for the next owner to suffer failure. Problem solved.

On Apr 17, 10:22*am, "Rainy" <sweetwr...@mchsi.com> wrote:
> I don't think so.. lol My whole computer is not failing, I will replace
> components if I need to.. but not leave it.. it's the only computer I have
> and very little money to replace it.. Problem might be solved for you, but
> not for me *

After reading so many replies in this topic, you conclusions are too
much reality for me. Letting a next homeowner suffer is more
satisfying - especially when it is not my computer.

Well you have a simple fix for your computer if you know the day it is
<G>!



~~~~


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

Rainy wrote:
> I think you are kidding.. I hope you are.. lol
> "w_tom" <w_tom1@usa.net> wrote in message
> news:01aa95db-61e3-435e-baf1-97e47cf9d8ea@k37g2000hsf.googlegroups.com...
> On Apr 17, 10:22 am, "Rainy" <sweetwr...@mchsi.com> wrote:
>> I don't think so.. lol My whole computer is not failing, I will
>> replace components if I need to.. but not leave it.. it's the only
>> computer I have and very little money to replace it.. Problem might
>> be solved for you, but not for me
>
> After reading so many replies in this topic, you conclusions are too
> much reality for me. Letting a next homeowner suffer is more
> satisfying - especially when it is not my computer.