Conflict between crash dump registry setting and GUI

  • Thread starter Thread starter BoneHead
  • Start date Start date
B

BoneHead

Hello!

I have a W2000 Advanced server on service pack 3. If I
look at the registry I see this:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashC
ontrol
AutoReboot REG_DWORD 0x1
CrashDumpEnabled REG_DWORD 0x1
DumpFile REG_EXPAND_SZ %SystemRoot%\MEMORY.DMP
LogEvent REG_DWORD 0x1
MinidumpDir REG_EXPAND_SZ %SystemRoot%\Minidump
Overwrite REG_DWORD 0x1
SendAlert REG_DWORD 0x1

According to KB 254649 the line "CrashDumpEnabled" is set
for a FULL Memory Dump ==> i.e. 0x1

But when I look in the Startup and Recovery settings GUI
(properties of the "my computer") it shows "Kernel Memory
Dump". If that were the case, the above-mentioned reg
setting should be at 0x2.

QUESTION: Is this a problem in windows 2000? Has anyone
else seen this?

(BTW, no dumps are occuring since the disk space and
pagefile are setup as per the kernel dump specs in that
kb. As well, there are no other instances of the OS on
this box as per the boot.ini file, so it's not as though
I'm looking at the wrong system startup settings in the
GUI. Finally, I experimented on other W2k boxes, and
found that just manually changing the registry value
seems to dynamically update the GUI to the proper
setting. Am about to try fixing this on the "problem"
box by manually adjusting the registry and see if that
fixes things.)

Thanks!
 
--------------------
From: "BoneHead" <[email protected]>
Subject: Conflict between crash dump registry setting and GUI
Date: Tue, 17 Feb 2004 12:41:50 -0800
Newsgroups: microsoft.public.win2000.registry

Hello!

I have a W2000 Advanced server on service pack 3. If I
look at the registry I see this:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashC
ontrol
AutoReboot REG_DWORD 0x1
CrashDumpEnabled REG_DWORD 0x1
DumpFile REG_EXPAND_SZ %SystemRoot%\MEMORY.DMP
LogEvent REG_DWORD 0x1
MinidumpDir REG_EXPAND_SZ %SystemRoot%\Minidump
Overwrite REG_DWORD 0x1
SendAlert REG_DWORD 0x1

According to KB 254649 the line "CrashDumpEnabled" is set
for a FULL Memory Dump ==> i.e. 0x1

But when I look in the Startup and Recovery settings GUI
(properties of the "my computer") it shows "Kernel Memory
Dump". If that were the case, the above-mentioned reg
setting should be at 0x2.

QUESTION: Is this a problem in windows 2000? Has anyone
else seen this?

(BTW, no dumps are occuring since the disk space and
pagefile are setup as per the kernel dump specs in that
kb. As well, there are no other instances of the OS on
this box as per the boot.ini file, so it's not as though
I'm looking at the wrong system startup settings in the
GUI. Finally, I experimented on other W2k boxes, and
found that just manually changing the registry value
seems to dynamically update the GUI to the proper
setting. Am about to try fixing this on the "problem"
box by manually adjusting the registry and see if that
fixes things.)

Thanks!
--

Natively Windows 2000 is not capable of doing a Complete Memory Dump of a system with more than 2GB RAM. If the
system has more than 2GB RAM someone may have tried to force a Complete Memory Dump by changing the registry
setting but the system would still default to a Kernel Memory Dump. The following article talks a little more about this.

274598 - Complete Memory Dumps Not Available on Computers with 2 or More Gigabytes of RAM
http://support.microsoft.com/default.aspx?scid=kb;[LN];274598

I said natively before because there is a hotfix, which is a back port from Windows 2003, that will allow a Complete Memory
Dump of up to 4GB of RAM. This hotfix does not change the GUI so Complete Memory Dump will still not be available
through the GUI and the only way to force the Complete Memory Dump once the hotfix is installed is to manually change
the registry setting. If you would like to get this hotfix you will need to open a support incident and request hotfix 820361.

Bill Peele
Microsoft Enterprise Support

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread
from which they originated.
 
--------------------
From: "BoneHead" <[email protected]>
Subject: Conflict between crash dump registry setting and GUI
Date: Tue, 17 Feb 2004 12:41:50 -0800
Newsgroups: microsoft.public.win2000.registry

Hello!

I have a W2000 Advanced server on service pack 3. If I
look at the registry I see this:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashC
ontrol
AutoReboot REG_DWORD 0x1
CrashDumpEnabled REG_DWORD 0x1
DumpFile REG_EXPAND_SZ %SystemRoot%\MEMORY.DMP
LogEvent REG_DWORD 0x1
MinidumpDir REG_EXPAND_SZ %SystemRoot%\Minidump
Overwrite REG_DWORD 0x1
SendAlert REG_DWORD 0x1

According to KB 254649 the line "CrashDumpEnabled" is set
for a FULL Memory Dump ==> i.e. 0x1

But when I look in the Startup and Recovery settings GUI
(properties of the "my computer") it shows "Kernel Memory
Dump". If that were the case, the above-mentioned reg
setting should be at 0x2.

QUESTION: Is this a problem in windows 2000? Has anyone
else seen this?

(BTW, no dumps are occuring since the disk space and
pagefile are setup as per the kernel dump specs in that
kb. As well, there are no other instances of the OS on
this box as per the boot.ini file, so it's not as though
I'm looking at the wrong system startup settings in the
GUI. Finally, I experimented on other W2k boxes, and
found that just manually changing the registry value
seems to dynamically update the GUI to the proper
setting. Am about to try fixing this on the "problem"
box by manually adjusting the registry and see if that
fixes things.)

Thanks!
--

Natively Windows 2000 is not capable of doing a Complete Memory Dump of a system with more than 2GB RAM. If the
system has more than 2GB RAM someone may have tried to force a Complete Memory Dump by changing the registry
setting but the system would still default to a Kernel Memory Dump. The following article talks a little more about this.

274598 - Complete Memory Dumps Not Available on Computers with 2 or More Gigabytes of RAM
http://support.microsoft.com/default.aspx?scid=kb;[LN];274598

I said natively before because there is a hotfix, which is a back port from Windows 2003, that will allow a Complete Memory
Dump of up to 4GB of RAM. This hotfix does not change the GUI so Complete Memory Dump will still not be available
through the GUI and the only way to force the Complete Memory Dump once the hotfix is installed is to manually change
the registry setting. If you would like to get this hotfix you will need to open a support incident and request hotfix 820361.

Bill Peele
Microsoft Enterprise Support

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread
from which they originated.
 
Thanks very much for your help, Bill! I believe that
explains the conflict.
-----Original Message-----
--------------------
From: "BoneHead" <[email protected]>
Subject: Conflict between crash dump registry setting and GUI
Date: Tue, 17 Feb 2004 12:41:50 -0800
Newsgroups: microsoft.public.win2000.registry

Hello!

I have a W2000 Advanced server on service pack 3. If I
look at the registry I see this:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Crash C
\Minidump
Overwrite REG_DWORD 0x1
SendAlert REG_DWORD 0x1

According to KB 254649 the line "CrashDumpEnabled" is set
for a FULL Memory Dump ==> i.e. 0x1

But when I look in the Startup and Recovery settings GUI
(properties of the "my computer") it shows "Kernel Memory
Dump". If that were the case, the above-mentioned reg
setting should be at 0x2.

QUESTION: Is this a problem in windows 2000? Has anyone
else seen this?

(BTW, no dumps are occuring since the disk space and
pagefile are setup as per the kernel dump specs in that
kb. As well, there are no other instances of the OS on
this box as per the boot.ini file, so it's not as though
I'm looking at the wrong system startup settings in the
GUI. Finally, I experimented on other W2k boxes, and
found that just manually changing the registry value
seems to dynamically update the GUI to the proper
setting. Am about to try fixing this on the "problem"
box by manually adjusting the registry and see if that
fixes things.)

Thanks!
Click to expand...
Memory Dump of a system with more than 2GB RAM. If the
system has more than 2GB RAM someone may have tried to
Click to expand...
force a Complete Memory Dump by changing the registry
setting but the system would still default to a Kernel
Click to expand...
Memory Dump. The following article talks a little more
about this.
274598 - Complete Memory Dumps Not Available on
Click to expand...
Computers with 2 or More Gigabytes of RAM
http://support.microsoft.com/default.aspx?scid=kb; [LN];274598

I said natively before because there is a hotfix, which
Click to expand...
is a back port from Windows 2003, that will allow a
Complete Memory
Dump of up to 4GB of RAM. This hotfix does not change
Click to expand...
the GUI so Complete Memory Dump will still not be
available
through the GUI and the only way to force the Complete
Click to expand...
Memory Dump once the hotfix is installed is to manually
change
the registry setting. If you would like to get this
Click to expand...
hotfix you will need to open a support incident and
request hotfix 820361.
Bill Peele
Microsoft Enterprise Support

This posting is provided "AS IS" with no warranties, and
Click to expand...
confers no rights. Use of included script samples are
subject to the
terms specified at http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all
Click to expand...
responses to this message are best directed to the
newsgroup/thread
 
Thanks very much for your help, Bill! I believe that
explains the conflict.
-----Original Message-----
--------------------
From: "BoneHead" <[email protected]>
Subject: Conflict between crash dump registry setting and GUI
Date: Tue, 17 Feb 2004 12:41:50 -0800
Newsgroups: microsoft.public.win2000.registry

Hello!

I have a W2000 Advanced server on service pack 3. If I
look at the registry I see this:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Crash C
\Minidump
Overwrite REG_DWORD 0x1
SendAlert REG_DWORD 0x1

According to KB 254649 the line "CrashDumpEnabled" is set
for a FULL Memory Dump ==> i.e. 0x1

But when I look in the Startup and Recovery settings GUI
(properties of the "my computer") it shows "Kernel Memory
Dump". If that were the case, the above-mentioned reg
setting should be at 0x2.

QUESTION: Is this a problem in windows 2000? Has anyone
else seen this?

(BTW, no dumps are occuring since the disk space and
pagefile are setup as per the kernel dump specs in that
kb. As well, there are no other instances of the OS on
this box as per the boot.ini file, so it's not as though
I'm looking at the wrong system startup settings in the
GUI. Finally, I experimented on other W2k boxes, and
found that just manually changing the registry value
seems to dynamically update the GUI to the proper
setting. Am about to try fixing this on the "problem"
box by manually adjusting the registry and see if that
fixes things.)

Thanks!
Click to expand...
Memory Dump of a system with more than 2GB RAM. If the
system has more than 2GB RAM someone may have tried to
Click to expand...
force a Complete Memory Dump by changing the registry
setting but the system would still default to a Kernel
Click to expand...
Memory Dump. The following article talks a little more
about this.
274598 - Complete Memory Dumps Not Available on
Click to expand...
Computers with 2 or More Gigabytes of RAM
http://support.microsoft.com/default.aspx?scid=kb; [LN];274598

I said natively before because there is a hotfix, which
Click to expand...
is a back port from Windows 2003, that will allow a
Complete Memory
Dump of up to 4GB of RAM. This hotfix does not change
Click to expand...
the GUI so Complete Memory Dump will still not be
available
through the GUI and the only way to force the Complete
Click to expand...
Memory Dump once the hotfix is installed is to manually
change
the registry setting. If you would like to get this
Click to expand...
hotfix you will need to open a support incident and
request hotfix 820361.
Bill Peele
Microsoft Enterprise Support

This posting is provided "AS IS" with no warranties, and
Click to expand...
confers no rights. Use of included script samples are
subject to the
terms specified at http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all
Click to expand...
responses to this message are best directed to the
newsgroup/thread
 
--------------------
From: "Bonehead" <[email protected]>
Subject: RE: Conflict between crash dump registry setting and GUI
Date: Wed, 18 Feb 2004 10:40:37 -0800
Newsgroups: microsoft.public.win2000.registry

Thanks very much for your help, Bill! I believe that
explains the conflict.
--

Glad to be of assistance.

Bill Peele
Microsoft Enterprise Support

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread
from which they originated.
 
--------------------
From: "Bonehead" <[email protected]>
Subject: RE: Conflict between crash dump registry setting and GUI
Date: Wed, 18 Feb 2004 10:40:37 -0800
Newsgroups: microsoft.public.win2000.registry

Thanks very much for your help, Bill! I believe that
explains the conflict.
--

Glad to be of assistance.

Bill Peele
Microsoft Enterprise Support

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread
from which they originated.
 
Back
Top