DOCUMENT:Q173277

TITLE   :No Memory.dmp File Created with RAM Above 1.7 GB

PRODUCT :Microsoft Windows NT

PROD/VER:4.00

OPER/SYS:WINDOWS

KEYWORDS:kbbug4.00 kberrmsg kbfix4.00 kbtool NTSrvWkst ntutil



--------------------------------------------------------------------------

The information in this article applies to:



 - Microsoft Windows NT Workstation version 4.0

 - Microsoft Windows NT Server version 4.0

--------------------------------------------------------------------------



SYMPTOMS

========



In systems where RAM exceeds 1.7 GB, Memory.dmp files are not generated

even though a sufficient pagefile (RAM + 1 GB) is available on the boot

drive.



Additionally, if larger Memory.dmp file images are produced (by applying

hotfixes referenced below), several support utilities should be updated to

read the larger Memory.dmp images. Without these updated files for dumpchk,

dumpexam, i386kd (or alphakd, mip, ppc) and windbg the following error

message is generated:



   Could not initialize crash dump file <path to dumpfile>.



CAUSE

=====



Several causes were isolated related to mapping views of very large memory

images.



RESOLUTION

==========



To resolve this problem, obtain the hotfix below, or wait for the next

service pack.



This hotfix has been posted to the following Internet location:



   ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40/

   hotfixes-postSP3/2gcrash



NOTE: The above link is one path; it has been wrapped for readability.



 - Ntoskrnl.exe (or Ntkrnlmp.exe) and Savedump.exe are used to produce

   larger Memory.dmp files.



 - Dumpchk.exe and Dumpexam.exe are used to verify the larger Memory.dmp

   files.



STATUS

======



Microsoft has confirmed this to be a problem in Windows NT version 4.0.

A supported fix is now available, but has not been fully regression tested

and should be applied only to systems experiencing this specific problem.

Unless you are severely impacted by this specific problem, Microsoft

recommends that you wait for the next Service Pack that contains this fix.

Contact Microsoft Technical Support for more information.



Additional query words: 4.00



============================================================================



THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS

PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND.  MICROSOFT DISCLAIMS

ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES

OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  IN NO

EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR

ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,

CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF

MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE

POSSIBILITY OF SUCH DAMAGES.  SOME STATES DO NOT ALLOW THE EXCLUSION

OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES

SO THE FOREGOING LIMITATION MAY NOT APPLY.