Yes. This is what bit me in the first place!
Normally when you dump the machine, the memory.dmp is automatically
over-written by the new one. For a while I was copying the memory.dmp
files
off to a different machine and NOT deleting the old memory.dmp. Later on
I
noticed that the memory.dmp for a period of several weeks never changed
(it
was the same file). It was then that I realized that dumping was no
longer
working. First thing I tried was deleting the memory.dmp file and
testing,
still did not work.
Then I found the KB that indicates you need 2x amount of RAM for pagefile,
I
set pagefile to 4GB to see if this would help, did not help.
So at this point I suspect there is some counter in Windows that just
stops
gathering dumps after a certain number are hit. I need to reset this
counter
somehow. I have a bug opened with the Windows folks and they are going to
investigate this. But since many customers out there certainly use this
feature I thought I would ping the world to see if anyone else had hit
this
and how to resolve it.
Unfortunately the box I'm debugging is a Lenovo T60P laptop with no COM
port
so I cannot kernel debug directly. I sent off for a replacement bay that
has
a built-in COM port but this set me back 70$, once I have this I can
kernel
debug directly and no longer need the dumps but I like having the dump
feature enabled in case the machine hangs I can capture state. Thanks
for
all your help thus far if you have any other suggestions I can try them
out.
Rick Rogers said:
Hi,
Have you tried deleting any existing memory.dmp file to see if a new one
gets created?
--
Best of Luck,
Rick Rogers, aka "Nutcase" - Microsoft MVP
Windows help -
www.rickrogers.org
My thoughts
http://rick-mvp.blogspot.com
in
message news:
[email protected]...
I didn't change anything. After the dumps stopped working I bumped up
my
page file to 4GB (I have 2GB RAM) after I read some KB about this but
the
dumps no longer work (Kernel dumps). Note I'm doing kernel and not
full
memory dumps. I think mini dumps still work.
:
Hi,
Not seen nor heard of that happening. Any chance you placed limits on
the
virtual memory?
--
Best of Luck,
Rick Rogers, aka "Nutcase" - Microsoft MVP
Windows help -
www.rickrogers.org
My thoughts
http://rick-mvp.blogspot.com
"Matt Neerincx [MSFT]" <
[email protected]>
wrote
in
message I've been using Ctrl-Scroll Lock Scroll Lock feature
(CrashOnCtrlScroll)
with
Vista to manually blue screen my machine to capture kernel memory
dumps
for
debugging purposes when my Vista box hangs. For some reason all of
a
sudden
this no longer works. The blue screen occurs every time but no
memory.dmp
file is generated. I have only one drive in the machine (C: drive)
and
there
is plenty of free space (12GB).
Any ideas why Vista would stop capturing dump files in this manner?
Is
there some limit where it will stop capturing them?
