Re: Memory Leak pooltag="Ddk", windows xp media center 2004, what driver is this?
- From: "Don Burn" <burn@xxxxxxxxxxxxxxxx>
- Date: Sun, 24 Sep 2006 20:01:55 -0400
Bad news Ddk is the default tag for those drivers that use ExAllocatePool
instead of ExAllocatePoolWithTag you are going to have to do some debugging
to get further. You might consider using driver verifier on all
non-Microsoft supplied drivers on the system, this will give you an
indication of who is using what. Unfortunately, a driver that is leaking
pool will also probably have additional problems with driver verifier.
--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
http://www.windrvr.com
Remove StopSpam from the email to reply
"kithana" <singha@xxxxxxxxxxxxx> wrote in message
news:1159141055.157960.292650@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
How can I find out what driver uses the tag "Ddk" because it
has a memory leak that I would like to get fixed, or remove the driver
if I do not require it. I have WinDbg installed on the machine, but
so far have found no way to tell what calls are using the memory tag
(pooltag="Ddk")(I am connecting to local computer with the debugger
which limits some o the output of the debugger). Running Windows XP
Machine:
Dual Core Dell XPS 400, 2.8 GHz,
Intel(R) Pro/1000 PL Network Connection
NVIDIA GeForce 7900 GS
Little history, I leave my machine up 24x7 hrs, after a couple of
days, windows would kind of get ill, things would not launch, I
couldn't
even bring up Task manager. I investigated with "Performance monitor"
and determined that something was eating up memory("Nonpaged Pool"
memory).
I looked at task manager, and could not see any processes that were
eating
up Nonpage Pool memory, at which time I started to suspect O/S or
driver.
I installed "Support Tools" off the XP CD, used the utility called
"poolmon.exe" (after turning on memory tagging with "gflags") and
determined that something with the pool tag "Ddk" was eating up all the
"NonPaged Pool" memory. I did some research, and found out that Ddk is
the default memory tag allocation that windows device developer kit
uses.
Hmmmm.
Researched a little more, and found the windows debugger "WinDbg" off
the windows web site. Installed it, and turned on "DEBUG" boot options,
and
was able to connect the debugger to my local machine. Unfortunately, at
this
point by running local WinDbg on my machine, I have been unable to
convert
the memory POOLTAG="Ddk" to a binary/DLL so I can determine what is the
cause of my problems.
Any Help/Advice would be appreciated.
Kithana
.
- References:
- Prev by Date: Memory Leak pooltag="Ddk", windows xp media center 2004, what driver is this?
- Next by Date: Re: NDIS WDM driver installation for multi-port NIC
- Previous by thread: Memory Leak pooltag="Ddk", windows xp media center 2004, what driver is this?
- Next by thread: Re: Memory Leak pooltag="Ddk", windows xp media center 2004, what driver is this?
- Index(es):
Relevant Pages
|
