Failures in the form of the screen "freezing" (not a BSoD)

  • Thread starter Thread starter Levlg
  • Start date Start date
L

Levlg

On my computer, sometimes there are failures in the form of the screen
"freezing" (not a BSoD). The exit of the situation is only by restarting.
Then usually (not always) I find the Event Viewer message: "EventID 2020 -
The server was unable to allocate from the system paged pool because the
pool was empty."

But my computer has a 4.096 GB of RAM. And I have the impression that
Pagefile.sys is not used in the work. I control it by the FileMon utility
and I see that there is no writing down to Pagefile.sys or reading from the
file. Date of Pagefile.sys is always equal to the time when I started my
computer.

Can anyone clarify the situation?

Thank you

Lev
 
Levlg said:
On my computer, sometimes there are failures in the form of the screen
"freezing" (not a BSoD). The exit of the situation is only by restarting.
Then usually (not always) I find the Event Viewer message: "EventID 2020 -
The server was unable to allocate from the system paged pool because the
pool was empty."

But my computer has a 4.096 GB of RAM. And I have the impression that
Pagefile.sys is not used in the work. I control it by the FileMon utility
and I see that there is no writing down to Pagefile.sys or reading from the
file. Date of Pagefile.sys is always equal to the time when I started my
computer.

Can anyone clarify the situation?

Thank you

Lev
Click to expand...

Try Poolmon ?

http://blogs.technet.com/b/markrussinovich/archive/2009/03/26/3211216.aspx

Paul
 
On my computer, sometimes there are failures in the form of the screen
"freezing" (not a BSoD). The exit of the situation is only by restarting.
. . .
my computer has a 4.096 GB of RAM. And I have the impression that
Pagefile.sys is not used in the work. I control it by the FileMon utility
and I see that there is no writing down to Pagefile.sys
Click to expand...

PAGEFILE.SYS is the name of the system swap file. WinXP has
no component named FILEMON. I.e. it looks as if you have let a
virus or trojan add itself to your system.

WinXP default is that Windows should optimize use of the swap/
paging file. Windows' tool for tinkering with this is
Control Panel / System / Advanced / Performance

In your case you should immediately deactivate FILEMON
(e.g. rename it XFILEMON, in a DOS box if necessary),
scan for malware and execute appropriate removal methods.
 
Don Phillipson said:
PAGEFILE.SYS is the name of the system swap file. WinXP has
no component named FILEMON. I.e. it looks as if you have let a
virus or trojan add itself to your system.

WinXP default is that Windows should optimize use of the swap/
paging file. Windows' tool for tinkering with this is
Control Panel / System / Advanced / Performance

In your case you should immediately deactivate FILEMON
(e.g. rename it XFILEMON, in a DOS box if necessary),
scan for malware and execute appropriate removal methods.
Click to expand...

FILEMON is (was) a Sys Internals utility, subsequently replaced by
Process Monitor after Microsoft bought out Sys Internals. Although
there is always the possibility that a program has become infected,
FILEMON as it came from Sys Internals is not a virus or Trojan.

--
Zaphod

Arthur: All my life I've had this strange feeling that there's
something big and sinister going on in the world.
Slartibartfast: No, that's perfectly normal paranoia. Everyone in the
universe gets that.
 
Back
Top