Very unusual problem

F

Fred

This is quite an unusual problem. Occasionally, while I am trying to run just
about anything (even wordpad) something unusual happens. From what I've
managed to piece together with unlimited patience, my computer suddenly usues
up all its RAM on no-op commands and other useless stuff. I've run continuous
virus scans and I'm fully up-to-date with all known ones, but there doesn't
appear to be any viruses. I've tried sharing files with another one of my
computers (one I use to test for viral activity, of course nothing works as
well as a culture sample) and there are no symptoms. I do not think it is
viral, yet my RAM keeps getting flooded with no-ops and random junk. I'm
wondering if anyone else has come across this problem while using an Acer
Incorperated computer with Vista as their OS, and if they've figured out a
solution.
Any response with a solution would help I'm sick of this stupidity.
--
Demo, mada yoku irimasen.
 
A

Adam Albright

On Fri, 6 Jul 2007 19:34:01 -0700, Fred <daswandrem@yahoo.com> wrote:

>This is quite an unusual problem. Occasionally, while I am trying to run just
>about anything (even wordpad) something unusual happens. From what I've
>managed to piece together with unlimited patience, my computer suddenly usues
>up all its RAM on no-op commands and other useless stuff. I've run continuous
>virus scans and I'm fully up-to-date with all known ones, but there doesn't
>appear to be any viruses. I've tried sharing files with another one of my
>computers (one I use to test for viral activity, of course nothing works as
>well as a culture sample) and there are no symptoms. I do not think it is
>viral, yet my RAM keeps getting flooded with no-ops and random junk. I'm
>wondering if anyone else has come across this problem while using an Acer
>Incorperated computer with Vista as their OS, and if they've figured out a
>solution.
>Any response with a solution would help I'm sick of this stupidity.


The short answer is Vista is designed to do that. Some would argue
unused memory is wasted memory. The key and where Windows falls down
and ALWAYS has regardless of what version of Windows we're talking
about it HOW it uses memory. Microsoft tinkers with the inner workings
in every new release of Windows.

What is suppose to happen but doesn't always is Windows should release
memory better so applications that need it can use it and the double
wammy is some applications are notorious for not releasing memory once
they're done with it. The end result is what you see, a sluggish
system.

Windows also tries to anticipate what you'll do next supposedly based
on past performance. This can mean Windows is constantly shuffling
things around back and forth between RAM and virtual memory. Sometimes
it works rather well, other times not really.
 

Similar threads

W
Replies
0
Views
57
Will AllenDL
W
T
Replies
0
Views
101
TylerTheeMighty
T
W
Replies
0
Views
85
Windowsuser_7_8.1_10_11
W
C
Replies
0
Views
108
Christian Dragotta
C
Back
Top Bottom