pwrichcreek
Tue Apr 22 07:14:01 PDT 2008
Thanks for your reply Sengupta.
I did try the safe mode and safe mode with networking. The error did not
occur in either mode and I have been running in normal mode for about 24
hours with no problems. After looking through the system event log, I find
that I have an occasional disk error on the paging area (event id 51) --
"occasional" being 5-10 times ever 24 hours. I can imagine that this might
result in being reflected back to an application as a paging problem such as
the 2020. But since the paging area disk errors in question are so
infrequent, it seems odd that the 2020 error would be so persistent if it
were related to the paging area disk error. A better way to say that is that
the event log does not demonstrate that all of the 2020 errors are preceded
by a paging disk error. Do you agree that the two errors are probably not
related?
My physical RAM is 512MB and the page area parameters are 758/1536.
Thanks,
Phil
"S.Sengupta" wrote:
> Do the following:-
>
> Start>Run>msconfig>OK
>
> Now click the Startup tab and disable everything.Restart the system and
> recheck.It's a sort of trial and error thing.
>
> How much physical RAM is in your computer?
>
> The recommended minimum size of page file is equivalent to 1.5 times the
> amount of RAM on your system, and 3 times that figure for the maximum size.
>
> regards,
> S.Sengupta[MS-MVP]
>
>
> pwrichcreek wrote:
> >>this solution is only applicable for the servers and not for XP.
> >
> >
> > Yes, I noticed that it only mentioned server/2003, but it did not
> > specifically state that a similar problem and solution would NOT apply to XP.
> > From your reply, I gather that you are certain that it only applies to
> > server. Do you think increasing the pagefile parameter would not help in XP?
> >
> >
> >>Do you use Trend Micro?If then disable that and recheck the issue.
> >
> >
> > No, I don't run Trend Micro. Do you know what behavior of Trend Micro
> > triggers the problem? Perhaps I can find out whether som application I'm
> > running exhibits simlar behavior and find a way to correct that.
> >
> > Thanks for you reply,
> >
> > Phil
> >
> > "S.Sengupta" wrote:
> >
> >
> >>The solution that you mentioned is referred to the following KB Article:-> this solution is only applicable for the servers and not for XP.
> >>
http://support.microsoft.com/kb/312362
> >>
> >
> >
> >>Re_
http://support.microsoft.com/kb/312362
> >>
> >>Do you use Trend Micro?If then disable that and recheck the issue.
> >>
> >>
> >>regards,
> >>S.Sengupta[MS-MVP]
> >>
> >>pwrichcreek wrote:
> >>
> >>>Recently I started getting this message
> >>>
> >>>"Unable to allocation from system paged pool because the pool was empty"
> >>>
> >>>I found a reference to this message on another forum and it gave the
> >>>following solution. Problem is, that solution was for Server/2003 and I am
> >>>running XP. Also, I have a pagefile size in my registry (Pagingfiles ... 758
> >>>1536) and don't know whether adding the PagedPoolSize referred to below will
> >>>conflict with Pagingfiles.
> >>>
> >>>The solution offered in the other forum is:
> >>>
> >>>HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro
> >>>l\Session Manager\Memory Management
> >>>
> >>>Value name: PoolUsageMaximum
> >>>Data type: REG_DWORD
> >>>Radix: Decimal
> >>>Value data: 60 < change to or add this value
> >>>
> >>>Value name: PagedPoolSize
> >>>Data type: REG_DWORD
> >>>Radix: Hex
> >>>Value data: 0xFFFFFFFF < change to or add this value
> >>>
> >>>Is it safe to make this change on my XP system?
> >>>
> >>>TIA,
> >>>
> >>>Phil
> >>
>