Not real "Availabe Physical Mem"

Hi,
I have a system running on WindowXP Professional.
The system has 2G of Physical Mem., 400G of Fast Hard
Drive space.
However, WindowXP will stop working and Post "Out of Mem"
When It reached 1.3g of memory used (roughly).
I Checked Task Manager and it said that there are more
than 700 Meg of Physical Mem Available.
I ran the Microsoft Mem Diag. Program all my hardware
seems okay.

Does any body have a clue why WindowXP stop working when
it used up to roughly 1.3 gig of mem.?

Thanks a million

I wonder if this is similar to an issue I have with
WINXPH and P and Office XP and a proprietary database
program that uses Access. Whenever the proprietary
program is installed the system will eventually (1-2
weeks) use all available physical RAM (512 MB) and start
a "physical memory dump" which somehow results in not
writing the necessary system files to re-start (or
possibly scrambling the NTFS FAT so it can't find the
files). A complete re-installation fixes it and all is
stable until the DB program is installed again. Are you
running Access, too?
>-----Original Message-----
>Hi,
>I have a system running on WindowXP Professional.
>The system has 2G of Physical Mem., 400G of Fast Hard
>Drive space.
>However, WindowXP will stop working and Post "Out of
Mem"
>When It reached 1.3g of memory used (roughly).
>I Checked Task Manager and it said that there are more
>than 700 Meg of Physical Mem Available.
>I ran the Microsoft Mem Diag. Program all my hardware
>seems okay.
>
>Does any body have a clue why WindowXP stop working when
>it used up to roughly 1.3 gig of mem.?
>
>Thanks a million
>
>
>.
>

I think you're misunderstanding what the memory dump is. It's for
troubleshooting. When your computer crashed unexpectedly, the computer saves
what's in memory to the drive for troubleshooting purposes. The dump isn't a
problem; when it happens, the problem -- the crash -- has already occurred.

If you think the procedure for writing the dump file is somehow flawed, you
can turn it off or choose a smaller size for the dump.

"Bill" <anonymous@discussions.microsoft.com> wrote in message
news:1f22d01c457dc$1c111640$a601280a@phx.gbl...
> I wonder if this is similar to an issue I have with
> WINXPH and P and Office XP and a proprietary database
> program that uses Access. Whenever the proprietary
> program is installed the system will eventually (1-2
> weeks) use all available physical RAM (512 MB) and start
> a "physical memory dump" which somehow results in not
> writing the necessary system files to re-start (or
> possibly scrambling the NTFS FAT so it can't find the
> files). A complete re-installation fixes it and all is
> stable until the DB program is installed again. Are you
> running Access, too?
> >-----Original Message-----
> >Hi,
> >I have a system running on WindowXP Professional.
> >The system has 2G of Physical Mem., 400G of Fast Hard
> >Drive space.
> >However, WindowXP will stop working and Post "Out of
> Mem"
> >When It reached 1.3g of memory used (roughly).
> >I Checked Task Manager and it said that there are more
> >than 700 Meg of Physical Mem Available.
> >I ran the Microsoft Mem Diag. Program all my hardware
> >seems okay.
> >
> >Does any body have a clue why WindowXP stop working when
> >it used up to roughly 1.3 gig of mem.?
> >
> >Thanks a million
> >
> >
> >.
> >

Guys, Guys...
I need to know if any of you can help me to get WindowXP
use the Available Mem and not stopping at ~1.3 gig and
leave ~700Meg available. My system not doing any memory
dump, it simply stop load more programs or files.

Thanks,
Han
>-----Original Message-----
>I think you're misunderstanding what the memory dump is.
It's for
>troubleshooting. When your computer crashed
unexpectedly, the computer saves
>what's in memory to the drive for troubleshooting
purposes. The dump isn't a
>problem; when it happens, the problem -- the crash --
has already occurred.
>
>If you think the procedure for writing the dump file is
somehow flawed, you
>can turn it off or choose a smaller size for the dump.
>
>"Bill" <anonymous@discussions.microsoft.com> wrote in
message
>news:1f22d01c457dc$1c111640$a601280a@phx.gbl...
>> I wonder if this is similar to an issue I have with
>> WINXPH and P and Office XP and a proprietary database
>> program that uses Access. Whenever the proprietary
>> program is installed the system will eventually (1-2
>> weeks) use all available physical RAM (512 MB) and
start
>> a "physical memory dump" which somehow results in not
>> writing the necessary system files to re-start (or
>> possibly scrambling the NTFS FAT so it can't find the
>> files). A complete re-installation fixes it and all is
>> stable until the DB program is installed again. Are you
>> running Access, too?
>> >-----Original Message-----
>> >Hi,
>> >I have a system running on WindowXP Professional.
>> >The system has 2G of Physical Mem., 400G of Fast Hard
>> >Drive space.
>> >However, WindowXP will stop working and Post "Out of
>> Mem"
>> >When It reached 1.3g of memory used (roughly).
>> >I Checked Task Manager and it said that there are more
>> >than 700 Meg of Physical Mem Available.
>> >I ran the Microsoft Mem Diag. Program all my hardware
>> >seems okay.
>> >
>> >Does any body have a clue why WindowXP stop working
when
>> >it used up to roughly 1.3 gig of mem.?
>> >
>> >Thanks a million
>> >
>> >
>> >.
>> >
>
>
>.
>