Guest Jeff Posted March 24, 2008 Posted March 24, 2008 I'm having a problem where every few weeks or so, my server gets hosed. All of the sudden it stops accepting network connections. Usually a reboot does the trick. We also notice that an error is always written to the event log whenever this occurs. The errror is "The server was unable to allocate from the system nonpaged pool because the pool was empty." After doing some research on the error, we figured that the problem was a memory leak. We have been running pool monitor for the last week. The tag called STRG has climbed all week. It is now at about 120mb. I guess this is our culprit - however what is STRG?
Guest Thee Chicago Wolf Posted March 24, 2008 Posted March 24, 2008 Re: Memory Leak >I'm having a problem where every few weeks or so, my server gets hosed. All >of the sudden it stops accepting network connections. Usually a reboot does >the trick. We also notice that an error is always written to the event log >whenever this occurs. The errror is > >"The server was unable to allocate from the system nonpaged pool because the >pool was empty." > >After doing some research on the error, we figured that the problem was a >memory leak. We have been running pool monitor for the last week. The tag >called STRG has climbed all week. It is now at about 120mb. I guess this is >our culprit - however what is STRG? There are gobs of patches / hotfixes for the nonpaged pool errors. http://support.microsoft.com/search/default.aspx?mode=r&query=nonpaged+pool&catalog=LCID%3D1033&1033comm=1&spid=3198 - Thee Chicago Wolf
Guest Pegasus \(MVP\) Posted March 24, 2008 Posted March 24, 2008 Re: Memory Leak "Jeff" <Jeff@discussions.microsoft.com> wrote in message news:AC69E517-5C1D-493D-BE24-03728BC75E00@microsoft.com... > I'm having a problem where every few weeks or so, my server gets hosed. > All > of the sudden it stops accepting network connections. Usually a reboot > does > the trick. We also notice that an error is always written to the event log > whenever this occurs. The errror is > > "The server was unable to allocate from the system nonpaged pool because > the > pool was empty." > > After doing some research on the error, we figured that the problem was a > memory leak. We have been running pool monitor for the last week. The tag > called STRG has climbed all week. It is now at about 120mb. I guess this > is > our culprit - however what is STRG? On my machine, all processes in the Task Manager are listed with a .exe extension (except System and Idle Process). I suspect it's the same on your machine, even though you did not report "strg.exe". If it is an .exe name then you should look on your disk where this file resides.
Guest Jeff Posted March 24, 2008 Posted March 24, 2008 Re: Memory Leak STRG is a memory tag that is displayed in the Memory Pool Monitor. It's not an executable. Someone told me that this was the best too to track down a memory leak. I think I've tracked it down to this tag - however I have no idea what the heck it is. "Pegasus (MVP)" wrote: > > "Jeff" <Jeff@discussions.microsoft.com> wrote in message > news:AC69E517-5C1D-493D-BE24-03728BC75E00@microsoft.com... > > I'm having a problem where every few weeks or so, my server gets hosed. > > All > > of the sudden it stops accepting network connections. Usually a reboot > > does > > the trick. We also notice that an error is always written to the event log > > whenever this occurs. The errror is > > > > "The server was unable to allocate from the system nonpaged pool because > > the > > pool was empty." > > > > After doing some research on the error, we figured that the problem was a > > memory leak. We have been running pool monitor for the last week. The tag > > called STRG has climbed all week. It is now at about 120mb. I guess this > > is > > our culprit - however what is STRG? > > On my machine, all processes in the Task Manager are listed with > a .exe extension (except System and Idle Process). I suspect it's > the same on your machine, even though you did not report "strg.exe". > If it is an .exe name then you should look on your disk where this > file resides. > > >
Recommended Posts