pc behaves oddly once commit charge goes past 1gb

[Guest]

Hi,

I'm running XP pro sp2 and have 4gb of memory. I've noticed that as soon as
my total commit charge gets to 1gb, XP and any applications that I've got
open start behaving very oddly. I start getting messages like "insufficient
memory to complete operation" or messages about insufficient resources.
Applications like Excel 2007 are no longer displayed correctly on the screen.


As soon as close some applications and get the commit charge back under 1gb
everything works ok again.

Does anybody know why this might be happening?

Thanks

eko

 

[Guest]

While 4GB of ram memory seems it would be more than enough,xp uses
virtual memory almost as much.Set youre virtual memory in system properties
to "let system manage" click set 2X,restart pc.Also,another page file on
another
hd would help instead of the OS using C: drive,but not manditory...

 

[cquirke (MVP Windows shell/user)]

On Mon, 23 Jul 2007 09:40:03 -0700, mr_eko

I'm running XP pro sp2 and have 4gb of memory. I've noticed that as soon as
my total commit charge gets to 1gb, XP and any applications that I've got
open start behaving very oddly. I start getting messages like "insufficient
memory to complete operation" or messages about insufficient resources.
Applications like Excel 2007 are no longer displayed correctly on the screen.

As soon as close some applications and get the commit charge back under 1gb
everything works ok again.

Does anybody know why this might be happening?

Is that the 64-bit edition of XP? AFAIK the 32-bit XP (and Vista) is
limited to addressing 4G memory or less.

If it is XP 64-bit, then are the wobbly apps 32-bit? Their own
addressing may be going wonky, and/or there may be a signed/unsiged
bug somewhere that kicks in over 2G or something.

There is Boot.ini syntax to restict RAM usage, if it turns out you are
forced to shrink the memory addressability range.

--------------- ----- ---- --- -- - - -

To one who only has a hammer,
everything looks like a nail