Memory.dmp File Is Missing or Contains Corrupted Data (257299)
The information in this article applies to:
- Microsoft Windows 2000 Server
This article was previously published under Q257299 SYMPTOMS
If the system partition is built with the dynamic mirrored volume, the
Memory.dmp file may not be generated or may contain corrupted data.
If you run Dumpchk.exe against the Memory.dmp file, the following error message is displayed:
Validating the integrity of the PsLoadedModuleList
Error: Could not read base of PsLoadedModuleList
Error: The module list is not valid
Error: The media is write protected
This dump file is bad.
CAUSE
The crash dump driver saves the information in the paging file only to the primary disk and causes the mirrored volume to go out of synchronization. On the first reboot after the crash, the system (Savedump.exe) reads the paging file to save the dump information in the Memory.dmp file.
By default, the disk read calls are optimized by performing round-robin reads from both of the disks in the mirror set. In this process, the Memory.dmp file receives corrupted data when the system reads the data from the second disk in the mirror set, which does not really have the dump information.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
This problem was first corrected in Windows 2000 Service Pack 1.
Modification Type: | Minor | Last Reviewed: | 9/23/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbbug kbenv kberrmsg kbfix kbWin2000SP1Fix KB257299 |
---|
|