Re: Memory leaking on W2003

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Thre is usually thread objects. The key is finding out which process is
creating the many threads or who is leaking a reference to one. Some of the
troubleshooting that you can do is remove filter drivers from the machine in
question to determine if for instance they may have the reference and the
kernel can't free the object until it's given up even though the thread is
Terminated.

You may be able to troubleshoot this externally without debugging.
Try some of the handle count troubleshooting, etc. here:

http://blogs.msdn.com/ntdebugging/archive/2006/12/18/Understanding-Pool-Consumption-and-Event-ID_3A00_--2020-or-2019.aspx

Indeed it might require you do create a memory.dmp of the machine during the
problem via KB244139 and submit that to Microsoft Support
http://support.microsoft.com or download the Debugging Tools for Windows,
open the dump in windbg.exe, and find the process, then the threads left
around to get more info about the nature of the problem.


"Edwin vMierlo" wrote:

Riccardo,

if you are going to do that, you might as well take some time to eliminate
by uninstalling one by one

anyway, good luck with your server !
Rgds,
Edwin.

<r.barghini@xxxxxxxxx> wrote in message
news:1166092000.661747.271160@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi Edwin,
thanks for your help.
I think i'm going to rebuild the server and add the drivers one by one.

Regards,
Riccardo

Edwin vMierlo ha scritto:

Riccardo,

Not a whole lot can be done by newsgroup posts, Thre is indeed used by a
lot
of drivers, as I just tested on one of my systems.

I guess you have two options
1) process of elimination (start uninstalling drivers one by one) until
you
have a bare system. I realise that if this is a production system this
might
not be possible
2) open a ticket with PSS, and get Microsoft involved to debug this
symptom

I know, not a lot of help, but that are the two options I see
Good Luck,
Edwin.


<r.barghini@xxxxxxxxx> wrote in message
news:1165869109.661320.157830@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi Edwin thanks for your answer.
No, we are not using any QMS printer driver. I can exclude a problem
of
printers drivers because the event happens even with the sooler
service
stopped and no drivers installed.

Riccardo


Edwin vMierlo ha scritto:

Are you using a (very) old QMS printer driver ?

this used to be a *very* old problem on 3.51 (I know... very old...
a
long
shot)
http://support.microsoft.com/kb/147293




<r.barghini@xxxxxxxxx> wrote in message
news:1165489740.494272.78390@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi everybody. One of our customers hit a problem of memory leaking
which requires a reboot every day. What happens is that after some
time
I get the error 2019 saying that the non paged memory pool is
empty.
The server has installed only the operating system (W2003 SP1 with
the
latest patch included Internet Explorer 7), Norton Antivirus
Corporate
edition 10, Veritas Storage Foundation HA for Windows ver 4.3 MP1
(clustering software) and a few printer drivers.
Wit the aid of Veritas software support I was able to exclude that
this
software could be the cause.
I used poolmon to capture the memory state of all process and the
only
strange thing that I could see was that the process tagged Thre
raises
slowly but steadily its memory allocations while not releasing,
thus
filling up the non paged pool. I tried uninstalling the printers
drivers and the antivirus but tha Thre process still raised. From
performance monitor I could see that the "system" process handle
count
increases continously, while the thread count remains stable.
Do you have some hints to identify the process consuming memory?
From
the findtrs search I can see that the Thre tag belongs to a lot of
drivers so I'm not able to narrow my search.

Thanks in advance,
Riccardo






.

Relevant Pages

  • Re: Memory leaking on W2003
    ... Not a whole lot can be done by newsgroup posts, Thre is indeed used by a lot ... of drivers, as I just tested on one of my systems. ... we are not using any QMS printer driver. ... I used poolmon to capture the memory state of all process and the only ...
    (microsoft.public.windows.server.general)
  • Re: Memory leaking on W2003
    ... I think i'm going to rebuild the server and add the drivers one by one. ... Edwin vMierlo ha scritto: ... Not a whole lot can be done by newsgroup posts, Thre is indeed used by a lot ... we are not using any QMS printer driver. ...
    (microsoft.public.windows.server.general)
  • 2 section mismatches for v2.6.28-rc3-54-g75fa677
    ... WARNING: vmlinux.o: Section mismatch in reference from the ... # Device Drivers ... # PCI IDE chipsets support ...
    (Linux-Kernel)
  • drivers/platform/x86/eeepc-wmi.c build error
    ... reference to `sparse_keymap_report_event' ... # Kernel Performance Events And Counters ... # CAN Device Drivers ...
    (Linux-Kernel)
  • latest git (linux-2.6.25-git6) compile error
    ... and when I was asked for leds support ... To see full details build your kernel with: ... reference to `led_classdev_resume' ... # Input Device Drivers ...
    (Linux-Kernel)